Skip to main content

Last Call Review of draft-ietf-dprive-dnsodtls-12

Request Review of draft-ietf-dprive-dnsodtls
Requested revision No specific revision (document currently at 15)
Type Last Call Review
Team General Area Review Team (Gen-ART) (genart)
Deadline 2016-12-13
Requested 2016-11-03
Authors Tirumaleswar Reddy.K , Dan Wing , Prashanth Patil
I-D last updated 2016-11-17
Completed reviews Genart Last Call review of -12 by Jouni Korhonen (diff)
Opsdir Last Call review of -12 by Éric Vyncke (diff)
Genart Telechat review of -13 by Jouni Korhonen (diff)
Assignment Reviewer Jouni Korhonen
State Completed
Request Last Call review on draft-ietf-dprive-dnsodtls by General Area Review Team (Gen-ART) Assigned
Reviewed revision 12 (document currently at 15)
Result Ready
Completed 2016-11-17
I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at


Document: draft-ietf-dprive-dnsodtls-12
Reviewer: Jouni Korhonen
Review Date: 2016-11-17
IETF LC End Date: 2016-11-16
IESG Telechat date: 2016-12-15


The document is ready for publication.


o Section 3.1. has “first-come, first-served” port range. What port range this 
  actually is? Does it refer to ephemeral port range (rfc6335).

o Section 6 describes a case where an anycasted DTLS packet reaches a DNS server
  that does not have an existing security association with the client. A DTLS
  session resumption should initiated as a result. Is it possible that the next
  DTLS message again reaches another DNS server without security association, which
  would cause a new fatal alert to be returned.. etc?? If this is the case there should
  be some text pointing at this case. If I am just confused the current text is fine.