[gnso-rds-pdp-wg] Notes and Action Items from RDS PDP WG Meeting - 9 March 2016

[Lisa Phifer]

ICANN55 - Marrakech

Session Title: Next-Generation RDS PDP WG Meeting - Wednesday 9 March 16.00
UTC

 

RDS PDP WG Wiki: https://community.icann.org/x/rjJ-Ag

 

Notes and Action Items

 

1.      Roll call / SOIs and Introductions (16.00-16.15)

 

.                  New members are welcome to join at any time but are
responsible for catching up on what has transpired before

.                  Observers can change status to Member (or vice versa) at
any time

.                  All members must complete SOIs and keep them up to date

 

2. Review of WG membership & expertise survey results (16.15-16.30)

 

.                  63 responses received (roughly half of WG members)

.                  For results, see
https://community.icann.org/download/attachments/58729156/RDS-PDP-Membership
-Review-Results-7March.pdf

 

Action Item #1: Small team to review membership survey results and make
recommendations on needed outreach (if any)

 

3. Overview and Q&A on process framework (16.30-16.45)

 

.                  Process Framework:
https://community.icann.org/download/attachments/56986648/next-generation-rd
s-framework-26apr15-en.pdf

.                  Overview Slides:
https://community.icann.org/download/attachments/58729196/RDS-Process-Framew
ork-Overview-090316.pdf

.                  Refer also to backgrounder distributed on email list:
http://mm.icann.org/pipermail/gnso-rds-pdp-wg/2016-March/000336.html

.                  First 5 questions are fundamental; next 6 are
cross-cutting

.                  Recommended order reflects inter-dependencies; thought to
be very important during phase 2-3 if the WG splits into subteams

.                  During phase 1, order is meaningful but may need to be
more fluid and iterative to come to a shared understanding

.                  How does the WG know when it is finished with phase 1?
The charter tasked the GNSO Council with questions to test whether
sufficient progress has been made to continue to next phases

.                  Note that requirements developed in phase 1 can
potentially include a requirement for a process to add new users or
purposes, if the WG chooses

.                  New consensus policies developed in phase 1 can change
the RDDS (whois) requirements currently specified in the 2013 RAA. Where
there is a policy change, consensus policy trumps contract requirements, but
implementation of policy must then take place (for example, Thick WHOIS
policy)

.                  Consensus policies developed by this PDP must be within
the remit of this PDP (that is, pertain to registration directory services).
However, any question within that scope can be considered by this WG,
including new questions not currently listed in the charter

.                  Where does RDAP fit into this PDP? System model, data
elements, and implementation guidance

.                  How do ongoing accuracy improvements fit into this PDP?
WHOIS ARS is an input to the question about accuracy; will need to
coordinate with continuing improvements

.                  Users/Purposes covers not just who should have access but
also why they should have access (that is, for what purpose). There is an
error in that question on the slide; the charter takes precedence. This
first question is intended to include what is the purpose of gTLD
registration directory services (but the WG can clarify or add questions as
part of its work)

.                  Where do IDNs and translation/transliteration fit into
the PDP? System mode, but again this needs to be coordinated with ongoing
work in that area

.                  Another important question is the overarching purpose of
gTLD registration directory services

.                  Does the charter ask the WG to decide whether a new
protocol is needed in phase 1? No, it tasks the WG with recommending a
whether an entire new system is needed - which may or may not include a new
protocol such as RDAP.

 

Action Item #2: All to read the process framework and charter and raise any
further questions to the WG list.

 

4. Review and discuss draft work plan, including next steps (16.45-17.30)

 

.                  Draft work plan reviewed during this part of the meeting:
https://community.icann.org/download/attachments/56986784/Draft-Phase1-WorkP
lan-29February2016.pdf

.                  Some initial tasks in the work plan have been completed,
such as Task 1, 5

.                  Task 2 (membership review) is underway

.                  Task 4 (input review) is ongoing but is important for all
WG members to start.

.                  Task 6 (work plan) - the topic of this session.

.                  Task 7 (outreach) is underway.

.                  Tasks 8-10 (possible requirements) will start after the
work plan drafting completes.

.                  Task 12 (deliberation on fundamental requirements) will
be a big part of the WG"s work.

.                  Tasks 13+ depend on initial recommendation for question
12.h: Is a next gen RDS needed or can the existing WHOIS system be modified
to satisfy requirements?

.                  When will group revise the process framework? It won't,
but it will decide how to apply the framework to the work plan and
deliberation on possible requirements (see Task 11)

.                  Proposal: Examine only a limited set of purposes and the
data elements for those purposes and application of data protection laws to
that data before considering all other purposes and their data elements.

.                  There are several proposals that have been made on the
list, need to consider all.

.                  When can additional questions be added? May occur during
Task 12 as the group deliberates and determines that a requirement for gTLD
registration directory services does not fit into existing questions.

 

Action Item #3: WG members to consult Background Materials on the wiki and
identify any topics where new primers or tutorials would be helpful.

 

5. Q&A (17.30-18.00)

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-rds-pdp-wg/attachments/20160309/c3d18721/attachment.html>