Advertisement of Multiple Paths in BGP
draft-ietf-idr-add-paths-13

Document Type Active Internet-Draft (idr WG)
Last updated 2016-04-29 (latest revision 2015-12-11)
Replaces draft-walton-bgp-add-paths
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Stream WG state Submitted to IESG for Publication Jun 2015
Revised I-D Needed - Issue raised by WGLC, Revised I-D Needed - Issue raised by IESG
Document shepherd Russ White
Shepherd write-up Show (last changed 2016-03-25)
IESG IESG state IESG Evaluation::Revised I-D Needed
Consensus Yes
Telechat date On agenda of 2016-05-05 IESG telechat
Needs 9 more YES or NO OBJECTION positions to pass.
Responsible AD Alia Atlas
Send notices to (None)
IANA IANA review state IANA OK - Actions Needed
IANA action state None
Network Working Group                                          D. Walton
Internet-Draft                                          Cumulus Networks
Intended status: Standards Track                               A. Retana
Expires: June 13, 2016                                           E. Chen
                                                     Cisco Systems, Inc.
                                                              J. Scudder
                                                        Juniper Networks
                                                       December 11, 2015

                 Advertisement of Multiple Paths in BGP
                      draft-ietf-idr-add-paths-13

Abstract

   This document defines a BGP extension that allows the advertisement
   of multiple paths for the same address prefix without the new paths
   implicitly replacing any previous ones.  The essence of the extension
   is that each path is identified by a path identifier in addition to
   the address prefix.

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 June 13, 2016.

Copyright Notice

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

Walton, et al.            Expires June 13, 2016                 [Page 1]
Internet-Draft                  ADD-PATH                   December 2015

   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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Specification of Requirements . . . . . . . . . . . . . .   2
   2.  How to Identify a Path  . . . . . . . . . . . . . . . . . . .   3
   3.  Extended NLRI Encodings . . . . . . . . . . . . . . . . . . .   3
   4.  ADD-PATH Capability . . . . . . . . . . . . . . . . . . . . .   3
   5.  Operation . . . . . . . . . . . . . . . . . . . . . . . . . .   4
   6.  Applications  . . . . . . . . . . . . . . . . . . . . . . . .   5
   7.  Deployment Considerations . . . . . . . . . . . . . . . . . .   5
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   6
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     11.1.  Normative References . . . . . . . . . . . . . . . . . .   6
     11.2.  Informative References . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   The BGP specification [RFC4271] defines an Update-Send Process to
   advertise the routes chosen by the Decision Process to other BGP
   speakers.  No provisions are made to allow the advertisement of
   multiple paths for the same address prefix, or Network Layer
   Reachability Information (NLRI).  In fact, a route with the same NLRI
   as a previously advertised route implicitly replaces the previous
   advertisement.

   This document defines a BGP extension that allows the advertisement
   of multiple paths for the same address prefix without the new paths
   implicitly replacing any previous ones.  The essence of the extension
   is that each path is identified by a path identifier in addition to
   the address prefix.

1.1.  Specification of Requirements

   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 [RFC2119].
Show full document text