All, I would like to suggest the following alternative, in the hopes that it can be a broadly acceptable formulation, and thread the needle on some of the discussions we've been having. ICANN shall act strictly in accordance with, and only as reasonably appropriate to achieve its Mission. Without limiting the foregoing: - ICANN shall not impose regulations on: - services (i.e., the software processes by which commands received via the Internet are processed and a response is generated and transmitted via the Internet, to be viewed in a web browser, email client, or the like) which use the Internet’s unique identifiers, or - the content that such services carry or provide - ICANN shall have the ability to enter into and enforce agreements with contracted parties, in furtherance of its Mission. Your thoughts would be most appreciated. Greg On Thu, Nov 12, 2015 at 3:24 PM, Burr, Becky <Becky.Burr@neustar.biz> wrote:
I share Keith’s confusion. Just where are we?
*J. Beckwith Burr* *Neustar, Inc.* / Deputy General Counsel & Chief Privacy Officer 1775 Pennsylvania Avenue NW, Washington D.C. 20006 *Office:* +1.202.533.2932 *Mobile:* +1.202.352.6367 */* *neustar.biz* <http://www.neustar.biz>
From: <Drazek>, Keith Drazek <kdrazek@verisign.com> Date: Thursday, November 12, 2015 at 10:00 AM To: Greg Shatan <gregshatanipc@gmail.com>, Malcolm Hutty <malcolm@linx.net
Cc: Accountability Community <accountability-cross-community@icann.org>
Subject: Re: [CCWG-ACCT] Attempt to summarize discussion regarding Mission and Contract
Apologies, but is this where we left off on the wordsmithing? Is Milton correct that we’re closer than I thought? Is it just a matter of resolving the definition around “services?”
Thanks,
Keith
*From:* accountability-cross-community-bounces@icann.org [ mailto:accountability-cross-community-bounces@icann.org <accountability-cross-community-bounces@icann.org>] *On Behalf Of *Greg Shatan *Sent:* Wednesday, November 11, 2015 2:11 PM *To:* Malcolm Hutty *Cc:* Accountability Cross Community *Subject:* Re: [CCWG-ACCT] Attempt to summarize discussion regarding Mission and Contract
I'm not looking for a technical definition -- rather a practical definition. Actually, I asked for examples, so a definition may not be necessary, as long as the examples offer sufficient clarity.
It's important that when the CCWG/Commenters/SOs/ACs/etc. look at the word "services" (or the word services plus some exemplars), they all see the same thing.
Otherwise, we are like "The Six Blind Men and the Elephant" (apologies for culturally-specific, archaic and politically incorrect reference; please note as a counterbalance that I am a member of the CCWG-Accessibility, seeking to improve web access (and ICANN access) for people with disabilities).
On Wed, Nov 11, 2015 at 2:05 PM, Malcolm Hutty <malcolm@linx.net> wrote:
On 11/11/2015 18:33, Greg Shatan wrote:
Malcolm,
Thanks for your reply. I took those terms from an email you wrote, but clearly did not apply it quite correctly. It's critically important to get clarity here, and drilling down and getting concrete examples is extremely helpful.
What are a few examples of what you mean when you say "web service" and "other services"?
On 11/11/2015 18:55, Greg Shatan wrote:
I am trying to get to a concrete and shared understanding of what this proposal means when it says "services." Based on the varying responses in this and earlier threads, we're not there yet.
I can't see my stumbling attempts to provide a technical definition helping this discussion. I'll write to you privately.
Perhaps Andrew can do better than me, or point us to a formal definition of a service? Has the IETF produced such a thing?
-- Malcolm Hutty | tel: +44 20 7645 3523 Head of Public Affairs | Read the LINX Public Affairs blog London Internet Exchange | http://publicaffairs.linx.net/ <https://urldefense.proofpoint.com/v2/url?u=http-3A__publicaffairs.linx.net_&...>
London Internet Exchange Ltd Monument Place, 24 Monument Street, London EC3R 8AJ
Company Registered in England No. 3137929 Trinity Court, Trinity Street, Peterborough PE1 1DA