OSPFv2 Extensions for Bit Index Explicit Replication (BIER)
Draft of message to be sent after approval:
From: The IESG <firstname.lastname@example.org> To: IETF-Announce <email@example.com> Cc: The IESG <firstname.lastname@example.org>, email@example.com, Reshad Rahman <firstname.lastname@example.org>, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com Subject: Protocol Action: 'OSPFv2 Extensions for BIER' to Proposed Standard (draft-ietf-bier-ospf-bier-extensions-17.txt) The IESG has approved the following document: - 'OSPFv2 Extensions for BIER' (draft-ietf-bier-ospf-bier-extensions-17.txt) as Proposed Standard This document is the product of the Bit Indexed Explicit Replication Working Group. The IESG contact persons are Alvaro Retana, Martin Vigoureux and Deborah Brungard. A URL of this Internet Draft is: https://datatracker.ietf.org/doc/draft-ietf-bier-ospf-bier-extensions/
Technical Summary This document describes the OSPFv2 protocol extension for Bit Index Explicit Replication (BIER) with MPLS encapsulation. Working Group Summary This document was presented and discussed at IETF91, IETF92 and IETF95. There were discussions on whether there was a mismatch with an example in the MPLS encapsulation draft, that was resolved by clarifying the text in that draft. The discussions on IPv6 support resulted in the decision to do a separate document for OSPFv3 BIER Extensions. There was a discussion on the BIER alias regarding allowing 0 for the label range size and, with WG agreement, a change was made. The WG is still discussing whether to change the BAR size from 8 bits to 16 (or with a type/subtype) for future-proofing to potentially allow interaction with an individual draft in a different WG. This discussion erupted on the list well after WGLC. IF there is clear WG consensus to make this change, then I will ensure a 1 week WGLC for this technical change. Document Quality Major vendors on the author list have working implementations or are working on the implementation of the extensions. Acee Lindem has done a thorough review of the document. Personnel The Document Shepherd is Reshad Rahman. The Responsible Area Director is Alvaro Retana.