Skip to main content

Telechat Review of draft-ietf-wish-whip-14
review-ietf-wish-whip-14-secdir-telechat-housley-2024-05-09-00

Request Review of draft-ietf-wish-whip
Requested revision No specific revision (document currently at 16)
Type Telechat Review
Team Security Area Directorate (secdir)
Deadline 2024-05-14
Requested 2024-05-07
Authors Sergio Garcia Murillo , Dr. Alex Gouaillard
I-D last updated 2025-03-26 (Latest revision 2024-08-21)
Completed reviews Secdir IETF Last Call review of -09 by Russ Housley (diff)
Artart IETF Last Call review of -09 by Barry Leiba (diff)
Genart IETF Last Call review of -09 by Dale R. Worley (diff)
Secdir Telechat review of -14 by Russ Housley (diff)
Tsvart IETF Last Call review of -09 by Dr. Bernard D. Aboba (diff)
Httpdir IETF Last Call review of -09 by Darrel Miller (diff)
Artart Early review of -08 by Barry Leiba (diff)
Secdir IETF Last Call review of -13 by Russ Housley (diff)
Assignment Reviewer Russ Housley
State Completed
Request Telechat review on draft-ietf-wish-whip by Security Area Directorate Assigned
Posted at https://mailarchive.ietf.org/arch/msg/secdir/TKPBpHyU2R7qclfAAgIm0vLrJbQ
Reviewed revision 14 (document currently at 16)
Result Ready
Completed 2024-05-09
review-ietf-wish-whip-14-secdir-telechat-housley-2024-05-09-00
I reviewed this document as part of the Security Directorate's ongoing
effort to review all IETF documents being processed by the IESG.  These
comments were written primarily for the benefit of the Security Area
Directors.  Document authors, document editors, and WG chairs should
treat these comments just like any other IETF Last Call comments.

Document: draft-ietf-wish-whip-14
Reviewer: Russ Housley
Review Date: 2024-05-09
IETF LC End Date: 2024-04-04
IESG Telechat date: 2024-05-16

Summary: Ready


Major Concerns: None


Minor Concerns: None


Nits:

IDnits offers these complaints:

 ** There are 15 instances of too long lines in the document, the longest
    one being 45 characters in excess of 72.

 == There are 2 instances of lines with non-RFC6890-compliant IPv4 addresses
    in the document.  If these are example addresses, they should be changed.

 -- The document has examples using IPv4 documentation addresses according
    to RFC6890, but does not use any IPv6 documentation addresses.  Maybe
    there should be IPv6 examples, too?