[Sidrops] Opsdir last call review of draft-ietf-sidrops-https-tal-07

Linda Dunbar via Datatracker <noreply@ietf.org> Mon, 18 March 2019 21:37 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: sidrops@ietf.org
Delivered-To: sidrops@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C3228131094; Mon, 18 Mar 2019 14:37:34 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Linda Dunbar via Datatracker <noreply@ietf.org>
To: <ops-dir@ietf.org>
Cc: draft-ietf-sidrops-https-tal.all@ietf.org, sidrops@ietf.org, ietf@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.94.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Linda Dunbar <ldunbar@huawei.com>
Message-ID: <155294505475.26094.8605317163998406572@ietfa.amsl.com>
Date: Mon, 18 Mar 2019 14:37:34 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/6sYaNqn8gWvLC05pOFlMZ_ydWVo>
Subject: [Sidrops] Opsdir last call review of draft-ietf-sidrops-https-tal-07
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.29
List-Id: A list for the SIDR Operations WG <sidrops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidrops>, <mailto:sidrops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidrops/>
List-Post: <mailto:sidrops@ietf.org>
List-Help: <mailto:sidrops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidrops>, <mailto:sidrops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Mar 2019 21:37:35 -0000

Reviewer: Linda Dunbar
Review result: Has Nits

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