IETF Logo Mail Archive

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

"John Levine" <johnl@taugh.com> Fri, 09 October 2015 01:11 UTC

Return-Path: <johnl@taugh.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 9FD021B2F39 for <dnsop@ietfa.amsl.com>; Thu, 8 Oct 2015 18:11:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.663
X-Spam-Level: *
X-Spam-Status: No, score=1.663 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_PASS=-0.001] 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 CWEjRpQ018LJ for <dnsop@ietfa.amsl.com>; Thu, 8 Oct 2015 18:11:02 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 834C51B2F37 for <dnsop@ietf.org>; Thu, 8 Oct 2015 18:11:02 -0700 (PDT)
Received: (qmail 62487 invoked from network); 9 Oct 2015 01:11:02 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 9 Oct 2015 01:11:02 -0000
Date: Fri, 09 Oct 2015 01:10:39 -0000
Message-ID: <20151009011039.36478.qmail@ary.lan>
From: John Levine <johnl@taugh.com>
To: dnsop@ietf.org
In-Reply-To: <2DA5F733-6854-4F08-BFF9-487B9543F2A4@karoshi.com>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/J6RdWN9-e69iDUseTzFpXHDAa_E>
Cc: 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 01:11:03 -0000

>In the past, when organizations found themselves in the same situation that ICANN seems to find itself in here
>(at least as outlined by yourself, below)
>they have done what ICANN has done and is trying to do now, which is to pass the document on to a neutral third
>party for “safe keeping”.   One thing
>the IETF used to do was insist that when/if such a document was remedied to its care, that it ALSO claimed change
>control over same.

That would suggest it'd be more appropriate for the independent
stream, wouldn't it?

R's,
John

v2.23.0 | Report a Bug | By Email