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

Andrei Robachevsky <andrei.robachevsky@gmail.com> Sun, 26 October 2014 22:21 UTC

Return-Path: <andrei.robachevsky@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 E49A21A1AC4 for <ianaplan@ietfa.amsl.com>; Sun, 26 Oct 2014 15:21:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.739
X-Spam-Level:
X-Spam-Status: No, score=-1.739 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, HTML_MESSAGE=0.001, HTML_OBFUSCATE_05_10=0.26, 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 Ek6k7Quv5qgB for <ianaplan@ietfa.amsl.com>; Sun, 26 Oct 2014 15:21:17 -0700 (PDT)
Received: from mail-qa0-x22a.google.com (mail-qa0-x22a.google.com [IPv6:2607:f8b0:400d:c00::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1898A1A1AB3 for <ianaplan@ietf.org>; Sun, 26 Oct 2014 15:21:17 -0700 (PDT)
Received: by mail-qa0-f42.google.com with SMTP id cs9so3089539qab.29 for <ianaplan@ietf.org>; Sun, 26 Oct 2014 15:21:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=5qsnr1J03nwRvHuiZZVYjvyBlFMtEhqfqF9d3wffatg=; b=gESJtldUo+lJohENAczRNCQCK/Lfo2HTm8fv0fkI2P8QCuQcTf6QAmTn5sqRAiDG4/ 0lhaODSbGmA5Bz7pYPzab0CU9JDplj9T0JSbcUJyt0ExNl4F2nnCu3khRHj+JMouYofr PYEc7cVigN2+weIDViUGMGfGaCjtwowHmOQqsTnMfvaZrPtob8eg5PFJqyeOV6fqwRQq yrCjAmLZrsZ2A+AwpCyF0IbqODZrJHc8Ly/wCuUE5Kt0GuIqt6Dx88apTsJQUZrtyDtg 1l1XKx41qVHHGzlrbbI8n66eR07TtSP2y9mL9nDrSEk/CXGPaniccmutnb2ogzag9ypF 523A==
MIME-Version: 1.0
X-Received: by 10.140.107.11 with SMTP id g11mr26050073qgf.38.1414362076188; Sun, 26 Oct 2014 15:21:16 -0700 (PDT)
Received: by 10.140.42.35 with HTTP; Sun, 26 Oct 2014 15:21:16 -0700 (PDT)
In-Reply-To: <E74C02CC-8A35-4057-95E4-14925B332456@cooperw.in>
References: <E74C02CC-8A35-4057-95E4-14925B332456@cooperw.in>
Date: Sun, 26 Oct 2014 23:21:16 +0100
Message-ID: <CAJvJpgBM5EHLYRXP=tScoityruNY0J8Q8LR3KeasQj_PyRx+yA@mail.gmail.com>
From: Andrei Robachevsky <andrei.robachevsky@gmail.com>
To: Alissa Cooper <alissa@cooperw.in>
Content-Type: multipart/alternative; boundary="001a113a619c2296e205065ad591"
Archived-At: http://mailarchive.ietf.org/arch/msg/ianaplan/nMXF-qypZvvIZy2YRO9X-OeXyP0
Cc: "ianaplan@ietf.org" <ianaplan@ietf.org>
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: Sun, 26 Oct 2014 22:21:19 -0000

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. And IMO should be explicitly
specified here, not just in the "overlap" section.


Andrei