<html>
<body>
<font face="Arial, Helvetica">Dear all,<br><br>
Below please find notes and action items from today's RDS PDP WG call.
<br><br>
Attached are the slides introduced by Chuck today, along with the Charter
Questions/Subquestions Mind Map. All WG members are asked to review these
materials in preparation for our F2F meeting at ICANN57, where we will
start deliberating on subsets of possible requirements. As a reminder,
the latest possible requirements list can be downloaded from
</font><a href="https://community.icann.org/x/shOOAw" eudora="autourl">
<font face="Arial, Helvetica" color="#0000FF"><u>
https://community.icann.org/x/shOOAw<br><br>
</a></u></font><font face="Arial, Helvetica">A redline documenting the
output of agenda item 2 (statement of purpose) will be circulated
separately and also posted on the wiki page linked below for your review
and comment.<br><br>
Best, Lisa<br><br>
<b>Notes 25/10 – RDS PDP WG Meeting<br><br>
</b><i>These high-level notes are designed to help PDP WG members
navigate through the content of the call and are not meant as a
substitute for the transcript and/or recording. The MP3, transcript, and
chat are provided separately and are posted on the wiki at
<a href="https://community.icann.org/x/LyS4Aw" eudora="autourl">
https://community.icann.org/x/LyS4Aw<br><br>
</a></i>1) Roll call/SOI update<br>
· Roll call will be taken from
AC<br>
· Please remember to update
your SOI<br><br>
2) Continue work on statement of purpose <br>
· Latest version dated 25
October:
<a href="https://community.icann.org/x/tiW4Aw" eudora="autourl">
https://community.icann.org/x/tiW4Aw</a>)<br>
· Additional comments submitted
by Peter Kimpian have also been reflected version displayed
on-screen<br>
· re: proposed alternative term
"ensure" - this may be too strong. "Promote" may not
be the right term either - or is it a reasonable description?<br>
· re: leadership team proposed
alternative phrasing - promoting both availability and accuracy may be
desirable.<br>
· Another alternative
phrasing: "A purpose of RDS is to provide an authoritative
source of registration data. A purpose of RDS is to collect
accurate data." We need to associate "accuracy" with
"collection" in some way, not with display.<br>
· Is purpose statement
co-mingling the goals of the RDS system with the goals of the policy
framework surrounding it?<br>
· Note that
"Authoritativeness" was discussed at length in the Thick Whois
PDP WG: see report
<a href="https://gnso.icann.org/en/issues/whois/thick-final-21oct13-en.pdf" eudora="autourl">
https://gnso.icann.org/en/issues/whois/thick-final-21oct13-en.pdf</a> at
pp. 35-38<br>
· Further alternative phrasing:
"A purpose of RDS is to provide authoritative access to registration
data." Focuses on RDS providing access to data, obtained from
authoritative source.<br>
· What's in the registry is
authoritative. What the registrar collects is a separate issue. One of
the reasons that a PDP decided that all gTLDs should be "Thick"
is to ensure that registries had all of the data and could be
authoritative.<br>
· Authoritativeness is
"Not to be confused with accuracy: accurate data is not necessarily
authoritative nor is authoritative data necessarily accurate." For
example, "accurate" data for someone else may be used
fraudulently in another registration. By some definitions, this would be
considered "inaccurate."<br>
· Straw poll: "A purpose
of RDS is to provide authoritative access to registration data."
Question: What does "authoritative" mean in this context?
Possible alternatives: "access to authoritative registration
data" or "provide an authoritative source of data."
Authoritative may be considered more precise than
"reliable."<br>
· Can #2 and #5 be merged with
regard to authoritative source of information. [Note that listed data
isn't necessarily exhaustive - that will be defined by policy.] If so, #5
can be dropped, at least with regard to "authoritative" -
remaining text in #5 then deals with accuracy.<br>
· With regard to accuracy, a
database store data to make it accessible - but this system may not be
responsible for promoting accuracy. The requirement for accuracy should
be applied to the data itself.<br>
· "Service" not equal
"System" - the service reflects policy and should provide
accurate data; a database system stores that data...<br>
· "Draft Registration Data
and Directory Service Statement of Purpose" means we can talk about
policy without tying it into a specific technical implementation.<br>
· We need to distinguish better
between the instrument and the policy - proposed text "A purpose of
RDS policy..."<br>
· We may need to look at every
place we use "RDS" and determine what we mean by it, and
whether it should be followed by "policy."<br><br>
<b>Action:</b> Staff to capture this proposed text for #2 and #5, as well
as Peter Kimpian's comments, for discussion on-line/after
ICANN57.<br><br>
3) Brief update on ICANN57 plans:<br>
· Introduce approach for
deliberations on possible requirements<br>
· Refer to draft slides to be
posted on meeting page and also used at ICANN57.<br>
· Iterating through 3 charter
questions in a randomized manner, per our work plan - this proposal
explores how that will occur.<br>
· Prerequisites, dependencies,
codes, and keywords are not fixed but intended to help organize possible
requirements in various ways during deliberation.<br>
· Randomized approach is
intended to not favor one question over another and get past barrier that
WG could not agree upon which should come first for deliberation<br>
· Iterative approach reflects
interdependencies between questions, allowing all to be considered during
deliberation<br>
· See proposed approach for
selecting subsets for deliberation - gives us a place to start but allows
for adjustment as we go<br><br>
<b>Action:</b> Staff to re-distribute Mind Map along with draft slides
describing this approach. All WG members to review these materials to
prepare for our WG F2F meeting at ICANN57.<br><br>
4) Confirm next meeting date: Thursday, 3 November 2016 at ICANN57 (see
http://sched.co/8cxj)<br>
<br><br>
<b>Meeting Materials:<br>
</b>· Statement of purpose
(latest version dated 25 October:
<a href="https://community.icann.org/x/tiW4Aw">
https://community.icann.org/x/tiW4Aw</a>)<br>
· Draft approach to start
deliberations:
<a href="https://community.icann.org/download/attachments/62399535/RDS-PDP-WG-StartOfDeliberationSlides-Draft6.pdf?version=1&modificationDate=1477417638015&api=v2">
RDS-PDP-WG-StartOfDeliberationSlides-Draft6.pdf</a><br>
· Mind Map:
<a href="https://community.icann.org/download/attachments/58739599/RDS-PDP-Phase1-FundamentalQs-SubQs-MindMap-2May%202016.pdf?version=1&modificationDate=1462234568000&api=v2">
RDS-PDP-Phase1-FundamentalQs-SubQs-MindMap-2May 2016.pdf</a><br>
· ICANN57 RDS PDP WG Meeting
<a href="http://sched.co/8cxj">Session Description</a><br>
</font></body>
</html>