[Last-Call] Opsdir telechat review of draft-ietf-acme-dtnnodeid-10
Linda Dunbar via Datatracker <noreply@ietf.org> Thu, 20 October 2022 22:54 UTC
Return-Path: <noreply@ietf.org>
X-Original-To: last-call@ietf.org
Delivered-To: last-call@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 26113C1522C8; Thu, 20 Oct 2022 15:54:48 -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: acme@ietf.org, draft-ietf-acme-dtnnodeid.all@ietf.org, last-call@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 8.18.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <166630648814.52985.10284820365346811952@ietfa.amsl.com>
Reply-To: Linda Dunbar <linda.dunbar@futurewei.com>
Date: Thu, 20 Oct 2022 15:54:48 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/last-call/CG8OVmPeZnSAOJ9qHNr7adEVpmM>
Subject: [Last-Call] Opsdir telechat review of draft-ietf-acme-dtnnodeid-10
X-BeenThere: last-call@ietf.org
X-Mailman-Version: 2.1.39
List-Id: IETF Last Calls <last-call.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/last-call>, <mailto:last-call-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/last-call/>
List-Post: <mailto:last-call@ietf.org>
List-Help: <mailto:last-call-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/last-call>, <mailto:last-call-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Oct 2022 22:54:48 -0000
Reviewer: Linda Dunbar Review result: Has Issues I have reviewed this document as part of the Ops area directorate's ongoing effort to review all IETF documents being processed by the IESG. These comments were written primarily for the benefit of the Ops area directors. Document editors and WG chairs should treat these comments just like any other last call comments. This document specifies an extension to ACME protocol which allows an ACME server to validate the Delay-Tolerant Networking Node ID for an ACME client. I had the following comments for the -07 version. I don't think the latest version (-10) resolved my comments. Issues: The document didn't describe how the Node ID described in this document is related to the Delay Tolerant Network. I see the mechanism can be equally used in any network. What are the specifics related to the "Delay Tolerant Network"? It would be helpful if the document adds a paragraph explaining the specific characteristics of the Delay-Tolerant Network that require the additional parameters/types used for validating the Node-ID for an ACME client. Thank you, Linda Dunbar
- [Last-Call] Opsdir telechat review of draft-ietf-… Linda Dunbar via Datatracker
- Re: [Last-Call] Opsdir telechat review of draft-i… Roman Danyliw
- Re: [Last-Call] Opsdir telechat review of draft-i… Linda Dunbar
- Re: [Last-Call] Opsdir telechat review of draft-i… Linda Dunbar
- Re: [Last-Call] Opsdir telechat review of draft-i… Roman Danyliw
- Re: [Last-Call] Opsdir telechat review of draft-i… Linda Dunbar
- Re: [Last-Call] Opsdir telechat review of draft-i… Roman Danyliw
- Re: [Last-Call] Opsdir telechat review of draft-i… Linda Dunbar
- Re: [Last-Call] Opsdir telechat review of draft-i… Deb Cooley
- Re: [Last-Call] Opsdir telechat review of draft-i… Linda Dunbar
- Re: [Last-Call] Opsdir telechat review of draft-i… Brian Sipos
- Re: [Last-Call] Opsdir telechat review of draft-i… Linda Dunbar