[cc-humanrights] proposed agenda

Thu Jan 21 17:57:40 UTC 2016

Sorry I missed the call (again) - it seems so difficult to remember at the
scheduled time....but I always remember just when its finished!

Sigh!

Karel

On Thu, Jan 21, 2016 at 1:04 PM, <vidushi at cis-india.org> wrote:

> Hello,
>
> I seem to have dropped off the call again. Here is the update from SG2:
>
> We are looking at documenting cases and examples in which ICANN is
> potentially impacting human rights.
>
> We decided to keep the mandate of our work restricted to those issues that
> will not overlap with the other SGs.
>
> The initial list of potential topics was:
>
> 1. The new gTLD Subsequent Procedures PDP: In the Preliminary Issues
> Report (31 August 2015), a set of 30+ issues have been set out. The
> following issues are missing or inadequately dealt with: (a) WHOIS
> privacy;(b) Freedom of expression considerations wrt to gTLD  applications,
> string contention and dispute resolution. This issue is noted in the
> Preliminary Report, and references the CoE report on ICANN and human rights
> (October 2014), but does not consider the list or scope of issues involved.
>
> 2. UDRP: In Clause 4(a) on Mandatory Administrative Proceedings for
> Applicable Disputes, the scope of applicable disputes is limited to
> trademark-related disputes. Issues surrounding freedom of expression,
> privacy, community interests in a domain name, geographical interests
> indomain names, etc. are not addressed.
>
> 3. Name Collisions Management Framework: The framework does not set out a
> process to hear parties with colliding names, but only authorises
> registries to undertake controlled interruption.
>
> 4. WHOIS and privacy, in light of the new PDP
>
> 5. gTLD Registration Data Services (RDS) :
> http://gnso.icann.org/en/group-activities/active/rds. There are WHOISdata
> access and accuracy questions. Not at public comment stage.
>
> 6. New gTLD Subsequent Procedures :
> http://gnso.icann.org/en/group-activities/active/new-gtld-subsequent-procedures.Issues
> of access & affordability, etc. PDP hasn't started yet. Preliminary Issues
> Report filed.
>
> 7. Proposed Implementation of GNSO Thick Whois Consensus Policy Requiring
> Consistent Labeling and Display of RDDS (Whois) Output forAll gTLDs :
> https://www.icann.org/public-comments/rdds-output-2015-12-03-en.Public
> comment is open and closes in 2 weeks. WHOIS privacy and access to domain
> name holder's data.
>
> 8. Geographic Regions Review Working Group -
> https://www.icann.org/public-comments/geo-regions-2015-12-23-en.Public
> comment period ongoing. Issues of substantive v. formal
> representation/inclusiveness, of proportional representation based on(for
> ex) number of Internet users across the continents.
>
> 9. Preliminary Issue Report on a GNSO Policy Development Process to Review
> All Rights Protection Mechanisms in All gTLDs -
> https://www.icann.org/public-comments/rpm-prelim-issue-2015-10-09-en.Public
> comment for Prelim Issue Report is closed, but PDP continues.This will
> affect UDRP, Rapid Suspension procedure and otherrights-protection measures
> for the gTLDs.
>
> 10. IAG Initial Report and Proposed Revisions to the ICANN Procedurefor
> Whois Conflicts with Privacy Laws -
> https://www.icann.org/public-comments/iag-whois-conflicts-privacy-2015-10-05-en.Public
> comment complete for this report.
>
>
> 11. Phase 1 Assessment of the Competitive Effects Associated with theNew
> gTLD Program -
> https://www.icann.org/public-comments/competitive-effects-assessment-2015-09-28-en.Public
> comment period complete. Affects affordability, etc. WithinICANN, this will
> be considered alongside the Competition, ConsumerTrust and Consumer Choice
> (CCT) review of the New gTLD Program.
>
> Based on the decision about the scope of our SG, we decided to focus on 2,
> 3, 8 and 9.
>
> We will have a call in the coming week to discuss our findings and take a
> call on how we want to take this further before Marrakesh.
>
> I would request members of the other SGs to please look over this list and
> let us know if there are topics that do not overlap with your work that we
> could look into.
>
> Sorry about the connectivity issues today and hope everyone has a great
> day!
>
> Vidushi
>
> ----- On Jan 21, 2016, at 7:27 PM, Niels ten Oever niels at article19.org
> wrote:
>
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA256
> >
> > Dear all,
> >
> > I hope this email finds you well. I'm looking forward to talk to you
> > on our call later today at 1600 UTC.
> >
> > I would like to propose the following agenda:
> >
> > 1. Welcome and agenda bashing
> > 2. Update CCWG - update on the last possible bylaw language
> > 3. Update SG1
> > 4. Update SG2
> > 5. Update SG3
> > 6. Update SG4
> > 7. Update SG5
> > 8. Update operational issues
> > 9. AOB
> >
> > Looking forward to talk to you all in two hours.
> >
> > Best,
> >
> > Niels
> >
> >
> > - --
> > Niels ten Oever
> > Head of Digital
> >
> > Article 19
> > www.article19.org
> >
> > PGP fingerprint    8D9F C567 BEE4 A431 56C4
> >                   678B 08B5 A0F2 636D 68E9
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v2
> >
> > iQEcBAEBCAAGBQJWoOOtAAoJEAi1oPJjbWjpFPEIAI2pT3Ukc+0zpqciIfGltRyh
> > Pj7FFDR8FviOgOBjHOE11epmaUYodLi72SHjFJwflp4C0Du3YKMlkUV4IwY5OESs
> > S9hS2hgkvXAqt6hAV3CioBJ/QTb+E/XnUiyBhrxZeOErcqJDgZAH39eoOomz6ve4
> > bysTofbUDMFv2lBo9gF8XkY7rUFrkeuVeaXHnXLUZn87JuyVX/p86PQHQrRzhU57
> > FTOmV2BF5BdlqwT4z+6PmHfi0FBpYkOjkJ3wnRxnfuTp1YHIBbh+kHnmYlCtUCK2
> > QFIoVPXGDLvEuTmtUpefb2ZRHppmG2FvEQpdNvM/tWEyxS0Pst6lI80YazIrAkA=
> > =nXg4
> > -----END PGP SIGNATURE-----
> > _______________________________________________
> > cc-humanrights mailing list
> > cc-humanrights at icann.org
> > https://mm.icann.org/mailman/listinfo/cc-humanrights
> _______________________________________________
> cc-humanrights mailing list
> cc-humanrights at icann.org
> https://mm.icann.org/mailman/listinfo/cc-humanrights
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/cc-humanrights/attachments/20160121/235a56ab/attachment.html>