--- 1/draft-ietf-mpls-label-encaps-06.txt 2006-02-05 00:39:37.000000000 +0100 +++ 2/draft-ietf-mpls-label-encaps-07.txt 2006-02-05 00:39:37.000000000 +0100 @@ -8,21 +8,21 @@ Tony Li Juniper Networks, Inc. Alex Conta Lucent Technologies September 1999 MPLS Label Stack Encoding - draft-ietf-mpls-label-encaps-06.txt + draft-ietf-mpls-label-encaps-07.txt Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. @@ -669,21 +669,22 @@ header, then: a. Create an ICMP Packet Too Big Message, and set its Next- Hop MTU field to the difference between the Effective Maximum Frame Payload Size and the value of N b. If possible, transmit the ICMP Packet Too Big Message to the source of the datagram. c. discard the labeled IPv6 datagram. - 4. If the IP datagram is not larger than 1280 octets, then + 4. If the IP datagram is not larger than 1280 octets, and it + contains a fragment header, then a. Convert it into fragments, each of which MUST be at least N bytes less than the Effective Maximum Frame Payload Size. b. Prepend each fragment with the same label header that would have been on the original datagram had fragmentation not been necessary. c. Forward the fragments.