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

Suzanne Woolf <suzworldwide@gmail.com> Fri, 09 October 2015 19:58 UTC

Return-Path: <suzworldwide@gmail.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 6ED351ABD3D for <dnsop@ietfa.amsl.com>; Fri, 9 Oct 2015 12:58:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 YiidISTScF8P for <dnsop@ietfa.amsl.com>; Fri, 9 Oct 2015 12:58:18 -0700 (PDT)
Received: from mail-qg0-x22b.google.com (mail-qg0-x22b.google.com [IPv6:2607:f8b0:400d:c04::22b]) (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 279BA1ABD36 for <dnsop@ietf.org>; Fri, 9 Oct 2015 12:58:18 -0700 (PDT)
Received: by qgew37 with SMTP id w37so19483871qge.0 for <dnsop@ietf.org>; Fri, 09 Oct 2015 12:58:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=xO2TGTrWnKd68tnN+CL6GEc0z1Jef+K8oqdpU99h5FA=; b=aHLzwnWjK5MGpsDxsORpgiQ6uYaENbq+bCyYpoxKHYfv55MqLR8MIMkGWNgz8+hG+r f354Z9sK7D9Ss98BPrG0m53Y025uWQeAhOKYMhx8BnQGI7dEuVopjRMsvjSJeb+R+ysk UYCsd5sF3VnbdhRSVsh3dIeXHUivK096jHTFJxQyiYnevejBtQlGMa+/YsUMfi83bond xI7P0C5agseNfrk7jyxD87YZhWjoxMZTr8K5Y4zc+U9I2HBC4cbpMVOaOX5KGaQ6nsqs 82VY++Ah7rtVGflyfbU2LttXkp7U3wGzY64fDBF+xSyXIRM4JuOUZ5YjJbQclL+49O7d frJg==
X-Received: by 10.140.93.47 with SMTP id c44mr5486881qge.59.1444420697190; Fri, 09 Oct 2015 12:58:17 -0700 (PDT)
Received: from ?IPv6:2601:181:c002:25ee:d4:36bc:8239:7e47? ([2601:181:c002:25ee:d4:36bc:8239:7e47]) by smtp.gmail.com with ESMTPSA id f200sm1343032qhe.7.2015.10.09.12.58.16 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 09 Oct 2015 12:58:16 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Suzanne Woolf <suzworldwide@gmail.com>
In-Reply-To: <F5A8CCB7-5E1C-4547-AD55-1EDE286E59C7@hopcount.ca>
Date: Fri, 09 Oct 2015 15:58:35 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <EC977C23-5F19-4866-BFD7-95234AC607D6@gmail.com>
References: <20151009011039.36478.qmail@ary.lan> <90410066-79B0-4DDE-89F7-CE2BB5DA2307@karoshi.com> <E6CCA2DC-7EA6-40BC-BBFE-EAE3505589A3@hopcount.ca> <790654E4-3EF8-44B3-BD92-638EACA0959A@karoshi.com> <F5A8CCB7-5E1C-4547-AD55-1EDE286E59C7@hopcount.ca>
To: Joe Abley <jabley@hopcount.ca>
X-Mailer: Apple Mail (2.1510)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/JZvCC9kcegLjxXh4dwd1AnSRvGM>
Cc: John Levine <johnl@taugh.com>, dnsop@ietf.org, manning <bmanning@karoshi.com>
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: Fri, 09 Oct 2015 19:58:19 -0000

On Oct 9, 2015, at 12:30 PM, Joe Abley <jabley@hopcount.ca> wrote:

> On 9 Oct 2015, at 12:20, manning wrote:
> 
>> On 9October2015Friday, at 4:41, Joe Abley <jabley@hopcount.ca> wrote:
>> 
>>> Aside from the motivation to provide a useful technical specification in a place where it can be easily found, I continue to feel that it is important that significant infrastructural elements of the Internet be described in the RFC series, even if they don't contain IETF working group output. This is our historical record. We would be doing a disservice to future enquiring minds if we chose to do otherwise.
>> 
>> [...]
>> 
>> It does beg the question however, why is this even being discussed in an IETF WG if its not expected to be IETF WG product?
> 
> My assumption was that there's value in awareness in this venue, and that any competent shepherd will require positive indications of review from the relevant technical community, and this is it. Apologies if people feel differently, though; despite appearances to the contrary, I'm not simply on a mission to drown everybody in mail.

Please note for the record that the chairs supported this course of action.

This wasn't the first time that WG discussion seemed useful for a document that would benefit from review in the WG even though not a WG document. It will not, I hope, be the last.

> So to clear up the lingering ambiguity, the authors are not requesting adoption of this document by the working group; we'll pick it up with the ISE. I will be bothering those who have demonstrated an opinion in due course for reviews for Nevil.

This sounds like the right course of action to me from what we've seen here.

thanks,
Suzanne