RFC 4781: Graceful Restart Mechanism for BGP with MPLS
In plain English — editorial summary, not part of the RFC
A mechanism for BGP that helps minimize the negative effects on routing caused by BGP restart has already been developed and is described in a separate document ("Graceful Restart Mechanism for BGP"). This document extends this mechanism to minimize the negative effects on MPLS forwarding caused by the Label Switching Router's (LSR's) control plane restart, and specifically by the restart of its BGP component when BGP is used to carry MPLS labels and the LSR is capable of preserving the MPLS forwarding state across the restart. The mechanism described in this document is agnostic with respect to the types of the addresses carried in the BGP Network Layer Reachability Information (NLRI) field. As such, it works in conjunction with any of the address families that could be carried in BGP (e.g., IPv4, IPv6, etc.). [STANDARDS-TRACK]
Document record
- Document ID
- RFC4781
- Published
- January 2007
- Authors
- Y. Rekhter; R. Aggarwal
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 10
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4659BGP-MPLS IP Virtual Private Network (VPN) Extension for IPv6 VPNCurrent
September 2006
- RFC 4761Virtual Private LAN Service (VPLS) Using BGP for Auto-Discovery and SignalingUpdated
January 2007
- RFC 4760Multiprotocol Extensions for BGP-4Updated
January 2007
- RFC 4724Graceful Restart Mechanism for BGPUpdated
January 2007
- RFC 4842Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Circuit Emulation over Packet (CEP)Current
April 2007
- RFC 4717Encapsulation Methods for Transport of Asynchronous Transfer Mode (ATM) over MPLS NetworksCurrent
December 2006
- RFC 4687Operations and Management (OAM) Requirements for Point-to-Multipoint MPLS NetworksCurrent
September 2006
- RFC 4893BGP Support for Four-octet AS Number SpaceObsoleted
May 2007
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?