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

Shane Kerr <shane@time-travellers.org> Mon, 28 September 2015 12:15 UTC

Return-Path: <shane@time-travellers.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 E40411A8AB4 for <dnsop@ietfa.amsl.com>; Mon, 28 Sep 2015 05:15:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.501
X-Spam-Level:
X-Spam-Status: No, score=-0.501 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, SPF_HELO_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 F8G9FESIJKeN for <dnsop@ietfa.amsl.com>; Mon, 28 Sep 2015 05:15:14 -0700 (PDT)
Received: from time-travellers.nl.eu.org (c.time-travellers.nl.eu.org [IPv6:2a02:2770::21a:4aff:fea3:eeaa]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A84BD1A8AAF for <dnsop@ietf.org>; Mon, 28 Sep 2015 05:15:14 -0700 (PDT)
Received: from [2001:610:719:1:fd64:c277:8bb4:4560] (helo=casual) by time-travellers.nl.eu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <shane@time-travellers.org>) id 1ZgXKp-0006kc-63; Mon, 28 Sep 2015 12:15:11 +0000
Date: Mon, 28 Sep 2015 12:15:09 +0000
From: Shane Kerr <shane@time-travellers.org>
To: Joe Abley <jabley@hopcount.ca>
Message-ID: <20150928121509.71b5f5db@casual>
In-Reply-To: <0E4AA958-7740-4602-A3CF-D2E481DBC15E@hopcount.ca>
References: <20150928114202.823.19868.idtracker@ietfa.amsl.com> <0E4AA958-7740-4602-A3CF-D2E481DBC15E@hopcount.ca>
X-Mailer: Claws Mail 3.12.0 (GTK+ 2.24.28; x86_64-pc-linux-gnu)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/tlK6D9BZuwBfa7tIYV532Jym7Tc>
Cc: dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] Fwd: 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: Mon, 28 Sep 2015 12:15:16 -0000

Joe,

On Mon, 28 Sep 2015 07:59:00 -0400
"Joe Abley" <jabley@hopcount.ca> wrote:

> I appreciate that the methods described in this document are not 
> universally liked. I have a feeling that we would get more discussion if 
> the question was more open-ended, e.g. how should trust anchors be 
> published?
> 
> This document describes existing practice, and provides guidance for 
> people who need to bootstrap a validator using the mechanisms provided 
> by ICANN back in 2009/2010 when the root zone was first published.
> 
> Here's a suggestion. If we were to consider publishing this document 
> as-is as a way of describing the current approach, we would at least 
> have a stable reference to the way we do things today. We could always 
> consider other approaches and, once implemented by ICANN, publish a new 
> document that obsoletes or updates this one.
> 
> If that's an approach that people could stomach, then I would suggest 
> the next step is to WGLC this document and for those who would like to 
> propose different mechanisms to write them down.

Given that this is supposed to turn into an informational RFC, and it
provides information about how the IANA currently publishes trust
anchors, I fully support it going forward as is.

Cheers,

--
Shane