RFC 8277: Using BGP to Bind MPLS Labels to Address Prefixes
In plain English — editorial summary, not part of the RFC
This document specifies a set of procedures for using BGP to advertise that a specified router has bound a specified MPLS label (or a specified sequence of MPLS labels organized as a contiguous part of a label stack) to a specified address prefix. This can be done by sending a BGP UPDATE message whose Network Layer Reachability Information field contains both the prefix and the MPLS label(s) and whose Next Hop field identifies the node at which said prefix is bound to said label(s). This document obsoletes RFC 3107.
Document record
- Document ID
- RFC8277
- Published
- October 2017
- Authors
- E. Rosen
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 23
- Also known as
- —
- Obsoletes:
- RFC 3107
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1626Default IP MTU for use over ATM AAL5Obsoleted
May 1994
- RFC 3134Terminology for ATM ABR BenchmarkingCurrent
June 2001
- RFC 2761Terminology for ATM BenchmarkingCurrent
February 2000
- RFC 2379RSVP over ATM Implementation GuidelinesCurrent
August 1998
- RFC 2366Definitions of Managed Objects for Multicast over UNI 3.0/3.1 based ATM NetworksObsoleted
July 1998
- RFC 2269Using the MARS Model in non-ATM NBMA NetworksCurrent
January 1998
- RFC 2226IP Broadcast over ATM NetworksCurrent
October 1997
- RFC 2225Classical IP and ARP over ATMUpdated
April 1998
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?