RFC 2545: Use of BGP-4 Multiprotocol Extensions for IPv6 Inter-Domain Routing
In plain English — editorial summary, not part of the RFC
BGP-4 Multiprotocol Extensions (BGP-MP) defines the format of two BGP attributes (MP_REACH_NLRI and MP_UNREACH_NLRI) that can be used to announce and withdraw the announcement of reachability information. This document defines how compliant systems should make use of those attributes for the purpose of conveying IPv6 routing information. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2545
- Published
- March 1999
- Authors
- P. Marques; F. Dupont
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 5
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5492Capabilities Advertisement with BGP-4Updated
February 2009
- RFC 5575Dissemination of Flow Specification RulesObsoleted
August 2009
- RFC 2519A Framework for Inter-Domain Route AggregationCurrent
February 1999
- RFC 2439BGP Route Flap DampingCurrent
November 1998
- RFC 2385Protection of BGP Sessions via the TCP MD5 Signature OptionObsoleted
August 1998
- RFC 2338Virtual Router Redundancy ProtocolObsoleted
April 1998
- RFC 2796BGP Route Reflection - An Alternative to Full Mesh IBGPObsoleted
April 2000
- RFC 2270Using a Dedicated AS for Sites Homed to a Single ProviderCurrent
January 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?