Re: [Last-Call] Opsdir telechat review of draft-ietf-acme-dtnnodeid-10

Roman Danyliw <rdd@cert.org> Fri, 21 October 2022 17:53 UTC

Return-Path: <rdd@cert.org>
X-Original-To: last-call@ietfa.amsl.com
Delivered-To: last-call@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 16434C157B3B; Fri, 21 Oct 2022 10:53:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.108
X-Spam-Level:
X-Spam-Status: No, score=-2.108 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cert.org
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p9UkEw7_j9_a; Fri, 21 Oct 2022 10:53:14 -0700 (PDT)
Received: from USG02-CY1-obe.outbound.protection.office365.us (mail-cy1usg02on0114.outbound.protection.office365.us [23.103.209.114]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 69422C14CE34; Fri, 21 Oct 2022 10:53:14 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector5401; d=microsoft.com; cv=none; b=irMKflihZ3/rpE/WDE11ryL+opoVPFdk01q6er3RMU8H9p9zWB+FigBufa2mErgx2yoFYCBoAe/muOPVK7RhKdQIrzTj4M+T7yiffx8Qe5OaWjWnkPNeJAvzlV6P+bsQEorJBU1ePRpozUMe8yBYJJQTv0tmKj7fdfVdxzX8EDN/DCx8Wvg0PhS1c7tu5JIt5V6EGLdRzIJD9INhKNJDQaoLono6LxIpqEJ/LqniE1JXD1QvEfUc6jXelJequ8H6i2FYbdf0+np3Wav+Cw/ijLwebVM9nDjcRuEIUm4QRWnufJ5b838Q8jF/zVQCQXND9eHbSkcN2dkmsQ487Yq1Dg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector5401; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=e6WU+uvHd8YgjL6VtQEeZxeMtjarNwtgwXRuAQFod/Y=; b=gbEjRzwZ63DnQikEQvgS3PF4SkEZCzdk/MdyXEKMOA4K/oWPkI6MZi/s2ggmusoXbxM/d3vhVb4x2dcf+mizSmspV7fKX0AgENVNM7iCAiVoIPBgfeXiG6ou+7zKKr2al7f+Zl/nJ2yeO5rUDhGr749c5WSMo/8MpbxFhfmNkjo7TiF11bHie6jWB+ovZTRzEP+oPWloGd8jGoy07ju0uHl5NI9d2VyoPi0L8U+iLnBv43/Ds56XGW9aMAxawoYumRWkT5GBIluqaCRZFMp3Ym2g+vYDkN97je9QWiSER5ly7MpfYaZ2nKzuaTKzSoVPPwXd+dY5SW0dHSCu2/KE+Q==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cert.org; dmarc=pass action=none header.from=cert.org; dkim=pass header.d=cert.org; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cert.org; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=e6WU+uvHd8YgjL6VtQEeZxeMtjarNwtgwXRuAQFod/Y=; b=pWCdqJavTy4u0Mx/1k4dyebte2aHdqduvwK13Cy6fJD8QWKuN5KR+TbI8LpZyTkSeexH83/YNpuqWyZpFhDg7sns9f5diWlidum1t2h9CL5cFkklUuRrt9dYpUG4u+cKEDqEUjP4fkHVLHgc5KUh6hQs+k8AWG7JK2nPVAzaQG4=
Received: from BN2P110MB1107.NAMP110.PROD.OUTLOOK.COM (2001:489a:200:168::11) by BN2P110MB1366.NAMP110.PROD.OUTLOOK.COM (2001:489a:200:17f::10) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5723.34; Fri, 21 Oct 2022 17:53:12 +0000
Received: from BN2P110MB1107.NAMP110.PROD.OUTLOOK.COM ([fe80::11dc:e93c:167b:f429]) by BN2P110MB1107.NAMP110.PROD.OUTLOOK.COM ([fe80::11dc:e93c:167b:f429%6]) with mapi id 15.20.5723.036; Fri, 21 Oct 2022 17:53:12 +0000
From: Roman Danyliw <rdd@cert.org>
To: Linda Dunbar <linda.dunbar@futurewei.com>, "ops-dir@ietf.org" <ops-dir@ietf.org>
CC: "acme@ietf.org" <acme@ietf.org>, "draft-ietf-acme-dtnnodeid.all@ietf.org" <draft-ietf-acme-dtnnodeid.all@ietf.org>, "last-call@ietf.org" <last-call@ietf.org>
Thread-Topic: Opsdir telechat review of draft-ietf-acme-dtnnodeid-10
Thread-Index: AQHY5Nb7CSCaC4phlkqTVSi9YQdN0K4X9FWwgAA+fICAANybAIAACtFwgAAGtwCAAAD9UA==
Date: Fri, 21 Oct 2022 17:53:12 +0000
Message-ID: <BN2P110MB1107102AF46BE43B6F3828C0DC2D9@BN2P110MB1107.NAMP110.PROD.OUTLOOK.COM>
References: <166630648814.52985.10284820365346811952@ietfa.amsl.com> <BN2P110MB11076DDD8A34680DE318379EDC2A9@BN2P110MB1107.NAMP110.PROD.OUTLOOK.COM> <855DAAAE-A1BF-4577-922D-BC0F671CD0E8@futurewei.com> <DE4B11FF-1E07-44FA-9D9E-7EAE51BC393F@futurewei.com> <BN2P110MB1107FE073820EFCEE803710ADC2D9@BN2P110MB1107.NAMP110.PROD.OUTLOOK.COM> <560A8DBD-4CA4-4E49-BFA9-7452E4E1FE4F@futurewei.com>
In-Reply-To: <560A8DBD-4CA4-4E49-BFA9-7452E4E1FE4F@futurewei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=cert.org;
x-ms-publictraffictype: Email
x-ms-traffictypediagnostic: BN2P110MB1107:EE_|BN2P110MB1366:EE_
x-ms-office365-filtering-correlation-id: 2871ab98-ec44-4235-7d94-08dab38d1f3d
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: P293haNLVazGuUA635DVjIvRH4S8QPmc1Ht3CIHaruWnTtZTIRUA6pa3yOUNfrEdN4TA68jPXcQTr6Q5nJBG0ZtIlX5mf9X0hlzN7HI5ZWhaTd6/O/E3tmZrn23VEuKsJe9BistlsYg1nvFUn1sOYYAX5rY1T8c5TOvKU+uTUi5lEIlyEepuAOFMykfbh/wAs4huTkGhghJhN2YapNDPubiWlPwO5Dtn3vERouhZEILZzrLpvEsLUI6/FnX//VIFegidDc72Sgn58npND5ukAC0n+O67o9ZcHc7b1o7SUU17QEWd+S0ktWzhY75EvPQ+5oMvOrCKia6Cyop3Hv83PLjFKSbtn/kr+KTKcx3pjn2YcBtEtJOJOoQcrhSsH/lz0jbW+cY4JOoFIocBbbATuPt5KB6cCVIxp2tI2y9is8Of0aYFCupyN1qw5gbDt8CnmYBI9EGZ0NBE0YX08GI+KQ4J3ZTQKyEFMd5j5WYQK9XEXsNRsWx3ARCxpWDQvAPeHy1jIf1Mr2W2tA1/NOSqkjDhLtzbB5Z5cODR9tEwwaU6IztqWDoDs2wJ7pwEtCXQT9nN3bzeH1bEvsotMvHHvW8bt5UE2XWP4muN8yJcKz8OEiEBML7gVmIrebxvJJ0l55OFyd1rP2bRxbvecbf2Svi4gUXiD7//OoJczXaa8HioGyqP4tEaUnXbSEmZBtnZY6ZtVbyMEz/XDjRFKtm5TA==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:BN2P110MB1107.NAMP110.PROD.OUTLOOK.COM; PTR:; CAT:NONE; SFS:(13230022)(366004)(451199015)(2906002)(966005)(45080400002)(498600001)(71200400001)(82960400001)(9686003)(186003)(38100700002)(122000001)(66446008)(53546011)(66946007)(66556008)(54906003)(110136005)(66476007)(4326008)(7696005)(38070700005)(8676002)(8936002)(64756008)(76116006)(6506007)(5660300002)(52536014)(83380400001)(33656002)(55016003)(86362001)(26005); DIR:OUT; SFP:1102;
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: ERrJ/M/2o1ce+GPqu0AWT0xGGbTvPdjBA+6RnhFbmeq7PVyLfp16M4iwPfCIhREUKCMBr9Lgk9L/2zjf5MHOJgtMGhpQiBRs/XfemgvpN5S8EmxJQ8Q5Gw/Oyn6A9jqptwUJyA6Bj9ahgjoH2uXJTV1yjgVJkZVhNAVE7W57jtovSYHO14cmwQ6zFZh1UHdc8t/PKFtrRRHU+7IApMaXbY/tRhB3bB92ip0/ygf8bX5M5TtDFtrohO0Jalefsh0faQJBHn6L3BR+kx/lk8xQP5PCX/Ex+y583fkNMkvgK3JcmSEJM+pXduNNI+svay+pQEvjBmdm2x+wfGowLcqfXzj9+OMmdvfuonNWz4o4wxu5W7SKcgzrGVVXDyxVvvswMw9jUytbsx2lhNc3u7BwwcLlujjNTzM89mRkPN1ZJew=
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: cert.org
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: BN2P110MB1107.NAMP110.PROD.OUTLOOK.COM
X-MS-Exchange-CrossTenant-Network-Message-Id: 2871ab98-ec44-4235-7d94-08dab38d1f3d
X-MS-Exchange-CrossTenant-originalarrivaltime: 21 Oct 2022 17:53:12.1605 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 95a9dce2-04f2-4043-995d-1ec3861911c6
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN2P110MB1366
Archived-At: <https://mailarchive.ietf.org/arch/msg/last-call/9NzDTCOVkZle4sHlsWFFfJ7nu_0>
Subject: Re: [Last-Call] Opsdir telechat review of draft-ietf-acme-dtnnodeid-10
X-BeenThere: last-call@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
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: Fri, 21 Oct 2022 17:53:19 -0000

IMO, the simplest thing would be to pose this question on the DTN WG mailing list.  This very specific work is being done in the ACME WG because it has the expertise on the certificate issuance mechanism, but I see you applicability to SD-WAN as more general.

Roman

> -----Original Message-----
> From: Linda Dunbar <linda.dunbar@futurewei.com>
> Sent: Friday, October 21, 2022 1:48 PM
> To: Roman Danyliw <rdd@cert.org>; ops-dir@ietf.org
> Cc: acme@ietf.org; draft-ietf-acme-dtnnodeid.all@ietf.org; last-call@ietf.org
> Subject: Re: Opsdir telechat review of draft-ietf-acme-dtnnodeid-10
> 
> Roman,
> 
> Can you give me a few names with who I can chat to find out more?
> 
> Thank you
> 
> Linda
> 
> On 10/21/22, 12:38 PM, "Roman Danyliw" <rdd@cert.org> wrote:
> 
>     Hi Linda!
> 
>     As I understand the scenario below, it would align to the work in this
> document only to the degree that the SD-WAN network would be an underlay
> to the DTN Bundle Protocol (via some as of yet undefined convergence layer)
> and the Virtual Network IDs would have an easy mapping to the DTN-specific
> addressing mechanism (Endpoint IDs per Section 4.2.5 of RFC9171).  I'll let the
> DTN experts correct me or provide more insight on the alignment.
> 
>     As an aside, there is a critical IANA issue with this document and it is being
> pulled from the planned telechat docket.
> 
>     Roman
> 
>     > -----Original Message-----
>     > From: Linda Dunbar <linda.dunbar@futurewei.com>
>     > Sent: Friday, October 21, 2022 12:46 PM
>     > To: Roman Danyliw <rdd@cert.org>; ops-dir@ietf.org
>     > Cc: acme@ietf.org; draft-ietf-acme-dtnnodeid.all@ietf.org; last-
> call@ietf.org
>     > Subject: Re: Opsdir telechat review of draft-ietf-acme-dtnnodeid-10
>     >
>     > Roman,
>     >
>     > Can the mechanism specified in the draft be used to validate the Virtual
>     > Network IDs of SD-WAN edge devices?
>     > For example, an SDWAN edge deployed in a remote site, say a shopping
> mall,
>     > might advertise the routes and client VPN IDs to the BGP Route-Reflector
> (RR).
>     > The RR needs to validate the Client's IDs are legitimate. Can the mechanism
>     > specified in the draft do the job?
>     >
>     > Thanks, Linda
>     >
>     >
>     > On 10/20/22, 10:36 PM, "Linda Dunbar" <linda.dunbar@futurewei.com>
>     > wrote:
>     >
>     >     Roman,
>     >
>     >     With you bringing back the explanation, all makes sense to me now.
> Wish
>     > your explanation is incorporated into the document.
>     >     Thanks, Linda
>     >
>     >     On 10/20/22, 6:53 PM, "Roman Danyliw" <rdd@cert.org> wrote:
>     >
>     >         Thanks for the re-review Linda.
>     >
>     >         ACME WG: here is the thread from the IETF LC where proposed
> changes
>     > were discussed:
>     >
> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmailarc
>     > hive.ietf.org%2Farch%2Fmsg%2Flast-
>     >
> call%2FnujBgHd6ZKHY6fG58ZWBKzFGVWs%2F&amp;data=05%7C01%7Clinda.
>     >
> dunbar%40futurewei.com%7C3d47157879904a302e3008dab2f65009%7C0fee
>     >
> 8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C638019068235813966%7CUn
>     >
> known%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik
>     >
> 1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=t83ICajIF%2FEIKz
>     > ibHtGs0T9FFSQpSFmBxKdxxgGHkPY%3D&amp;reserved=0
>     >
>     >         > -----Original Message-----
>     >         > From: Linda Dunbar via Datatracker <noreply@ietf.org>
>     >         > Sent: Thursday, October 20, 2022 6:55 PM
>     >         > To: ops-dir@ietf.org
>     >         > Cc: acme@ietf.org; draft-ietf-acme-dtnnodeid.all@ietf.org; last-
>     > call@ietf.org
>     >         > Subject: Opsdir telechat review of draft-ietf-acme-dtnnodeid-10
>     >         >
>     >         > 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
>     >         >
>     >
>     >
>