On 2012-04-03 05:40, Ole Trøan wrote:
1) MAP-E supports independence of IPv4 and IPv6 addressing. by using hub and
spoke mode with a separate
mapping rule per subscriber. in this mode e.g only ports could be embedded
in the address. this is not
possible in a translation solution like 4rd-U.
This mode of operation was suggested last week during the SD-NAT
presentation. There seemed to be consensus among operators that it was
not practically feasible.
2) a node inside the network will treat translated packets different from
encapsulated ones.
e.g. for the purposes of counting or for applying features. for an
encapsulated packet both the complete
IPv4 datagram and the IPv6 header is available, and different features can
be applied to both.
In practice, the contents of encapsulated packets are rarely inspected
by firewalls and other such devices.
IMHO at this point we should let the market decide. Publish both as
experimental. Let's work on something else now.
Simon
--
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source --> http://ecdysis.viagenie.ca
STUN/TURN server --> http://numb.viagenie.ca
_______________________________________________
Softwires mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/softwires
