On Mar 5, 2015, at 12:47 AM, Jari Arkko <jari.arkko@xxxxxxxxx> wrote: >>> 3) Mark Andrews' suggestion of further requirements regarding EDNS0 has >>> not been discussed, but I would note that at this stage we should not add >>> major requirements without substantial community portion indicating that >>> this is needed. I'm not hearing it. >> >> I suspect this is because the root servers actually correctly >> implement EDNS. If a server was changed to a implementation that >> failed to correctly implement EDNS that would change. > > Perhaps. What do others think? Mark's proposed addition of EDNS0 is a very nice thing to have. If all the root servers always responding to queries that have EDNS0 with EDNS0 in their responses, the DNS would be operationally more stable, particularly as response sizes increase over time. However, it seems inappropriate for the IETF to say "and here is the exact list of protocol bits that we require for the root service" when we are sure that servers using few of those bits will work adequately. Also, it is important to note that RSSAC-001 says: [E.3.2 - A] Individual Root Servers will adopt or continue to implement the current DNS protocol and associated best practices through appropriate software and infrastructure choices. EDNS0 very clearly falls under "best practices": no one can deny that. So, to some extent, the expectation is already on the root server operators to use EDNS0. It's not clear if the IETF saying "here's a thing we insist on" will help the cause. Further note: just saying "EDNS0" is not sufficient: we would have to say which features, options, and extensions would be needed. This is "obvious" to many folks, and not at all clear to others. --Paul Hoffman
Attachment:
signature.asc
Description: Message signed with OpenPGP using GPGMail