Hi all,
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://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
Document:draft-ietf-pim-null-register-packing-13
Reviewer:Behcet Sarikaya
Review Date:2022-02-17
IETF LC End Date:2022-02-22
IESG Telechat date: (if known)
Summary:
Major issues:Two new messages for Protocol Independent Multicast – Sparse Mode(PIM-SM) PIM Packed Null-Register and a PIM Packed Register-Stop
message and related behaviour extensions to PIM-SM are defined.
PIM Packed Null-Register messages are sent from the first-hop
routers (called Designated Router, DR) to the Rendezvous Point
(RP) in order to enable registering more than one multicast
sources. PIM Packed Register-Stop messages are sent from RP
to DR to indicate stopping the PIM registration process.
This document is basically ready for publication, but has nits as indicated below.
Minor issues:
Nits/editorial comments:
Nits:
From IETF ID nits tool:
** Downref: Normative reference to an Informational RFC: RFC 3446
s/multiple PIM Null-Registers [RFC7761] and Register-Stops [RFC7761]/ multiple PIM Null-Registers and Register-Stops [RFC7761]Flag Bit 7 in PIM common header is defined as Capability bit but in Figure 1 and throughout the draft it is marked as P bit not as C bitHowever, RFC 8736 seems to indicate that Flag Bit 7 is already reserved as No-Forward bit in RFC 5059So maybe another Flag bit needs to be used.
Behcet
-- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call