Hi Authors, All, The IETF Last-Call is completed since 26 January 2026: https://mailarchive.ietf.org/arch/msg/ietf-announce/946zJzs3W0v5NIPdKbbDRQLONIY/
There is one open item identified by IANA on 21 January 2026 and the full IANA request can be observed here: https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-unequal-lb/history/ Once the document is updated accordingly I'll request IESG ballot scheduling. Brgds, G/ -----Original Message----- From: David Dong via RT <[email protected]> Sent: Thursday, January 22, 2026 12:46 AM Cc: [email protected]; [email protected] Subject: [IANA #1441205] Last Call: <draft-ietf-bess-evpn-unequal-lb-30.txt> (Weighted Multi-Path Procedures for EVPN Multi-Homing) to Proposed Standard CAUTION: This is an external email. Please be very careful when clicking links or opening attachments. See the URL nok.it/ext for additional information. IESG/Authors/WG Chairs: IANA has completed its review of draft-ietf-bess-evpn-unequal-lb-30. If any part of this review is inaccurate, please let us know. IANA has a question about one of the actions requested in the IANA Considerations section of this document. IANA understands that, upon approval of this document, there are three actions which we must complete. First, in the DF Election Capabilities registry in the Border Gateway Protocol (BGP) Extended Communities registry group located at: https://www.iana.org/assignments/bgp-extended-communities/ a single new registration will be made as follows: Bit: [ TBD-at-Registration ] Name: BW (Bandwidth Weighted DF Election) Reference: [ RFC-to-be ] Date: [ TBD-at-Registration ] IANA notes that the authors have suggested that Bit 4 be used for this capability. Second, in the EVPN Extended Community Sub-Types registry also in the Border Gateway Protocol (BGP) Extended Communities registry group located at: https://www.iana.org/assignments/bgp-extended-communities/ the existing registration for Sub-Type Value 0x10 will have its reference changed to [ RFC-to-be ] as follows: Sub-Type Value: 0x10 Name: EVPN Link Bandwidth Extended Community Reference: [ RFC-to-be ] Date: [ TBD-at-Registration ] Third, a new registry is to be created called the Value-Units is to be created. IANA QUESTION --> Is it possible to have a slightly more descriptive title for the registry name in Section 10.3 of the current draft? IANA QUESTION --> Where should this new registry be located? Should it be added to an existing registry group, or is this to be under a new registry group? The registry is managed via RFC Required as defined in [RFC8126]. There are initial registrations in the new registry as follows: Value Name Reference ------------------------ 0 Weight in units of Mbps [ RFC-to-be ] 1 Generalized Weight [ RFC-to-be ] 2-255 Unassigned We understand that these are the only actions required to be completed upon approval of this document. NOTE: The actions requested in this document will not be completed until the document has been approved for publication as an RFC. This message is meant only to confirm the list of actions that will be performed. For definitions of IANA review states, please see: https://datatracker.ietf.org/help/state/draft/iana-review Thank you, David Dong IANA Services Sr. Specialist _______________________________________________ BESS mailing list -- [email protected] To unsubscribe send an email to [email protected]
