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

Jari Arkko <jari.arkko@piuha.net> Wed, 26 August 2015 15:26 UTC

Return-Path: <jari.arkko@piuha.net>
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 EADE81B2DEA for <ianaplan@ietfa.amsl.com>; Wed, 26 Aug 2015 08:26:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 3x393pcHsfPF for <ianaplan@ietfa.amsl.com>; Wed, 26 Aug 2015 08:26:14 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 79AD11B2E04 for <ianaplan@ietf.org>; Wed, 26 Aug 2015 08:26:14 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 02B072CEA0; Wed, 26 Aug 2015 18:26:13 +0300 (EEST) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E1YqVePnIAkw; Wed, 26 Aug 2015 18:26:12 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 6CB542CC5C; Wed, 26 Aug 2015 18:26:12 +0300 (EEST) (envelope-from jari.arkko@piuha.net)
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_B5B23D93-BF67-4630-B6D7-4063BE0307D1"; protocol="application/pgp-signature"; micalg="pgp-sha512"
X-Pgp-Agent: GPGMail 2.5.1
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <55DCB209.6090702@cisco.com>
Date: Wed, 26 Aug 2015 18:26:11 +0300
Message-Id: <EED33495-B385-44D9-B252-6FB62918869B@piuha.net>
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> <55DCB209.6090702@cisco.com>
To: Eliot Lear <lear@cisco.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ianaplan/fnPjniairUQVZifuMpkMYhTyQt4>
Cc: "Ianaplan@Ietf. Org" <ianaplan@ietf.org>, "Leslie Daigle (ThinkingCat)" <ldaigle@thinkingcat.com>
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: Wed, 26 Aug 2015 15:26:16 -0000

> 
> 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.

This would work for me.

(We’re trying to find a very fine balance between how well the overall setup works for us vs. claiming something about the details of parts that do not affect us. Perhaps understandably, finding the right words is difficult. But I think this or something along these lines would be reasonable and accurate.)

Jari