RFC 3107: Carrying Label Information in BGP-4
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 8277.
Current version: RFC 8277 — Using BGP to Bind MPLS Labels to Address Prefixes
In plain English — editorial summary, not part of the RFC
This document specifies the way in which the label mapping information for a particular route is piggybacked in the same Border Gateway Protocol (BGP) Update message that is used to distribute the route itself. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3107
- Published
- May 2001
- Authors
- Y. Rekhter; E. Rosen
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 8
- Also known as
- —
Topics
Referenced by
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3108Conventions for the use of the Session Description Protocol (SDP) for ATM Bearer ConnectionsCurrent
May 2001
- RFC 3038VCID Notification over ATM link for LDPUpdated
January 2001
- RFC 3035MPLS using LDP and ATM VC SwitchingCurrent
January 2001
- RFC 2918Route Refresh Capability for BGP-4Updated
September 2000
- RFC 3355Layer Two Tunnelling Protocol (L2TP) Over ATM Adaptation Layer 5 (AAL5)Current
September 2002
- RFC 2844OSPF over ATM and Proxy-PARCurrent
May 2000
- RFC 3392Capabilities Advertisement with BGP-4Obsoleted
November 2002
- RFC 2796BGP Route Reflection - An Alternative to Full Mesh IBGPObsoleted
April 2000
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?