<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-idr-nhc" target="https://datatracker.ietf.org/doc/html/draft-ietf-idr-nhc-07">
   <front>
      <title>BGP Next Hop Dependent Characteristics Attribute</title>
      <author initials="B." surname="Decraene" fullname="Bruno Decraene">
         <organization>Orange</organization>
      </author>
      <author initials="K." surname="Kompella" fullname="Kireeti Kompella">
         <organization>HPE</organization>
      </author>
      <author initials="S." surname="Krier" fullname="Serge Krier">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="M. R." surname="Satya" fullname="SATYA R MOHANTY">
         <organization>Zscaler</organization>
      </author>
      <author initials="J." surname="Scudder" fullname="John Scudder">
         <organization>HPE</organization>
      </author>
      <author initials="K." surname="Wang" fullname="Kevin Wang">
         <organization>HPE</organization>
      </author>
      <author initials="B." surname="Wen" fullname="Bin Wen">
         <organization>Comcast</organization>
      </author>
      <date month="June" day="4" year="2026" />
      <abstract>
	 <t>   RFC 5492 allows a BGP speaker to advertise its capabilities to a
   peer.  When a route is propagated beyond the immediate peer, it is
   useful to allow certain characteristics to be conveyed further.  In
   particular, it is useful to advertise forwarding plane features.

   This specification defines a BGP transitive attribute to carry such
   information, the &quot;Next Hop Dependent Characteristics Attribute,&quot; or
   NHC.  Unlike the capabilities defined by RFC 5492, the
   characteristics conveyed in the NHC apply solely to the routes
   advertised by the BGP UPDATE that contains the particular NHC.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-idr-nhc-07" />
   
</reference>
