Multi-Threaded Routing Toolkit (MRT) Routing Information Export Format with BGP Additional Path Extensions
RFC 8050

Document Type RFC - Proposed Standard (May 2017; No errata)
Last updated 2017-05-19
Replaces draft-petrie-grow-mrt-add-paths
Stream IETF
Formats plain text pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Peter Schoenmaker
Shepherd write-up Show (last changed 2017-01-17)
IESG IESG state RFC 8050 (Proposed Standard)
Consensus Boilerplate Yes
Telechat date
Responsible AD Joel Jaeggli
Send notices to (None)
IANA IANA review state IANA OK - Actions Needed
IANA action state RFC-Ed-Ack
Internet Engineering Task Force (IETF)                         C. Petrie
Request for Comments: 8050                                      RIPE NCC
Category: Standards Track                                        T. King
ISSN: 2070-1721                                                   DE-CIX
                                                                May 2017

 Multi-Threaded Routing Toolkit (MRT) Routing Information Export Format
                  with BGP Additional Path Extensions

Abstract

   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.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in Section 2 of RFC 7841.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc8050.

Copyright Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Petrie & King                Standards Track                    [Page 1]
RFC 8050            Additional Path Extensions in MRT           May 2017

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Rationale . . . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  MRT Subtypes for Types BGP4MP/BGP4MP_ET . . . . . . . . . . .   3
   4.  MRT Subtypes for Type TABLE_DUMP_V2 . . . . . . . . . . . . .   3
     4.1.  AFI/SAFI-Specific RIB Subtypes  . . . . . . . . . . . . .   4
     4.2.  RIB_GENERIC_ADDPATH Subtype . . . . . . . . . . . . . . .   4
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
     5.1.  BGP4MP/BGP4MP_ET Subtype Codes  . . . . . . . . . . . . .   5
     5.2.  TABLE_DUMP_V2 Subtype Codes . . . . . . . . . . . . . . .   5
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   7.  Normative References  . . . . . . . . . . . . . . . . . . . .   6
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   The MRT record format [RFC6396] was developed to provide researchers
   and engineers a means to encapsulate, export, and archive routing
   protocol transactions and RIB snapshots.

   The Advertisement of Multiple Paths in BGP [RFC7911] defines a BGP
   extension to allow the advertisement of multiple paths for the same
   address prefix without the new paths implicitly replacing any
   previous ones.

   This document contains an optional extension to the MRT format
   [RFC6396] and introduces additional definitions of MRT subtype fields
   to permit representation of multiple path advertisements [RFC7911].

2.  Rationale

   MRT parsers are usually stateless.  In order to parse BGP messages
   that contain data structures that depend on the capabilities
   negotiated during the BGP session setup, the MRT subtypes are
   utilized.  The Advertisement of Multiple Paths [RFC7911] extension
   for BGP alters the encoding of the BGP Network Layer Reachability
   Information (NLRI) format for withdraws and announcements.
   Therefore, new BGP4MP/BGP4MP_ET subtypes as defined in [RFC6396] are
   required to signal to an MRT parser how to parse the NLRI.

   In Section 4.3 of the MRT specification [RFC6396], RIB subtypes are
   specified.  Prefix length and prefix fields are encoded in the same
   manner as the BGP NLRI encoding.  In order to support Path Identifier
   information as defined in [RFC7911], new subtypes need to be added.

   The following two sections define the required subtypes.

Petrie & King                Standards Track                    [Page 2]
RFC 8050            Additional Path Extensions in MRT           May 2017

3.  MRT Subtypes for Types BGP4MP/BGP4MP_ET
Show full document text