Multiprotocol Label Switching (mpls) ------------------------------------ Charter Last Modified: 2006-03-24 Current Status: Active Working Group Chair(s): George Swallow Loa Andersson Routing Area Director(s): Ross Callon Bill Fenner Routing Area Advisor: Ross Callon Mailing Lists: General Discussion:mpls@lists.ietf.org To Subscribe: https://www1.ietf.org/mailman/listinfo/mpls Archive: http://cell.onecall.net/cell-relay/archives/mpls/mpls.index.html Description of Working Group: The MPLS working group is responsible for standardizing a base technology for using label switching and for the implementation of label-switched paths over various packet based link-level technologies, such as Packet-over-Sonet, Frame Relay, ATM, and LAN technologies (e.g. all forms of Ethernet, Token Ring, etc.). This includes procedures and protocols for the distribution of labels between routers and encapsulation. The working group is also responsible for specifying the necessary MIBs for the functionality specified in the base MPLS technology. The first generation of the MPLS standards are largely complete, and the current WG work items are: - Define requirements, mechanisms and protocol extensions for point-to-multipoint (P2MP) MPLS - Define requirements, mechanisms and protocol extensions for traffic engineered point-to-multipoint (P2MP) MPLS, including soft preemption - Define requirements and mechanisms for MPLS OAM - Define an overall OAM framework for MPLS applications - MPLS-specific aspects of traffic engineering for multi-areas/multi-AS in cooperation with the CCAMP WG - Determine (with CCAMP) what procedures are appropriate for evaluating proposals to extend the MPLS and GMPLS protocols, and document these - Document current implementation practices for MPLS load sharing The Working Group chairs tracking of the working group documents can be viewed at http://www.tla-group.com/~mpls/mpls-wg-docs.htm Goals and Milestones: Done Submit documents from original MPLS effort to IESG Done Framework for IP multicast over label-switched paths ready for advancement. Done LDP fault tolerance specification ready for advancement to Proposed Standard. Done Submit Definitions of Managed Objects for MultoiProtocol Label Switching, Label Distribution Protocol (LDP) to the IESG for publication as Proposed Standards Done Specification for MPLS-specific recovery ready for advancement. Done Submit Multiprotocol Label Switching (MPLS) Forward Equivalency Class-To-Next Hop Label Forwarding Entry Management Information Base to the IESG for publication as Proposed Standards Done Submit Multiprotocol Label Switching (MPLS) Label Switching Router (LSR), Management Information Base to the IESG for publication as Proposed Standards Done Submit Multiprotocol Label Switching (MPLS) Management Overview to the IESG for publication as Proposed Standards Done Submit Definitions of Textual Conventions for Multiprotocol Label Switching (MPLS) Management to the IESG for publication as Proposed Standards Done Submit Multiprotocol Label Switching (MPLS) Traffic Engineering Management Information Base to the IESG for publication as Proposed Standards Done Submit the Traffic Engineering Link MIB to the IESG for as a Proposed Standard Done Submit a specification on Encapsulations to carry MPLS over IP and GRE to the IESG for as a Proposed Standard Done Submit specification on LSP Ping to the IESG for publication as a Proposed Standard Done Submit a document defining the scope, requirements, and issues to resolve for setup of P2MP TE LSPs (MPLS and GMPLS) Done Submit an OAM Framework Document to the IESG for publication as an Informational RFC Done Submit a BCP on MPLS load sharing to the IESG Done Submit specification on LSR Self Test to the IESG for publication as a Proposed Standard Dec 2005 Submit a specification on Soft Pre-emption of LSP Tunnels to the IESG for publication as a Proposed Standard Dec 2005 Submit document(s) specifying protocol extensions, enhancements and mechanisms for setup of P2MP TE LSPs Feb 2006 Submit requirements for point-to-multipoint extensions to LDP Apr 2006 Advance 'Extension to RSVP for LSP Tunnels' to Draft Standard Apr 2006 Advance MPLS Architecture and MPLS encapsulation to Draft Standard Aug 2006 Submit document(s) specifying LDP extensions for setup of P2MP LSPs Internet-Drafts: Posted Revised I-D Title ------ ------- -------------------------------------------- Jul 1999 Mar 2006 ICMP Extensions for MultiProtocol Label Switching Feb 2002 Aug 2005 Graceful Restart Mechanism for BGP with MPLS Jul 2002 Jul 2006 Multiprotocol Label Switching (MPLS) Traffic Engineering Management Information Base for Fast Reroute Apr 2003 Jan 2006 MPLS Traffic Engineering Soft Preemption Oct 2003 Oct 2005 Label Switching Router Self-Test Oct 2004 Oct 2005 LDP Specification Oct 2004 Oct 2005 Avoiding Equal Cost Multipath Treatment in MPLS Networks Nov 2004 Aug 2006 Extensions to RSVP-TE for Point-to-Multipoint TE LSPs Feb 2005 Feb 2006 Encapsulation of MPLS over Layer 2 Tunneling Protocol Version 3 Sep 2005 Apr 2006 Detecting Data Plane Failures in Point-to-Multipoint MPLS Traffic Engineering - Extensions to LSP Ping Sep 2005 Feb 2006 Component Link Recording and Resource Control for GMPLS Link Bundles Sep 2005 Sep 2005 Experience with the LDP protocol Oct 2005 Oct 2005 LDP Implementation Survey Results Dec 2005 Feb 2006 OAM Requirements for Point-to-Multipoint MPLS Networks Feb 2006 Feb 2006 MPLS Multicast Encapsulations Mar 2006 Jun 2006 Label Distribution Protocol Extensions for Point-to-Multipoint and Multipoint-to-Multipoint Label Switched Paths Mar 2006 Mar 2006 MPLS Upstream Label Assignment and Context Specific Label Space Mar 2006 Mar 2006 MPLS Upstream Label Assignment for RSVP-TE Apr 2006 Apr 2006 MPLS Upstream Label Assignment for LDP May 2006 Jun 2006 Requirements for point-to-multipoint extensions to the Label Distribution Protocol May 2006 Jun 2006 A Link-Type sub-TLV to convey the number of Traffic Engineering Label Switch Paths signalled across a link Jul 2006 Jul 2006 Codepoint Registry for The Flags Field in the Resource Reservation Protocol Traffic Engineering (RSVP-TE) Session Attribute Object Request For Comments: RFC Stat Published Title ------- -- ----------- ------------------------------------ RFC2702 I Sep 1999 Requirements for Traffic Engineering Over MPLS RFC3031 PS Jan 2001 Multiprotocol Label Switching Architecture RFC3032 PS Jan 2001 MPLS Label Stack Encoding RFC3034 PS Jan 2001 Use of Label Switching on Frame Relay Networks Specification RFC3035 PS Jan 2001 MPLS using LDP and ATM VC Switching RFC3036 PS Jan 2001 LDP Specification RFC3038 PS Jan 2001 VCID Notification over ATM link for LDP RFC3037 PS Jan 2001 LDP Applicability RFC3033 PS Jan 2001 The Assignment of the Information Field and Protocol Identifier in the Q.2941 Generic Identifier and Q.2957 User-to-user Signaling for the Internet Protocol RFC3063 E Feb 2001 MPLS Loop Prevention Mechanism RFC3107 PS May 2001 Carrying Label Information in BGP-4 RFC3210 I Dec 2001 Applicability Statement for Extensions to RSVP for LSP-Tunnels RFC3209 PS Dec 2001 RSVP-TE: Extensions to RSVP for LSP Tunnels RFC3212 PS Feb 2002 Constraint-Based LSP Setup using LDP RFC3213 I Feb 2002 Applicability Statement for CR-LDP RFC3214 PS Feb 2002 LSP Modification Using CR-LDP RFC3215 I Feb 2002 LDP State Machine RFC3270 PS May 2002 MPLS Support of Differentiated Services RFC3353 I Aug 2002 Framework for IP Multicast in MPLS RFC3443 PS Jan 2003 Time to Live (TTL) Processing in MPLS Networks (Updates RFC 3032) RFC3477 PS Feb 2003 Signalling Unnumbered Links in Resource ReSerVation Protocol - Traffic Engineering (RSVP-TE) RFC3469 I Feb 2003 Framework for MPLS-based Recovery RFC3479 PS Feb 2003 Fault Tolerance for the Label Distribution Protocol (LDP) RFC3478 PS Feb 2003 Graceful Restart Mechanism for Label Distribution Protocol RFC3480 PS Feb 2003 Signalling Unnumbered Links in CR-LDP (Constraint-Routing Label Distribution Protocol) RFC3612 I Sep 2003 Applicability Statement for Restart Mechanisms for the Label Distribution Protocol (LDP) RFC3811Standard Jun 2004 Definitions of Textual Conventions for Multiprotocol Label Switching (MPLS) Management RFC3815Standard Jun 2004 Definitions of Managed Objects for the Multiprotocol Label Switching, Label Distribution Protocol (LDP) RFC3814Standard Jun 2004 Multiprotocol Label Switching (MPLS) Forwarding Equivalence Class To Next Hop Label Forwarding Entry (FEC-To-NHLFE)Management Information Base RFC3813Standard Jun 2004 Multiprotocol Label Switching (MPLS) Label Switching Router (LSR)Management Information Base RFC3812Standard Jun 2004 Multiprotocol Label Switching (MPLS) Traffic Engineering Management Information Base RFC3988 E Feb 2005 Maximum Transmission Unit Signalling Extensions for the Label Distribution Protocol RFC4023Standard Mar 2005 Encapsulating MPLS in IP or Generic Routing Encapsulation (GRE) RFC4090Standard May 2005 Fast Reroute Extensions to RSVP-TE for LSP Tunnels RFC4182Standard Sep 2005 Removing a Restriction on the use of MPLS Explicit NULL RFC4201Standard Oct 2005 Link Bundling in MPLS Traffic Engineering RFC4206Standard Oct 2005 Label Switched Paths (LSP) Hierarchy with Generalized Multi-Protocol Label Switching (GMPLS) Traffic Engineering (TE) RFC4221 I Nov 2005 Multiprotocol Label Switching (MPLS) Management Overview RFC4220Standard Nov 2005 Traffic Engineering Link Management Information Base RFC4368Standard Jan 2006 Multiprotocol Label Switching (MPLS) Label-Controlled ATM and Frame-Relay Management Interface Definition RFC4379Standard Feb 2006 Detecting Multi-Protocol Label Switched (MPLS) Data Plane Failures RFC4378 I Feb 2006 A Framework for Multi-Protocol Label Switching (MPLS) Operations and Management (OAM) RFC4377 I Feb 2006 Operations and Management (OAM) Requirements for Multi-Protocol Label Switched (MPLS) Networks RFC4420 PS Feb 2006 Encoding of Attributes for Multiprotocol Label Switching (MPLS) Label Switched Path (LSP) Establishment Using Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) RFC4461 I Apr 2006 Signaling Requirements for Point to Multipoint Traffic Engineered MPLS Label Switched Paths (LSPs) RFC4561 PS Jun 2006 Definition of a Record Route Object (RRO) Node-Id Sub-Object