Hi all, We (authors) recently published an updated version of "Deprecation of AS_SET and AS_CONFED_SET..." draft: https://datatracker.ietf.org/doc/html/draft-ietf-idr-deprecate-as-set-confed-set-10
Please give it a read and let us know if you have some comments before we go to WGLC. The following two paragraphs (Section 3, Recommendations) are kind of central to the document: "BGP speakers conforming to this document (i.e., conformant BGP speakers) SHOULD NOT locally generate BGP UPDATE messages containing AS_SETs or AS_CONFED_SETs. Conformant BGP speakers SHOULD NOT send BGP UPDATE messages containing AS_SETs or AS_CONFED_SETs. Upon receipt of such messages, conformant BGP speakers SHOULD use the "treat-as-withdraw" error handling behavior as per [RFC7606]." "The document uses normative language such as "SHOULD NOT send" rather than "MUST NOT send" with the intention of allowing some transition time for existing implementations and avoiding abrupt disruptions for the operators currently using AS_SETs or AS_CONFED_SETs. However, it is strongly urged that operators stop sending UPDATEs with AS_SETs or AS_CONFED_SETs as quickly as possible to avoid having UPDATEs dropped by BGP security mechanisms such as RPKI-ROV and BGPsec." We have added new Appendices A and B which describe how to avoid data plane loops while performing "brief" aggregation and how to avoid origin AS ambiguity for creating a ROA for the aggregate. Included are changes to how brief aggregation is performed. Please let us also know if you would have interest in providing an implementation. Thank you. Sriram _______________________________________________ GROW mailing list GROW@ietf.org https://www.ietf.org/mailman/listinfo/grow
