Re: Signaling Message Fragmentation
"Templin, Fred L" <[email protected]>
| Newsgroups | gmane.ietf.nemo |
|---|---|
| Message-ID | <2134F8430051B64F815C691A62D9831832D23D03@XCH-BLV-504.nw.nos.boeing.com> |
Hi Sri, My understanding is that if a source sends fragmented messages it must have assurance that the destination has a large enough reassembly buffer. Since the minimum IPv6 reassembly unit is only 1500 bytes, the source SHOULD NOT send fragmented packets larger than 1500 bytes unless there is some other means of determining whether the destination's reassembly buffer can accommodate the larger size. How big do you need? Thanks - Fred From: dmm [mailto:[email protected]] On Behalf Of Sri Gundavelli (sgundave) Sent: Thursday, September 18, 2014 1:04 PM To: [email protected] Subject: [DMM] Signaling Message Fragmentation [Discussion under the maintenance scope] With the standardization of all the new mobility options (ANI, QoS, IFOM, MNP..etc) and specially with the NAI/Domain type fields in some of those options, we are almost close to hitting the PBU/BU fragmentation limit. Any thoughts on how to deal with this ? How is it solved in other message based protocols ? I've seen some work on IPSecme WG on IKEv2 message fragmentation for the same issue. Should we do some thing here ? Or, if any one has invested time on this and has a proposal ? Comments ? Regards Sri _______________________________________________ dmm mailing list [email protected] https://www.ietf.org/mailman/listinfo/dmm