draft-ietf-idr-bgp-open-policy-23.txt   draft-ietf-idr-bgp-open-policy-24.txt 
Network Working Group A. Azimov Network Working Group A. Azimov
Internet-Draft Qrator Labs & Yandex Internet-Draft Qrator Labs & Yandex
Intended status: Standards Track E. Bogomazov Intended status: Standards Track E. Bogomazov
Expires: 4 September 2022 Qrator Labs Expires: 3 October 2022 Qrator Labs
R. Bush R. Bush
Internet Initiative Japan & Arrcus, Inc. Internet Initiative Japan & Arrcus, Inc.
K. Patel K. Patel
Arrcus Arrcus
K. Sriram K. Sriram
USA NIST USA NIST
3 March 2022 1 April 2022
Route Leak Prevention and Detection using Roles in UPDATE and OPEN Route Leak Prevention and Detection using Roles in UPDATE and OPEN
Messages Messages
draft-ietf-idr-bgp-open-policy-23 draft-ietf-idr-bgp-open-policy-24
Abstract Abstract
Route leaks are the propagation of BGP prefixes that violate Route leaks are the propagation of BGP prefixes that violate
assumptions of BGP topology relationships, e.g., announcing a route assumptions of BGP topology relationships, e.g., announcing a route
learned from one transit provider to another transit provider or a learned from one transit provider to another transit provider or a
lateral (i.e., non-transit) peer or announcing a route learned from lateral (i.e., non-transit) peer or announcing a route learned from
one lateral peer to another lateral peer or a transit provider. one lateral peer to another lateral peer or a transit provider.
These are usually the result of misconfigured or absent BGP route These are usually the result of misconfigured or absent BGP route
filtering or lack of coordination between autonomous systems (ASes). filtering or lack of coordination between autonomous systems (ASes).
skipping to change at page 2, line 15 skipping to change at page 2, line 15
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 4 September 2022. This Internet-Draft will expire on 3 October 2022.
Copyright Notice Copyright Notice
Copyright (c) 2022 IETF Trust and the persons identified as the Copyright (c) 2022 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 (https://trustee.ietf.org/ Provisions Relating to IETF Documents (https://trustee.ietf.org/
license-info) in effect on the date of publication of this document. license-info) in effect on the date of publication of this document.
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
skipping to change at page 11, line 25 skipping to change at page 11, line 25
+-------+-------------------------------+---------------+ +-------+-------------------------------+---------------+
| 4 | Peer (i.e., Lateral Peer) | This document | | 4 | Peer (i.e., Lateral Peer) | This document |
+-------+-------------------------------+---------------+ +-------+-------------------------------+---------------+
| 5-255 | To be assigned by IETF Review | | | 5-255 | To be assigned by IETF Review | |
+-------+-------------------------------+---------------+ +-------+-------------------------------+---------------+
Table 3: IANA Registry for BGP Role Table 3: IANA Registry for BGP Role
IANA has registered a new OPEN Message Error subcode named the "Role IANA has registered a new OPEN Message Error subcode named the "Role
Mismatch" (see Section 3.2) in the OPEN Message Error subcodes Mismatch" (see Section 3.2) in the OPEN Message Error subcodes
registry. IANA has assigned the value TBD [to be removed upon registry. IANA has assigned the value 11 [to be removed upon
publication: https://www.iana.org/assignments/bgp-parameters/bgp- publication: https://www.iana.org/assignments/bgp-parameters/bgp-
parameters.xhtml#bgp-parameters-6]. This document is the reference parameters.xhtml#bgp-parameters-6]. This document is the reference
for the new subcode. for the new subcode.
Due to improper use of the values 8, 9, and 10 in the OPEN Message
Error subcodes registry, this document requested IANA to mark these
values as "Deprecated". IANA has marked values 8-10 as "Deprecated"
in the OPEN Message Error subcodes registry. This document is listed
as the reference.
IANA has also registered a new path attribute named "Only to Customer IANA has also registered a new path attribute named "Only to Customer
(OTC)" (see Section 4) in the "BGP Path Attributes" registry. IANA (OTC)" (see Section 4) in the "BGP Path Attributes" registry. IANA
has assigned code value 35 [To be removed upon publication: has assigned code value 35 [To be removed upon publication:
http://www.iana.org/assignments/bgp-parameters/bgp- http://www.iana.org/assignments/bgp-parameters/bgp-
parameters.xhtml#bgp-parameters-2]. This document is the reference parameters.xhtml#bgp-parameters-2]. This document is the reference
for the new attribute. for the new attribute.
7. Security Considerations 7. Security Considerations
The security considerations of BGP (as specified in [RFC4271] and The security considerations of BGP (as specified in [RFC4271] and
 End of changes. 6 change blocks. 
5 lines changed or deleted 11 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/