[Internal-cg] Charter commenting

Joseph Alhadeff joseph.alhadeff at oracle.com
Tue Aug 5 10:08:39 UTC 2014

Alissa as relates to questions of our own process and transparency we  should be ready to accept direct comments, as to the RFMWJE related proposals we should try to make, sure those are channeled in the processes at the outset.  In all cases we should highlight that comments which are part of larger community of interstate comments are always preferred as it improves our ability to manage the number of comments as well as helps better understand the provenance of the comment.  I would be concerned if anyone read our phrasing as an attempt to preclude comments not coming through a community... as I have noted in previous messages I think we deal with when we can accept comments on proposal topics separately from when and how we address comments on ICC processes...


Sent from my Android phone using TouchDown (www.nitrodesk.com)

-----Original Message-----

From: Mohamed El Bashir [mbashir at mbash.net]
Received: Tuesday, 05 Aug 2014, 10:42AM
To: Alissa Cooper [alissa at cooperw.in]
CC: ICANN Internal [internal-cg at icann.org]
Subject: Re: [Internal-cg] Charter commenting

Thanks Alissa for proceeding with this process, i support the bellow
is practical and clear. formal/Clear processes and procedures are important
for ICG work/outcomes.

The communities as well should be encouraged to review the submitted
comments received from stakeholders outside their constituents.

ICANN staff can also create a page which include clear instructions how
participate and submit comments to the different IANA-related communities
processes, this will be helpful as we move ahead.

Looking forward to receive formal communities comments on the charter and
other future documents, these community comments will ensure that the
current created IANA-related community process are working and producing
consultative outcomes submitted to ICG.


On Tue, Aug 5, 2014 at 2:56 AM, Alissa Cooper <alissa at cooperw.in> wrote:

> Here is some proposed text for the landing page that describes the charter
> commenting process:
> ICG Charter Open for Public Comments
> On July 18, the IANA Stewardship Transition Coordination Group (ICG)
> produced a draft charter <link> that defines its own tasks. The charter is
> open for public comment until August XX, 2014 at 20:00 UTC. <bold>It is
> the strong preference of the ICG that comments about the charter from the
> public be submitted via existing IANA-related community processes, and NOT
> through the link provided below.</bold> If you need assistance finding
> those processes or contacting the appropriate ICG participant, please
> contact <secretariat-email>. If you are absolutely not able to provide
> comments through a relevant community or ICG participant, a mechanism for
> submitting comments via an email alias is linked below.
> Please be aware that the ICG views defining the broad outlines of its
> charter as important, but it views finalizing the charter and moving on to
> the real work of the transition planning to be of equal importance. As a
> result not all comments submitted concerning the charter will necessarily
> be incorporated.
> Public comment submission process links:
> Comment submission: <link>
> List of comments submitted via this site: <link>
> Charter: <link>
> Deadline: August XX, 2014 at 20:00 UTC
> On 8/4/14, 4:41 PM, "Alissa Cooper" <alissa at cooperw.in> wrote:
> >Not too many people have commented on this, but all the comments are in a
> >similar direction, so I’m going to go ahead and ask the ICANN folks to
> >setup a forum and get a page ready that has all the relevant details,
> >including a notice along the lines that Daniel proposes below about our
> >much preferred communication mechanism being via the relevant communities
> >and ICG participants. I’d like to also list an email address contact for
> >the secretariat on the forum landing page, so that if people don’t know
> >how to find a particular community or ICG participant, the secretariat can
> >help point those people in the right direction or ask us for such
> >direction.
> >
> >Let’s give a 10-day comment period once the page and forum get setup —
> >compromise between 7 and 14. :) Plus if we do that we should have a decent
> >chance of having some synthesis of the charter comments ready in time for
> >our to-be-scheduled teleconference in late August.
> >
> >Comments welcome on this plan, of course.
> >Alissa
> >
> >On 8/4/14, 8:30 AM, "Daniel Karrenberg" <daniel.karrenberg at ripe.net>
> >wrote:
> >
> >>Hash: SHA1
> >>
> >>
> >>
> >>I agree that we should set up a mechanism for comments from the
> >>general public with the following properties:
> >>
> >>It clearly, bluntly, repeatedly and unavoidably states that the
> >>preferred method for participation is via the relevant communities.
> >>  Maybe we should have a check box where people have to acknowledge
> >>that they understand this before they can post a comment. ;-)
> >>
> >>All comments should be stored in a public archive for all to see,
> >>including for us. Comments in this archive should be kept available
> >>for all to see for at least 5 years after they are made.
> >>
> >>Discussion should be strongly discouraged in this mechanism. There are
> >>other places for that already; the most appropriate are the relevant
> >>communities.
> >>
> >>We can then see all these comments and take them into account as
> >>appropriate.
> >>
> >>
> >>- ----
> >>
> >>
> >>Comments for the charter should be treated as just a special case of
> >>the above.  14 calendar days is about the right time for this as this
> >>is about the time we would need to get substantive comments from our
> >>communities and I do not see that final agreement on the charter will
> >>substantially delay our other current work.
> >>
> >>
> >>Daniel
> >>Version: GnuPG v1.4.7 (Darwin)
> >>
> >>iQIVAwUBU9+nINDY5Emqa716AQLdBQ//SiFPTNCCn69DUAeN44Q0zrUdzwnw924H
> >>JIGV5mNTO2BaHrwdgdJOm1D7PZUIHkyOPZ56OorvXWyQDgZy0bM7jA/P0IuHAfXL
> >>CtSGI2+o5jqmN/er00JaS1M7XvjD+1ELC0OkG5zmUY8PD1W+yOGreJ0P2e6y/T7A
> >>9SQr1aaGCASlPrCRFTZ3yggSBzkIh1/atlcZk84tnYf04hnTmjuX3w8eJIt9kixp
> >>qzRZj8qOTyRW8fbQNYD9BeiMiqpcha4uaU27/gK0Xa91LtQoVGFY5sRceRcBHp4C
> >>XiqlH1QQa2vN2AXvQJ3uAVJep/CCUCBRl+i/rfAcjTA7TWegNL6PEidTbatJzGO4
> >>NC36/UDflT99KcGM7F8i/UBDcIiiv56vjbzRez7id7VRQMVxn58pLusKVDYHkkQc
> >>JDVgo3IB9HETfUqRr3gFQYA9Wx7gklF0ssbZuoz70534r2CQzEtqGOlqC/6OJzjx
> >>u4PsUhHPlnkzJk+P1k3o0eC6TqrRTzpGwblDiiq5/bGCDmNXBXZW9NXTWewwbB9q
> >>ZxuP6K0BNiM1pKLXkHlTw3IQNVtIFKodIjHnp/b0vcGtGYEz7gBu4lHhJHbzks9/
> >>SUNpeIRcPeVUD92+G75MDDNDlli/+sFu89pOrv0l8x6y0KOikILLpknlY9+BlHZC
> >>WmXf5z9aPHg=
> >>=1pee
> >>-----END PGP SIGNATURE-----
> >>_______________________________________________
> >>Internal-cg mailing list
> >>Internal-cg at icann.org
> >>https://mm.icann.org/mailman/listinfo/internal-cg
> >
> >
> >_______________________________________________
> >Internal-cg mailing list
> >Internal-cg at icann.org
> >https://mm.icann.org/mailman/listinfo/internal-cg
> _______________________________________________
> Internal-cg mailing list
> Internal-cg at icann.org
> https://mm.icann.org/mailman/listinfo/internal-cg

More information about the Internal-cg mailing list