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

"Joe Abley" <jabley@hopcount.ca> Mon, 28 September 2015 11:59 UTC

Return-Path: <jabley@hopcount.ca>
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 5A3661A8A66 for <dnsop@ietfa.amsl.com>; Mon, 28 Sep 2015 04:59:13 -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] 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 UI3JBSgFqDPX for <dnsop@ietfa.amsl.com>; Mon, 28 Sep 2015 04:59:12 -0700 (PDT)
Received: from mail-ig0-x234.google.com (mail-ig0-x234.google.com [IPv6:2607:f8b0:4001:c05::234]) (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 38FD51A8A63 for <dnsop@ietf.org>; Mon, 28 Sep 2015 04:59:12 -0700 (PDT)
Received: by igbkq10 with SMTP id kq10so53448976igb.0 for <dnsop@ietf.org>; Mon, 28 Sep 2015 04:59:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=from:to:subject:date:message-id:references:mime-version :content-type:content-transfer-encoding; bh=1KH0TTeJTN3Y1OKZUYJAkqecAPFPYBwd8MSPusLVcQI=; b=b2jjrj1gvV/gPAgJuO37SAE+bVfC2VfKKRhIOe9grW59Ki/DUc2jR9Wg15EvHFRPTe 9jOicmRAhkM7FDH7xWWO8wVn0R2g4YwPStUoFGPL93887wUp6MNrFLSUOmmhPvnLJez+ dUKNWp4CX9cTnUaWqDThaWu+FQCQ2oITA3v3k=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:subject:date:message-id:references :mime-version:content-type:content-transfer-encoding; bh=1KH0TTeJTN3Y1OKZUYJAkqecAPFPYBwd8MSPusLVcQI=; b=RZV7KrjO6TKwLxVwdiwav8IXjx9j3R0HTJtb57FCe7rGM96vLv7mIBh8OYzHdbUcGF gxKz513r9omBmZqiqo6eC8qwEmK9tX/sr9X7rNvKJM9EGYTFVqzwz9iONIMABmAsIlWA lYN7tNH/ZuwJ0PW7VLRDbfehtsOlBQOSffIT+u3QC03nIUncHzIErNVL7yekjZGXGyrC KVTaXhSVmj0Edu5rlgB8ceKkl+02WJnpKN7JrRBUJp9k60ouzI3YOOb8nQkLweqmWFSB f3A2aKgkXkPI/rBP5cWkbKp7e5b7VzhTHjhPX9TZPSU/WwTYtrjXvK0asGW3GzK4d/Rr GFoQ==
X-Gm-Message-State: ALoCoQmnqtSYoJoKZL/Up2t4CrmzRuWmv4lh1zdZPEbUnk6rCt6HXcoyr3ehioerbp8qN+F1yP+T
X-Received: by 10.50.134.231 with SMTP id pn7mr7675089igb.89.1443441551508; Mon, 28 Sep 2015 04:59:11 -0700 (PDT)
Received: from [172.19.128.238] (135-23-68-43.cpe.pppoe.ca. [135.23.68.43]) by smtp.gmail.com with ESMTPSA id m25sm8325992iod.32.2015.09.28.04.59.10 for <dnsop@ietf.org> (version=TLSv1 cipher=RC4-SHA bits=128/128); Mon, 28 Sep 2015 04:59:10 -0700 (PDT)
From: Joe Abley <jabley@hopcount.ca>
To: dnsop <dnsop@ietf.org>
Date: Mon, 28 Sep 2015 07:59:00 -0400
Message-ID: <0E4AA958-7740-4602-A3CF-D2E481DBC15E@hopcount.ca>
References: <20150928114202.823.19868.idtracker@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Mailer: MailMate (1.9.1r5103)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/HwpmlzyyPSjEyn9R_3_s2Kssc-Y>
Subject: [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 11:59:13 -0000

Hi all,

We don't seem to be getting anywhere with this draft. (Jakob is going to 
bump it to -12; there have been no real updates apart from the version 
bump in

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.

Chair-people, can we do that?


Joe

Forwarded message:

> From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
> To: Guy Bailey <gubailey@microsoft.com>, Jakob Schlyter 
> <jakob@kirei.se>, Joe Abley <jabley@dyn.com>
> Subject: Expiration impending: 
> <draft-jabley-dnssec-trust-anchor-11.txt>
> Date: Mon, 28 Sep 2015 04:42:02 -0700
>
> The following draft will expire soon:
>
> Name:     draft-jabley-dnssec-trust-anchor
> Title:    DNSSEC Trust Anchor Publication for the Root Zone
> State:    I-D Exists
> Expires:  2015-10-08 (in 1 week, 2 days)
>