Re: [Internetgovtech] an initial proposal wrt IANA developments
Eliot Lear <lear@cisco.com> Fri, 21 March 2014 00:02 UTC
Return-Path: <lear@cisco.com>
X-Original-To: internetgovtech@ietfa.amsl.com
Delivered-To: internetgovtech@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 416151A07D2 for <internetgovtech@ietfa.amsl.com>; Thu, 20 Mar 2014 17:02:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.048
X-Spam-Level:
X-Spam-Status: No, score=-10.048 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001, 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 Fk8qPnz02vrQ for <internetgovtech@ietfa.amsl.com>; Thu, 20 Mar 2014 17:02:12 -0700 (PDT)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) by ietfa.amsl.com (Postfix) with ESMTP id 202071A077C for <internetgovtech@iab.org>; Thu, 20 Mar 2014 17:02:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4406; q=dns/txt; s=iport; t=1395360124; x=1396569724; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=i8wkMtB1ipbiUuOdXFOTAKMl0k0Xxcbk3PWWtnqLylQ=; b=jvj07Qy6zsS3mXZjcWAXYw7K93ePyERvfIZZBdHNWhrm73aXz2DFxGY7 JCB+62oW/g4vxd6Th6RDT4giI9MYfKVhSfwbeKtEYhwbj+KEW8YA8T/6v jX9Yr0QcV5SZzHAaoj0oQo7BLrwpVf6pYFXbZkA/MNc9yT01KVwfi3qRv w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhwFAAuBK1OQ/khR/2dsb2JhbABZgwaEGb9LgRMWdIIlAQEBAwEjSAcGBgsLGgIFFgsCAgkDAgECAUUGAQwIAQEQh10IrTCiUxeBKYxoW4JvgUkBA4lQiwuDbJIwgzow
X-IronPort-AV: E=Sophos;i="4.97,699,1389744000"; d="scan'208";a="5500695"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by aer-iport-3.cisco.com with ESMTP; 21 Mar 2014 00:02:01 +0000
Received: from ELEAR-M-C3ZS.CISCO.COM (rtp-vpn4-1151.cisco.com [10.82.212.127]) by ams-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s2L01w0J013599; Fri, 21 Mar 2014 00:01:59 GMT
Message-ID: <532B8177.5050703@cisco.com>
Date: Fri, 21 Mar 2014 08:01:59 +0800
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.4.0
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>, "internetgovtech@iab.org" <internetgovtech@iab.org>
References: <2EA5E4B4-DE50-494F-BB7B-E9604E03513D@piuha.net>
In-Reply-To: <2EA5E4B4-DE50-494F-BB7B-E9604E03513D@piuha.net>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/internetgovtech/JI4GhvCLwjZxLOEiim15TBoPoVs
Subject: Re: [Internetgovtech] an initial proposal wrt IANA developments
X-BeenThere: internetgovtech@iab.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Internet Governance and IETF technical work <internetgovtech.iab.org>
List-Unsubscribe: <https://www.iab.org/mailman/options/internetgovtech>, <mailto:internetgovtech-request@iab.org?subject=unsubscribe>
List-Archive: <http://www.iab.org/mail-archive/web/internetgovtech/>
List-Post: <mailto:internetgovtech@iab.org>
List-Help: <mailto:internetgovtech-request@iab.org?subject=help>
List-Subscribe: <https://www.iab.org/mailman/listinfo/internetgovtech>, <mailto:internetgovtech-request@iab.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Mar 2014 00:02:15 -0000
Hi Jari, I appreciate that many people have views as to what should happen, going forward. However, the text you quote below doesn't seem to me consistent with the principles that we have been establishing. On 3/21/14, 12:59 AM, Jari Arkko wrote: > > In order to ensure global acceptance and affirmation of ICANN's role as > administrator of the IANA functions, we are now pursuing the transition of USG's > stewardship of the IANA functions from the USG to ICANN. The roles of all > Internet registry policy bodies (such as the RIRs, IAB, IETF, ASO, ccNSO, ccTLD ROs, and > gNSO) stay unchanged. These bodies continue to hold policy authority for the > protocol parameter, number, and name spaces, including responsibility to ensure > the faithful registry implementation according to those policies. The above text should be aligned with principle #5, at least as far as the IANA parameters are concerned. > > This transition from the USG has been envisaged since the early days of ICANN. > It is now feasible due to the growing maturity of ICANN and other organisations > in the Internet ecosystem. It is beyond feasible. The job has been and is being done by the various organizations, generally with good collaboration between them. > ICANN's structures and accountability mechanisms > continue to evolve and advance guided by the AoC community reviews, including > ATRT. In addition, ICANN will continue to embrace its aggressive roadmap to > truly globalize its structures. This sounds very good, but why should this text not be addressed in an ICANN context? > In order to operationalize the transition from USG, ICANN will engage with the Internet > community in a bottom-up public consultation process to ensure appropriate > accountability mechanisms. In addition, ICANN will work with the names, numbers, > and protocol communities to formalize relationships, commitments, and mutual > responsibilities. Much of this has already been said by ICANN. > > When community stakeholders have input about the policies emanating from the > names, numbers, and protocol communities, they would be directed to pursue their > interests through the relevant Internet communities (such as the gNSO, ccNSO, ccTLD ROs, > ASO, IAB, IETF, or the RIRs) and their mechanisms for consideration and > potential redress. I like this part, actually. It seems to form the basis for the notion that consultation should flow to the communities where the experts are, and where those who are most impacted are likely to participate. IMHO the whole statement should be about this. > > The IETF, IAB, and RIRs are committed to open and transparent processes. They > also are committed to the role of ICANN as the IANA protocol parameter and IP > address registry operator. The accountability mechanisms for ICANN's > administration of these core internet functions will provide escalation routes > that assure the names, numbers, and protocol communities that if IANA's > performance is lacking, those communities can pursue defined processes for > improving performance, including pre-agreed independent 3rd party > arbitration processes. There was general agreement in London that ICANN does a good job for the IETF managing protocol parameters. As someone who has worked very closely with that team, I must agree. They deserve all the applause we gave them, and more. They do this work on our behalf. As a general rule, however, I prefer bilateral voluntary agreements rather than arbitration processes. That is, the IETF should always control its own destiny, and arbitration dilutes that autonomy. The above paragraph also should be aligned to our principles. > > ICANN reaffirms its commitment to implement all IANA registry functions in > accordance with the respective policies. ICANN will also provide affirmations to > all stakeholders (including governments) from all Internet registry policy > bodies and itself that all of us will use open and transparent processes. > Again, this sounds like an ICANN statement. A very GOOD ICANN statement, mind you, but I feel a little funny suggesting changes to their words as to what they would commit to. But a thousand blessings upon their house if they actually say this (I feel confident that they will, by the way, in some positive form). Eliot
- [Internetgovtech] an initial proposal wrt IANA de… Jari Arkko
- Re: [Internetgovtech] an initial proposal wrt IAN… Richard Barnes
- Re: [Internetgovtech] an initial proposal wrt IAN… Jari Arkko
- Re: [Internetgovtech] an initial proposal wrt IAN… S Moonesamy
- Re: [Internetgovtech] an initial proposal wrt IAN… Eliot Lear
- Re: [Internetgovtech] an initial proposal wrt IAN… John Curran
- Re: [Internetgovtech] an initial proposal wrt IAN… Brian E Carpenter
- Re: [Internetgovtech] an initial proposal wrt IAN… JFC Morfin
- Re: [Internetgovtech] an initial proposal wrt IAN… Alissa Cooper