Re: [Ianaplan] Review of draft-ietf-ianaplan-icg-response-01

Brian E Carpenter <brian.e.carpenter@gmail.com> Mon, 27 October 2014 00:08 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ianaplan@ietfa.amsl.com
Delivered-To: ianaplan@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B9CB21A1B2A for <ianaplan@ietfa.amsl.com>; Sun, 26 Oct 2014 17:08:27 -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, FREEMAIL_FROM=0.001, SPF_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 s7MDFwthMXEw for <ianaplan@ietfa.amsl.com>; Sun, 26 Oct 2014 17:08:26 -0700 (PDT)
Received: from mail-pa0-x229.google.com (mail-pa0-x229.google.com [IPv6:2607:f8b0:400e:c03::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 83B691A1B28 for <ianaplan@ietf.org>; Sun, 26 Oct 2014 17:08:26 -0700 (PDT)
Received: by mail-pa0-f41.google.com with SMTP id rd3so4322885pab.28 for <ianaplan@ietf.org>; Sun, 26 Oct 2014 17:08:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=yIj4Xgu/d06tSJ1mqH+14hQ4ftTan1NYZu9VPFEjp4o=; b=zLcGzZ21IUOYQjJJb2YyH0M+RXRab/Dur5i93tPHCc7wDR46BE/Mdb16wj6kJEMeNm tmCeYonDQkDZBs5jHJJ1SDccuJbh/3oqyAAuqfg4qmvSa9hVYtc6hoWBIvYzHKSPUv5k DGhBGrKrKtrzUzCcTogeuw/h9XRx3KU5AwkdivFy1QrgoIYzabKPX0SpmM4Z9A/B0L1h cPjFzidwF8eTYl3CL8a/9wwknFu434ytLaR8M9S5wHi2dtnrv1n1Tl3aSC0dLWSiNTp2 2+uHW30gJyoqsuhR72s2u6VEODxFFkfIe1ZHeL9t1w0UIWORz7VD/PsOVm1KtBWsLOP/ Mugw==
X-Received: by 10.70.48.106 with SMTP id k10mr24943pdn.143.1414368506217; Sun, 26 Oct 2014 17:08:26 -0700 (PDT)
Received: from [192.168.178.23] (234.193.69.111.dynamic.snap.net.nz. [111.69.193.234]) by mx.google.com with ESMTPSA id lr4sm9268638pab.42.2014.10.26.17.08.22 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 26 Oct 2014 17:08:25 -0700 (PDT)
Message-ID: <544D8CF4.609@gmail.com>
Date: Mon, 27 Oct 2014 13:08:20 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Andrei Robachevsky <andrei.robachevsky@gmail.com>
References: <E74C02CC-8A35-4057-95E4-14925B332456@cooperw.in> <CAJvJpgBM5EHLYRXP=tScoityruNY0J8Q8LR3KeasQj_PyRx+yA@mail.gmail.com>
In-Reply-To: <CAJvJpgBM5EHLYRXP=tScoityruNY0J8Q8LR3KeasQj_PyRx+yA@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/ianaplan/ihSmDvfzLStbTU3J3i4FPI0ZyDE
Cc: "ianaplan@ietf.org" <ianaplan@ietf.org>, Alissa Cooper <alissa@cooperw.in>
Subject: Re: [Ianaplan] Review of draft-ietf-ianaplan-icg-response-01
X-BeenThere: ianaplan@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IANA Plan <ianaplan.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ianaplan>, <mailto:ianaplan-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ianaplan/>
List-Post: <mailto:ianaplan@ietf.org>
List-Help: <mailto:ianaplan-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ianaplan>, <mailto:ianaplan-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Oct 2014 00:08:27 -0000

On 27/10/2014 11:21, Andrei Robachevsky wrote:
> On 25 October 2014 01:35, Alissa Cooper <alissa@cooperw.in> wrote:
> 
>>
>> "The protocol parameter registries are the product of IETF work.”
>>
>> This seems like an under-specified answer. For example, the IP address
>> space registries could certainly be considered to be the product of IETF
>> work. But I did not think it was the intent to cover them in this
>> transition plan document. I apologize if there has been discussion of this
>> on the list that I missed, but I feel like the answer to this question is
>> specifically our opportunity to explain exactly what is covered by this
>> particular transition plan, and “the product of IETF work” is a rather
>> vague answer.
>>
>>
>> Alissa, I agree that it is under-specified.
> 
> There was some prior discussion of the point about the IP address space and
> I thought that a general agreement was that the IETF created the numbering
> space and identified part of it (global unicast) for allocation via the
> Internet Number Registry System. Which to me means that it indeed should be
> considered as a protocol parameter registry. 

This is unambiguously true for the IPv6 address regitstry.

It is less clear for the IPv4 address registry, which predated the
existence of the IETF; therefore the language would have to be
quite nuanced.

The same goes for the the null label of the DNS root, which
goes back at least to 1983 (RFC 882).

> And IMO should be explicitly
> specified here, not just in the "overlap" section.

I think we are on shaky ground if we do that, except for IPv6.

    Brian