<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-idr-bgp4-rfc4271bis" target="https://datatracker.ietf.org/doc/html/draft-ietf-idr-bgp4-rfc4271bis-01">
   <front>
      <title>A Border Gateway Protocol 4 (BGP-4)</title>
      <author initials="Y." surname="Rekhter" fullname="Yakov Rekhter">
         <organization>Retired</organization>
      </author>
      <author initials="T." surname="Li" fullname="Tony Li">
         <organization>HPE</organization>
      </author>
      <author initials="S." surname="Hares" fullname="Susan Hares">
         <organization>Huawei</organization>
      </author>
      <author initials="J." surname="Scudder" fullname="John Scudder">
         <organization>HPE</organization>
      </author>
      <date month="July" day="6" year="2026" />
      <abstract>
	 <t>   This document discusses the Border Gateway Protocol (BGP), which is
   an inter-Autonomous System routing protocol.

   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.

   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 &quot;class&quot; within BGP.  BGP-4 also introduces
   mechanisms that allow aggregation of routes, including aggregation of
   AS paths.

   This document obsoletes RFC 4271.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-idr-bgp4-rfc4271bis-01" />
   
</reference>
