Loading…
This event has ended. Visit the official site or create your own event on Sched.
Welcome!  ICANN60 will be our Annual General Meeting for 2017. This seven-day meeting will be focused on outreach, capacity building, and showcasing ICANN’s work to a broader global audience. For general information about ICANN60, please visit http://icann60.abudhabi
View analytic
Saturday, October 28 • 08:30 - 12:00
GNSO Next-Generation Registration Directory Services (RDS) to replace WHOIS Policy Development Process Working Group Meeting

Sign up or log in to save this to your schedule and see who's attending!

Feedback form is now closed.
On 26 May, 2015, the ICANN Board reaffirmed its 2012 request for a Board-initiated PDP to define the purpose of collecting, maintaining and providing access to gTLD registration data, and to consider safeguards for protecting data, using the recommendations in the EWG’s Final Report as an input to, and, if appropriate, as the foundation for a new gTLD policy. Accordingly, the GNSO Next-Generation gTLD RDS PDP Working Group is currently working through phase 1 of the Board-requested PDP, using the Framework’s 3-phase process to (1) establish gTLD registration data requirements to determine if and why a next-generation RDS is needed, (2) design policies that detail functions that must be provided by a next-generation RDS to support those requirements, and (3) provide guidance for how a next-generation RDS should implement those policies, coexisting with and eventually replacing WHOIS. This session provides an opportunity for WG members, WG observers and guests to help shape possible requirements to be deliberated upon by this WG. The WG will strive to reach consensus on requirements, using them to decide if and why a next-generation RDS is needed to replace WHOIS. During this session, the WG will focus on making progress on near-term tasks outlined in the WG's work plan (see https://community.icann.org/x/oIxlAw). This session will be led by RDS PDP WG chair Chuck Gomes, supported by vice chairs David Cake, Susan Kawaguchi, and Michele Neylon and by ICANN Policy Staff members Marika Konings, Lisa Phifer, and Amr Elsadr. For further information about this PDP, please see https://community.icann.org/x/rjJ-Ag. Wiki agenda page: https://community.icann.org/x/oiIhB
-
Staff Leader: Marika Konings
Staff Facilitator: Nathalie Peregrine

Staff Leader & Facilitator
avatar for Marika Konings

Marika Konings

Vice President, Policy Development Support - GNSO, ICANN
Marika joined in July 2008. She serves as the Vice President, Policy Development Support - Generic Names Supporting Organization (GNSO). Prior to joining ICANN she was Director of European Affairs for the CyberSecurity Industry Alliance. Previously, Marika spent seven years as... Read More →
avatar for Nathalie Peregrine

Nathalie Peregrine

Manager, Operations Support (GNSO)



Saturday October 28, 2017 08:30 - 12:00
*Hall B, Sec. B/C (GNSO)
https://icann60abudhabi2017.sched.com/event/CbIZ/gnso-next-generation-registration-directory-services-rds-to-replace-whois-policy-development-process-working-group-meeting
icann60abudhabi2017.sched.com
crawl=CC-MAIN-2018-39
63256
application/http; msgtype=response
sha1:EWFZMGTCRAM64OR2RSUVBA3MUJXBSM6W
<urn:uuid:b5b1a351-c4de-4629-b1f3-20a4171cd2c0>
2018-09-22T21:47:55Z
108.62.103.29
application/xhtml+xml
sha1:FSZESHYBYM2ASAKPNIIQLSUB5YD3USMC
<urn:uuid:210f969b-c29a-4d80-8785-2299cbc735ca>
https://icann60abudhabi2017.sched.com/event/CbIZ/gnso-next-generation-registration-directory-services-rds-to-replace-whois-policy-development-process-working-group-meeting
response
<urn:uuid:253e0303-b5a0-4d06-9d08-d16a0c6e058c>
isPartOf: CC-MAIN-2018-39
publisher: Common Crawl
description: Wide crawl of the web for September 2018
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-138-196-149.ec2.internal
software: Apache Nutch 1.15 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 0.11-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: http://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/