Re: [Ianaplan] draft-ietf-ianaplan-icg-response-02 working group last call

Eliot Lear <lear@cisco.com> Wed, 29 October 2014 17:27 UTC

Return-Path: <lear@cisco.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 1B4DA1A700B for <ianaplan@ietfa.amsl.com>; Wed, 29 Oct 2014 10:27:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 Kjlc-pV1B69B for <ianaplan@ietfa.amsl.com>; Wed, 29 Oct 2014 10:27:40 -0700 (PDT)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 48B501A6FD5 for <ianaplan@ietf.org>; Wed, 29 Oct 2014 10:27:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2353; q=dns/txt; s=iport; t=1414603660; x=1415813260; h=message-id:date:from:mime-version:to:subject:references: in-reply-to; bh=mxJ5mWUVzLS4XlgPIIQ1e5U+KxmXGVhN7hiLNHnWqWc=; b=QXGql25jyiR/xrCogAYu49NhFbQmVZNPaS5C45A3e7Az2/rudF22tkMQ SinNxS/HkOwmsDrX/pOEumV2vfJnlJWjlDZc3lNGe5fvf9lAv/JVJSkSf go+ucbZ+tcj+asdpd5BDTL6tcPBblH3QJ0p/+JzZ/HEgiQUoYmu+mKCTE s=;
X-Files: signature.asc : 486
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqgEADIjUVStJssW/2dsb2JhbABcg2JTziaHUQKBMQEBAQEBfYQDAQEEIyYvEQsYCRYLAgIJAwIBAgFFBgEMCAEBBYg4CLJ/lQEBAQEBAQEBAwEBAQEBAQEbkReCd4FUBZQfgVCHe4Exg0qCdIdrhmaDeTyCegEBAQ
X-IronPort-AV: E=Sophos;i="5.07,278,1413244800"; d="asc'?scan'208";a="225146371"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP; 29 Oct 2014 17:27:38 +0000
Received: from [10.61.194.151] ([10.61.194.151]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s9THRc5b005022; Wed, 29 Oct 2014 17:27:38 GMT
Message-ID: <54512389.8040404@cisco.com>
Date: Wed, 29 Oct 2014 18:27:37 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Andrei Robachevsky <andrei.robachevsky@gmail.com>, ianaplan@ietf.org
References: <6ACE138D-0969-4D8F-9A64-3D1FBB96885A@viagenie.ca> <5451204B.1030509@gmail.com>
In-Reply-To: <5451204B.1030509@gmail.com>
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="5rs7HSjx5DeEjcAlqpkSIpoKILeQTjfnC"
Archived-At: http://mailarchive.ietf.org/arch/msg/ianaplan/npRtS3fu4iDL_WuteV7lGYHqCOw
Subject: Re: [Ianaplan] draft-ietf-ianaplan-icg-response-02 working group last call
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: Wed, 29 Oct 2014 17:27:42 -0000

Hi Andrei,

On 10/29/14, 6:13 PM, Andrei Robachevsky wrote:
>>    >>> What registries are involved in providing the service or
>>    >>> activity.
>>    >>>
>>
>>
>>    IETF Response:
>>
>>    The protocol parameters registries are the product of IETF work.
>>    Administration of the protocol parameters registries is the service
>>    that is provided to the IETF.
> I think that the "protocol parameters registries" are not (well) defined
> in this context. A reader will most probably associate this with
> www.iana.org/protocols, which is a subset.
>
> Since we seemed to agree that the IETF is responsible for all number
> space with the exception of the space delegated to the Internet Number
> Registry System, I think mentioning this in the overlap section only is
> not enough.
>
> Perhaps we can say:
>
> IETF Response:
>
> The protocol parameters registries are the product of IETF work. These
> also include the top-level registry for the entire IP address space and
> some of its sub-registries, AS number space, and a number of special use
> registries with regard to domain names. For more detail please refer to
> the documentation in the "overlaps or interdependencies" section.
>
> Administration of the protocol parameters registries is the service that
> is provided to the IETF.
>

I have no objection to this proposed change.

Eliot