Telechat Review of draft-ietf-opsec-probe-attribution-08
review-ietf-opsec-probe-attribution-08-opsdir-telechat-dunbar-2023-07-11-00

Request Review of draft-ietf-opsec-probe-attribution
Requested revision No specific revision (document currently at 09)
Type Telechat Review
Team Ops Directorate (opsdir)
Deadline 2023-07-04
Requested 2023-06-26
Authors Éric Vyncke , Benoit Donnet , Justin Iurman
I-D last updated 2023-07-11
Completed reviews Genart Last Call review of -05 by Peter E. Yee (diff)
Secdir Last Call review of -06 by Tirumaleswar Reddy.K (diff)
Tsvart Last Call review of -05 by Magnus Westerlund (diff)
Opsdir Last Call review of -05 by Linda Dunbar (diff)
Opsdir Telechat review of -08 by Linda Dunbar (diff)
Assignment Reviewer Linda Dunbar
State Completed
Request Telechat review on draft-ietf-opsec-probe-attribution by Ops Directorate Assigned
Posted at https://mailarchive.ietf.org/arch/msg/ops-dir/OKXkQdRbMadujAylFAyk9N3BWCY
Reviewed revision 08 (document currently at 09)
Result Has issues
Completed 2023-07-11
review-ietf-opsec-probe-attribution-08-opsdir-telechat-dunbar-2023-07-11-00
I have reviewed this document as part of the Ops area directorate's ongoing
effort to review all IETF documents being processed by the IESG.  These
comments were written primarily for the benefit of the Ops area directors.
Document editors and WG chairs should treat these comments just like any other
last-call comments.

Summary: This document suggests some simple techniques for a source to identify
its probes.

This is my second time reviewing the draft. (last review was the -05 version).
Thanks for the authors replies, which helps me understand the draft much
better. However, there are still unsolved issues: - Is the "Probe" another ICMP
message?  Does the "probe" have an ICMP Header? or just simple "Echo" request?
- Should a new ICMP code be specified so that target nodes can decode the
content carried by the ICMP message?

Thank you,
Linda