[pim] draft-ietf-pim-p2mp-policy-ping-16 telechat Secdir revie w

Wes Hardaker via Datatracker <[email protected]>
Newsgroups gmane.ietf.pim
Message-ID <175519229073.935311.15027027459572587931@dt-datatracker-6f95f9d9c-8g9j6>
Document: draft-ietf-pim-p2mp-policy-ping
Title: Segment Routing Point-to-Multipoint (P2MP) Policy Ping
Reviewer: Wes Hardaker
Review result: Ready

I have reviewed this document as part of the security directorate's ongoing
effort to rev iew all IETF documents being processed by the IESG. These
comments were written primarily
 for the benefit of the security area directors. Document editors and WG chairs
 should tr
eat these comments just like any other last call comments.

Version reviewed: -16
State: Ready

Congratulations on a very well written document.  Honestly one of the cleanest
documents I've ever reviewed.

I only had one question, and it's a question not even an issue: Why is there
both a address family and an address length in the packet, if the address
length is prescribed by the family (including in the text)?  I assume this is
just safe planning for future IP versions???

Cheers,
Wes


_______________________________________________
pim mailing list -- [email protected]
To unsubscribe send an email to [email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.