Multi-Threaded Routing Toolkit (MRT) Routing Information Export Format with BGP Additional Paths Extensions
draft-ietf-grow-mrt-add-paths-01

The information below is for an old version of the document
Document Type Active Internet-Draft (grow WG)
Last updated 2016-12-07 (latest revision 2016-07-08)
Replaces draft-petrie-grow-mrt-add-paths
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Reviews
Additional URLs
- Mailing list discussion
Stream WG state WG Consensus: Waiting for Write-Up
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Global Routing Operations                                      C. Petrie
Internet-Draft                                                  RIPE NCC
Intended status: Standards Track                                 T. King
Expires: January 9, 2017                          DE-CIX Management GmbH
                                                            July 8, 2016

 Multi-Threaded Routing Toolkit (MRT) Routing Information Export Format
                  with BGP Additional Paths Extensions
                    draft-ietf-grow-mrt-add-paths-01

Abstract

   This document updates the Multi-threaded Routing Toolkit (MRT) export
   format for Border Gateway Protocol (BGP) routing information by
   extending it to support the Advertisement of Multiple Paths in BGP
   extensions.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on January 9, 2017.

Copyright Notice

   Copyright (c) 2016 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

Petrie & King            Expires January 9, 2017                [Page 1]
Internet-Draft     Additional Paths Extensions in MRT          July 2016

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Requirements Language . . . . . . . . . . . . . . . . . . . .   2
   3.  Rationale . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  MRT Subtypes for Types BGP4MP/BGP4MP_ET . . . . . . . . . . .   3
   5.  MRT Subtypes for Type TABLE_DUMP_V2 . . . . . . . . . . . . .   3
     5.1.  AFI/SAFI specific RIB Subtypes  . . . . . . . . . . . . .   4
     5.2.  RIB_GENERIC_ADDPATH Subtype . . . . . . . . . . . . . . .   4
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
     6.1.  BGP4MP/BGP4MP_ET Subtype codes: . . . . . . . . . . . . .   5
     6.2.  TABLE_DUMP_V2 Subtype codes:  . . . . . . . . . . . . . .   5
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   6
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   6
     8.3.  URIs  . . . . . . . . . . . . . . . . . . . . . . . . . .   6
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   7

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 routing information base snapshots.

   The Advertisement of Multiple Paths in BGP [I-D.ietf-idr-add-paths]
   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
   [I-D.ietf-idr-add-paths].

2.  Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

Petrie & King            Expires January 9, 2017                [Page 2]
Internet-Draft     Additional Paths Extensions in MRT          July 2016

3.  Rationale

   MRT parsers are usually stateless.  In order to parse BGP messages
   which contain data structures that depend on the capabilities
   negotiated during the BGP session setup, the so-called MRT subtypes
   are utilized.  The Advertisement of Multiple Path
   [I-D.ietf-idr-add-paths] extension for BGP alters the encoding of the
   BGP NLRI format for withdraws and announcements.  Therefore new
Show full document text