< draft-martini-l2circuit-trans-mpls-08.txt		draft-martini-l2circuit-trans-mpls-09.txt >
	Network Working Group Luca Martini		Network Working Group Luca Martini
	Internet Draft Nasser El-Aawar		Internet Draft Nasser El-Aawar
	Expiration Date: May 2002 Level 3 Communications, LLC.		Expiration Date: October 2002 Level 3 Communications, LLC.
	Steve Vogelsang Daniel Tappan		Steve Vogelsang Daniel Tappan
	John Shirron Eric C. Rosen		John Shirron Eric C. Rosen
	Toby Smith Alex Hamilton		Toby Smith Alex Hamilton
	Laurel Networks, Inc. Jayakumar Jayakumar		Laurel Networks, Inc. Jayakumar Jayakumar
	Cisco Systems, Inc.		Cisco Systems, Inc.
	Vasile Radoaca Dimitri Stratton Vlachos		Vasile Radoaca Dimitri Stratton Vlachos
	Nortel Networks Mazu Networks, Inc.		Nortel Networks Mazu Networks, Inc.
	Andrew G. Malis Chris Liljenstolpe		Andrew G. Malis Chris Liljenstolpe
	Vinai Sirkay Cable & Wireless		Vinai Sirkay Cable & Wireless
	Vivace Networks, Inc.		Vivace Networks, Inc.
	Giles Heron		Giles Heron
	Dave Cooper PacketExchange Ltd.		Dave Cooper PacketExchange Ltd.
	Global Crossing		Global Crossing
	Kireeti Kompella		Kireeti Kompella
	Juniper Networks		Juniper Networks
	November 2001		April 2002
	Transport of Layer 2 Frames Over MPLS		Transport of Layer 2 Frames Over MPLS
	draft-martini-l2circuit-trans-mpls-08.txt		draft-martini-l2circuit-trans-mpls-09.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 other		Task Force (IETF), its areas, and its working groups. Note that other
	groups may also distribute working documents as Internet-Drafts.		groups may also distribute working documents as Internet-Drafts.
	skipping to change at page 5, line 34 ¶		skipping to change at page 5, line 34 ¶
	signaling to the Frame Relay network. If the MPLS edge LSR detects a		signaling to the Frame Relay network. If the MPLS edge LSR detects a
	service affecting condition as defined in [2] Q.933 Annex A.5 sited		service affecting condition as defined in [2] Q.933 Annex A.5 sited
	in IA FRF1.1, it MUST withdraw the label that corresponds to the		in IA FRF1.1, it MUST withdraw the label that corresponds to the
	frame relay DLCI. The Egress LSR SHOULD generate the corresponding		frame relay DLCI. The Egress LSR SHOULD generate the corresponding
	errors and alarms as defined in [2] on the egress Frame relay VC.		errors and alarms as defined in [2] on the egress Frame relay VC.
	4.2. ATM		4.2. ATM
	4.2.1. ATM AAL5 VCC Transport		4.2.1. ATM AAL5 VCC Transport
	ATM AAL5 CSPS-SDUs are encapsulated according to [7] ATM AAL5 CPCS-		ATM AAL5 CSPS-SDUs are encapsulated according to [10] ATM AAL5 CPCS-
	SDU mode. This mode allows the transport of ATM AAL5 CSPS-SDUs		SDU mode. This mode allows the transport of ATM AAL5 CSPS-SDUs
	traveling on a particular ATM PVC across the MPLS network to another		traveling on a particular ATM PVC across the MPLS network to another
	ATM PVC.		ATM PVC.
	4.2.2. ATM Transparent Cell Transport		4.2.2. ATM Transparent Cell Transport
	This mode is similar to the Ethernet port mode. Every cell that is		This mode is similar to the Ethernet port mode. Every cell that is
	received at the ingress ATM port on the ingress LSR, R1, is		received at the ingress ATM port on the ingress LSR, R1, is
	encapsulated according to [7], ATM cell mode, and sent across the LSP		encapsulated according to [10], ATM cell mode, and sent across the
	to the egress LSR, R2. This mode allows an ATM port to be connected		LSP to the egress LSR, R2. This mode allows an ATM port to be
	to only one other ATM port. [7] allows for grouping of multiple cells		connected to only one other ATM port. [10] allows for grouping of
	into a single MPLS frame. Grouping of ATM cells is OPTIONAL for		multiple cells into a single MPLS frame. Grouping of ATM cells is
	transmission at the ingress LSR, R1. If the Egress LSR R2 supports		OPTIONAL for transmission at the ingress LSR, R1. If the Egress LSR
	cell concatenation the ingress LSR, R1, should only concatenate cells		R2 supports cell concatenation the ingress LSR, R1, should only
	up to the "Maximum Number of concatenated ATM cells" parameter		concatenate cells up to the "Maximum Number of concatenated ATM
	received as part of the FEC element.		cells" parameter received as part of the FEC element.
	4.2.3. ATM VCC and VPC Cell Transport		4.2.3. ATM VCC and VPC Cell Transport
	This mode is similar to the ATM AAL5 VCC transport except that cells		This mode is similar to the ATM AAL5 VCC transport except that cells
	are transported. Every cell that is received on a pre-defined ATM		are transported. Every cell that is received on a pre-defined ATM
	PVC, or ATM PVP, at the ingress ATM port on the ingress LSR, R1, is		PVC, or ATM PVP, at the ingress ATM port on the ingress LSR, R1, is
	encapsulated according to [7], ATM cell mode, and sent across the LSP		encapsulated according to [10], ATM cell mode, and sent across the
	to the egress LSR R2. Grouping of ATM cells is OPTIONAL for		LSP to the egress LSR R2. Grouping of ATM cells is OPTIONAL for
	transmission at the ingress LSR, R1. If the Egress LSR R2 supports		transmission at the ingress LSR, R1. If the Egress LSR R2 supports
	cell concatenation the ingress LSR, R1, MUST only concatenate cells		cell concatenation the ingress LSR, R1, MUST only concatenate cells
	up to the "Maximum Number of concatenated ATM cells in a frame"		up to the "Maximum Number of concatenated ATM cells in a frame"
	parameter received as part of the FEC element.		parameter received as part of the FEC element.
	4.2.4. OAM Cell Support		4.2.4. OAM Cell Support
	OAM cells MAY be transported on the VC LSP. When the LSR is operating		OAM cells MAY be transported on the VC LSP. When the LSR is operating
	in AAL5 CPCS-SDU transport mode if it does not support transport of		in AAL5 CPCS-SDU transport mode if it does not support transport of
	ATM cells, the LSR MUST discard incoming MPLS frames on an ATM VC LSP		ATM cells, the LSR MUST discard incoming MPLS frames on an ATM VC LSP
	that contain a VC label with the T bit set [7]. When operating in		that contain a VC label with the T bit set [10]. When operating in
	AAL5 SDU transport mode an LSR that supports transport of OAM cells		AAL5 SDU transport mode an LSR that supports transport of OAM cells
	using the T bit defined in [7], or an LSR operating in any of the		using the T bit defined in [7], or an LSR operating in any of the
	three cell transport modes MUST follow the procedures outlined in [9]		three cell transport modes MUST follow the procedures outlined in [9]
	section 8 for mode 0 only, in addition to the applicable procedures		section 8 for mode 0 only, in addition to the applicable procedures
	specified in [6].		specified in [6].
	4.2.4.1. OAM Cell Emulation Mode		4.2.4.1. OAM Cell Emulation Mode
	AN LSR that does not support transport of OAM cells across an LSP MAY		AN LSR that does not support transport of OAM cells across an LSP MAY
	provide OAM support on ATM PVCs using the following procedures:		provide OAM support on ATM PVCs using the following procedures:
	skipping to change at page 7, line 29 ¶		skipping to change at page 7, line 29 ¶
	An MPLS edge LSR MAY provide an ATM ILMI to the ATM edge switch. If		An MPLS edge LSR MAY provide an ATM ILMI to the ATM edge switch. If
	an ingress LSR receives an ILMI message indicating that the ATM edge		an ingress LSR receives an ILMI message indicating that the ATM edge
	switch has deleted a VC, or if the physical interface goes down, it		switch has deleted a VC, or if the physical interface goes down, it
	MUST withdraw the label mappings for all VCs associated with the		MUST withdraw the label mappings for all VCs associated with the
	failure. When a VC label mapping is withdrawn, the egress LSR SHOULD		failure. When a VC label mapping is withdrawn, the egress LSR SHOULD
	notify its client of this failure by deleting the VC using ILMI.		notify its client of this failure by deleting the VC using ILMI.
	4.3. Ethernet VLAN		4.3. Ethernet VLAN
	The Ethernet frame will be encapsulated according to the procedures		The Ethernet frame will be encapsulated according to the procedures
	in [7]. It should be noted that if the VLAN identifier is modified		in [12]. It should be noted that if the VLAN identifier is modified
	by the egress LSR, according to the procedures outlined above, the		by the egress LSR, according to the procedures outlined above, the
	Ethernet spanning tree protocol might fail to work properly. If the		Ethernet spanning tree protocol might fail to work properly. If the
	LSR detects a failure on the Ethernet physical port, or the port is		LSR detects a failure on the Ethernet physical port, or the port is
	administratively disabled, it MUST withdraw the label mappings for		administratively disabled, it MUST withdraw the label mappings for
	all VCs associated with the port.		all VCs associated with the port.
	4.4. Ethernet		4.4. Ethernet
	The Ethernet frame will be encapsulated according to the procedures		The Ethernet frame will be encapsulated according to the procedures
	in [7]. If the LSR detects a failure on the Ethernet physical port,		in [12]. If the LSR detects a failure on the Ethernet physical port,
	or the port is administratively disabled, the corresponding VC label		or the port is administratively disabled, the corresponding VC label
	mapping MUST be withdrawn.		mapping MUST be withdrawn.
	4.5. HDLC		4.5. HDLC
	HDLC frames are encapsulated according to the procedures in [7]. If		HDLC frames are encapsulated according to the procedures in [11]. If
	the MPLS edge LSR detects that the physical link has failed, or the		the MPLS edge LSR detects that the physical link has failed, or the
	port is adminstratively disabled, it MUST withdraw the label mapping		port is adminstratively disabled, it MUST withdraw the label mapping
	that corresponds to the HDLC link.		that corresponds to the HDLC link.
	4.6. PPP		4.6. PPP
	PPP frames are encapsulated according to the procedures in [7]. If		PPP frames are encapsulated according to the procedures in [11]. If
	the MPLS edge LSR detects that the physical link has failed, or the		the MPLS edge LSR detects that the physical link has failed, or the
	port is adminstratively disabled, it MUST withdraw the label mapping		port is adminstratively disabled, it MUST withdraw the label mapping
	that corresponds to the PPP link.		that corresponds to the PPP link.
	5. LDP		5. LDP
	The VC label bindings are distributed using the LDP downstream		The VC label bindings are distributed using the LDP downstream
	unsolicited mode described in [1]. The LSRs will establish an LDP		unsolicited mode described in [1]. The LSRs will establish an LDP
	session using the Extended Discovery mechanism described in [1,		session using the Extended Discovery mechanism described in [1,
	section 2.4.2 and 2.5], for this purpose a new type of FEC element is		section 2.4.2 and 2.5], for this purpose a new type of FEC element is
	skipping to change at page 15, line 50 ¶		skipping to change at page 15, line 50 ¶
	Fedorkow, D. Farinacci, T. Li, A. Conta. RFC3032		Fedorkow, D. Farinacci, T. Li, A. Conta. RFC3032
	[4] "IEEE 802.3ac-1998" IEEE standard specification.		[4] "IEEE 802.3ac-1998" IEEE standard specification.
	[5] American National Standards Institute, "Synchronous Optical		[5] American National Standards Institute, "Synchronous Optical
	Network Formats," ANSI T1.105-1995.		Network Formats," ANSI T1.105-1995.
	[6] ITU Recommendation G.707, "Network Node Interface For The		[6] ITU Recommendation G.707, "Network Node Interface For The
	Synchronous Digital Hierarchy", 1996.		Synchronous Digital Hierarchy", 1996.
	[7] "Encapsulation Methods for Transport of Layer 2 Frames Over		[7] "Encapsulation Methods for Transport of Frame-Relay Over IP and
	MPLS", draft-martini-l2circuit-encap-mpls-04.txt ( Work in progress )		MPLS Networks", draft-martini-frame-encap-mpls-00.txt. ( work in
			progress )
	[8] "SONET/SDH Circuit Emulation Service Over MPLS (CEM)		[8] "SONET/SDH Circuit Emulation Service Over MPLS (CEM)
	Encapsulation", draft-malis-sonet-ces-mpls-05.txt ( Work in progress		Encapsulation", draft-malis-sonet-ces-mpls-05.txt ( Work in progress
	)		)
	[9] "Frame Based ATM over SONET/SDH Transport (FAST)," 2000.		[9] "Frame Based ATM over SONET/SDH Transport (FAST)," 2000.
			[10] "Encapsulation Methods for Transport of ATM Cells/Frame Over IP
			and MPLS Networks", draft-martini-atm-encap-mpls-00.txt. ( work in
			progress )
			[11] "Encapsulation Methods for Transport of PPP/HDLC Frames Over IP
			and MPLS Networks", draft-martini-ppp-hdlc-encap-mpls-00.txt. ( work
			in progress )
			[12] "Encapsulation Methods for Transport of Ethernet Frames Over IP
			and MPLS Networks", draft-martini-ethernet-encap-mpls-00.txt. ( work
			in progress )
	[note1] FEC element type 128 is pending IANA approval. [note2]		[note1] FEC element type 128 is pending IANA approval. [note2]
	Status codes assigment is pending IANA approval.		Status codes assigment is pending IANA approval.
	9. Author Information		9. Author Information
	Luca Martini		Luca Martini
	Level 3 Communications, LLC.		Level 3 Communications, LLC.
	1025 Eldorado Blvd.		1025 Eldorado Blvd.
	Broomfield, CO, 80021		Broomfield, CO, 80021
	e-mail: luca@level3.net		e-mail: luca@level3.net
End of changes. 13 change blocks.
	22 lines changed or deleted		35 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/