Skip to main content

Telechat Review of draft-ietf-core-echo-request-tag-12

Request Review of draft-ietf-core-echo-request-tag
Requested revision No specific revision (document currently at 14)
Type Telechat Review
Team Internet of Things Directorate (iotdir)
Deadline 2021-02-14
Requested 2021-02-02
Requested by Éric Vyncke
Authors Christian Amsüss , John Preuß Mattsson , Göran Selander
I-D last updated 2021-02-05
Completed reviews Genart Last Call review of -11 by Ines Robles (diff)
Tsvart Last Call review of -11 by Joerg Ott (diff)
Opsdir Last Call review of -11 by Jürgen Schönwälder (diff)
Iotdir Telechat review of -12 by Eliot Lear (diff)
Thank you in advance for the review of this 32-page draft taking into account the IoT point of view.
Assignment Reviewer Eliot Lear
State Completed
Request Telechat review on draft-ietf-core-echo-request-tag by Internet of Things Directorate Assigned
Posted at
Reviewed revision 12 (document currently at 14)
Result Ready w/issues
Completed 2021-02-05
All in all, a very nice piece of work.  I'm not reviewing for other than IoT

An issue in Section 2.2.1 (you decide if it's minor or major or really just a

I do not understand why the Echo option requires opaque data, and why this
should not be standardized, as it seems that the behavior you are seeking is
standardized.   As you give two example methods in the draft, why not reserve a
few extra bits to specify which method is in use?  This would also allow you to
drop the necessary callback routines in libraries.


The last sentence in 2.2: is this meant to be limited to OSCORE or all uses of
DTLS?  I found the inner/outer text confusing, and that a diagram might
actually help.