Re: [DNSOP] Expiration impending: <draft-jabley-dnssec-trust-anchor-11.txt>

"Paul Hoffman" <paul.hoffman@vpnc.org> Thu, 08 October 2015 19:15 UTC

Return-Path: <paul.hoffman@vpnc.org>
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 5C59E1AC3E5 for <dnsop@ietfa.amsl.com>; Thu, 8 Oct 2015 12:15:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.347
X-Spam-Level:
X-Spam-Status: No, score=-1.347 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553] autolearn=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 KzRKlKNyIRHl for <dnsop@ietfa.amsl.com>; Thu, 8 Oct 2015 12:15:44 -0700 (PDT)
Received: from hoffman.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 411061AC3D2 for <dnsop@ietf.org>; Thu, 8 Oct 2015 12:15:44 -0700 (PDT)
Received: from [10.32.60.48] (50-1-51-139.dsl.dynamic.fusionbroadband.com [50.1.51.139]) (authenticated bits=0) by hoffman.proper.com (8.15.1/8.14.9) with ESMTPSA id t98JFf5Q025764 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 8 Oct 2015 12:15:42 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: hoffman.proper.com: Host 50-1-51-139.dsl.dynamic.fusionbroadband.com [50.1.51.139] claimed to be [10.32.60.48]
From: Paul Hoffman <paul.hoffman@vpnc.org>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
Date: Thu, 08 Oct 2015 12:15:40 -0700
Message-ID: <9956CC4C-E551-4A6A-9809-788CA93B659A@vpnc.org>
In-Reply-To: <20151008180817.GM17602@mx2.yitter.info>
References: <13F1D87F-1C07-40EB-86B0-564C4109C9B0@virtualized.org> <1973252D-924F-4EF1-A38F-5EC01AD331F6@gmail.com> <FDD04DCC-59C5-41F5-8CAF-1EF31CD65A34@virtualized.org> <63E1E01E-C172-4A0F-B434-F796546BB657@gmail.com> <C4FA9FA6-76E3-4FF3-862B-C5C0DF75C761@kirei.se> <D1C15986-603E-4932-B551-0497638D9849@vpnc.org> <02869F43-87A4-4797-8FD3-276C02DF665D@kirei.se> <EEA946B1-8BF3-4AB7-99D2-4C8CDCCF0EC0@vpnc.org> <20151008164015.GJ17602@mx2.yitter.info> <4BC462D4-F6B9-4AB1-A021-234218072562@virtualized.org> <20151008180817.GM17602@mx2.yitter.info>
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"
X-Mailer: MailMate (1.9.2r5141)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/bJEJVN-uS_awoNA3vuMNcG0vocI>
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] Expiration impending: <draft-jabley-dnssec-trust-anchor-11.txt>
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: Thu, 08 Oct 2015 19:15:49 -0000

On 8 Oct 2015, at 11:08, Andrew Sullivan wrote:

> On Thu, Oct 08, 2015 at 10:06:47AM -0700, David Conrad wrote:
>>
>> What am I missing?
>
>> From my POV, nothing.  Paul seemed to be suggesting that the current
> arrangements should be published somehow other than as "an IETF
> document".  Maybe he meant "send it up the Independent Submissions
> editor with ICANN staff on the top".  I don't really know.

I did. To me, an organization that wants to publish its procedures 
should do so itself. If that organization wants to duplicate those 
procedures in the RFC series, then it should do so through the ISE, not 
wasting the time of the IETF.

> If that is what he meant, then I think the distinction is not that
> interesting.  IME nobody except a tiny fraction of IETF participants
> makes the ISE/IETF product distinction.

My preference is not because of the distinction of the series, but in 
the review process. I am sure that, no matter how often we say "this is 
documenting current practice only", people in the IETF will want to make 
changes based on different design preferences. That is a waste of 
everyone's time.

> If it's not what he meant, then I see no value in creating a new
> publication path.

Agree. (Mind you, if ICANN published many procedure documents in the RFC 
series, it might be worth considering having an ICANN stream in the 
future, but that consideration is likely to cause so much consternation 
it is not worth trying.)

> IMO, what is current practice, whatever it is, ought to be in the
> document.

Fully agree.

--Paul Hoffman