On Wed, Nov 11, 2009 at 3:08 PM, Scott Brim <[email protected]> wrote: > Tony Li allegedly wrote on 11/11/2009 4:28 AM: >> We already understand enough about the routing token and the transport >> token to understand that we need to fix this overloading. > > But it's not routing's problem that transport misuses location-dependent > information.
Hi Scott, Nor is it DNS's fault that applications ignore the TTL binding the name to the IP address. But I'm going to throw your point about NAT back at you: for better or for worse, these are now architecture. On Mon, Nov 9, 2009 at 6:59 PM, Brian E Carpenter <[email protected]> wrote: > On 2009-11-10 12:06, William Herrin wrote: >> I could swear we already did that. IIRC, that's why I grouped the >> ideas in Christian Vogt's Six/One Router with the map-encaps in the >> solutions summary document instead of splitting it off into its own >> section. Six/One Router obviously worked in a system strictly split >> between DFZ address space and user address space that distributed a >> map to the translators and detranslators but no one could demonstrate >> how it would work statelessly or without a strict split in light of >> the various DNS issues. I vaguely remember there was also a DNS server >> scope problem... ran afoul of some issues discussed in Paul Vixie's >> recent rant about "DNS lies." > > Not disagreeing, my point is that we need a consensus version of > this in the (supporting text for the) recommendation. Hi Brian, Does this mean http://tools.ietf.org/html/draft-irtf-rrg-recommendation-02 is moving forward again? I'm willing to try to write a drop-in that talks to how a NAT66-like system would work (like Christian discussed with Six/One Router) and what the criticisms are vis-a-vis DNS and client connection attempt behavior. Regards, Bill herrin -- William D. Herrin ................ [email protected] [email protected] 3005 Crane Dr. ...................... Web: <http://bill.herrin.us/> Falls Church, VA 22042-3004 _______________________________________________ rrg mailing list [email protected] http://www.irtf.org/mailman/listinfo/rrg
