Le 2014-01-16 02:19, Mikael Abrahamsson a écrit :
The fragmentation handling needs more guidance. 5.2.1. says:"On receiving an encapsulated packet containing an IPv4 fragment, the lwB4 MUST wait until all other fragments have been received and de- capsulated." What happens if one of the fragments are lost? I would believe there is work to be referenced when it comes to handling fragmentation, and the document would be better guidance if that was referenced.
You're right, the advice in the text is wrong, if only because it's possible to do it correctly without waiting for all fragments (e.g., what Cisco calls "virtual reassembly").
We need to keep in mind that fragmentation and reassembly issues 1) are very complex, 2) apply to a ton of protocols in addition to lw4o6, 3) there's more than one way to do it, and 4) there's no one true way to do it, they all suck a little in different ways.
My suggestion would be to steal the very carefully written text from RFC 6146, page 19.
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
