Fred Baker wrote: > > On Mar 23, 2009, at 2:05 PM, Keith Moore wrote: > >> B thinks its traffic arrived at a ULA, but B presumably can't use that >> ULA as a referral address as it won't work everywhere, > > http://tools.ietf.org/html/draft-wing-behave-nat64-referrals > "Referrals Across a NAT64", Dan Wing, 4-Mar-09, > <draft-wing-behave-nat64-referrals-00.txt>
I'm glad to see someone is thinking about this. However, merely being able to do referrals across nat64 for SIP and Bittorrent is not sufficient. It needs to work for every kind of NAT, and for anything else that blocks referrals other than for policy reasons, and for any kind of app that wishes to do referrals. Of course we can't expect deployed boxes to magically upgrade themselves, so what I'm talking about is the desired end-state. The point is that if we're going to have NATs of any kind in the architecture, we need to define a way for the apps to do referrals in spite of those NATs. It's not sufficient to provide a piecemeal solution that works only for specific kinds of NATs or specific apps. Keith _______________________________________________ nat66 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nat66
