IETF Logo Mail Archive

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

Paul Hoffman <paul.hoffman@icann.org> Sat, 12 September 2020 02:26 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 064A83A0A82 for <dnsop@ietfa.amsl.com>; Fri, 11 Sep 2020 19:26:22 -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 4CfSCugYnvYV for <dnsop@ietfa.amsl.com>; Fri, 11 Sep 2020 19:26:20 -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 CB98A3A0A7E for <dnsop@ietf.org>; Fri, 11 Sep 2020 19:26:20 -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 08C2QJtp008155 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sat, 12 Sep 2020 02:26:20 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; Fri, 11 Sep 2020 19:26:18 -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 19:26:18 -0700
From: Paul Hoffman <paul.hoffman@icann.org>
To: John Levine <johnl@taugh.com>
CC: "dnsop@ietf.org" <dnsop@ietf.org>
Thread-Topic: [DNSOP] [Ext] Authoritative servers announcing capabilities
Thread-Index: AQHWiKvEkTwEuqKA9Uy2/6v0BBnHSalkvDIA
Date: Sat, 12 Sep 2020 02:26:18 +0000
Message-ID: <A9FAB272-BDF6-4584-8175-0DD3D561AEB2@icann.org>
References: <676DE8DE-DA20-4162-B81C-C358DC7084E7@icann.org> <294f8ab0-285b-d5f2-705f-5db8c0da584d@uniregistry.com> <2B4B3FF6-44D4-4F08-81D2-718FD33A7CF0@isc.org> <92CA6178-FE2D-407E-97FB-A9E44E2647C7@icann.org> <rjhbfc$2ghk$1@gal.iecc.com>
In-Reply-To: <rjhbfc$2ghk$1@gal.iecc.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=_74B82B07-6D7D-4707-B0CE-73CF1718625A"; 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/8_FFxNsxWkQ2ahW5aJEdvd3Vlo4>
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: Sat, 12 Sep 2020 02:26:22 -0000

On Sep 11, 2020, at 7:23 PM, John Levine <johnl@taugh.com> wrote:
> 
> In article <92CA6178-FE2D-407E-97FB-A9E44E2647C7@icann.org>,
> Paul Hoffman  <paul.hoffman@icann.org> wrote:
>> On Sep 11, 2020, at 4:40 PM, Mark Andrews <marka@isc.org> wrote:
>>> 
>>> and why is it a RR type at all.
>> 
>> So that the answer can be signed and thus validated.
> 
> It looks to me like all of the servers for a particular zone would
> have to return the same AUTHINFO, which seems like a bad idea since
> they don't necessarily all have the same features.

At this point, the only information we defined in the draft is for doing client subnet. If there are server sets for a single zone where some do client subnet, and others don't, then your concern is valid. Changing this to an uncacheable, unverifiable EDNS option is easy.

--Paul Hoffman

v2.23.0 | Report a Bug | By Email