Re: [Ianaplan] Adrian Farrel's No Record on draft-ietf-ianaplan-icg-response-06: (with COMMENT)
Eliot Lear <lear@cisco.com> Wed, 17 December 2014 13:01 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 996641A8A3F; Wed, 17 Dec 2014 05:01:31 -0800 (PST)
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 YDGohAKSWhbF; Wed, 17 Dec 2014 05:01:29 -0800 (PST)
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 C290F1A8A44; Wed, 17 Dec 2014 05:01:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=31791; q=dns/txt; s=iport; t=1418821289; x=1420030889; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=rAM8BE/ycThB4vd5eUpgjIX4Srlt+TJhM5eqbL7yAgo=; b=fmgJzvPBYNRWrjh7PU/R2CFSO6gqoWenyn4zpDm/T/HRf81fb1c4ClU2 QL8Te8HugnJ8ptFRMLv0G22l9MSTcFLNjcswMoiU8n2Y4No2eEbemSYtC uzPTLczBuXUx8bq3uoPOnSmWt0PjDMkPsbZAczjWLKT8WCrse5l5pE8PS E=;
X-Files: signature.asc : 486
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AsIEAF9+kVStJssW/2dsb2JhbABagkOEc7h7gzmMLgKBNwEBAQEBfYQNAQEEIwpLARAJAhgJDAoBAQkCAgkDAgECARQxBgEMAQQBAgEBiCihJpxoliUBAQEBAQEBAQEBAQEBAQEBAQEBAQEXjw8BEQFQBwqCXoFBAQSPUoEnhX+FfItEIoIwgT09gT2BNwEBAQ
X-IronPort-AV: E=Sophos;i="5.07,593,1413244800"; d="asc'?scan'208,217";a="273521923"
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; 17 Dec 2014 13:01:22 +0000
Received: from [10.61.70.122] (ams3-vpn-dhcp1658.cisco.com [10.61.70.122]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id sBHD1MpW014625; Wed, 17 Dec 2014 13:01:22 GMT
Message-ID: <54917EA1.5000304@cisco.com>
Date: Wed, 17 Dec 2014 14:01:21 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: adrian@olddog.co.uk, 'The IESG' <iesg@ietf.org>
References: <20141215104500.11417.21764.idtracker@ietfa.amsl.com> <548EDBC5.3010007@cisco.com> <091701d01873$f3531b40$d9f951c0$@olddog.co.uk> <548EFFD7.8010208@cisco.com> <0c4701d0197c$5ea90a40$1bfb1ec0$@olddog.co.uk>
In-Reply-To: <0c4701d0197c$5ea90a40$1bfb1ec0$@olddog.co.uk>
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="vkV546JpQxd76EprMx1v0fODvI4QLAXxs"
Archived-At: http://mailarchive.ietf.org/arch/msg/ianaplan/IkDChJ0YnFjM-5XR108UFDgJegk
Cc: ianaplan@ietf.org, ianaplan-chairs@tools.ietf.org, draft-ietf-ianaplan-icg-response.all@tools.ietf.org, ajs@anvilwalrusden.com
Subject: Re: [Ianaplan] Adrian Farrel's No Record on draft-ietf-ianaplan-icg-response-06: (with COMMENT)
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, 17 Dec 2014 13:01:32 -0000
To address Adrian's point below: On 12/16/14, 11:05 PM, Adrian Farrel wrote: > > Thanks again, Eliot, for pushing on with this. > > > > Eliot and I chatted to complete the details of our differences. I > think we're there on all of the points. > > > > Perhaps the biggest issue was around my question on the first response > in Question V. > > > > What i intended to try to draw out was the difference between the > multistakeholder aspects in the development of the proposal, and in > the content of the proposal (i.e. in the structures and process that > would be put in place if the proposal was accepted). > > > > The current text is a good explanation of how the IETF is open and > effectively a multistakeholder organisation. But it lacks the hooks to > the two different points. > > > > I think this can be handled easily with a little lead in text about > how the proposal was developed using normal IETF processes and how the > essence of the proposal is to use existing IETF processes to continue > to set policy for and guide the IANA protocol registry functions. > I propose replacement text as follow: OLD: Everyone is welcome to participate in IETF activities. The policies and procedures are outlined in the documents we named above. In-person attendance is not required for participation, and many people participate in email discussions that have never attended an IETF meeting. An email account is the only requirement to participate. The IETF makes use of both formal and informal lines of communication to collaborate with other organizations within the multistakeholder ecosystem. NEW: Because the IETF is open to everyone, participation is open to all stakeholders. IETF processes outlined in Section I were used to develop this proposal. Those same processes have been and shall be used to amend governance of the protocol parameters function. As mentioned previously, anyone may propose amendments to those processes, and anyone may take part in the decision process. This text is somewhat more directed at the question. I do not propose to make a distinction between the different forms of multistakeholderism, although I agree with Richard that there are different forms. Our response is clearly within the bounds of what the NTIA and the ICG has discussed. Eliot
- [Ianaplan] Adrian Farrel's No Record on draft-iet… Adrian Farrel
- Re: [Ianaplan] Adrian Farrel's No Record on draft… Eliot Lear
- Re: [Ianaplan] Adrian Farrel's No Record on draft… Adrian Farrel
- Re: [Ianaplan] Adrian Farrel's No Record on draft… Eliot Lear
- Re: [Ianaplan] Adrian Farrel's No Record on draft… Brian E Carpenter
- Re: [Ianaplan] Adrian Farrel's No Record on draft… Dave Crocker
- Re: [Ianaplan] Adrian Farrel's No Record on draft… Martin J. Dürst
- Re: [Ianaplan] Adrian Farrel's No Record on draft… Adrian Farrel
- Re: [Ianaplan] Adrian Farrel's No Record on draft… Olaf Kolkman
- Re: [Ianaplan] Adrian Farrel's No Record on draft… Jari Arkko
- Re: [Ianaplan] Adrian Farrel's No Record on draft… Adrian Farrel
- Re: [Ianaplan] Adrian Farrel's No Record on draft… Jefsey
- Re: [Ianaplan] Adrian Farrel's No Record on draft… Richard Hill
- Re: [Ianaplan] Adrian Farrel's No Record on draft… Stephen Farrell
- Re: [Ianaplan] Adrian Farrel's No Record on draft… Eliot Lear
- Re: [Ianaplan] Adrian Farrel's No Record on draft… Jefsey
- [Ianaplan] The IETF Fork. [was: Adrian Farrel's N… JFC Morfin