--- 1/draft-ietf-grow-route-leak-detection-mitigation-05.txt 2021-10-24 08:13:14.403733095 -0700 +++ 2/draft-ietf-grow-route-leak-detection-mitigation-06.txt 2021-10-24 08:13:14.427733697 -0700 @@ -1,19 +1,19 @@ IDR and SIDR K. Sriram, Ed. Internet-Draft USA NIST Intended status: Standards Track A. Azimov, Ed. -Expires: October 30, 2021 Yandex - April 28, 2021 +Expires: 27 April 2022 Yandex + 24 October 2021 Methods for Detection and Mitigation of BGP Route Leaks - draft-ietf-grow-route-leak-detection-mitigation-05 + draft-ietf-grow-route-leak-detection-mitigation-06 Abstract Problem definition for route leaks and enumeration of types of route leaks are provided in RFC 7908. This document describes a new well- known Large Community that provides a way for route-leak prevention, detection, and mitigation. The configuration process for this Community can be automated with the methodology for setting BGP roles that is described in ietf-idr-bgp-open-policy draft. @@ -25,43 +25,42 @@ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at https://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on October 30, 2021. + This Internet-Draft will expire on 27 April 2022. Copyright Notice Copyright (c) 2021 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal - Provisions Relating to IETF Documents - (https://trustee.ietf.org/license-info) in effect on the date of - publication of this document. Please review these documents - carefully, as they describe your rights and restrictions with respect - to this document. Code Components extracted from this document must - include Simplified BSD License text as described in Section 4.e of - the Trust Legal Provisions and are provided without warranty as - described in the Simplified BSD License. + Provisions Relating to IETF Documents (https://trustee.ietf.org/ + license-info) in effect on the date of publication of this document. + Please review these documents carefully, as they describe your rights + and restrictions with respect to this document. Code Components + extracted from this document must include Simplified BSD License text + as described in Section 4.e of the Trust Legal Provisions and are + provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3 2. Peering Relationships . . . . . . . . . . . . . . . . . . . . 3 - 3. Community vs Attribute . . . . . . . . . . . . . . . . . . . 3 + 3. Community vs Attribute . . . . . . . . . . . . . . . . . . . 4 4. Down Only Community . . . . . . . . . . . . . . . . . . . . . 4 4.1. Route-Leak Mitigation . . . . . . . . . . . . . . . . . . 5 4.2. Only Marking . . . . . . . . . . . . . . . . . . . . . . 6 5. Implementation Considerations . . . . . . . . . . . . . . . . 7 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 7. Security Considerations . . . . . . . . . . . . . . . . . . . 8 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 8 8.1. Normative References . . . . . . . . . . . . . . . . . . 8 8.2. Informative References . . . . . . . . . . . . . . . . . 8 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 9 @@ -99,30 +98,30 @@ "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here. 2. Peering Relationships As described in [I-D.ietf-idr-bgp-open-policy] there are several common peering relations between eBGP neighbors: - o Provider - sender is a transit provider of the neighbor; + * Provider - sender is a transit provider of the neighbor; - o Customer - sender is a customer of the neighbor; + * Customer - sender is a customer of the neighbor; - o Route Server (RS) - sender is route server at an internet exchange + * Route Server (RS) - sender is route server at an internet exchange (IX) - o RS-client - sender is client of an RS at an IX + * RS-client - sender is client of an RS at an IX - o Peer - sender and neighbor are lateral (non-transit) peers; + * Peer - sender and neighbor are lateral (non-transit) peers; If a route is received from a provider, peer, or RS-client, it MUST follow the 'down only' rule, i.e., it MAY be advertised only to customers. If a route is sent to a customer, peer, or RS-client, it also MUST follow the 'down only' rule at each subsequent AS in the AS path. A standardized transitive route-leak detection signal is needed that will prevent Autonomous Systems (ASes) from leaking and also inform a remote ISP (or AS) in the AS path that a received route violates the @@ -359,23 +358,25 @@ . [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 2017, . 8.2. Informative References [I-D.ietf-idr-bgp-open-policy] Azimov, A., Bogomazov, E., Bush, R., Patel, K., and K. - Sriram, "Route Leak Prevention using Roles in Update and - Open messages", draft-ietf-idr-bgp-open-policy-15 (work in - progress), January 2021. + Sriram, "Route Leak Prevention and Detection using Roles + in UPDATE and OPEN Messages", Work in Progress, Internet- + Draft, draft-ietf-idr-bgp-open-policy-17, 13 October 2021, + . [RFC4264] Griffin, T. and G. Huston, "BGP Wedgies", RFC 4264, DOI 10.17487/RFC4264, November 2005, . [RFC7908] Sriram, K., Montgomery, D., McPherson, D., Osterweil, E., and B. Dickson, "Problem Definition and Classification of BGP Route Leaks", RFC 7908, DOI 10.17487/RFC7908, June 2016, . @@ -424,14 +425,13 @@ USA National Institute of Standards and Technology 100 Bureau Drive Gaithersburg, MD 20899 United States of America Email: ksriram@nist.gov Alexander Azimov (editor) Yandex Ulitsa Lva Tolstogo 16 - Moscow 119021 - Russia + Moscow Email: a.e.azimov@gmail.com