Re: [weirds] Fwd: I-D Action: draft-ietf-weirds-bootstrap-11.txt

Peter Koch <pk@DENIC.DE> Thu, 18 December 2014 20:59 UTC

Return-Path: <peter@denic.de>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 763E31A1B39 for <weirds@ietfa.amsl.com>; Thu, 18 Dec 2014 12:59:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.86
X-Spam-Level:
X-Spam-Status: No, score=-3.86 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] 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 ylLL7EQskoW9 for <weirds@ietfa.amsl.com>; Thu, 18 Dec 2014 12:59:07 -0800 (PST)
Received: from office.denic.de (office.denic.de [81.91.160.182]) (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 569E11A047A for <weirds@ietf.org>; Thu, 18 Dec 2014 12:59:06 -0800 (PST)
Received: from office.denic.de (mailout1.denic.de [10.122.34.3]) by office.denic.de (Postfix) with ESMTPS id CC7E3240021; Thu, 18 Dec 2014 21:58:53 +0100 (CET)
Received: from x27.adm.denic.de (x28.fra2.if.denic.de [10.122.64.17]) by office.denic.de with esmtps (TLSv1:AES256-SHA:256) id 1Y1i9t-0000FL-KL; Thu, 18 Dec 2014 21:58:53 +0100
Received: from localhost by x27.adm.denic.de with local id 1Y1i9q-0002jL-Dv; Thu, 18 Dec 2014 21:58:50 +0100
Date: Thu, 18 Dec 2014 21:58:50 +0100
From: Peter Koch <pk@DENIC.DE>
To: Marc Blanchet <marc.blanchet@viagenie.ca>
Message-ID: <20141218205850.GH28899@x28.adm.denic.de>
Mail-Followup-To: Marc Blanchet <marc.blanchet@viagenie.ca>, Barry Leiba <barryleiba@computer.org>, Pete Resnick <presnick@qti.qualcomm.com>, "Murray S. Kucherawy" <superuser@gmail.com>, Michael Szucs <mszucs@afilias.info>, draft-ietf-weirds-bootstrap.all@tools.ietf.org, "<weirds@ietf.org>" <weirds@ietf.org>
References: <20141218193248.30639.20974.idtracker@ietfa.amsl.com> <0F70F800-D7F1-49AF-97D3-34568DFA3C9C@viagenie.ca>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <0F70F800-D7F1-49AF-97D3-34568DFA3C9C@viagenie.ca>
User-Agent: Mutt/1.4.2.3i
Sender: Peter Koch <peter@denic.de>
Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/9JjQjqWNClrlio9i9GCycuNgAMI
Cc: Pete Resnick <presnick@qti.qualcomm.com>, "<weirds@ietf.org>" <weirds@ietf.org>, draft-ietf-weirds-bootstrap.all@tools.ietf.org, Barry Leiba <barryleiba@computer.org>
Subject: Re: [weirds] Fwd: I-D Action: draft-ietf-weirds-bootstrap-11.txt
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/weirds/>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Dec 2014 20:59:09 -0000

On Thu, Dec 18, 2014 at 02:39:26PM -0500, Marc Blanchet wrote:
> Hello,
>  this new version shall address all comments received from IESG review. IMHO, it should clear the DISCUSS and move ahead.

I've re-read the updated IANA considerations section.  This new
version still does not focus on the IETF side of things and in fact
tries to make ICANN's work with IETF tools.  In fact, what is about
to be established here is not even a registry, it is operational data
(fed from existing registries coming from different, non-IETF IANA pillars).
more like the DNS root zone than an IETF protocol parameters registry.

Therefore what the IETF should do is specify the format only and let
"the other entity" (aka ICANN) describe (in an RFC, independent submission stream)
the operational details of the initial "hook".
The end result for users would be the same with the benefit of untangling the
policy space.  Let us please use this opportunity not to further contribute to
overlaps between different IANA functions where in neighboring venues we
try to more precisely specify the separation of duties.

-Peter