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

Barry Leiba <barryleiba@computer.org> Thu, 18 December 2014 21:35 UTC

Return-Path: <barryleiba@gmail.com>
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 9E03E1A8730 for <weirds@ietfa.amsl.com>; Thu, 18 Dec 2014 13:35:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level:
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, 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 bCf-OehwqObI for <weirds@ietfa.amsl.com>; Thu, 18 Dec 2014 13:35:26 -0800 (PST)
Received: from mail-la0-x22c.google.com (mail-la0-x22c.google.com [IPv6:2a00:1450:4010:c03::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5B36F1A702E for <weirds@ietf.org>; Thu, 18 Dec 2014 13:35:26 -0800 (PST)
Received: by mail-la0-f44.google.com with SMTP id gd6so1794415lab.3 for <weirds@ietf.org>; Thu, 18 Dec 2014 13:35:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=vLzCWAZSo0qdcvRiarMDGBJnD1ozwIYtWAodW5Hdu5M=; b=o7An4+abMofnE9jKfaDKnislmc0EHIKuZBKUESn8/6+5VD261f97AhxjANBDVEOKQC bqJ5RcLDcnNlN00hrtRlVRW88zKJJ2ufEtRNA1gFG2fNZMhY8jZlHY2iPu2GQmYvgQE9 1GMGvAIuc754qz9PfFT0R+zmaSIIVpEocPt+PMwxt+0bh7H1sPYuyjJHvpo1eluOgOfg N7HB4gb/mUOq19Q2DGm5DL2QZKZ2ToNd7fzby1COIYiyzONvtFfyDV8HYsX0ch3eKKQU hXFGf5PNi6fHKVuTUrhpvETsNsTbSk6P/gCS3Uquwhf9sGhAr8+y8xOh+JCEmnhh24+w GFVA==
MIME-Version: 1.0
X-Received: by 10.112.185.99 with SMTP id fb3mr4353595lbc.21.1418938524826; Thu, 18 Dec 2014 13:35:24 -0800 (PST)
Sender: barryleiba@gmail.com
Received: by 10.152.127.168 with HTTP; Thu, 18 Dec 2014 13:35:24 -0800 (PST)
In-Reply-To: <CALaySJJ2FkkOE0L8EBbKmUnX5ukDN3RVpykC7XiT0wisP52dqg@mail.gmail.com>
References: <20141218193248.30639.20974.idtracker@ietfa.amsl.com> <0F70F800-D7F1-49AF-97D3-34568DFA3C9C@viagenie.ca> <20141218205850.GH28899@x28.adm.denic.de> <CALaySJJ2FkkOE0L8EBbKmUnX5ukDN3RVpykC7XiT0wisP52dqg@mail.gmail.com>
Date: Thu, 18 Dec 2014 16:35:24 -0500
X-Google-Sender-Auth: z7meX_K7Vq7e1r3Q8ftVDSm0MVE
Message-ID: <CALaySJL5y8KhkwUV9yAhEW5oAD0njxoVGVbjdtUX0LKcgK8chw@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: Peter Koch <pk@denic.de>
Content-Type: text/plain; charset="ISO-8859-1"
Archived-At: http://mailarchive.ietf.org/arch/msg/weirds/BQeN7TEPG_0gZszxFdzDvBcDSiA
Cc: Pete Resnick <presnick@qti.qualcomm.com>, "<weirds@ietf.org>" <weirds@ietf.org>, "draft-ietf-weirds-bootstrap.all@tools.ietf.org" <draft-ietf-weirds-bootstrap.all@tools.ietf.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 21:35:27 -0000

Further following up...

On Thu, Dec 18, 2014 at 4:09 PM, Barry Leiba <barryleiba@computer.org> wrote:
>> 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".
>
> I would be happy with that alternative, as long as it's a normative
> reference, which this document would then have to wait for.  I think
> it's important for this document (along with its normative references)
> to provide the complete information necessary to create
> implementations.
>
> I'm not sure we want to delay things for that, but you're welcome to argue it.

I'll add that we have already run this version by IANA (and, so,
ICANN), and they're fine with it.  Are you sure that they'd rather
publish a separate document of their own for this?

Barry