The IESG has approved the following document: - 'Deprecation of AS_SET and AS_CONFED_SET in BGP' (draft-ietf-idr-deprecate-as-set-confed-set-18.txt) as Proposed Standard
This document is the product of the Inter-Domain Routing Working Group. The IESG contact persons are Gunter Van de Velde, Jim Guichard and John Scudder. A URL of this Internet-Draft is: https://datatracker.ietf.org/doc/draft-ietf-idr-deprecate-as-set-confed-set/ Technical Summary 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. Working Group Summary Per the shepherd writeup, WG consensus was good. Document Quality It should be noted that this document is the final step of a long-running process to deprecate AS_SETs, dating back to before 2011 when RFC 6472 ("Recommendation for Not Using AS_SET and AS_CONFED_SET in BGP") was published as a BCP. Personnel The Document Shepherd for this document is Susan Hares. The Responsible Area Director is John Scudder. _______________________________________________ IETF-Announce mailing list -- [email protected] To unsubscribe send an email to [email protected]
