Hi! Sorry for not having followed the details of the discussion lately, so please excuse me if I'm too late with comments or ask about stuff discussed in a gazillion emails before.
Section 3: I really like this here, but would like it to be expanded a bit to help implementors. The DNS SRV RFC is not easy to understand and in the IP world RFC 3263 has confused a lot of people. DNS SRV says that all candidates for a given priority should be attempted before one moves to the next priority. It doesn't say anything about order, which this document does when you say "SHOULD be performed in parallell". If one given priority have two hosts with two IPv4 and three IPv6 each - should all of them be tried in parallell? This is a big issue and may be too big an issue for this document to cover, especially with normative language. Section 3.2 Please change "A/AAAA" to "A and AAAA" to be very clear that it's not a choice if the client is dual stack. In fact the DNS SRV rfc talks about "any address family" - now and in the future ;-) 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 That will help me in sipcore :-) Section 6: I think it would help implementors to explain a bit more detail - that if you have multiple names in the cert, one could be the CN and the others Subject Alt Names. According to the SIP domain cert RFC the CN should be disregarded and NOT used if there are any SANs. I don't know the reasoning behind this. Anyone? Should we do that here too or just forget it? Sorry I couldn't be in Toronto :-( /O _______________________________________________ dane mailing list [email protected] https://www.ietf.org/mailman/listinfo/dane
