Skip to main content

Last Call Review of draft-ietf-bier-ospfv3-extensions-07
review-ietf-bier-ospfv3-extensions-07-genart-lc-knodel-2023-07-11-00

Request Review of draft-ietf-bier-ospfv3-extensions
Requested revision No specific revision (document currently at 07)
Type Last Call Review
Team General Area Review Team (Gen-ART) (genart)
Deadline 2023-07-11
Requested 2023-06-27
Authors Peter Psenak , Nagendra Kumar Nainar , IJsbrand Wijnands
I-D last updated 2023-07-11
Completed reviews Rtgdir Last Call review of -07 by Adrian Farrel
Secdir Last Call review of -07 by Vincent Roca
Genart Last Call review of -07 by Mallory Knodel
Assignment Reviewer Mallory Knodel
State Completed
Request Last Call review on draft-ietf-bier-ospfv3-extensions by General Area Review Team (Gen-ART) Assigned
Posted at https://mailarchive.ietf.org/arch/msg/gen-art/rs2T0E1-YLLyW1HSLJ8KLizuOA8
Reviewed revision 07
Result Ready w/nits
Completed 2023-07-11
review-ietf-bier-ospfv3-extensions-07-genart-lc-knodel-2023-07-11-00
I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://wiki.ietf.org/en/group/gen/GenArtFAQ>.

Document: draft-ietf-bier-ospfv3-extensions-??
Reviewer: Mallory Knodel
Review Date: 2023-07-11
IETF LC End Date: 2023-07-11
IESG Telechat date: Not scheduled for a telechat

Summary: This document extends another and is very similar in text and
format to other documents that extend the same protocol, except for the
critical text that relates to this particular protocol extension. Therefore for
consistency and readability I think very few changes can or even should be made
other than the incisive changes proposed by the authors. Only three small
editorial suggestions: one is mere copy editing suggestion and the others are
stylistic choices to improve readability.

Major issues:

Minor issues:

Nits/editorial comments:

 * The acronym "Bit Index Explicit Replication (BIER)" need only be expanded
 once, in the abstract, and therefore the Introduction might start simply with
 "BIER".

 * Parentheticals can be cumbersome for readers, and thus the second sentence
 of Section 2 might instead read, "Within a given BIER domain, a BFR prefix is
 a unique, routable..." It would also be trivial to remove the parenthetical
 statement from the final sentence of section 2.3.

 * While not all acronyms need be expanded, eg BCP, domain-specific acronyms
 can provide more context to the reader. It is not my determination that these
 acronyms are domain specific, eg MPLS is defined in other documents and in
 other IETF working groups. However LSA, TLV, TBD1, BAR, IPA, perhaps are
 specific enough to BIER to warrant expansion the first time they appear.