IETF Logo Mail Archive

Re: [DNSOP] [Ext] Call for Adoption: draft-hoffman-dns-terminology-ter

Paul Hoffman <paul.hoffman@icann.org> Thu, 01 August 2019 16:21 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 1D6DF120193 for <dnsop@ietfa.amsl.com>; Thu, 1 Aug 2019 09:21:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 0H0JYfhf4S8G for <dnsop@ietfa.amsl.com>; Thu, 1 Aug 2019 09:21:45 -0700 (PDT)
Received: from out.west.pexch112.icann.org (out.west.pexch112.icann.org [64.78.40.7]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 81F871200E0 for <dnsop@ietf.org>; Thu, 1 Aug 2019 09:21:45 -0700 (PDT)
Received: from PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) by PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 1 Aug 2019 09:21:43 -0700
Received: from PMBX112-W1-CA-1.pexch112.icann.org ([64.78.40.21]) by PMBX112-W1-CA-1.PEXCH112.ICANN.ORG ([64.78.40.21]) with mapi id 15.00.1473.005; Thu, 1 Aug 2019 09:21:43 -0700
From: Paul Hoffman <paul.hoffman@icann.org>
To: dnsop <dnsop@ietf.org>
Thread-Topic: [Ext] [DNSOP] Call for Adoption: draft-hoffman-dns-terminology-ter
Thread-Index: AQHVSIN25uXqgTnEWkmck9+OapJ/7Kbm7roA
Date: Thu, 01 Aug 2019 16:21:42 +0000
Message-ID: <D738CECC-BAD2-4686-8B06-AC055FD10610@icann.org>
References: <CADyWQ+Eu+bGRGi7C=5d5NQGq-11Bt8ZPbDYcr8wGtujwKEWK5w@mail.gmail.com>
In-Reply-To: <CADyWQ+Eu+bGRGi7C=5d5NQGq-11Bt8ZPbDYcr8wGtujwKEWK5w@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [192.0.32.234]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <B08E35B00BA1184FB4D19ACC6B8426DC@pexch112.icann.org>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/bqOtRIug2lC9V-hnHfnmaENbTDA>
Subject: Re: [DNSOP] [Ext] Call for Adoption: draft-hoffman-dns-terminology-ter
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, 01 Aug 2019 16:21:47 -0000

On Aug 1, 2019, at 9:08 AM, Tim Wicinski <tjw.ietf@gmail.com> wrote:
> 
> 
> Back in 2014, we started with "DNS Terminology" which became RFC7719
> Then In 2016, this became a BCP version of "DNS Terminology" which is now RFC8499
> 
> Now, in 2109, there is a request to include additional terms to reflect
> the new transports DNS is being used over.    There is still discussion over 
> whether all these terms make sense, but the underlying need exists.
> 
> This starts a Call for Adoption for draft-hoffman-dns-terminology-ter
> 
> The draft is available here: https://datatracker.ietf.org/doc/draft-hoffman-dns-terminology-ter/
> 
> 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: 15 August 2019

FWIW, some people where asking for changes in the -01 version even after the -02 came out. As a WG document, the content will belong to the WG, and I'm happy to make whatever changes the WG wants. (FWIW2: that is the way all WG documents are supposed to work....)

--Paul Hoffman

v2.23.0 | Report a Bug | By Email