| < draft-ietf-idr-deprecate-as-set-confed-set-05.txt | draft-ietf-idr-deprecate-as-set-confed-set-06.txt > | |||
|---|---|---|---|---|
| Network Working Group W. Kumari | Network Working Group W. Kumari | |||
| Internet-Draft Google, Inc. | Internet-Draft Google, Inc. | |||
| Obsoletes: 6472 (if approved) K. Sriram | Obsoletes: 6472 (if approved) K. Sriram | |||
| Updates: 4271 5065 (if approved) L. Hannachi | Updates: 4271 5065 (if approved) L. Hannachi | |||
| Intended status: Standards Track USA NIST | Intended status: Standards Track USA NIST | |||
| Expires: September 13, 2021 J. Haas | Expires: 16 March 2022 J. Haas | |||
| Juniper Networks, Inc. | Juniper Networks, Inc. | |||
| March 12, 2021 | 12 September 2021 | |||
| Deprecation of AS_SET and AS_CONFED_SET in BGP | Deprecation of AS_SET and AS_CONFED_SET in BGP | |||
| draft-ietf-idr-deprecate-as-set-confed-set-05 | draft-ietf-idr-deprecate-as-set-confed-set-06 | |||
| Abstract | Abstract | |||
| BCP 172 (i.e., RFC 6472) recommends not using AS_SET and | BCP 172 (i.e., RFC 6472) recommends not using AS_SET and | |||
| AS_CONFED_SET in the Border Gateway Protocol. This document advances | AS_CONFED_SET in the Border Gateway Protocol. This document advances | |||
| this recommendation to a standards requirement in BGP; it proscribes | 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 | 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 | 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. | BGP and to make the semantics of the originator of a route clearer. | |||
| This will also simplify the design, implementation, and deployment of | This will also simplify the design, implementation, and deployment of | |||
| skipping to change at page 1, line 43 ¶ | skipping to change at page 1, line 43 ¶ | |||
| Internet-Drafts are working documents of the Internet Engineering | Internet-Drafts are working documents of the Internet Engineering | |||
| Task Force (IETF). Note that other groups may also distribute | Task Force (IETF). Note that other groups may also distribute | |||
| working documents as Internet-Drafts. The list of current Internet- | working documents as Internet-Drafts. The list of current Internet- | |||
| Drafts is at https://datatracker.ietf.org/drafts/current/. | Drafts is at https://datatracker.ietf.org/drafts/current/. | |||
| Internet-Drafts are draft documents valid for a maximum of six months | Internet-Drafts are draft documents valid for a maximum of six months | |||
| and may be updated, replaced, or obsoleted by other documents at any | and may be updated, replaced, or obsoleted by other documents at any | |||
| time. It is inappropriate to use Internet-Drafts as reference | time. It is inappropriate to use Internet-Drafts as reference | |||
| material or to cite them other than as "work in progress." | material or to cite them other than as "work in progress." | |||
| This Internet-Draft will expire on September 13, 2021. | This Internet-Draft will expire on 16 March 2022. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2021 IETF Trust and the persons identified as the | Copyright (c) 2021 IETF Trust and the persons identified as the | |||
| document authors. All rights reserved. | document authors. All rights reserved. | |||
| This document is subject to BCP 78 and the IETF Trust's Legal | This document is subject to BCP 78 and the IETF Trust's Legal | |||
| Provisions Relating to IETF Documents | Provisions Relating to IETF Documents (https://trustee.ietf.org/ | |||
| (https://trustee.ietf.org/license-info) in effect on the date of | license-info) in effect on the date of publication of this document. | |||
| publication of this document. Please review these documents | Please review these documents carefully, as they describe your rights | |||
| carefully, as they describe your rights and restrictions with respect | and restrictions with respect to this document. Code Components | |||
| to this document. Code Components extracted from this document must | extracted from this document must include Simplified BSD License text | |||
| include Simplified BSD License text as described in Section 4.e of | as described in Section 4.e of the Trust Legal Provisions and are | |||
| the Trust Legal Provisions and are provided without warranty as | provided without warranty as described in the Simplified BSD License. | |||
| described in the Simplified BSD License. | ||||
| Table of Contents | Table of Contents | |||
| 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 | 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 | |||
| 2. Requirements Language . . . . . . . . . . . . . . . . . . . . 3 | 2. Requirements Language . . . . . . . . . . . . . . . . . . . . 3 | |||
| 3. Recommendations . . . . . . . . . . . . . . . . . . . . . . . 3 | 3. Recommendations . . . . . . . . . . . . . . . . . . . . . . . 3 | |||
| 4. Updates to Existing RFCs . . . . . . . . . . . . . . . . . . 4 | 4. Updates to Existing RFCs . . . . . . . . . . . . . . . . . . 4 | |||
| 5. Operational Considerations . . . . . . . . . . . . . . . . . 4 | 5. Operational Considerations . . . . . . . . . . . . . . . . . 4 | |||
| 6. Security Considerations . . . . . . . . . . . . . . . . . . . 5 | 6. Security Considerations . . . . . . . . . . . . . . . . . . . 5 | |||
| 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 | 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 | |||
| skipping to change at page 6, line 17 ¶ | skipping to change at page 6, line 17 ¶ | |||
| DOI 10.17487/RFC4271, January 2006, | DOI 10.17487/RFC4271, January 2006, | |||
| <https://www.rfc-editor.org/info/rfc4271>. | <https://www.rfc-editor.org/info/rfc4271>. | |||
| [RFC5065] Traina, P., McPherson, D., and J. Scudder, "Autonomous | [RFC5065] Traina, P., McPherson, D., and J. Scudder, "Autonomous | |||
| System Confederations for BGP", RFC 5065, | System Confederations for BGP", RFC 5065, | |||
| DOI 10.17487/RFC5065, August 2007, | DOI 10.17487/RFC5065, August 2007, | |||
| <https://www.rfc-editor.org/info/rfc5065>. | <https://www.rfc-editor.org/info/rfc5065>. | |||
| 9.2. Informative References | 9.2. Informative References | |||
| [Analysis] | [Analysis] Hannachi, L. and K. Sriram, "Detailed analysis of AS_SETs | |||
| Hannachi, L. and K. Sriram, "Detailed analysis of AS_SETs | ||||
| in BGP updates", NIST Robust Inter-domain Routing Project | in BGP updates", NIST Robust Inter-domain Routing Project | |||
| Website , October 2019, | Website , October 2019, | |||
| <https://www.nist.gov/sites/default/files/ | <https://www.nist.gov/sites/default/files/ | |||
| documents/2019/10/23/detailed-as_set-analysis.txt>. | documents/2019/10/23/detailed-as_set-analysis.txt>. | |||
| [IANA-SP-ASN] | [IANA-SP-ASN] | |||
| "Special-Purpose Autonomous System (AS) Numbers", | "Special-Purpose Autonomous System (AS) Numbers", | |||
| <https://www.iana.org/assignments/iana-as-numbers-special- | <https://www.iana.org/assignments/iana-as-numbers-special- | |||
| registry/iana-as-numbers-special-registry.xhtml>. | registry/iana-as-numbers-special-registry.xhtml>. | |||
| skipping to change at page 7, line 18 ¶ | skipping to change at page 7, line 18 ¶ | |||
| [RFC8205] Lepinski, M., Ed. and K. Sriram, Ed., "BGPsec Protocol | [RFC8205] Lepinski, M., Ed. and K. Sriram, Ed., "BGPsec Protocol | |||
| Specification", RFC 8205, DOI 10.17487/RFC8205, September | Specification", RFC 8205, DOI 10.17487/RFC8205, September | |||
| 2017, <https://www.rfc-editor.org/info/rfc8205>. | 2017, <https://www.rfc-editor.org/info/rfc8205>. | |||
| Authors' Addresses | Authors' Addresses | |||
| Warren Kumari | Warren Kumari | |||
| Google, Inc. | Google, Inc. | |||
| 1600 Amphitheatre Parkway | 1600 Amphitheatre Parkway | |||
| Mountain View, CA 94043 | Mountain View, CA 94043 | |||
| US | United States of America | |||
| Phone: +1 571 748 4373 | Phone: +1 571 748 4373 | |||
| Email: warren@kumari.net | Email: warren@kumari.net | |||
| Kotikalapudi Sriram | Kotikalapudi Sriram | |||
| USA NIST | USA NIST | |||
| 100 Bureau Drive | 100 Bureau Drive | |||
| Gaithersburg, MD 20899 | Gaithersburg, MD 20899 | |||
| US | United States of America | |||
| Phone: +1 301 975 3973 | Phone: +1 301 975 3973 | |||
| Email: ksriram@nist.gov | Email: ksriram@nist.gov | |||
| Lilia Hannachi | Lilia Hannachi | |||
| USA NIST | USA NIST | |||
| 100 Bureau Drive | 100 Bureau Drive | |||
| Gaithersburg, MD 20899 | Gaithersburg, MD 20899 | |||
| US | United States of America | |||
| Phone: +1 301 975 3259 | Phone: +1 301 975 3259 | |||
| Email: lilia.hannachi@nist.gov | Email: lilia.hannachi@nist.gov | |||
| Jeffrey Haas | Jeffrey Haas | |||
| Juniper Networks, Inc. | Juniper Networks, Inc. | |||
| 1133 Innovation Way | 1133 Innovation Way | |||
| Sunnyvale, CA 94089 | Sunnyvale, CA 94089 | |||
| United States of America | United States of America | |||
| Email: jhaas@juniper.net | Email: jhaas@juniper.net | |||
| End of changes. 10 change blocks. | ||||
| 21 lines changed or deleted | 19 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||