%% You should probably cite draft-ietf-idr-deprecate-as-set-confed-set-12 instead of this revision. @techreport{ietf-idr-deprecate-as-set-confed-set-05, number = {draft-ietf-idr-deprecate-as-set-confed-set-05}, 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/05/}, author = {Warren "Ace" Kumari and Kotikalapudi Sriram and Lilia Hannachi and Jeffrey Haas}, title = {{Deprecation of AS\_SET and AS\_CONFED\_SET in BGP}}, pagetotal = 7, year = , month = , day = , abstract = {BCP 172 (i.e., RFC 6472) recommends not using AS\_SET and AS\_CONFED\_SET in the Border Gateway Protocol. This document advances this recommendation to a standards requirement in BGP; it proscribes the use of the AS\_SET and AS\_CONFED\_SET types of path segments 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 route clearer. This will also simplify the design, implementation, and deployment of various BGP security mechanisms. This document (if approved) updates RFC 4271 and RFC 5065 by eliminating AS\_SET and AS\_CONFED\_SET types, and obsoletes RFC 6472.}, }