hi, On Sat, Aug 27, 2011 at 2:32 AM, Tina TSOU <[email protected]>wrote:
> Dear Jacni,**** > > Just after reading RFC 1981, I think fragmentation of IPv6 is needed. In > section 5.1, it says, “It is possible that a packetization layer, perhaps > a UDP application outside the kernel, is unable to change the size of > messages it sends. This may result in a packet size that exceeds the Path > MTU.**** > > To accommodate such situations, IPv6 defines a mechanism that allows large > payloads to be divided into fragments, with each fragment sent in a separate > packet (see [IPv6-SPEC] section "Fragment Header").”**** > > ** ** > > If the node which makes PMTU is the multicast source, it can change the > size of message when the size exceeds the PMTU value.**** > > However, mAFTR, as a router, is unable to change the size of the message. > Here is an example: An IPv4 packet is sent from the multicast source to > mAFTR with size of 1000, while the IPv6 PMTU for mAFTR and mB4 is 960, how > does mAFTR forward the packet? One possible way is to make IPv6 > fragmentation, with two fragments: one is 960 and the other is 40 with “IPv6 > Fragment Header”.**** > > In addition, there may be also other ways to avoid fragmentation, e.g., > cache in mAFTR as defined in [draft-jiang-behave-v4v6mc-proxy].**** > > ** ** > > ** > Jacni>: Please see Yiu's comments, while for the discovery if you really want to do it, this way to help you to understand, it's the end point of tunnel which seems to "source" the v6 packets. Hope you can get it. Cheers, Jacni
_______________________________________________ Softwires mailing list [email protected] https://www.ietf.org/mailman/listinfo/softwires
