[CCWG-ACCT] Mission/Contract

Seun Ojedeji seun.ojedeji at gmail.com
Tue Nov 10 08:49:57 UTC 2015


On Tue, Nov 10, 2015 at 7:11 AM, Greg Shatan <gregshatanipc at gmail.com>
wrote:

>
> [2] This is taken from an email from Malcolm Hutty, as a description of
> what is meant by “services” in this context.  Due to the variety of
> meanings that “services” can have, it is necessary to avoid ambiguity.
>
adding "....and the like" already creates ambiguity. WHOIS(or to be more
generic, any content related to a registrant) for instance does not run
from Pluto as it can indeed be classified as a service, which IMO should
have some form of regulation.


> [3] Once the nature of the “services” is clarified, the nature of their
> “use” no longer needs to be clarified.
>
> [4] This is taken almost verbatim from the Second Draft Report, para.
> 158.  Since it is a direct comment on the contents of the Bylaw, it should
> be reflected in the draft Bylaw.  Once this is here, Malcolm’s last
> sentence is no longer needed.
>
> [5] This is a recommendation taken from the “Comment Summary PRINCIPLES”
> analysis prepared by WP1 after the second Public Comment period.
>
I don't think mission should be tied to documents that can change at any
point in time. Its also good to use few technical/complicated words as much
as possible....thats why I find that of Malcom quite on point and
understandable. I am though in agreement with removing the word "strictly"
as proposed by Greg. In other to ensure that ICANN mission supersedes any
possible contract/agreement, I will also suggest the section below be
updated as thus:

"ICANN shall have the ability to negotiate, enter into and enforce
agreements with contracted parties in service of its Mission.
TO
"ICANN shall have the ability to negotiate, enter into and enforce
agreements with contracted parties in accordance to and in service of its
Mission.

On a lighter note, i expect that this is only looking at one of the open
items of the mission statement.

Regards


>
>
> On Mon, Nov 9, 2015 at 7:09 PM, Burr, Becky <Becky.Burr at neustar.biz>
> wrote:
>
>> All -
>>
>> In advance of our call tomorrow I want to flag the open issue in the
>> Mission Statement – language prohibiting ICANN from regulating "services
>> that use the Internet’s unique identifiers or the content that they carry
>> or provide."
>>
>> While there is strong consensus that (1) ICANN’s mission is limited and
>> (2) ICANN should act only in furtherance of its mission, strong and
>> divergent perspectives on the proposed language itself remain.  The
>> language has been in the proposed Mission Statement since our Frankfurt
>> meeting last January.  Numerous commenters supported the language in both
>> the first and second comment periods on the grounds that ICANN should not
>> attempt to regulate third parties through its agreements with registries
>> and registrars.  On the other hand, many commenters expressed concerns
>> about potential unintended consequences of this language, and the impact
>> that it might have, for example, on ICANN’s ability to enforce commitments
>> contained in registry and/or registrar commitments (e.g., Public Interest
>> Commitments, special-interest new gTLD applications, etc.).
>>
>> The following chart (also attached as a PDF) compares the language in the
>> 2nd Draft Report with language circulated shortly following the Dublin
>> meeting, and suggested language proposed by Greg Shatan and Malcolm Hutty
>> respectively to resolve this issue.   (Another approach, which I floated,
>> was strongly criticized.)  As we review and discuss this language tomorrow,
>> please keep in mind that we have always been clear that the language in the
>> proposed Mission Statement is not final Bylaws language, rather it intended
>> to guide those crafting final Bylaws.  I look forward to a fruitful
>> discussion in 12 hours!
>>
>>
>> 2nd Draft Report Language
>>
>>
>>
>> Post-Dublin Language
>>
>>
>>
>> Greg Shatan Proposal 2 Nov 2015
>>
>> Malcolm Hutty Proposal 6 Nov 2015
>>
>>
>>
>> ICANN shall have no power to act other than in accordance with, and as
>> reasonably appropriate to achieve its Mission.
>>
>>
>>
>> Without in any way limiting the foregoing absolute prohibition, ICANN
>> shall not engage in or use its powers to attempt the regulation of services
>> that use the Internet's unique identifiers, or the content that they carry
>> or provide.
>>
>>
>>
>> ICANN shall have no power to act strictly other than in accordance with,
>> and only as reasonably appropriate to achieve its Mission.
>>
>>
>>
>> Without in any way limiting the foregoing absolute prohibition, ICANN
>> shall not regulate services that use the Internet's unique identifiers, or
>> the content that such services carry or provide.
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> In service of its Mission ICANN shall have the ability to enforce
>> agreements with contracted parties, subject to established means of
>> community input on those agreements and reasonable checks and balances on
>> its ability to impose obligations exceeding ICANN’s Mission on registries
>> and registrars.
>>
>>
>>
>> ICANN shall have no power to act other than in accordance with, and as
>> reasonably appropriate to achieve its Mission.
>>
>>
>>
>>
>>
>> Without in any way limiting the foregoing absolute prohibition, ICANN
>> shall not regulate services that use the Internet's unique identifiers, or
>> the content that such services carry or provide.
>>
>>
>>
>> ICANN and contracted parties entering into, complying with and enforcing
>> agreements does not constitute regulation.
>>
>>
>>
>>  In service of its Mission, ICANN shall have the ability to enforce
>> agreements with contracted parties, subject to established means of
>> community input on those agreements and reasonable checks and balances on
>> its ability to impose obligations exceeding ICANN’s Mission on registries
>> and registrars.
>>
>> ICANN shall only act strictly in accordance with and as reasonably
>> appropriate to achieve its Mission.
>>
>>
>>
>>
>>
>> Without in any way limiting the foregoing, ICANN shall not engage in or
>> use its powers to attempt the regulation of services that use the
>> Internet's unique identifiers to enable or facilitate their reachability
>> over the Internet, nor shall it regulate or the content that those
>> services carry or provide.
>>
>>
>>
>>
>>
>>
>>
>> ICANN shall have the ability to negotiate, enter into and enforce
>> agreements with contracted parties in service of its Mission.
>>
>> subject to established means of community input on those agreements and
>> reasonable checks and balances on its ability to impose obligations
>> exceeding ICANN’s Mission on registries and registrars
>>
>>
>>
>>
>>
>>
>>
>>
>> *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>
>>
>> _______________________________________________
>> Accountability-Cross-Community mailing list
>> Accountability-Cross-Community at icann.org
>> https://mm.icann.org/mailman/listinfo/accountability-cross-community
>>
>>
>
> _______________________________________________
> Accountability-Cross-Community mailing list
> Accountability-Cross-Community at icann.org
> https://mm.icann.org/mailman/listinfo/accountability-cross-community
>
>


-- 
------------------------------------------------------------------------





*Seun Ojedeji,Federal University Oye-Ekitiweb:      http://www.fuoye.edu.ng
<http://www.fuoye.edu.ng> Mobile: +2348035233535**alt email:
<http://goog_1872880453>seun.ojedeji at fuoye.edu.ng
<seun.ojedeji at fuoye.edu.ng>*

Bringing another down does not take you up - think about your action!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/accountability-cross-community/attachments/20151110/5b681e9d/attachment-0001.html>


More information about the Accountability-Cross-Community mailing list