Re: [DNSOP] [Ext] Fwd: Working Group Last Call for draft-ietf-dnsop-rfc5933-bis

Paul Hoffman <paul.hoffman@icann.org> Thu, 14 April 2022 21:09 UTC

Return-Path: <paul.hoffman@icann.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CCE883A18CC; Thu, 14 Apr 2022 14:09:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7C52ziqIdgGA; Thu, 14 Apr 2022 14:09:08 -0700 (PDT)
Received: from ppa3.lax.icann.org (ppa3.lax.icann.org [192.0.33.78]) (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 6BE543A18CA; Thu, 14 Apr 2022 14:09:08 -0700 (PDT)
Received: from MBX112-W2-CO-1.pexch112.icann.org (out.mail.icann.org [64.78.33.5]) by ppa3.lax.icann.org (8.16.0.43/8.16.0.43) with ESMTPS id 23EL96aE032056 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 14 Apr 2022 21:09:06 GMT
Received: from MBX112-W2-CO-1.pexch112.icann.org (10.226.41.128) by MBX112-W2-CO-2.pexch112.icann.org (10.226.41.130) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.986.22; Thu, 14 Apr 2022 14:09:05 -0700
Received: from MBX112-W2-CO-1.pexch112.icann.org ([10.226.41.128]) by MBX112-W2-CO-1.pexch112.icann.org ([10.226.41.128]) with mapi id 15.02.0986.022; Thu, 14 Apr 2022 14:09:05 -0700
From: Paul Hoffman <paul.hoffman@icann.org>
To: dnsop-chairs <dnsop-chairs@ietf.org>
CC: dnsop <dnsop@ietf.org>
Thread-Topic: [Ext] [DNSOP] Fwd: Working Group Last Call for draft-ietf-dnsop-rfc5933-bis
Thread-Index: AQHYF6ti2Q2uhoukek2t25cf+8tgw6zwzcCA
Date: Thu, 14 Apr 2022 21:09:05 +0000
Message-ID: <D0737445-5AF5-4079-9B8B-71E6890C5C29@icann.org>
References: <CADyWQ+Fch-C8LPCEHkouRxCnkMcpMeh7bmQRPTXRwodx01xWNw@mail.gmail.com> <CADyWQ+F-oop9Cvo7nNF-O86vvJhNVrNs2AdBytnith3+JzGCdQ@mail.gmail.com>
In-Reply-To: <CADyWQ+F-oop9Cvo7nNF-O86vvJhNVrNs2AdBytnith3+JzGCdQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [192.0.32.234]
x-source-routing-agent: Processed
Content-Type: multipart/signed; boundary="Apple-Mail=_59065514-AB72-4D73-8586-930967F948A0"; protocol="application/pkcs7-signature"; micalg="sha-256"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.486, 18.0.858 definitions=2022-04-14_05:2022-04-14, 2022-04-14 signatures=0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/ApKUYBBLg_KAP3CDXFcMZ-9AvQ0>
Subject: Re: [DNSOP] [Ext] Fwd: Working Group Last Call for draft-ietf-dnsop-rfc5933-bis
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Apr 2022 21:09:10 -0000

On Feb 1, 2022, at 12:35 PM, Tim Wicinski <tjw.ietf@gmail.com> wrote:
> We were reviewing the Working Group Last Call for this, and we received no comments.  We know there was interest in at least moving this forward, but even Warren concurred we can't send this to the IESG unless there are folks saying they feel it is ready to be published.

That was a few months ago. There were only two responses, one negative, one blandly positive ("seems reasonable"). 

Can the chairs please say what they expect to do with this draft? I ask because it is directly relevant to draft-ietf-dnsop-dnssec-bcp, where the draft's predecessor is mentioned.

--Paul Hoffman