Hi Fred, On 2009-03-24 10:39, Fred Baker wrote: ... > The draft states that hairpinning is required, but doesn't go into how > it is done. > > NAT66 devices MUST support hairpinning behavior, as defined in the > NAT Behavioral Requirements for UDP document [RFC4787]. This means > that when a NAT66 device receives a packet on the internal interface > that has a destination address that matches the site's external > prefix,
s/the site's external prefix/one of the site's external prefixes/ Since this is IPv6, there might be more than one, unless we plan a rule that one NAT66 can only support one external prefix, in which it's s/the site's external prefix/the site's external prefix to which the NAT66 in question is connected/ Brian _______________________________________________ nat66 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nat66
