IETF Logo Mail Archive

Re: [DNSOP] [Ext] Authoritative servers announcing capabilities

Paul Hoffman <paul.hoffman@icann.org> Fri, 11 September 2020 23:39 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 0F1083A096B for <dnsop@ietfa.amsl.com>; Fri, 11 Sep 2020 16:39:49 -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 JtBnuhsuYo5Y for <dnsop@ietfa.amsl.com>; Fri, 11 Sep 2020 16:39:47 -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 D9DFA3A091F for <dnsop@ietf.org>; Fri, 11 Sep 2020 16:39:45 -0700 (PDT)
Received: from MBX112-W2-CO-2.pexch112.icann.org (out.mail.icann.org [64.78.33.6]) by ppa3.lax.icann.org (8.16.0.42/8.16.0.42) with ESMTPS id 08BNdj2c016611 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 11 Sep 2020 23:39:45 GMT
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 Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.659.4; Fri, 11 Sep 2020 16:39:43 -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; Fri, 11 Sep 2020 16:39:43 -0700
From: Paul Hoffman <paul.hoffman@icann.org>
To: Patrick Mevzek <mevzek@uniregistry.com>
CC: "dnsop@ietf.org" <dnsop@ietf.org>
Thread-Topic: [Ext] [DNSOP] Authoritative servers announcing capabilities
Thread-Index: AQHWiJTT3kTySmE+lkWi9qm2+ABhug==
Date: Fri, 11 Sep 2020 23:39:43 +0000
Message-ID: <815E7487-C48D-4120-AD22-C77D893EB6E7@icann.org>
References: <676DE8DE-DA20-4162-B81C-C358DC7084E7@icann.org> <294f8ab0-285b-d5f2-705f-5db8c0da584d@uniregistry.com>
In-Reply-To: <294f8ab0-285b-d5f2-705f-5db8c0da584d@uniregistry.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=_6412159C-EE8B-4A46-AAA8-020080C61B27"; 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-11_12:2020-09-10, 2020-09-11 signatures=0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/CFhqiEOwQUt5sh4EMVskHa_S7HA>
Subject: Re: [DNSOP] [Ext] Authoritative servers announcing capabilities
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: Fri, 11 Sep 2020 23:39:49 -0000

On Sep 11, 2020, at 4:24 PM, Patrick Mevzek <mevzek@uniregistry.com> wrote:
> 
> On 11/09/2020 15:37, Paul Hoffman wrote:
>> Greetings. Puneet and I have an new draft, <https://urldefense.com/v3/__https://tools.ietf.org/html/draft-pp-dnsop-authinfo__;!!PtGJab4!tA3Rg8zYWrkxVj0XhVFgOSw3njnqVfZ1lZb89fZi40rNWqnTDHsqJvazW8HMMZej0qCL5X79cg$ >, that we would like DNSOP to consider. From the abstract:
>>   This document defines a new DNS RRtype, AUTHINFO, that is used by
> 
> [..]
> 
>> We would like DNSOP to adopt this, and of course we are open to suggestions on how to improve the protocol.
> 
> I know it is unrelated, but EPP uses authInfo term extensively (for authentication purposes and in practice basically as synonym of "password"), so I really recommend using another name for this record type, because otherwise I am pretty sure somewhere somehow someone will confuse both things.

The name can be bikeshedded, but "authinfo" is used in multiple protocols because it is quite descriptive.

> Plus, why couldn't this be extended in the future to recursive nameservers as well? In which case, the name should be resolver genre agnostic.

There is already a draft for RESINFO. The difference is important, because a single host might be both a resolver and an authoritative server.

> Maybe something like "CAPABILITIES" or "ABILITIES"?
> (or shorter version)

And you're thinking those aren't used in other protocols? :-)

--Paul Hoffman

v2.23.0 | Report a Bug | By Email