%% You should probably cite rfc9774 instead of this I-D.
@techreport{ietf-idr-deprecate-as-set-confed-set-18,
    number =    {draft-ietf-idr-deprecate-as-set-confed-set-18},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-ietf-idr-deprecate-as-set-confed-set/18/},
    author =    {Warren Kumari and Kotikalapudi Sriram and Lilia Hannachi and Jeffrey Haas},
    title =     {{Deprecation of AS\_SET and AS\_CONFED\_SET in BGP}},
    pagetotal = 15,
    year =      2025,
    month =     mar,
    day =       7,
    abstract =  {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.},
}