Skip to main content

Telechat Review of draft-ietf-dnsop-onion-tld-00
review-ietf-dnsop-onion-tld-00-opsdir-telechat-taylor-2015-08-23-00

Request Review of draft-ietf-dnsop-onion-tld
Requested revision No specific revision (document currently at 01)
Type Telechat Review
Team Ops Directorate (opsdir)
Deadline 2015-09-01
Requested 2015-08-03
Authors Jacob Appelbaum , Alec Muffett
I-D last updated 2015-08-23
Completed reviews Genart Last Call review of -00 by Joel M. Halpern (diff)
Secdir Last Call review of -00 by Christian Huitema (diff)
Opsdir Telechat review of -00 by Tom Taylor (diff)
Assignment Reviewer Tom Taylor
State Completed
Request Telechat review on draft-ietf-dnsop-onion-tld by Ops Directorate Assigned
Reviewed revision 00 (document currently at 01)
Result Ready
Completed 2015-08-23
review-ietf-dnsop-onion-tld-00-opsdir-telechat-taylor-2015-08-23-00
I have reviewed draft-ietf-dnsop-onion-tld-00 as part of the Operational 


directorate's ongoing effort to review all IETF documents being 


processed by the IESG.  These comments were written with the intent of 


improving the operational aspects of the IETF drafts. Comments that are 


not addressed in last call may be included in AD reviews during the IESG 


review.  Document editors and WG chairs should treat these comments just 


like any other (rather belated) last call comments.




Tom Taylor

Summary



As I understand it, this document is formalizing an established usage. 


Hence no consideration of transition is required. The template indicates 


how the DNS infrastructure should react to .onion domain name requests, 


but does not spell out which aspects of that would be managed and which 


would be a matter of implementation. It would be nice if this were made 


explicit but is probably unnecessary.






Note the IANA objection to the current wording of the template and IANA 


section. But from this reviewer's point of view the document is good to go.




Nits/editorials

Section 2 item 3: s/either either/either/