RFC 8050: Multi-Threaded Routing Toolkit (MRT) Routing Information Export Format with BGP Additional Path Extensions
In plain English — editorial summary, not part of the RFC
This document extends the Multi-threaded Routing Toolkit (MRT) export format for Border Gateway Protocol (BGP) routing information by supporting the advertisement of multiple paths in BGP extensions.
Document record
- Document ID
- RFC8050
- Published
- May 2017
- Authors
- C. Petrie; T. King
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 6
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8049YANG Data Model for L3VPN Service DeliveryObsoleted
February 2017
- RFC 8056Extensible Provisioning Protocol (EPP) and Registration Data Access Protocol (RDAP) Status MappingCurrent
January 2017
- RFC 8040RESTCONF ProtocolUpdated
January 2017
- RFC 8063Key Relay Mapping for the Extensible Provisioning ProtocolCurrent
February 2017
- RFC 8071NETCONF Call Home and RESTCONF Call HomeCurrent
February 2017
- RFC 8072YANG Patch Media TypeCurrent
February 2017
- RFC 8027DNSSEC Roadblock AvoidanceCurrent
November 2016
- RFC 8022A YANG Data Model for Routing ManagementObsoleted
November 2016
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?