Hi there Olle, folks OK, whilst we're adding references, please don't put in a reference to an obsoleted RFC. 2915 was obsoleted by that fine collection, RFCs 3401-3504 -- ages ago. SIP always was kinda different (allowing an informational RFC through that included MUSTs), so sipcore may not care, but ...
BTW, I found 3263 to be not too bad at all; it does lose it and drift into philosophy (or at least, not English) half way through, but the protocol use bits are fine, IMHO. The 2543 A record and guess approach was and is fugly -- 3263 with its NAPTRs & SRVs has to be a better way. With Dane, it's even better. all the best, Lawrence On 19 Aug 2014, at 19:11, Olle E. Johansson <[email protected]> wrote: > On 19 Aug 2014, at 18:33, Peter Saint-Andre <[email protected]> wrote: >> <snip> >>> Section 5: >>> >>> It would help me if you add a bullet like >>> >>> * Handling in the case of protocols using NAPTR for transport >>> selection, like the Session Initiation Protocol >> >> How is this? >> >> o Use of SRV records with additional discovery technologies, such as >> the use of both SRV records and NAPTR records [RFC2915] for >> transport selection in the Session Initiation Protocol (SIP). > Great. >> >>> That will help me in sipcore :-) >> >> We're here for you! > Thank you! > <snip> > /O _______________________________________________ dane mailing list [email protected] https://www.ietf.org/mailman/listinfo/dane
