<?xml version='1.0' encoding='utf-8'?>
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" version="3" category="std" consensus="true" docName="draft-ietf-idr-add-paths" indexInclude="true" ipr="trust200902" number="7911" prepTime="2023-01-17T08:47:10" scripts="Common,Latin" sortRefs="true" submissionType="IETF" symRefs="true" tocDepth="3" tocInclude="true" xml:lang="en">
  <link href="https://dx.doi.org/10.17487/rfc7911" rel="alternate"/>
  <link href="urn:issn:2070-1721" rel="alternate"/>
  <link href="https://datatracker.ietf.org/doc/draft-ietf-idr-add-paths" rel="prev"/>
  
  
  <front>
    <title abbrev="ADD-PATH">Advertisement of Multiple Paths in BGP</title>
    <seriesInfo name="RFC" value="7911" stream="IETF"/>
    <author fullname="Daniel Walton" initials="D." surname="Walton">
      <organization abbrev="Cumulus Networks" showOnFrontPage="true">Cumulus Networks</organization>
      <address>
        <postal>
          <street>185 E. Dana Street</street>
          <city>Mountain View</city>
          <region>CA</region>
          <code>94041</code>
          <country>United States of America</country>
        </postal>
        <email>dwalton@cumulusnetworks.com</email>
      </address>
    </author>
    <author fullname="Alvaro Retana" initials="A." surname="Retana">
      <organization showOnFrontPage="true">Cisco Systems, Inc.</organization>
      <address>
        <postal>
          <street>Kit Creek Rd.</street>
          <city>Research Triangle Park</city>
          <region>NC</region>
          <code>27709</code>
          <country>United States of America</country>
        </postal>
        <email>aretana@cisco.com</email>
      </address>
    </author>
    <author fullname="Enke Chen" initials="E." surname="Chen">
      <organization showOnFrontPage="true">Cisco Systems, Inc.</organization>
      <address>
        <postal>
          <street>170 W. Tasman Dr.</street>
          <city>San Jose</city>
          <region>CA</region>
          <code>95134</code>
          <country>United States of America</country>
        </postal>
        <email>enkechen@cisco.com</email>
      </address>
    </author>
    <author fullname="John Scudder" initials="J." surname="Scudder">
      <organization abbrev="Juniper Networks" showOnFrontPage="true">Juniper Networks</organization>
      <address>
        <postal>
          <street>1194 N. Mathilda Ave</street>
          <city>Sunnyvale</city>
          <region>CA</region>
          <code>94089</code>
          <country>United States of America</country>
        </postal>
        <email>jgs@juniper.net</email>
      </address>
    </author>
    <date month="07" year="2016"/>
    <abstract pn="section-abstract">
      <t indent="0" pn="section-abstract-1">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.</t>
    </abstract>
    <boilerplate>
      <section anchor="status-of-memo" numbered="false" removeInRFC="false" toc="exclude" pn="section-boilerplate.1">
        <name slugifiedName="name-status-of-this-memo">Status of This Memo</name>
        <t indent="0" pn="section-boilerplate.1-1">
            This is an Internet Standards Track document.
        </t>
        <t indent="0" pn="section-boilerplate.1-2">
            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.
        </t>
        <t indent="0" pn="section-boilerplate.1-3">
            Information about the current status of this document, any
            errata, and how to provide feedback on it may be obtained at
            <eref target="http://www.rfc-editor.org/info/rfc7911" brackets="none"/>.
        </t>
      </section>
      <section anchor="copyright" numbered="false" removeInRFC="false" toc="exclude" pn="section-boilerplate.2">
        <name slugifiedName="name-copyright-notice">Copyright Notice</name>
        <t indent="0" pn="section-boilerplate.2-1">
            Copyright (c) 2016 IETF Trust and the persons identified as the
            document authors. All rights reserved.
        </t>
        <t indent="0" pn="section-boilerplate.2-2">
            This document is subject to BCP 78 and the IETF Trust's Legal
            Provisions Relating to IETF Documents
            (<eref target="http://trustee.ietf.org/license-info" brackets="none"/>) 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 Revised BSD License text as described in
            Section 4.e of the Trust Legal Provisions and are provided without
            warranty as described in the Revised BSD License.
        </t>
      </section>
    </boilerplate>
    <toc>
      <section anchor="toc" numbered="false" removeInRFC="false" toc="exclude" pn="section-toc.1">
        <name slugifiedName="name-table-of-contents">Table of Contents</name>
        <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1">
          <li pn="section-toc.1-1.1">
            <t indent="0" keepWithNext="true" pn="section-toc.1-1.1.1"><xref derivedContent="1" format="counter" sectionFormat="of" target="section-1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-introduction">Introduction</xref></t>
            <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.1.2">
              <li pn="section-toc.1-1.1.2.1">
                <t indent="0" keepWithNext="true" pn="section-toc.1-1.1.2.1.1"><xref derivedContent="1.1" format="counter" sectionFormat="of" target="section-1.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-specification-of-requiremen">Specification of Requirements</xref></t>
              </li>
            </ul>
          </li>
          <li pn="section-toc.1-1.2">
            <t indent="0" keepWithNext="true" pn="section-toc.1-1.2.1"><xref derivedContent="2" format="counter" sectionFormat="of" target="section-2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-how-to-identify-a-path">How to Identify a Path</xref></t>
          </li>
          <li pn="section-toc.1-1.3">
            <t indent="0" pn="section-toc.1-1.3.1"><xref derivedContent="3" format="counter" sectionFormat="of" target="section-3"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-extended-nlri-encodings">Extended NLRI Encodings</xref></t>
          </li>
          <li pn="section-toc.1-1.4">
            <t indent="0" pn="section-toc.1-1.4.1"><xref derivedContent="4" format="counter" sectionFormat="of" target="section-4"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-add-path-capability">ADD-PATH Capability</xref></t>
          </li>
          <li pn="section-toc.1-1.5">
            <t indent="0" pn="section-toc.1-1.5.1"><xref derivedContent="5" format="counter" sectionFormat="of" target="section-5"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-operation">Operation</xref></t>
          </li>
          <li pn="section-toc.1-1.6">
            <t indent="0" pn="section-toc.1-1.6.1"><xref derivedContent="6" format="counter" sectionFormat="of" target="section-6"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-deployment-considerations">Deployment Considerations</xref></t>
          </li>
          <li pn="section-toc.1-1.7">
            <t indent="0" pn="section-toc.1-1.7.1"><xref derivedContent="7" format="counter" sectionFormat="of" target="section-7"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-iana-considerations">IANA Considerations</xref></t>
          </li>
          <li pn="section-toc.1-1.8">
            <t indent="0" pn="section-toc.1-1.8.1"><xref derivedContent="8" format="counter" sectionFormat="of" target="section-8"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-security-considerations">Security Considerations</xref></t>
          </li>
          <li pn="section-toc.1-1.9">
            <t indent="0" pn="section-toc.1-1.9.1"><xref derivedContent="9" format="counter" sectionFormat="of" target="section-9"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-references">References</xref></t>
            <ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.9.2">
              <li pn="section-toc.1-1.9.2.1">
                <t indent="0" pn="section-toc.1-1.9.2.1.1"><xref derivedContent="9.1" format="counter" sectionFormat="of" target="section-9.1"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-normative-references">Normative References</xref></t>
              </li>
              <li pn="section-toc.1-1.9.2.2">
                <t indent="0" pn="section-toc.1-1.9.2.2.1"><xref derivedContent="9.2" format="counter" sectionFormat="of" target="section-9.2"/>.  <xref derivedContent="" format="title" sectionFormat="of" target="name-informative-references">Informative References</xref></t>
              </li>
            </ul>
          </li>
          <li pn="section-toc.1-1.10">
            <t indent="0" pn="section-toc.1-1.10.1"><xref derivedContent="" format="none" sectionFormat="of" target="section-appendix.a"/><xref derivedContent="" format="title" sectionFormat="of" target="name-acknowledgments">Acknowledgments</xref></t>
          </li>
          <li pn="section-toc.1-1.11">
            <t indent="0" pn="section-toc.1-1.11.1"><xref derivedContent="" format="none" sectionFormat="of" target="section-appendix.b"/><xref derivedContent="" format="title" sectionFormat="of" target="name-authors-addresses">Authors' Addresses</xref></t>
          </li>
        </ul>
      </section>
    </toc>
  </front>
  <middle>
    <section numbered="true" toc="include" removeInRFC="false" pn="section-1">
      <name slugifiedName="name-introduction">Introduction</name>
      <t indent="0" pn="section-1-1">The BGP specification <xref format="default" target="RFC4271" sectionFormat="of" derivedContent="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.</t>
      <t indent="0" pn="section-1-2">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.</t>
      <t indent="0" pn="section-1-3">The availability of the additional paths can help reduce or eliminate
      persistent route oscillations <xref format="default" target="RFC3345" sectionFormat="of" derivedContent="RFC3345"/>.  It can also help with optimal routing and routing 
      convergence in a network by providing potential alternate or backup paths, 
      respectively.</t>
      <section numbered="true" toc="include" removeInRFC="false" pn="section-1.1">
        <name slugifiedName="name-specification-of-requiremen">Specification of Requirements</name>
        <t indent="0" pn="section-1.1-1">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 <xref format="default" target="RFC2119" sectionFormat="of" derivedContent="RFC2119"/>.</t>
      </section>
    </section>
    <section numbered="true" toc="include" removeInRFC="false" pn="section-2">
      <name slugifiedName="name-how-to-identify-a-path">How to Identify a Path</name>
      <t indent="0" pn="section-2-1">As defined in <xref format="default" target="RFC4271" sectionFormat="of" derivedContent="RFC4271"/>, a path refers to the information reported in the
      Path Attribute field of an UPDATE message. As the procedures specified
      in <xref format="default" target="RFC4271" sectionFormat="of" derivedContent="RFC4271"/> allow only
      the advertisement of one path for a particular address prefix, a path
      for an address prefix from a BGP peer can be keyed on the address
      prefix.</t>
      <t indent="0" pn="section-2-2">In order for a BGP speaker to advertise multiple paths for the same
      address prefix, a new identifier (termed "Path Identifier" hereafter)
      needs to be introduced so that a particular path for an address prefix
      can be identified by the combination of the address prefix and the Path
      Identifier.</t>
      <t indent="0" pn="section-2-3">The assignment of the Path Identifier for a path by a BGP speaker is
      purely a local matter. However, the Path Identifier MUST be assigned in
      such a way that the BGP speaker is able to use the (Prefix, Path
      Identifier) to uniquely identify a path advertised to a neighbor. A BGP
      speaker that re-advertises a route MUST generate its own Path Identifier
      to be associated with the re-advertised route. A BGP speaker that
      receives a route should not assume that the identifier carries any
      particular semantics.</t>
    </section>
    <section anchor="code" numbered="true" toc="include" removeInRFC="false" pn="section-3">
      <name slugifiedName="name-extended-nlri-encodings">Extended NLRI Encodings</name>
      <t indent="0" pn="section-3-1">In order to carry the Path Identifier in an UPDATE message, the NLRI
      encoding MUST be extended by prepending the Path Identifier field, which
      is of four octets.</t>
      <t indent="0" pn="section-3-2">For example, the NLRI encoding specified in <xref format="default" target="RFC4271" sectionFormat="of" derivedContent="RFC4271"/> is extended as the following:</t>
      <artwork name="" type="" align="left" alt="" pn="section-3-3"><![CDATA[
               +--------------------------------+
               | Path Identifier (4 octets)     |
               +--------------------------------+
               | Length (1 octet)               |
               +--------------------------------+
               | Prefix (variable)              |
               +--------------------------------+]]></artwork>
      <t indent="0" pn="section-3-4">The usage of the extended NLRI encodings is specified in <xref target="ops" format="default" sectionFormat="of" derivedContent="Section 5"/>.</t>
    </section>
    <section anchor="capa" numbered="true" toc="include" removeInRFC="false" pn="section-4">
      <name slugifiedName="name-add-path-capability">ADD-PATH Capability</name>
      <t indent="0" pn="section-4-1">The ADD-PATH Capability is a BGP capability <xref format="default" target="RFC5492" sectionFormat="of" derivedContent="RFC5492"/>, with Capability Code
      69. The Capability Length field of this capability is
      variable. The Capability Value field consists of one or more of the
      following tuples:</t>
      <artwork name="" type="" align="left" alt="" pn="section-4-2"><![CDATA[
             +------------------------------------------------+
             | Address Family Identifier (2 octets)           |
             +------------------------------------------------+
             | Subsequent Address Family Identifier (1 octet) |
             +------------------------------------------------+
             | Send/Receive (1 octet)                         |
             +------------------------------------------------+]]></artwork>
      <t indent="0" pn="section-4-3">The meaning and use of the fields are as follows: </t>
      <ul empty="true" spacing="normal" bare="false" indent="3" pn="section-4-4">
        <li pn="section-4-4.1">
          <t indent="0" pn="section-4-4.1.1">Address Family Identifier (AFI): </t>
          <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-4-4.1.2">
            <li pn="section-4-4.1.2.1">This field is the same as the one used in <xref format="default" target="RFC4760" sectionFormat="of" derivedContent="RFC4760"/>.</li>
          </ul>
        </li>
        <li pn="section-4-4.2">
          <t indent="0" pn="section-4-4.2.1">Subsequent Address Family Identifier (SAFI): </t>
          <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-4-4.2.2">
            <li pn="section-4-4.2.2.1">This field is the same as the one used in <xref format="default" target="RFC4760" sectionFormat="of" derivedContent="RFC4760"/>.</li>
          </ul>
        </li>
        <li pn="section-4-4.3">
          <t indent="0" pn="section-4-4.3.1">Send/Receive: </t>
          <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-4-4.3.2">
            <li pn="section-4-4.3.2.1">This field indicates whether the sender is (a) able to
              receive multiple paths from its peer (value 1), (b) able to send
              multiple paths to its peer (value 2), or (c) both (value 3) for
              the &lt;AFI, SAFI&gt;.</li>
            <li pn="section-4-4.3.2.2">If any other value is received, then the capability SHOULD be
              treated as not understood and ignored <xref format="default" target="RFC5492" sectionFormat="of" derivedContent="RFC5492"/>.</li>
          </ul>
        </li>
      </ul>
      <t indent="0" pn="section-4-5">A BGP speaker that wishes to indicate support for multiple
      AFI/SAFIs MUST do so by including the information in a single instance of
      the ADD-PATH Capability.</t>
    </section>
    <section anchor="ops" numbered="true" toc="include" removeInRFC="false" pn="section-5">
      <name slugifiedName="name-operation">Operation</name>
      <t indent="0" pn="section-5-1">The Path Identifier specified in <xref target="code" format="default" sectionFormat="of" derivedContent="Section 3"/> can be used to
      advertise multiple paths for the same address prefix without subsequent
      advertisements replacing the previous ones. Apart from the fact that
      this is now possible, the route advertisement rules of <xref format="default" target="RFC4271" sectionFormat="of" derivedContent="RFC4271"/> are not changed. In
      particular, a new advertisement for a given address prefix and a given
      Path Identifier replaces a previous advertisement for the same address
      prefix and Path Identifier. If a BGP speaker receives a message to
      withdraw a prefix with a Path Identifier not seen before, it SHOULD
      silently ignore it.</t>
      <t indent="0" pn="section-5-2">For a BGP speaker to be able to send multiple paths to its peer, that
      BGP speaker MUST advertise the ADD-PATH Capability with the Send/Receive
      field set to either 2 or 3, and MUST receive from its peer the ADD-PATH
      Capability with the Send/Receive field set to either 1 or 3, for the
      corresponding &lt;AFI, SAFI&gt;.</t>
      <t indent="0" pn="section-5-3">A BGP speaker MUST follow the procedures defined in <xref format="default" target="RFC4271" sectionFormat="of" derivedContent="RFC4271"/> when generating an
      UPDATE message for a particular &lt;AFI, SAFI&gt; to a peer unless the
      BGP speaker advertises the ADD-PATH Capability to the peer indicating
      its ability to send multiple paths for the &lt;AFI, SAFI&gt;, and also
      receives the ADD-PATH Capability from the peer indicating its ability to
      receive multiple paths for the &lt;AFI, SAFI&gt;, in which case the
      speaker MUST generate a route update for the &lt;AFI, SAFI&gt; based on
      the combination of the address prefix and the Path Identifier, and use
      the extended NLRI encodings specified in this document. The peer SHALL
      act accordingly in processing an UPDATE message related to a particular
      &lt;AFI, SAFI&gt;.</t>
      <t indent="0" pn="section-5-4">A BGP speaker SHOULD include the best route <xref format="default" target="RFC4271" sectionFormat="of" derivedContent="RFC4271"/> when more than one path is
      advertised to a neighbor, unless it is a path received from
      that neighbor.</t>
      <t indent="0" pn="section-5-5">As the Path Identifiers are locally assigned, and may or may not be
      persistent across a control plane restart of a BGP speaker, an
      implementation SHOULD take special care so that the underlying
      forwarding plane of a "Receiving Speaker" as described in <xref format="default" target="RFC4724" sectionFormat="of" derivedContent="RFC4724"/> is not affected
      during the graceful restart of a BGP session.</t>
    </section>
    <section numbered="true" toc="include" removeInRFC="false" pn="section-6">
      <name slugifiedName="name-deployment-considerations">Deployment Considerations</name>
      <t indent="0" pn="section-6-1">The extension proposed in this document provides a mechanism for a
      BGP speaker to advertise multiple paths over a BGP session. Care needs
      to be taken in its deployment to ensure consistent routing and
      forwarding in a network <xref format="default" target="ADDPATH" sectionFormat="of" derivedContent="ADDPATH"/>.</t>
      <t indent="0" pn="section-6-2">The only explicit indication that the encoding described in <xref target="code" format="default" sectionFormat="of" derivedContent="Section 3"/>
      is in use in a particular BGP session is the exchange of Capabilities
      described in <xref target="capa" format="default" sectionFormat="of" derivedContent="Section 4"/>.  If the exchange is successful <xref format="default" target="RFC5492" sectionFormat="of" derivedContent="RFC5492"/>, then the BGP speakers
      will be able to process all BGP UPDATES properly, as described in <xref target="ops" format="default" sectionFormat="of" derivedContent="Section 5"/>.
      However, if, for example, a packet analyzer is used on the wire to examine 
      an active BGP session, it may not be able to properly decode the BGP UPDATES
      because it lacks prior knowledge of the exchanged Capabilities.</t>
      <t indent="0" pn="section-6-3">When deployed as a provider edge router or a peering router that
      interacts with external neighbors, a BGP speaker usually advertises at
      most one path to the internal neighbors in a network. In the case where the
      speaker is configured to advertise multiple paths to the internal
      neighbors, and additional information is needed for the application, the
      speaker could use attributes such as the Edge_Discriminator attribute
      <xref format="default" target="FAST" sectionFormat="of" derivedContent="FAST"/>. The use of that type of
      additional information is outside the scope of this document.</t>
    </section>
    <section numbered="true" toc="include" removeInRFC="false" pn="section-7">
      <name slugifiedName="name-iana-considerations">IANA Considerations</name>
      <t indent="0" pn="section-7-1">IANA has assigned the value 69 for the ADD-PATH Capability
      described in this document. This registration is in the "Capability
      Codes" registry.</t>
    </section>
    <section numbered="true" toc="include" removeInRFC="false" pn="section-8">
      <name slugifiedName="name-security-considerations">Security Considerations</name>
      <t indent="0" pn="section-8-1">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. As a result, multiple paths for
      a large number of prefixes may be received by a BGP speaker, potentially
      depleting memory resources or even causing network-wide instability, which
      can be considered a denial-of-service attack.  Note that this is not a new
      vulnerability, but one that is present in the base BGP specification <xref format="default" target="RFC4272" sectionFormat="of" derivedContent="RFC4272"/>.</t>
      <t indent="0" pn="section-8-2">
  The use of the ADD-PATH Capability is intended to address specific
  needs related to, for example, <xref target="STOP-OSC" format="default" sectionFormat="of" derivedContent="STOP-OSC">eliminating route oscillations that
  were induced by the MULTI_EXIT_DISC (MED) attribute</xref>.

  While describing the applications for the
      ADD-PATH Capability is outside the scope of this document, users
      are encouraged to examine their behavior and potential impact by
      studying the best practices described in <xref format="default" target="ADDPATH" sectionFormat="of" derivedContent="ADDPATH"/>.</t>
      <t indent="0" pn="section-8-3">Security concerns in the base operation of <xref format="default" target="RFC4271" sectionFormat="of" derivedContent="RFC4271">BGP</xref> also apply.</t>
    </section>
  </middle>
  <back>
    <references pn="section-9">
      <name slugifiedName="name-references">References</name>
      <references pn="section-9.1">
        <name slugifiedName="name-normative-references">Normative References</name>
        <reference anchor="RFC2119" target="https://www.rfc-editor.org/info/rfc2119" quoteTitle="true" derivedAnchor="RFC2119">
          <front>
            <title>Key words for use in RFCs to Indicate Requirement Levels</title>
            <author fullname="S. Bradner" initials="S." surname="Bradner"/>
            <date month="March" year="1997"/>
            <abstract>
              <t indent="0">In many standards track documents several words are used to signify the requirements in the specification.  These words are often capitalized.  This document defines these words as they should be interpreted in IETF documents.  This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="14"/>
          <seriesInfo name="RFC" value="2119"/>
          <seriesInfo name="DOI" value="10.17487/RFC2119"/>
        </reference>
        <reference anchor="RFC4271" target="https://www.rfc-editor.org/info/rfc4271" quoteTitle="true" derivedAnchor="RFC4271">
          <front>
            <title>A Border Gateway Protocol 4 (BGP-4)</title>
            <author fullname="Y. Rekhter" initials="Y." role="editor" surname="Rekhter"/>
            <author fullname="T. Li" initials="T." role="editor" surname="Li"/>
            <author fullname="S. Hares" initials="S." role="editor" surname="Hares"/>
            <date month="January" year="2006"/>
            <abstract>
              <t indent="0">This document discusses the Border Gateway Protocol (BGP), which is an inter-Autonomous System routing protocol.</t>
              <t indent="0">The primary function of a BGP speaking system is to exchange network reachability information with other BGP systems. This network reachability information includes information on the list of Autonomous Systems (ASes) that reachability information traverses. This information is sufficient for constructing a graph of AS connectivity for this reachability from which routing loops may be pruned, and, at the AS level, some policy decisions may be enforced.</t>
              <t indent="0">BGP-4 provides a set of mechanisms for supporting Classless Inter-Domain Routing (CIDR). These mechanisms include support for advertising a set of destinations as an IP prefix, and eliminating the concept of network "class" within BGP. BGP-4 also introduces mechanisms that allow aggregation of routes, including aggregation of AS paths.</t>
              <t indent="0">This document obsoletes RFC 1771. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="4271"/>
          <seriesInfo name="DOI" value="10.17487/RFC4271"/>
        </reference>
        <reference anchor="RFC4760" target="https://www.rfc-editor.org/info/rfc4760" quoteTitle="true" derivedAnchor="RFC4760">
          <front>
            <title>Multiprotocol Extensions for BGP-4</title>
            <author fullname="T. Bates" initials="T." surname="Bates"/>
            <author fullname="R. Chandra" initials="R." surname="Chandra"/>
            <author fullname="D. Katz" initials="D." surname="Katz"/>
            <author fullname="Y. Rekhter" initials="Y." surname="Rekhter"/>
            <date month="January" year="2007"/>
            <abstract>
              <t indent="0">This document defines extensions to BGP-4 to enable it to carry routing information for multiple Network Layer protocols (e.g., IPv6, IPX, L3VPN, etc.).  The extensions are backward compatible - a router that supports the extensions can interoperate with a router that doesn't support the extensions. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="4760"/>
          <seriesInfo name="DOI" value="10.17487/RFC4760"/>
        </reference>
        <reference anchor="RFC5492" target="https://www.rfc-editor.org/info/rfc5492" quoteTitle="true" derivedAnchor="RFC5492">
          <front>
            <title>Capabilities Advertisement with BGP-4</title>
            <author fullname="J. Scudder" initials="J." surname="Scudder"/>
            <author fullname="R. Chandra" initials="R." surname="Chandra"/>
            <date month="February" year="2009"/>
            <abstract>
              <t indent="0">This document defines an Optional Parameter, called Capabilities, that is expected to facilitate the introduction of new capabilities in the Border Gateway Protocol (BGP) by providing graceful capability advertisement without requiring that BGP peering be terminated.</t>
              <t indent="0">This document obsoletes RFC 3392. [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="5492"/>
          <seriesInfo name="DOI" value="10.17487/RFC5492"/>
        </reference>
      </references>
      <references pn="section-9.2">
        <name slugifiedName="name-informative-references">Informative References</name>
        <reference anchor="ADDPATH" quoteTitle="true" derivedAnchor="ADDPATH">
          <front>
            <title>Best Practices for Advertisement of Multiple Paths in IBGP</title>
            <author initials="J" surname="Uttaro" fullname="Jim Uttaro">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="P" surname="Francois" fullname="Pierre Francois">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="K" surname="Patel" fullname="Keyur Patel">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="J" surname="Haas" fullname="Jeffrey Haas">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="A" surname="Simpson" fullname="Adam Simpson">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="R" surname="Fragassi" fullname="Roberto Fragassi">
              <organization showOnFrontPage="true"/>
            </author>
            <date month="April" day="25" year="2016"/>
          </front>
          <seriesInfo name="Work in Progress," value="draft-ietf-idr-add-paths-guidelines-08"/>
        </reference>
        <reference anchor="FAST" quoteTitle="true" derivedAnchor="FAST">
          <front>
            <title>Fast Connectivity Restoration Using BGP Add-path</title>
            <author initials="P" surname="Mohapatra" fullname="Pradosh Mohapatra">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="R" surname="Fernando" fullname="Rex Fernando">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="C" surname="Filsfils" fullname="Clarence Filsfils">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="R" surname="Raszuk" fullname="Robert Raszuk">
              <organization showOnFrontPage="true"/>
            </author>
            <date month="January" day="22" year="2013"/>
          </front>
          <seriesInfo name="Work in Progress," value="draft-pmohapat-idr-fast-conn-restore-03"/>
        </reference>
        <reference anchor="RFC3345" target="https://www.rfc-editor.org/info/rfc3345" quoteTitle="true" derivedAnchor="RFC3345">
          <front>
            <title>Border Gateway Protocol (BGP) Persistent Route Oscillation Condition</title>
            <author fullname="D. McPherson" initials="D." surname="McPherson"/>
            <author fullname="V. Gill" initials="V." surname="Gill"/>
            <author fullname="D. Walton" initials="D." surname="Walton"/>
            <author fullname="A. Retana" initials="A." surname="Retana"/>
            <date month="August" year="2002"/>
          </front>
          <seriesInfo name="RFC" value="3345"/>
          <seriesInfo name="DOI" value="10.17487/RFC3345"/>
        </reference>
        <reference anchor="RFC4272" target="https://www.rfc-editor.org/info/rfc4272" quoteTitle="true" derivedAnchor="RFC4272">
          <front>
            <title>BGP Security Vulnerabilities Analysis</title>
            <author fullname="S. Murphy" initials="S." surname="Murphy"/>
            <date month="January" year="2006"/>
            <abstract>
              <t indent="0">Border Gateway Protocol 4 (BGP-4), along with a host of other infrastructure protocols designed before the Internet environment became perilous, was originally designed with little consideration for protection of the information it carries. There are no mechanisms internal to BGP that protect against attacks that modify, delete, forge, or replay data, any of which has the potential to disrupt overall network routing behavior.</t>
              <t indent="0">This document discusses some of the security issues with BGP routing data dissemination. This document does not discuss security issues with forwarding of packets. This memo provides information for the Internet community.</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="4272"/>
          <seriesInfo name="DOI" value="10.17487/RFC4272"/>
        </reference>
        <reference anchor="RFC4724" target="https://www.rfc-editor.org/info/rfc4724" quoteTitle="true" derivedAnchor="RFC4724">
          <front>
            <title>Graceful Restart Mechanism for BGP</title>
            <author fullname="S. Sangli" initials="S." surname="Sangli"/>
            <author fullname="E. Chen" initials="E." surname="Chen"/>
            <author fullname="R. Fernando" initials="R." surname="Fernando"/>
            <author fullname="J. Scudder" initials="J." surname="Scudder"/>
            <author fullname="Y. Rekhter" initials="Y." surname="Rekhter"/>
            <date month="January" year="2007"/>
            <abstract>
              <t indent="0">This document describes a mechanism for BGP that would help minimize the negative effects on routing caused by BGP restart. An End-of-RIB marker is specified and can be used to convey routing convergence information. A new BGP capability, termed "Graceful Restart Capability", is defined that would allow a BGP speaker to express its ability to preserve forwarding state during BGP restart. Finally, procedures are outlined for temporarily retaining routing information across a TCP session termination/re-establishment.</t>
              <t indent="0">The mechanisms described in this document are applicable to all routers, both those with the ability to preserve forwarding state during BGP restart and those without (although the latter need to implement only a subset of the mechanisms described in this document). [STANDARDS-TRACK]</t>
            </abstract>
          </front>
          <seriesInfo name="RFC" value="4724"/>
          <seriesInfo name="DOI" value="10.17487/RFC4724"/>
        </reference>
        <reference anchor="STOP-OSC" quoteTitle="true" derivedAnchor="STOP-OSC">
          <front>
            <title>BGP Persistent Route Oscillation Solutions</title>
            <author initials="D" surname="Walton" fullname="Daniel Walton">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="A" surname="Retana" fullname="Alvaro Retana">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="E" surname="Chen" fullname="Enke Chen">
              <organization showOnFrontPage="true"/>
            </author>
            <author initials="J" surname="Scudder" fullname="John Scudder">
              <organization showOnFrontPage="true"/>
            </author>
            <date month="April" day="30" year="2016"/>
          </front>
          <seriesInfo name="Work in Progress," value="draft-ietf-idr-route-oscillation-stop-03"/>
        </reference>
      </references>
    </references>
    <section numbered="false" toc="include" removeInRFC="false" pn="section-appendix.a">
      <name slugifiedName="name-acknowledgments">Acknowledgments</name>
      <t indent="0" pn="section-appendix.a-1">We would like to thank David Cook and Naiming Shen for their
      contributions to the design and development of the extension.</t>
      <t indent="0" pn="section-appendix.a-2">Many people have made valuable comments and suggestions, including
      Rex Fernando, Eugene Kim, Danny McPherson, Dave Meyer, Pradosh
      Mohapatra, Keyur Patel, Robert Raszuk, Eric Rosen, Srihari Sangli, Dan
      Tappan, Mark Turner, Jeff Haas, Jay Borkenhagen, Mach Chen, Denis Ovsienko,
      Carlos Pignataro, Meral Shirazipour, and Kathleen Moriarty.</t>
    </section>
    <section anchor="authors-addresses" numbered="false" removeInRFC="false" toc="include" pn="section-appendix.b">
      <name slugifiedName="name-authors-addresses">Authors' Addresses</name>
      <author fullname="Daniel Walton" initials="D." surname="Walton">
        <organization abbrev="Cumulus Networks" showOnFrontPage="true">Cumulus Networks</organization>
        <address>
          <postal>
            <street>185 E. Dana Street</street>
            <city>Mountain View</city>
            <region>CA</region>
            <code>94041</code>
            <country>United States of America</country>
          </postal>
          <email>dwalton@cumulusnetworks.com</email>
        </address>
      </author>
      <author fullname="Alvaro Retana" initials="A." surname="Retana">
        <organization showOnFrontPage="true">Cisco Systems, Inc.</organization>
        <address>
          <postal>
            <street>Kit Creek Rd.</street>
            <city>Research Triangle Park</city>
            <region>NC</region>
            <code>27709</code>
            <country>United States of America</country>
          </postal>
          <email>aretana@cisco.com</email>
        </address>
      </author>
      <author fullname="Enke Chen" initials="E." surname="Chen">
        <organization showOnFrontPage="true">Cisco Systems, Inc.</organization>
        <address>
          <postal>
            <street>170 W. Tasman Dr.</street>
            <city>San Jose</city>
            <region>CA</region>
            <code>95134</code>
            <country>United States of America</country>
          </postal>
          <email>enkechen@cisco.com</email>
        </address>
      </author>
      <author fullname="John Scudder" initials="J." surname="Scudder">
        <organization abbrev="Juniper Networks" showOnFrontPage="true">Juniper Networks</organization>
        <address>
          <postal>
            <street>1194 N. Mathilda Ave</street>
            <city>Sunnyvale</city>
            <region>CA</region>
            <code>94089</code>
            <country>United States of America</country>
          </postal>
          <email>jgs@juniper.net</email>
        </address>
      </author>
    </section>
  </back>
</rfc>
