Re: [DNSOP] [Ext] Call for Adoption: RFC8499-bis

Paul Hoffman <paul.hoffman@icann.org> Sat, 26 September 2020 15:06 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 4DE043A046A for <dnsop@ietfa.amsl.com>; Sat, 26 Sep 2020 08:06:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 1SfoD-alavmU for <dnsop@ietfa.amsl.com>; Sat, 26 Sep 2020 08:06:28 -0700 (PDT)
Received: from ppa4.dc.icann.org (ppa4.dc.icann.org [192.0.46.77]) (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 ED3813A044A for <dnsop@ietf.org>; Sat, 26 Sep 2020 08:06:27 -0700 (PDT)
Received: from MBX112-E2-CO-1.pexch112.icann.org (out.mail.icann.org [64.78.33.7]) by ppa4.dc.icann.org (8.16.0.42/8.16.0.42) with ESMTPS id 08QF6QjB025674 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <dnsop@ietf.org>; Sat, 26 Sep 2020 15:06:26 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.659.4; Sat, 26 Sep 2020 08:06:25 -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.0659.006; Sat, 26 Sep 2020 08:06:25 -0700
From: Paul Hoffman <paul.hoffman@icann.org>
To: dnsop <dnsop@ietf.org>
Thread-Topic: [Ext] [DNSOP] Call for Adoption: RFC8499-bis
Thread-Index: AQHWk0/ojmL4xzx2YkG1YkPUhPV91al7e+sA
Date: Sat, 26 Sep 2020 15:06:24 +0000
Message-ID: <FC265476-6EB4-4459-B8C4-542AC77092D6@icann.org>
References: <CADyWQ+HO1fjuBWTmNNr1F4ydc=KPPpCeg01WTKsNaeNH0F2QJA@mail.gmail.com>
In-Reply-To: <CADyWQ+HO1fjuBWTmNNr1F4ydc=KPPpCeg01WTKsNaeNH0F2QJA@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=_E72E9D7B-50A5-4B0D-81D1-1224C105D192"; protocol="application/pkcs7-signature"; micalg=sha-256
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.235, 18.0.687 definitions=2020-09-26_11:2020-09-24, 2020-09-26 signatures=0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/gFN5jxxY6qlsgJVKX0sjPQlprHU>
Subject: Re: [DNSOP] [Ext] Call for Adoption: RFC8499-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: Sat, 26 Sep 2020 15:06:29 -0000

On Sep 25, 2020, at 8:23 AM, Tim Wicinski <tjw.ietf@gmail.com> wrote:
> 
> 
> During the IETF108 meeting, it was brought up by the chairs that we have been talking to the authors of RFC8499 on updating the document.  We propose these steps: 
> 
> - Update some of the current language in the existing RFC8499
> 
> - Add new terms draft-ietf-dnsop-terminology-ter on which the WG agrees
> 
> - Reach consensus and be ready for the Working Group Last Call in the IETF109 timeframe. 
> 
> 
> This starts a Call for Adoption for RFC8499-bis
> 
> Current text is https://tools.ietf.org/html/rfc8499 and the current terminology additions are https://tools.ietf.org/html/draft-ietf-dnsop-terminology-ter-02
> 
> Please review this draft to see if you think it is suitable for adoption by DNSOP, and comments to the list, clearly stating your view.
> 
> Please also indicate if you are willing to contribute text, review, etc.
> 
> This call for adoption ends: 9 October 2020

Just a note: this could be easy and quick because we have heard almost nothing since the publication of RFC 8499 that needs significant revision. It really is about adding the few names from draft-ietf-dnsop-terminology-ter.

--Paul Hoffman