Re: [DNSOP] Call for Adoption for draft-wessels-edns-key-tag

"Wessels, Duane" <dwessels@verisign.com> Mon, 30 November 2015 17:30 UTC

Return-Path: <dwessels@verisign.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 13D4A1B29F0 for <dnsop@ietfa.amsl.com>; Mon, 30 Nov 2015 09:30:03 -0800 (PST)
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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1] autolearn=ham
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 YrQS82Liy0zG for <dnsop@ietfa.amsl.com>; Mon, 30 Nov 2015 09:30:00 -0800 (PST)
Received: from mail-oi0-x261.google.com (mail-oi0-x261.google.com [IPv6:2607:f8b0:4003:c06::261]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 442881B2A1A for <dnsop@ietf.org>; Mon, 30 Nov 2015 09:29:56 -0800 (PST)
Received: by oiww189 with SMTP id w189so10749339oiw.2 for <dnsop@ietf.org>; Mon, 30 Nov 2015 09:29:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=verisign-com.20150623.gappssmtp.com; s=20150623; h=from:to:cc:subject:thread-topic:thread-index:date:message-id :references:in-reply-to:accept-language:content-language :content-type:content-id:content-transfer-encoding:mime-version; bh=34ApPnEatp3/wj7f+/wIq6VfRusfbQ06JoUlZQjz3C8=; b=azAu+K/ntPSTtC8V/UKgNvSD4I6KtVMFXvLuv3sXrBby8+TFYp1zBnl9CK+oBH5ifm +Y0gBCbgqo0UGSd7v1afLkgNFjemtHnPpkjtFrnPc22opytHMeFDFmmkaCAZM8hZ2JBw NZotVOCmnwpLKyVA55x7U2M6PBa73WV6zbG9uFPWOARvlyQ88V6a5gEbN5rch9jPlsTP 3VdLeGDo/xofJAIEQ0smpWO0RRVJGY34FUi9fZdkYeZjlztlsQjBQz19tmiNwfcmWYUe 6/6Z5fXfRx1idDo9+Ad+CyjPtQ2tWlJNZuWnQFlaO9AVj0a97eGIFL9oDki7WoLyTWzG a3cA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:thread-topic:thread-index :date:message-id:references:in-reply-to:accept-language :content-language:content-type:content-id:content-transfer-encoding :mime-version; bh=34ApPnEatp3/wj7f+/wIq6VfRusfbQ06JoUlZQjz3C8=; b=i8wtB6FYTCIJ9uBCUUQDrHwiWcCWbQ0msyz5vdx4u+y9vjwXQk9QnbIVzSubk9xvU4 VG6HYEcZ3vH4F83YGwImUSs0lOy3yUKwmLf2ZJNTKCp6zhz18E6m+Ww0rOYjiGrXbw2M 9FlBSwolKfN2Rk7FW2oBaMThMAnXDZBQJsA/wDbzYnJrhukjV17SNtSbq69QjN8FyrYI Jm4CIrQRBVs11FHEYUVx7pTLlHMjxOKXmsw2Q3RQgNatnPRWlXnKf2lq9u8LMc9egi9z QNLZljOZQa8xM8XnJIsp01FJ4RtvjdRyVCFv8OB/aJTGg9ET1ob4FOIsAIHpl/L+XWDV ZgFQ==
X-Gm-Message-State: ALoCoQnAz/AXwZDkaJ3ZjSYFfR3X3WZluXuS2hY+Cr4RZKaSQl5mfZqk3BU1FV9oadov+F1jfEMJg8rI6w3VP5Ie97bKIHm7yg==
X-Received: by 10.140.235.212 with SMTP id g203mr32029952qhc.11.1448904595558; Mon, 30 Nov 2015 09:29:55 -0800 (PST)
Received: from brn1lxmailout01.verisign.com (brn1lxmailout01.verisign.com. [72.13.63.41]) by smtp-relay.gmail.com with ESMTPS id z201sm5695760qka.1.2015.11.30.09.29.55 (version=TLS1 cipher=AES128-SHA bits=128/128); Mon, 30 Nov 2015 09:29:55 -0800 (PST)
X-Relaying-Domain: verisign.com
Received: from BRN1WNEXCHM01.vcorp.ad.vrsn.com (brn1wnexchm01 [10.173.152.255]) by brn1lxmailout01.verisign.com (8.13.8/8.13.8) with ESMTP id tAUHTts0005864 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 30 Nov 2015 12:29:55 -0500
Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by BRN1WNEXCHM01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0174.001; Mon, 30 Nov 2015 12:29:54 -0500
From: "Wessels, Duane" <dwessels@verisign.com>
To: Mark Andrews <marka@isc.org>
Thread-Topic: [DNSOP] Call for Adoption for draft-wessels-edns-key-tag
Thread-Index: AQHRKdqr1OqvHxjgs0S6Ecws+GvPd56z4YRXgAFICQA=
Date: Mon, 30 Nov 2015 17:29:53 +0000
Message-ID: <4BDC4E85-3A98-4120-991B-EDE20E923ADD@verisign.com>
References: <5659A1DB.5090102@gmail.com> <20151130025526.1FF813DBD937@rock.dv.isc.org>
In-Reply-To: <20151130025526.1FF813DBD937@rock.dv.isc.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.173.152.4]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <0ED96E3A9EA7CA438BD119978B5A6954@verisign.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/sjPPstFw-sxK-a5mQGVn4Dn3Els>
Cc: Tim Wicinski <tjw.ietf@gmail.com>, dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] Call for Adoption for draft-wessels-edns-key-tag
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
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: Mon, 30 Nov 2015 17:30:03 -0000

Hi Mark,


> On Nov 29, 2015, at 6:55 PM, Mark Andrews <marka@isc.org> wrote:
> 
> 
> 
> Some feedback with respect to installed trust anchors is needed.
> 
> Whether this is the correct solution I'm not sure.  It requires
> updating all resolvers in the resolution path to both cache and
> relay tags.

I'm not sure where you got the idea that a resolver would cache key tags.
The document I've drafted does not propose that.  It does propose that
a recursive would forward key tag values for cache misses.

>  The same can be achieved by encoding the tags into
> qnames/qtypes

Yes, perhaps.  But then we start to run into all the problems of special
use and non-service names, don't we?

As I've said a number of times before, the edns-key-tag proposal is modelled
after RFC 6975, which does the same thing for algorithms.  If it works for
algorithms why wouldn't it work for key tags?

> without needing the entire ecosystem to be upgraded
> which this proposal requires.

I disagree with this characterization that "the entire ecosystem" needs
to be upgraded.  Yes a non-key-tag-aware recursive won't know to forward
the option, but this is true for all EDNS options.


DW


> 
> e.g.
> 	_ta_<base32-tag-sequence>.<trustanchor>/NULL
> 
> Mark
> 
> In message <5659A1DB.5090102@gmail.com>om>, Tim Wicinski writes:
>> 
>> This starts a Call for Adoption for draft-wessels-edns-key-tag
>> 
>> The draft is available here:
>> https://datatracker.ietf.org/doc/draft-wessels-edns-key-tag/
>> 
>> There was unanimous support this during the meeting in Yokohama, so this 
>> is more of a formality, unless we hear strong negative reaction.
>> 
>> However, please indicate if you are willing to contribute text, review, etc.
>> 
>> Since there was unanimous support for this draft, I am going with a one 
>> week Call for Adoption. Please feel free to protest if anyone feels this 
>> is out of line.
>> 
>> This call for adoption ends 7 December 2015.
>> 
>> Thanks,
>> tim wicinski
>> DNSOP co-chair
>> 
>> _______________________________________________
>> DNSOP mailing list
>> DNSOP@ietf.org
>> https://www.ietf.org/mailman/listinfo/dnsop
> -- 
> Mark Andrews, ISC
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org
> 
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop