On Fri, 1 Oct 2004, Johan Ihrén wrote: > Dean, > > Nothing in the messages quoted below says anything about DNSSEC > requiring TCP. > > Nothing in the protocol specs says anything about DNSSEC requiring TCP. It is the case that DNSSEC queries may in fact trigger more TCP queries and that TCP is described as an acceptable option. It is the case that other proposals under consideration will trigger more TCP queries and assume that TCP is available. Your argument that certain things __could__ be done __without__ TCP is irrelevant to the fact that we need (at the roots) to support the fact that they __may__ be done __with__ TCP and therefore that TCP needs to be supported by the roots. The red herring is the assertion that we can ignore the fact the TCP cannot work with anycast. It is the case that TCP will be more prevalent in the forseeable future. --Dean -- Av8 Internet Prepared to pay a premium for better service? www.av8.net faster, more reliable, better service 617 344 9000 _______________________________________________ Ietf@xxxxxxxx https://www1.ietf.org/mailman/listinfo/ietf