[CCWG-ACCT] The Board's take on the Mission Statement

[Kavouss Arasteh]

Dear Becky
Thank you very much for the comparative works
I have noted that a major part  as contained in CCWG bullets are proposed
to be removed. These are important points and must be retained
Kavouss

2015-12-16 18:27 GMT+01:00 Seun Ojedeji <seun.ojedeji at gmail.com>:

> Okay I see the point, so it's really not about asking why role 2 (as I
> listed) is not covered in policy implementation because they are 2 distinct
> roles. It's more about asking why the dependencies are not evident in the
> current wording of the 2 roles.
>
> Regards
> My question, Seun, is why that is not already covered by implementation of
> policy.  I surely do not have an objection to ICANN allocating and
> assigning names in the root zone consistent with applicable policy (e.g.,
> New gTLD PDP, RFC 1591 in the case of ccTLDs), but absent that caveat, the
> addition seems potentially broad.
>
> *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: Seun Ojedeji <seun.ojedeji at gmail.com>
> Date: Wednesday, December 16, 2015 at 11:26 AM
> To: Becky Burr <becky.burr at neustar.biz>
> Cc: Accountability Community <accountability-cross-community at icann.org>
> Subject: Re: [CCWG-ACCT] The Board's take on the Mission Statement
>
> On Dec 16, 2015 17:00, "Burr, Becky" <Becky.Burr at neustar.biz> wrote:
> >
> >
> > I have asked Bruce to explain what is encompassed by "the allocation
> and assignment of names in the root zone” that is not covered
> by “coordination of the development and implantation of policies.”
> >
> SO(Not Bruce): The former is an action item in relation to RZ, the later
> is means to the former. We may be concerned if just the former is preferred
> but from your pasted table, I see that both was accommodated.
>
> I hope no one would argue that ICANN performs 2 main roles in relation to
> names;
> 1. Coordinate development and implementation of policies
> 2. Allocate names to the root zone
>
> So I don't see anything wrong in trying to reflect its actual role if
> indeed the goal is to ensure clarity on role.
>
> Regards
>
> > I encourage each of you to study the side-by-side comparison attached to
> determine for yourself whether the Board’s approach is consistent with the
> goals of clarifying ICANN’s limited Mission.
> >
> >
> > 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
> >
> >
> > _______________________________________________
> > Accountability-Cross-Community mailing list
> > Accountability-Cross-Community at icann.org
> > https://mm.icann.org/mailman/listinfo/accountability-cross-community
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_listinfo_accountability-2Dcross-2Dcommunity&d=CwMFaQ&c=MOptNlVtIETeDALC_lULrw&r=62cJFOifzm6X_GRlaq8Mo8TjDmrxdYahOP8WDDkMr4k&m=I_lsQXHH-_-YpVvnJPiJR-So7R07mgx9CAvYeXCUPlg&s=Ghv7wcAWeQryJQcT-w63p2pW38WmDtFSBwUET-1SVg4&e=>
> >
>
> _______________________________________________
> Accountability-Cross-Community mailing list
> Accountability-Cross-Community at icann.org
> https://mm.icann.org/mailman/listinfo/accountability-cross-community
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/accountability-cross-community/attachments/20151216/55ed2661/attachment.html>