RFC 3031: Multiprotocol Label Switching Architecture

In plain English — editorial summary, not part of the RFC

This document specifies the architecture for Multiprotocol Label Switching (MPLS). [STANDARDS-TRACK]

Document record

Document ID

RFC3031

Published

January 2001

Authors

E. Rosen; A. Viswanathan; R. Callon

Status

PROPOSED STANDARD

Stream

IETF

Area

rtg

Pages

61

Also known as

—

Updated by:

RFC 6178, RFC 6790

• Read the full RFC text →
• Plain text version
• IETF Datatracker history
• DOI: 10.17487/RFC3031
• Reported errata exist →

Topics

• MPLS
• Multiprotocol Label Switching

Referenced by

2 later RFCs formally update or obsolete part of this document.

• RFC 6178Label Edge Router Forwarding of IPv4 Option PacketsCurrent

  March 2011

• RFC 6790The Use of Entropy Labels in MPLS ForwardingUpdated

  November 2012

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

• RFC 3063MPLS Loop Prevention MechanismCurrent

  February 2001

• RFC 3479Fault Tolerance for the Label Distribution Protocol (LDP)Current

  February 2003

• RFC 3480Signalling Unnumbered Links in CR-LDP (Constraint-Routing Label Distribution Protocol)Current

  February 2003

• RFC 3612Applicability Statement for Restart Mechanisms for the Label Distribution Protocol (LDP)Current

  September 2003

• RFC 3811Definitions of Textual Conventions (TCs) for Multiprotocol Label Switching (MPLS) ManagementUpdated

  June 2004

• RFC 3812Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Management Information Base (MIB)Current

  June 2004

• RFC 3814Multiprotocol Label Switching (MPLS) Forwarding Equivalence Class To Next Hop Label Forwarding Entry (FEC-To-NHLFE) Management Information Base (MIB)Current

  June 2004

• RFC 3815Definitions of Managed Objects for the Multiprotocol Label Switching (MPLS), Label Distribution Protocol (LDP)Current

  June 2004

Also filed under

• PROPOSED STANDARD
• 2001
• IETF stream
• rtg area