On 2012-05-22 12:29, Maoke wrote:
1. it is not the time to compare 4rd with MAP-T or with MAP-E
separately, but with the MAP-suite. i never think MAP-T is intended
to be the *unique* standard in the scope of residual deployment. (maybe
it "was" but we'd better discuss things based on current understanding)
My understanding: 4rd is a compromise.
What you gain: only one protocol to consider.
What you lose: some edge cases are not supported.
So any argument to the effect that "MAP-E|T does X and 4rd doesn't" is
empty. This is expected, it's a compromise.
The argument should be: "I need 4rd to do X because ..."
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
