]> Huawei

7453 Hickory Hill Saline MI 48176 USA shares@ndzh.com

Routing Area IDR Working Group RFC Request for Comments I-D Internet-Draft IANA BGP Registries The BGP Registries at IANA were set-up as one of the earliest IANA registries. Over time, the registries have become denoted as requiring "standards action", "early allocation", "FCFS (first-come, first server)", "vendor specific", and "IETF review". This draft proposes that certain BGP registries that are labelled "standards action", "early allocation", or "IETF Review" add to these registration actions a "Expert Review. It also proposes that the chairs of BGP Protocol related WG groups be part of the review team. The intent is that these chairs will be responsible to bring questionable allocations to their workings attention. The BGP relate working groups are currently the IDR, BESS, SIDROPS, and GROW, but other working groups like SPRING might be added.

During 2016, several BGP attributes were squatted upon causing operational problems during the early deployment of large communities . Due these problems, deprecated the use of 5 attribute numbers. To avoid this problem in the future, it is helpful to increase pace of early-allocations process and to coordinate the review of key BGP registries. This document proposes to augment existing registration process for BGP registries with Expert review. This draft proposes that certain BGP registries that are labelled "standards action", "early allocation", or "IETF Review" add to these registration actions a "Expert Review. It also recommends that the chairs of BGP Protocol related WG groups be part of the review team.

This document proposes the IETF BGP registries in Table 1 below to require their curent registration policy plus Expert Review. It recommends that the chairs of the BGP related working groups (e.g. IDR, Bess, SIDROPS, GROW) be a part of this review team. The IESG can define which working groups are BGP working groups, but it is important to get the chairs of the Working Groups that originate or maintain the drafts in Table 1 as part of the review team. If no BGP WG groups remain, the IESG may select designated experts to fulfill this role.

ER = Expert Review Table 1 - Registries with changes +----------------------+------------------+-----------+--------+ | BGP registry | Registration | reference | Add ER | +----------------------+------------------+-----------+--------+ | Message Types | Standards Action | RFC4271 | yes | ---------------------------------------------------------------- | BGP Path Attributes | Standards Action | RFC4271 | yes | +--------------------------------------------------------------+ | BGP Error | Standards Action | RFC4271 | yes | | (notification) codes | | RFC7313 | | +--------------------------------------------------------------+ | BGP Error Subcodes | Standards Action | RFC4271 | yes | ---------------------------------------------------------------- | Open Message Error | Standards Action | RFC4271 | yes | | subcodes | | | | +--------------------------------------------------------------+ | Update Message Error | Standards Action | RFC4271 | yes | | subcodes | | | | ---------------------------------------------------------------- | BGP Finite State | Standards Action | RFC6608 | yes | | Machine Error | | | | | subcodes | | | | +--------------------------------------------------------------+ | BGP Cease | Standards Action | RFC4486 | yes | | NOTIFICATION | or Early | | | | message subcodes | Allocation | | | +--------------------------------------------------------------+ | BGP Route Refresh | Standards Action | RFC7313 | yes | | Message Error | (1-127 range | | | | subcodes | | | | +--------------------------------------------------------------+ | BGP Outbound Route | Standards Action | RFC5291 | yes | | Filtering (ORF) | | | | | Types | | | | +--------------------------------------------------------------+ | BGP Open Optional | IETF Review | RFC5492 | yes | | Parameter types | | | | +----------------------+---------------------------------------+ | BGP Tunnel | Standards Action | RFC5512 | yes | | Encapsulation | | | | | Attribute Sub-TLVS | | | | +----------------------+---------------------------------------+ | BGP AIGP Attribute | Standards Action | RFC7311 | Yes | ---------------------------------------------------------------+ | BGP Tunnel | Standards Action | RFC5512 | yes | | Encapsulation | | | | | Attribute Sub-TLVS | | | | +----------------------+---------------------------------------+ | BGP AIGP Attribute | Standards Action | RFC7311 | Yes | ---------------------------------------------------------------+ | Route Refresh | Standards Action | RFC7313 | Yes | | Subcdes | (1-127) | | | +--------------------------------------------------------------+ | P-Multicast Service | IETF Review | RFC7385 | Yes | | Interface Tunnel | | | | | (PMSI) Tunnel Types | | | | +--------------------------------------------------------------+ | P-Multicast Service | Standards Action | RFC7385 | Yes | | Interface Tunnel | | | | | (PMSI) Attribute | | | | | Flags | | | | +--------------------------------------------------------------+ | BGP MCAST-VPN Route | Standards Action | RFC7441 | Yes | | Types | | | | +----------------------+------------------+-----------+--------+

The registries in Table 2 have Expert Review. This document requests that IANA increase their designated expert pool by adding the pool of chairs in BGP related Working Groups (E.g. IDR, BESS, SIDROPS, GROW).

ER = Expert Review Table 2 - Registries with Expert Review +----------------------+------------------+-----------+--------+ | BGP registry | Registration | reference | Add ER | +----------------------+------------------+-----------+--------+ | BGP Layer 2 | Expert Review | RFC6624 | yes | | Encapsulation Types | (0-127) | | | +--------------------------------------------------------------+ | BGP Layer 2 TLV | Expert Review | RFC6624 | yes | | Types | | | | +--------------------------------------------------------------+

Administrative process - Not applicable.

For all of the BGP registries or portions of BGP Registries listed in table 1 append "Designated reviewers" to the registration process. This docuemnt requests the IESG nominate the chairs of the current BGP related working groups which manage the following base protocols that established the registries: , , , , , , , , , , ,

The authors would like to thank Alavaro Retana, John Scudder, Jeff Haas, Job Snider, and members of the IDR and Grow working groups for the active discussion at IETF 97 and post-IETF 97 that inspired this draft.

&RFC2119; &RFC4271; &RFC4486; &RFC5291; &RFC5492; &RFC5512; &RFC6608; &RFC6624; &RFC7311; &RFC7313; &RFC7385; &RFC7441; &RFC8092; &RFC8093;