<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-idr-deprecate-as-set-confed-set" target="https://datatracker.ietf.org/doc/html/draft-ietf-idr-deprecate-as-set-confed-set-18">
   <front>
      <title>Deprecation of AS_SET and AS_CONFED_SET in BGP</title>
      <author initials="W." surname="Kumari" fullname="Warren Kumari">
         <organization>Google, Inc.</organization>
      </author>
      <author initials="K." surname="Sriram" fullname="Kotikalapudi Sriram">
         <organization>USA NIST</organization>
      </author>
      <author initials="L." surname="Hannachi" fullname="Lilia Hannachi">
         <organization>USA NIST</organization>
      </author>
      <author initials="J." surname="Haas" fullname="Jeffrey Haas">
         <organization>Juniper Networks, Inc.</organization>
      </author>
      <date month="March" day="7" year="2025" />
      <abstract>
	 <t>   BCP 172 (i.e., RFC 6472) recommends not using AS_SET and
   AS_CONFED_SET AS_PATH segment types in the Border Gateway Protocol
   (BGP).  This document advances that recommendation to a standards
   requirement in BGP; it prohibits the use of the AS_SET and
   AS_CONFED_SET path segment types in the AS_PATH.  This is done to
   simplify the design and implementation of BGP and to make the
   semantics of the originator of a BGP route clearer.  This will also
   simplify the design, implementation, and deployment of various BGP
   security mechanisms.  This document updates RFC 4271 by deprecating
   the origination of BGP routes with AS_SET (Type 1 AS_PATH segment)
   and updates RFC 5065 by deprecating the origination of BGP routes
   with AS_CONFED_SET (Type 4 AS_PATH segment).  Finally, it obsoletes
   RFC 6472.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-idr-deprecate-as-set-confed-set-18" />
   
</reference>
