<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.haas-idr-path-attribute-filtering" target="https://datatracker.ietf.org/doc/html/draft-haas-idr-path-attribute-filtering-02">
   <front>
      <title>BGP-4 Path Attribute Filtering Capability</title>
      <author initials="J." surname="Haas" fullname="Jeffrey Haas">
         <organization>HPE</organization>
      </author>
      <author initials="J." surname="Scudder" fullname="John Scudder">
         <organization>HPE</organization>
      </author>
      <date month="August" day="20" year="2025" />
      <abstract>
	 <t>   Path Attributes in the BGP-4 protocol (RFC 4271) carry data
   associated with BGP routes.  Many of the Path Attributes carried in
   BGP are intended for limited scope deployment.  However, the
   extension mechanism defined by BGP that carries these attributes
   often carries them farther than necessary, sometimes with unfortunate
   results.

   This document defines a mechanism using BGP Capabilities (RFC 5492)
   that permits eBGP speakers to determine what Path Attributes should
   be permitted to cross external BGP routing boundaries.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-haas-idr-path-attribute-filtering-02" />
   
</reference>
