On Mar 23, 2009, at 4:04 PM, Keith Moore wrote:
IMHO, an even more appropriate solution would be to drop the datagram
and reply "Destination Unreachable", to cause the originating host
to do
a better job of address selection.
See, now you're asking the host or the app to do the network's job.
Actually, no. I am asking the host to do it's job.
RFC 3484, whatever its issues may be, makes it the host's job to
select an address pair that makes sense. Among other things, it asks
the system opening the session to look at the list of addresses
advertised in DNS for its target, compare them to its own set of
addresses, and choose the address pair that simultaneously minimizes
scope and maximizes the length of the matching prefix.
I'm simply suggesting that if the device has the option of hairpinning
and the option of not hairpinning, not hairpinning makes the most
sense. Therefore it is reasonable for the network to advise the host
to try a different address pair.
_______________________________________________
nat66 mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/nat66
