RFC 6060: Generalized Multiprotocol Label Switching (GMPLS) Control of Ethernet Provider Backbone Traffic Engineering (PBB-TE)
In plain English — editorial summary, not part of the RFC
This specification is complementary to the GMPLS Ethernet Label Switching Architecture and Framework and describes the technology-specific aspects of GMPLS control for Provider Backbone Bridge Traffic Engineering (PBB-TE). The necessary GMPLS extensions and mechanisms are described to establish Ethernet PBB-TE point-to-point (P2P) and point-to-multipoint (P2MP) connections. This document supports, but does not modify, the standard IEEE data plane. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6060
- Published
- March 2011
- Authors
- D. Fedyk; H. Shah; N. Bitar; A. Takacs
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 20
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6053Implementation Report for Forwarding and Control Element Separation (ForCES)Updated
November 2010
- RFC 6073Segmented PseudowireUpdated
January 2011
- RFC 6074Provisioning, Auto-Discovery, and Signaling in Layer 2 Virtual Private Networks (L2VPNs)Current
January 2011
- RFC 6041Forwarding and Control Element Separation (ForCES) Applicability StatementCurrent
October 2010
- RFC 6107Procedures for Dynamically Signaled Hierarchical Label Switched PathsCurrent
February 2011
- RFC 6007Use of the Synchronization VECtor (SVEC) List for Synchronized Dependent Path ComputationsCurrent
September 2010
- RFC 6006Extensions to the Path Computation Element Communication Protocol (PCEP) for Point-to-Multipoint Traffic Engineering Label Switched PathsObsoleted
September 2010
- RFC 6005Generalized MPLS (GMPLS) Support for Metro Ethernet Forum and G.8011 User Network Interface (UNI)Current
October 2010
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?