Le 2014-03-03 14:52, Wojciech Dec a écrit : > Lightweight 4over6 provides a solution for a hub-and-spoke softwire > architecture only, > where the AFTR maintains (softwire) state for each subscriber. A means for > optmizing the amount of such state using IPv4-IPv6 address mapping rules, as > well as the option of meshed IPv4 > connectivity between subscribers, are features of the [I-D.ietf-softwire-map > <http://tools.ietf.org/html/draft-ietf-softwire-lw4over6-07#ref-I-D.ietf-softwire-map>] > solution.
Optimality is in the eye of the operator. What MAP does is *minimize* the amount of state at the cost of flexibility. It may be more or less optimal depending on what you need. Suggestion: create a two-axis ASCII graph labeled "state" and "flexibility". Put MAP, lw4o6, and heck even DS-Lite in it at the appropriate spots. (This is not wordsmithing since I'm proposing a figure. It's figure-smithing.) 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
