draft-ietf-mpls-label-encaps-05.txt		draft-ietf-mpls-label-encaps-06.txt
	Network Working Group Eric C. Rosen		Network Working Group Eric C. Rosen
	Internet Draft Yakov Rekhter		Internet Draft Yakov Rekhter
	Expiration Date: February 2000 Daniel Tappan		Expiration Date: March 2000 Daniel Tappan
	Dino Farinacci		Dino Farinacci
	Guy Fedorkow		Guy Fedorkow
	Cisco Systems, Inc.		Cisco Systems, Inc.
	Tony Li		Tony Li
	Juniper Networks, Inc.		Juniper Networks, Inc.
	Alex Conta		Alex Conta
	Lucent Technologies		Lucent Technologies
	August 1999		September 1999
	MPLS Label Stack Encoding		MPLS Label Stack Encoding
	draft-ietf-mpls-label-encaps-05.txt		draft-ietf-mpls-label-encaps-06.txt
	Status of this Memo		Status of this Memo
	This document is an Internet-Draft and is in full conformance with		This document is an Internet-Draft and is in full conformance with
	all provisions of Section 10 of RFC2026.		all provisions of Section 10 of RFC2026.
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF), its areas, and its working groups. Note that		Task Force (IETF), its areas, and its working groups. Note that
	other groups may also distribute working documents as Internet-		other groups may also distribute working documents as Internet-
	Drafts.		Drafts.
	skipping to change at page 15, line 43		skipping to change at page 15, line 43
	To process a labeled IPv6 datagram which is too big, an LSR MUST		To process a labeled IPv6 datagram which is too big, an LSR MUST
	execute the following algorithm:		execute the following algorithm:
	1. Strip off the label stack entries to obtain the IP datagram.		1. Strip off the label stack entries to obtain the IP datagram.
	2. Let N be the number of bytes in the label stack (i.e, 4 times		2. Let N be the number of bytes in the label stack (i.e, 4 times
	the number of label stack entries).		the number of label stack entries).
	3. If the IP datagram contains more than 1280 bytes (not counting		3. If the IP datagram contains more than 1280 bytes (not counting
	the label stack entries), then:		the label stack entries), or if it does not contain a fragment
			header, then:
	a. Create an ICMP Packet Too Big Message, and set its Next-		a. Create an ICMP Packet Too Big Message, and set its Next-
	Hop MTU field to the difference between the Effective		Hop MTU field to the difference between the Effective
	Maximum Frame Payload Size and the value of N		Maximum Frame Payload Size and the value of N
	b. If possible, transmit the ICMP Packet Too Big Message to		b. If possible, transmit the ICMP Packet Too Big Message to
	the source of the datagram.		the source of the datagram.
	c. discard the labeled IPv6 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, then
	skipping to change at page 19, line 45		skipping to change at page 19, line 45
	headers that may exist.		headers that may exist.
	The ethertype value 8847 hex is used to indicate that a frame is		The ethertype value 8847 hex is used to indicate that a frame is
	carrying an MPLS unicast packet.		carrying an MPLS unicast packet.
	The ethertype value 8848 hex is used to indicate that a frame is		The ethertype value 8848 hex is used to indicate that a frame is
	carrying an MPLS multicast packet.		carrying an MPLS multicast packet.
	These ethertype values can be used with either the ethernet		These ethertype values can be used with either the ethernet
	encapsulation or the 802.3 LLC/SNAP encapsulation to carry labeled		encapsulation or the 802.3 LLC/SNAP encapsulation to carry labeled
	packets.		packets. The procedure for choosing which of these two
			encapsulations to use is beyond the scope of this document.
	6. IANA Considerations		6. IANA Considerations
	Label values 0-15 inclusive have special meaning, as specified in		Label values 0-15 inclusive have special meaning, as specified in
	this document, or as further assigned by IANA.		this document, or as further assigned by IANA.
	In this document, label values 0-3 are specified in section 2.1.		In this document, label values 0-3 are specified in section 2.1.
	Label values 4-15 may be assigned by IANA, based on IETF Consensus.		Label values 4-15 may be assigned by IANA, based on IETF Consensus.
End of changes.
This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/