Re: [DNSOP] Fwd: New Version Notification for draft-pan-dnsop-swild-rr-type-00.txt

Dave Crocker <dhc2@dcrocker.net> Sat, 12 August 2017 16:55 UTC

Return-Path: <dhc2@dcrocker.net>
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 BC1D313244D for <dnsop@ietfa.amsl.com>; Sat, 12 Aug 2017 09:55:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.79
X-Spam-Level:
X-Spam-Status: No, score=-1.79 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=dcrocker.net
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 C6tk1mu1SLtF for <dnsop@ietfa.amsl.com>; Sat, 12 Aug 2017 09:55:21 -0700 (PDT)
Received: from simon.songbird.com (simon.songbird.com [72.52.113.5]) (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 6FD7613246D for <dnsop@ietf.org>; Sat, 12 Aug 2017 09:55:21 -0700 (PDT)
Received: from [192.168.1.168] (76-218-8-128.lightspeed.sntcca.sbcglobal.net [76.218.8.128]) (authenticated bits=0) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id v7CGtprf021318 (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256 verify=NOT); Sat, 12 Aug 2017 09:55:51 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=default; t=1502556951; bh=xjavGqwWf+6vWM0aix/948XqRKV59YsgLhV80xty7kE=; h=Subject:To:Cc:References:From:Reply-To:Date:In-Reply-To:From; b=h7z+VJ2XROK3ZTZqX2S4fnSNPSWN/0krco4gwUDmMHXmXe/9zUOyZC4R2MXuyY36Z BZEzqid7+QE9699x33nALspihnEhkzQvcByCVHAZwFWe0yDiEF+jiTsyZFroLDwmk5 oXmXIPFYV/cMyeYS1cYhtgLpSs8Y55m0fSYvy1yk=
To: Paul Vixie <paul@redbarn.org>
Cc: dnsop@ietf.org, Lanlan Pan <abbypan@gmail.com>, Petr Špaček <petr.spacek@nic.cz>, Paul Hoffman <paul.hoffman@vpnc.org>
References: <149908054910.760.8140876567010458934.idtracker@ietfa.amsl.com> <CAAiTEH8ntOerB6MGKMS2xcCK3TL9n4fyLq6F+bpUY6oTUpWN8w@mail.gmail.com> <CANLjSvWOzaJcVL64BhNFKnTUEgfq06TQtoy=ZNJ_JafvPU1aSA@mail.gmail.com> <1659363.yAWSxLQAC2@tums.local>
From: Dave Crocker <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
Reply-To: dcrocker@bbiw.net
Message-ID: <a636709f-5ee5-33e9-3af8-c9316634d8ef@dcrocker.net>
Date: Sat, 12 Aug 2017 09:55:13 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <1659363.yAWSxLQAC2@tums.local>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/b-mWqaNQYR9TL2Z-TEnaGM-Wrlg>
Subject: Re: [DNSOP] Fwd: New Version Notification for draft-pan-dnsop-swild-rr-type-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
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 Aug 2017 16:55:23 -0000

On 8/12/2017 8:42 AM, Paul Vixie wrote:
> we do, though, and we must. DNSSEC development began in 1996,


Hmmm.  As I recall, discussions on the topic began in 1990 and I thought 
I was cognizant AD, briefly, when the first working group was formed, 
after that.

I had understood that the IETF effort went through two false-starts in 
design before landing on the current design, but don't have an adequate 
sense of the milestone dates for these phases.

I note that the DNSSEC History Project should document this, in detail, 
but lacks dates(*)


d/

(*) https://wiki.tools.isoc.org/DNSSEC_History_Project

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net