At Fri, 16 Oct 2015 17:07:27 +0000, "Darcy Kevin (FCA)" <kevin.da...@fcagroup.com> wrote:
> Let's see, millions of full-service resolvers, times the > packet-count differential between UDP and TCP, times the average > reload/restart frequency of those full-service resolvers per > day/week/month. Can't a case be made from sheer volume? I've not checked the validity of the math, but even if that's valid, I believe a SHOULD is enough for such a purpose. Sane implementations would honor that, and insane implementations would do whatever they want whether it's a SHOULD or MUST. > > > I have separate issue, which is this text: > > > > > > The priming query MUST be sent over UDP (section 6.1.3.2 of > > > [RFC1123]). My interpretation of this was that since the support for TCP was a SHOULD in section 6.1.3.2 of RFC1123 trying TCP could result in an interoperability problem (hence the MUST). And what I tried to say is that now that the support for TCP is a REQUIRED this MUST looks like a 'super-strong recommendation'. -- JINMEI, Tatuya _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
