Skip to main content

Last Call Review of draft-shore-icmp-aup-06
review-shore-icmp-aup-06-opsdir-lc-chown-2014-01-23-00

Request Review of draft-shore-icmp-aup
Requested revision No specific revision (document currently at 12)
Type IETF Last Call Review
Team Ops Directorate (opsdir)
Deadline 2014-01-21
Requested 2013-11-11
Authors Melinda Shore , Carlos Pignataro
I-D last updated 2018-12-20 (Latest revision 2014-02-03)
Completed reviews Genart IETF Last Call review of -06 by Vijay K. Gurbani (diff)
Genart Telechat review of -09 by Vijay K. Gurbani (diff)
Secdir IETF Last Call review of -06 by Hilarie Orman (diff)
Opsdir IETF Last Call review of -06 by Tim Chown (diff)
Assignment Reviewer Tim Chown
State Completed
Request IETF Last Call review on draft-shore-icmp-aup by Ops Directorate Assigned
Reviewed revision 06 (document currently at 12)
Result Has nits
Completed 2014-01-23
review-shore-icmp-aup-06-opsdir-lc-chown-2014-01-23-00
Hi,

I have reviewed draft-shore-icmp-aup-09 on behalf of the OPS DIR and believe
the document is Ready.

I believe the guidance presented in the document is useful to publish, and
having the consensus on the subject written up provides a useful point of
reference when certain uses of ICMP are proposed in future draft documents.

A couple of non-blocking nits:

1. One might add at the end of Section 2.3 that filtering of ICMPv6 Packet Too
Big messages has caused problems for IPv6 deployment wrt PMTUD, despite the
advice of RFC4890. There's actually some good material in RFC4890 on ICMPv6 use
cases and issues with its use and its security - is it worth adding a reference
to that in this document?

2. I would suggest putting the "AUP" in a separate section, before Section 5,
perhaps called "Recommended AUP for ICMP" or similar, making Section 2 called
something like "Comments on the existing use of ICMP".  I find the existing
structure a little bit odd - I think the recommendation would sit better as the
conclusion of the document.  That is just a personal preference however.

Tim