Re: [DNSOP] I-D Action: draft-ietf-dnsop-edns-key-tag-02.txt

"Paul Hoffman" <paul.hoffman@vpnc.org> Wed, 10 August 2016 23:54 UTC

Return-Path: <paul.hoffman@vpnc.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 CF78B12D13A for <dnsop@ietfa.amsl.com>; Wed, 10 Aug 2016 16:54:43 -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] 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 HqEkNm0rYDvQ for <dnsop@ietfa.amsl.com>; Wed, 10 Aug 2016 16:54:42 -0700 (PDT)
Received: from mail.proper.com (Opus1.Proper.COM [207.182.41.91]) (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 6AE7B12D0D3 for <dnsop@ietf.org>; Wed, 10 Aug 2016 16:54:42 -0700 (PDT)
Received: from [10.32.60.150] (50-1-98-193.dsl.dynamic.fusionbroadband.com [50.1.98.193]) (authenticated bits=0) by mail.proper.com (8.15.2/8.14.9) with ESMTPSA id u7ANsdnr003900 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <dnsop@ietf.org>; Wed, 10 Aug 2016 16:54:40 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: mail.proper.com: Host 50-1-98-193.dsl.dynamic.fusionbroadband.com [50.1.98.193] claimed to be [10.32.60.150]
From: Paul Hoffman <paul.hoffman@vpnc.org>
To: dnsop@ietf.org
Date: Wed, 10 Aug 2016 16:54:39 -0700
Message-ID: <9E342C42-7649-4776-BA22-DF9F5A84654A@vpnc.org>
In-Reply-To: <8FD4B2FF-9E51-4FF3-829A-1D4D7CFAB19E@vpnc.org>
References: <20160708223044.32131.72663.idtracker@ietfa.amsl.com> <8FD4B2FF-9E51-4FF3-829A-1D4D7CFAB19E@vpnc.org>
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"
X-Mailer: MailMate (1.9.4r5234)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/QdGszkGCZ0x-jsJvdv0tscSPpTA>
Subject: Re: [DNSOP] I-D Action: draft-ietf-dnsop-edns-key-tag-02.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.17
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: Wed, 10 Aug 2016 23:54:44 -0000

[[ A month later, we're still eager to hear responses to the draft. We 
got a few that we have incorporated for a new version, but want to be 
sure we're on the right track before we move ahead. ]]

On 8 Jul 2016, at 15:36, Paul Hoffman wrote:

> Greetings again; I'm the new co-author on this draft. Based on the WG 
> discussion where a bunch of us wanted to use EDNS0 and a bunch of us 
> wanted to use queries, the authors tentatively decided that the best 
> way to go forwards is to put both methods in the draft. After all, a 
> motivated observer of the signals will not have much problem watching 
> both types of signals, and end systems can decide which of the two 
> they want to use.
>
> We understand that "specify more than one" is often an unpopular 
> choice in the IETF, about as unpopular as "don't get consensus on 
> one". This is a WG document so we need consensus even to go with two 
> ways. We look forward to hearing from you about this choice and how we 
> can move forwards.
>
> --Paul Hoffman
>
>
> On 8 Jul 2016, at 15:30, internet-drafts@ietf.org wrote:
>
>> A New Internet-Draft is available from the on-line Internet-Drafts 
>> directories.
>> This draft is a work item of the Domain Name System Operations of the 
>> IETF.
>>
>>         Title           : Signaling Trust Anchor Knowledge in DNS 
>> Security Extensions (DNSSEC)
>>         Authors         : Duane Wessels
>>                           Warren Kumari
>>                           Paul Hoffman
>> 	Filename        : draft-ietf-dnsop-edns-key-tag-02.txt
>> 	Pages           : 13
>> 	Date            : 2016-07-08
>>
>> Abstract:
>>    The DNS Security Extensions (DNSSEC) were developed to provide 
>> origin
>>    authentication and integrity protection for DNS data by using 
>> digital
>>    signatures.  These digital signatures can be verified by building 
>> a
>>    chain-of-trust starting from a trust anchor and proceeding down to 
>> a
>>    particular node in the DNS.  This document specifies two different
>>    ways for validating resolvers to signal to a server which keys are
>>    referenced in their chain-of-trust.  The data from such signaling
>>    allow zone administrators to monitor the progress of rollovers in 
>> a
>>    DNSSEC-signed zone.
>>
>>    This document describes two independent methods for validating
>>    resolvers to publish their referenced keys: an EDNS option and a
>>    differnt DNS query.  The reason there are two methods instead of 
>> one
>>    is some people see significant problems with each method.  Having 
>> two
>>    methods is clearly worse than having just one, but it is probably
>>    better for the Internet than having no way to gain the information
>>    from the resolvers.
>>
>>
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-dnsop-edns-key-tag/
>>
>> There's also a htmlized version available at:
>> https://tools.ietf.org/html/draft-ietf-dnsop-edns-key-tag-02
>>
>> A diff from the previous version is available at:
>> https://www.ietf.org/rfcdiff?url2=draft-ietf-dnsop-edns-key-tag-02
>>
>>
>> Please note that it may take a couple of minutes from the time of 
>> submission
>> until the htmlized version and diff are available at tools.ietf.org.
>>
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>
>> _______________________________________________
>> DNSOP mailing list
>> DNSOP@ietf.org
>> https://www.ietf.org/mailman/listinfo/dnsop
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop