Re: [Ianaplan] Updated text Re: Please keep context in mind Re: Consensus call -- text reply for ICG proposal review

Eliot Lear <lear@cisco.com> Tue, 25 August 2015 18:21 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 839B51A8A93 for <ianaplan@ietfa.amsl.com>; Tue, 25 Aug 2015 11:21:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level:
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, 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 iKftEpv2eAQ9 for <ianaplan@ietfa.amsl.com>; Tue, 25 Aug 2015 11:21:02 -0700 (PDT)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7BC491A8A98 for <ianaplan@ietf.org>; Tue, 25 Aug 2015 11:21:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6050; q=dns/txt; s=iport; t=1440526861; x=1441736461; h=subject:to:references:from:message-id:date:mime-version: in-reply-to; bh=NPJvC4j6RI28lkTHNzPYK9OejYJ2v23Uap3Cz/TM4dU=; b=Oy+xOzAZlMUScgvDpjbWnf7yz2vRR5YaswEP5y7WP71cmAp/8wJFGZsj WZUk90mErOUQQ1R6csk/BfI9P1COYEABCUg12thb+vX9STnmNZ5wzPzCb EIGV6P7IEwIceu9CJIIqWc/gyjmQJwjmZRp5WarRvCU9Gl61HOLrubTR1 E=;
X-Files: signature.asc : 481
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DlBABlsdxV/xbLJq1dgk6FL8JiAoIBAQEBAQEBgQuEJAEBAwEjVQYLCwQdFgQHAgIJAwIBAgFFBgEMCAEBiCIIswGVGQEBAQEBAQEDAQEBAQEBAQEai1eFEYJpgUMBBJU3gkCBXIhWgUqEMoJ5kV8mgkCBQDyCfwEBAQ
X-IronPort-AV: E=Sophos;i="5.17,747,1437436800"; d="asc'?scan'208,217";a="606588705"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP; 25 Aug 2015 18:20:58 +0000
Received: from [10.61.90.205] (ams3-vpn-dhcp6862.cisco.com [10.61.90.205]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id t7PIKvI9016335; Tue, 25 Aug 2015 18:20:58 GMT
To: "Leslie Daigle (ThinkingCat)" <ldaigle@thinkingcat.com>, "Ianaplan@Ietf. Org" <ianaplan@ietf.org>
References: <3A072B1E-FE4C-476E-B6F8-0309F377D221@thinkingcat.com> <55DB487A.2060303@cisco.com> <6f7112a4-4313-4c33-b7d9-a238f01920f8@email.android.com> <55DB4F0E.9000105@cisco.com> <aced0eb7-deed-48e4-85cf-a0ffe55b34aa@email.android.com> <55DB5C8E.20406@cisco.com> <55DB7C4C.7070801@cs.tcd.ie> <55DB99D6.6080201@gmail.com> <001b01d0defb$0b93d660$22bb8320$@ch> <7F697519-64D9-4C76-8CBE-FA02AEF36CF5@viagenie.ca> <08D2F0BC9153387337240538@JcK-HP8200.jck.com> <02f701d0df4f$56f128c0$04d37a40$@ch> <4559744B-2523-4D85-B855-5075E08D14F1@thinkingcat.com>
From: Eliot Lear <lear@cisco.com>
Message-ID: <55DCB209.6090702@cisco.com>
Date: Tue, 25 Aug 2015 20:20:57 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <4559744B-2523-4D85-B855-5075E08D14F1@thinkingcat.com>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="RIWIXRO3HLGOuCH20PPfIwUijnQlV82Bk"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ianaplan/iWwxDpM21UnF6qs4NefsQx-T38I>
Subject: Re: [Ianaplan] Updated text Re: Please keep context in mind Re: Consensus call -- text reply for ICG proposal review
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 25 Aug 2015 18:21:03 -0000

Hi Leslie,

On 8/25/15 6:58 PM, Leslie Daigle (ThinkingCat) wrote:

> Addressing the scope question head on, I could suggest:
>
> The IETF IANAPLAN WG has reviewed the draft ICG proposal within the
> context of the WG’s charter (<ref>) — specifically, “Should proposals
> made by other communities regarding the transition of other IANA
> functions affect the IETF protocol parameter registries or the IETF,
> the WG may also review and comment on them.”   The IETF IANAPLAN
> working group continues to believe that a transition away from a US
> Government role in IANA management and oversight is appropriate and
> confirms consensus of its participants that the draft proposal is not
> perceived to pose problems for the Protocol Parameters function.   
> The IETF raised two transition points that are mentioned in Paragraph
> 3062 of the proposal.  We would ask that they be referenced in Part 0,
> Section V of the proposal as well.

For me this is ALMOST there.  I believe that our  remit extends beyond
protocol parameters but to address issues that may relate to their
access and use.  And so I would suggest the following as an alternative:

The IETF IANAPLAN WG has reviewed the draft ICG proposal within the
context of the WG’s charter (<ref>) — specifically, “Should proposals
made by other communities regarding the transition of other IANA
functions affect the IETF protocol parameter registries or the IETF, the
WG may also review and comment on them.”   The IETF IANAPLAN working
group continues to believe that a transition away from a US Government
role in IANA management and oversight is appropriate and confirms
consensus of its participants that the draft proposal is not perceived
to pose problems for the Protocol Parameters function or to interfere with
the development or safe use of IETF standards.    The IETF raised two
transition points that are mentioned in Paragraph 3062 of the proposal. 
We would ask that they be referenced in Part 0, Section V of the
proposal as well.

Eliot