Last Call Review of draft-ietf-sidrops-https-tal-07
review-ietf-sidrops-https-tal-07-opsdir-lc-dunbar-2019-03-18-00

Request Review of draft-ietf-sidrops-https-tal
Requested revision No specific revision (document currently at 08)
Type Last Call Review
Team Ops Directorate (opsdir)
Deadline 2019-03-18
Requested 2019-03-04
Authors Geoff Huston , Samuel Weiler , George G. Michaelson , Stephen Kent , Tim Bruijnzeels
I-D last updated 2019-03-18
Completed reviews Genart Last Call review of -07 by Pete Resnick (diff)
Opsdir Last Call review of -07 by Linda Dunbar (diff)
Rtgdir Telechat review of -07 by John Drake (diff)
Assignment Reviewer Linda Dunbar
State Completed
Request Last Call review on draft-ietf-sidrops-https-tal by Ops Directorate Assigned
Reviewed revision 07 (document currently at 08)
Result Has nits
Completed 2019-03-18
review-ietf-sidrops-https-tal-07-opsdir-lc-dunbar-2019-03-18-00
Reviewer: Linda Dunbar
Review result: Ready with Comments & Nits

I have reviewed this document 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 last call comments.

This document defines the syntax of Trust Anchor Locator (TAL) for Replying
Parties to retrieve the Trust Anchor, to avoid repeating the distribution
procedure when Trust Anchor changes.

My question: if the Trust Anchor changes, does the URI in the TAL changes?
Another questions: Section 2.4 Example: is the Public Key listed there for both
URI?

Typo: Section 2.1 second paragraph:  "without needing to effect..", do you mean
"without needing to affect ..??

Cheers,

Linda Dunbar