[CCWG-ACCT] Attempt to summarize discussion regarding Mission and Contract
Alan Greenberg
alan.greenberg at mcgill.ca
Fri Nov 13 13:26:04 UTC 2015
Andrew, without commenting on the specific
wording issues, I strongly support the intent to
put words in the Bylaws to accurately reflect
ICANN's responsibilities related to Names as well
as both the numbering community and the protocol community.
I understand the possible difficulty of getting
it right, but it is something that we do need to fix at this point.
Alan
At 12/11/2015 09:16 PM, Andrew Sullivan wrote:
> > 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?”
> >
>
>I can't tell, but your earlier message with part of the other text I
>thought we'd already settled made me worried, too. So, here's what
>_I_ think is the state of affairs. I'm probably wrong, but maybe the
>fact that I'm confused and how will us to converge on what questions
>are still open. I thought it might be good to put down before the
>call tonight (I hope I wake up). This includes a bit I just saw from
>Greg, with some edits from me; I'll justify those in the other thread.
>I hope this is useful; if not, feel free to flame me off list.
>
>SLIGHT CONTROVERSY:
>
> The Mission of The Internet Corporation for Assigned Names and
> Numbers ("ICANN") is to ensure the stable and secure operation of
> the Internet's unique identifier systems as described below.
> Specifically, ICANN:
>
>***OR***
>
> The Mission of The Internet Corporation for Assigned Names and
> Numbers ("ICANN") is to ensure the stable and secure operation of
> the Internet's unique identifier systems in the ways described
> below. Specifically, ICANN:
>
>[The difference here is the "as described" vs "in the ways described".
>I think the latter is more flexible.]
>
>AGREED:
>
> 1. Coordinates the allocation and assignment of names in the root
> zone of the Domain Name System ("DNS"). In this role, ICANN’s
> Mission is to coordinate the development and implementation of
> policies:
>
> • For which uniform or coordinated resolution is reasonably
> necessary to facilitate the openness, interoperability,
> resilience, security and/or stability:
> • That are developed through a bottom-up, consensus-based
> multi- stakeholder process and designed to ensure the stable
> and secure operation of the Internet’s unique names systems.
>
> 2. Coordinates the operation and evolution of the DNS root name
> server system. In this role, ICANN’s Mission is to [to be provided
> by root server operators].
>
>[note: this could be called "controversial" since it's not filled in.]
>
> 3. Coordinates the allocation and assignment at the top-most
> level of Internet Protocol ("IP") and Autonomous System ("AS")
> numbers. ICANN’s Mission is described in the ASO MoU between ICANN
> and RIRs.
>
>SLIGHT CONTROVERSY:
>
> 4. Collaborates with other bodies as appropriate to publish core
> registries needed for the functioning of the Internet. In this
> role, with respect to protocol ports and parameters, ICANN's
> Mission is to provide registration services and open access for
> registries in the public domain requested by Internet protocol
> development organizations, such as the Internet Engineering Task
> Force.
>
>***OR***
>
> 4. Collaborates with other bodies as appropriate to publish core
> registries needed for the functioning of the Internet. In this
> role, with respect to protocol ports and parameters, ICANN's
> Mission is to provide registration services and open access for
> registries in the public domain requested by the Internet
> Engineering Task Force.
>
>[The difference here is the "such as". I prefer that a little bit
>because I think it is more consistent with the MoU between ICANN and
>the IETF and IAB -- ICANN's allowed to do this for other
>organizations, too.]
>
>AGREED:
>
> ICANN shall act strictly other than in accordance with, and only
> as reasonably appropriate to achieve its Mission.
>
>CONTROVERSIAL:
>
> ICANN shall not impose regulations on:
>
> • services (i.e., any software process that accepts
> connections from the Internet) that 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.
>
>[this is the latest version from Greg, adjusted to deal with what a
>"service" might be. I'll follow up on that text in that thread.]
>
>
>Best regards,
>
>A
>
>--
>Andrew Sullivan
><https://mm.icann.org/mailman/listinfo/accountability-cross-community>ajs
>at anvilwalrusden.com
>
>
> > Thanks,
> > Keith
> >
> > From:
> <https://mm.icann.org/mailman/listinfo/accountability-cross-community>accountability-cross-community-bounces
> at icann.org
> [mailto:accountability-cross-community-bounces
> at 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
> <<https://mm.icann.org/mailman/listinfo/accountability-cross-community>malcolm
> at linx.net<mailto:malcolm at 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<tel:%2B44%2020%207645%203523>
> > Head of Public Affairs | Read the LINX Public Affairs blog
> > London Internet Exchange |
> <http://publicaffairs.linx.net/>http://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
> >
> >
>
> > _______________________________________________
> > Accountability-Cross-Community mailing list
> >
> <https://mm.icann.org/mailman/listinfo/accountability-cross-community>Accountability-Cross-Community
> at icann.org
> > https://mm.icann.org/mailman/listinfo/accountability-cross-community
>
>
>--
>Andrew Sullivan
><https://mm.icann.org/mailman/listinfo/accountability-cross-community>ajs
>at anvilwalrusden.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/accountability-cross-community/attachments/20151113/3cefea97/attachment.html>
More information about the Accountability-Cross-Community
mailing list