[gnso-rds-pdp-wg] IMPORTANT: Notes from RDS PDP WG Meeting - 4 April
Lisa Phifer
lisa at corecom.com
Tue Apr 4 18:36:55 UTC 2017
Dear all,
Below please find notes from today's RDS PDP WG meeting.
To recap action items:
* Action Item #1: Staff to reflect proposed agreement on specific
purpose 1) and decision to defer discussion on purpose 5) in Working Draft.
* Action Item #2: Staff to test support using a poll (not this week
but but after "authoritive" is defined by WG - see below) for the split
purposes, using the term "access" and a footnote re: "authoritative"
* Action Item #3: WG volunteers to come up with a proposed definintion
of "authoritative" for use by the RDS, to be reviewed by the WG in next
week's call: Andrew Sullivan, David Cake, Michael Palage
* Action Item #4: All WG members to prepare for deliberation on
charter question on Data Elements by reviewing
<https://community.icann.org/download/attachments/64076964/Sullivan-Suggesti
onForPurposeInDetail.pdf> Andrew Sullivan's proposal,
<https://community.icann.org/download/attachments/64078512/EWG-AnnexD-ThinDa
taOnly.pdf?version=1&modificationDate=1491328937473&api=v2> Annex D of the
EWG final report (thin data only),
<https://community.icann.org/download/attachments/64078512/Merged-ThinDataPu
rposes-v1.pdf?version=1&modificationDate=1491326385242&api=v2>
Merged-ThinDataPurposes-v1.pdf, and Section 3.1 of
<https://community.icann.org/download/attachments/56986791/KeyConceptsDelibe
ration-WorkingDraft-7March2017.pdf?version=3&modificationDate=1489036968927&
api=v2> KeyConceptsDeliberation-WorkingDraft-7March2017.pdf
There will be NO POLL this week.
Best regards,
Lisa
Notes RDS PDP WG Meeting - 4 April 2017:
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 here: <https://community.icann.org/x/sMLRAw>
https://community.icann.org/x/sMLRAw
1) Roll Call/SOI Updates/New Member Intros
. Attendance will be taken from AC
. Please remember to state your name before speaking and remember to
mute your microphones when not speaking
. SOI Updates: none
. Several new Members joining or upgrading from Observer in the past
two weeks - see <https://community.icann.org/x/I4xlAw>
https://community.icann.org/x/I4xlAw
. Calls and polls are open only to Members; to upgrade from Observer
to Member (or join), email <mailto:gnso-secs at icann.org> gnso-secs at icann.org
directly
2) Review 28 March Poll on Purpose results:
. See SummaryResults-Poll-on-Purpose-from-28MarchCall.pdf
. 38 respondents
Q2: Alternatives to "1) A purpose of gTLD registration data is to provide
information about the lifecycle of a domain name."
. Alternative C has the greatest support (28) and least opposition
(6), although probably not strong enough to be rough consensus
Proposed Agreement (not quite rough consensus): A purpose of gTLD
registration data is to provide information about the lifecycle of a domain
name and its resolution on the Internet.
Action Item #1: Staff to reflect proposed agreement on specific purpose 1)
and decision to defer discussion on purpose 5) in Working Draft.
Q3: Alternatives to "2) A purpose of RDS is to provide an authoritative
source of information about, for example, domain contacts , domain names and
name servers for gTLDs, [based on approved policy]."
. More diversity in results, quite a lot of opposition - hard to
reach a conclusion
. Comments 5 & 6 propose a new alternative which is more concise: A
purpose of RDS is to facilitate possible dissemination of gTLD registration
data in accordance with applicable policy. (possible added by Chuck)
. Comment: Either an RDS disseminates data, or it does not. WHAT data
is as per policy.
. Alternative C and D (above) are fundamentally different
. Disagreement with adding "possible" - consider Alternative D: A
purpose of RDS is to provide an authoritative source of information about,
for example, domain contacts, domain names and name servers for gTLDs,
[based on approved policy].
. Parsing this into collection, storage, and used as a source for
access or disseminated - does this blend two or more purposes?
. A purpose is to provide an authoritative source... separate from
(2) A purpose is to facilitate dissemination....
. Concern over term "dissemination" - implies push out or publish -
suggest alternative "provide access to"
. Caveat with 1) is WG still needs a common understanding of what is
meant by "authoritative" as used by the RDS PDP WG recommendations
. Definition of "authoritative" as per the "thick" WHOIS PDP:
""Authoritative, withrespect to provision of Whois services, shall be
interpreted as to signify the single database within ahierarchical database
structure holding the data that is assumed to be the final authority
regardingthe question of which record shall be considered accurate and
reliable in case of conflicting records;administered by a single
administrative [agent] and consisting of data provided by the registrants
ofrecord through their registrars."
. Another specific use of "authoritative" is within the RDAP RFCs -
either we use the term consistently as there or we use a different term to
reflect what we mean
. Chat: authoritative data is _by definition_ accurate in the sense
that it's the real data, but it is not accurate in the sense of capturing
the world
. See also
<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource
s_pages_reconsideration-2D17-2D1-2Dsmith-2Drequest-2D2017-2D03-2D16-2Den&d=D
wMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=DZVUAuc1juldSXNq8YmDoa
dUOY0MfYdjlopAUQyOxRQ&m=GrmnmvPzthEFROEArSzfcgMS8J9Vc7G0tnCaMLIi_D4&s=SZuHDg
_aOAXdGj4EQF8nPk-kurwZYT_3lpnIUIibp7Y&e=>
https://www.icann.org/resources/pages/reconsideration-17-1-smith-request-201
7-03-16-en[icann.org]
Action Item #2: Staff to test support using a poll (not this week but rather
after "authoritive" is defined by WG - see below) for the split purposes,
using the term "access" and a footnote re: "authoritative."
. (2a) A purpose is to provide an authoritative source... (footnote
"authoritative")
. (2b) A purpose is to provide access to...
Action Item #3: WG volunteers to come up with a proposed definintion of
"authoritative" for use by the RDS,
to be reviewed by the WG in next week's call: Andrew Sullivan, David Cake,
Michael Palage
Q4: Alternatives to "5) A purpose of RDS policy is to facilitate the
accuracy of gTLD registration data."
. Five (5) respondents suggested deleting this purpose entirely
. Equal levels of support for Altenatives A and C (difference is
whether or not to include footnote) 22 in support, 8 opposed for both
. Possibly table further discussion on "accuracy" until we get to the
accuracy conversation
. Questions regarding active participation of RDS in accuracy,
charter tasks WG with defining accuracy requirements and policy but the RDS
may or may not be an active participant - it may improve accuracy without
being actively involved (in a new RDS system where privacy is protected,
more accurate data may be entered because registrants are less afraid of
doing so)
. Red/Green poll on deletion produced very mixed results
. Proposal: Lacking clear direction, and unlikely to get clear
direction from poll, retain Alternative A for now, include clear notation
there is divergence on this, and revisit later
. Alternative (resolution for now) is placeholder: "Accuracy as it
pertains to the RDS will be defined later in this PDP (see Charter question
on Accuracy)."
3) Review updated Work Plan: <https://community.icann.org/x/oIxlAw>
https://community.icann.org/x/oIxlAw
. A few potential target dates have been set:
. 12.a) Started deliberation on all 3 questions
. Starting data elements today (4 April)
. 12.b) Starting "thick data" by 2 May for those same questions
. 13.a) Goal from last week: 28 October (ICANN60 Abu Dabi meeting
start)
. Need to plot a timeline to progress from 12a/b to 13
4) Proposed approaches to define purposes for each data element:
. See Section 3 of
<https://community.icann.org/download/attachments/56986791/KeyConceptsDelibe
ration-WorkingDraft-7March2017.pdf?version=3&modificationDate=1489036968927&
api=v2> KeyConceptsDeliberation-WorkingDraft-7March2017.pdf and
<https://community.icann.org/download/attachments/64076964/Sullivan-Suggesti
onForPurposeInDetail.pdf?version=1&modificationDate=1490583766000&api=v2>
Sullivan-SuggestionForPurposeInDetail.pdf and Annex D of
<https://www.icann.org/en/system/files/files/final-report-06jun14-en.pdf>
EWG Final Report
. Intent of suggestion was to provide a working example of how to
approach matching purposes across "thin" data elements, taking into
consideration EWG final report and the information provided by the privacy
experts at ICANN58
. Put together a matrix that ties data elements to each purpose
already addressed, or yet to be addressed (iterative process) - create very
specific purposes for collection of data elements
. Be sure to keep in mind work done and recommendations in the EWG
final report while deliberating purpose now
. Refer to purposes listed for each data element in
<https://community.icann.org/download/attachments/64078512/EWG-AnnexD-ThinDa
taOnly.pdf?version=1&modificationDate=1491328937473&api=v2> Annex D of the
EWG final report (thin data only)
. Next week, we will deliberate on this under charter question on
Data Elements, see section 3.1
. Plan for next week is to go through "thin" data elements one by
one, and use purposes recommended in the EWG final report as a starting
point of discussion
. "Sanity check": Develop consensus on purposes for thin data, and
ensure that they do not conflict with local privacy/data protection laws
(example: GDPR) - Intent of suggestion by Andrew Sullivan is to address
purpose for each data elements being collected to mitigate concerns raised
by privacy experts at ICANN58 on GDPR
Action Item #4: All WG members to prepare for deliberation on charter
question on Data Elements by reviewing
<https://community.icann.org/download/attachments/64076964/Sullivan-Suggesti
onForPurposeInDetail.pdf> Andrew Sullivan's proposal,
<https://community.icann.org/download/attachments/64078512/EWG-AnnexD-ThinDa
taOnly.pdf?version=1&modificationDate=1491328937473&api=v2> Annex D of the
EWG final report (thin data only),
<https://community.icann.org/download/attachments/64078512/Merged-ThinDataPu
rposes-v1.pdf?version=1&modificationDate=1491326385242&api=v2>
Merged-ThinDataPurposes-v1.pdf, and Section 3.1 of
<https://community.icann.org/download/attachments/56986791/KeyConceptsDelibe
ration-WorkingDraft-7March2017.pdf?version=3&modificationDate=1489036968927&
api=v2> KeyConceptsDeliberation-WorkingDraft-7March2017.pdf
5) Confirm action items and proposed decision points
. Action Item #1: Staff to reflect proposed agreement on specific
purpose 1) and decision to defer discussion on purpose 5) in Working Draft.
. Action Item #2: Staff to test support using a poll (not this week
but but after "authoritive" is defined by WG - see below) for the split
purposes, using the term "access" and a footnote re: "authoritative"
. Action Item #3: WG volunteers to come up with a proposed
definintion of "authoritative" for use by the RDS, to be reviewed by the WG
in next week's call: Andrew Sullivan, David Cake, Michael Palage
. Action Item #4: All WG members to prepare for deliberation on
charter question on Data Elements by reviewing
<https://community.icann.org/download/attachments/64076964/Sullivan-Suggesti
onForPurposeInDetail.pdf> Andrew Sullivan's proposal,
<https://community.icann.org/download/attachments/64078512/EWG-AnnexD-ThinDa
taOnly.pdf?version=1&modificationDate=1491328937473&api=v2> Annex D of the
EWG final report (thin data only),
<https://community.icann.org/download/attachments/64078512/Merged-ThinDataPu
rposes-v1.pdf?version=1&modificationDate=1491326385242&api=v2>
Merged-ThinDataPurposes-v1.pdf, and Section 3.1 of
<https://community.icann.org/download/attachments/56986791/KeyConceptsDelibe
ration-WorkingDraft-7March2017.pdf?version=3&modificationDate=1489036968927&
api=v2> KeyConceptsDeliberation-WorkingDraft-7March2017.pdf
Proposed Agreement (not quite rough consensus) for Specific Purpose 1)
1) A purpose of gTLD registration data is to provide information about the
lifecycle of a domain name and its resolution on the Internet.
Decision Point for Specific Purpose 5)
Defer discussion by replacing with a placeholder: "[Accuracy as it pertains
to the RDS will be defined later in this PDP (see Charter question on
Accuracy).]"
6) Confirm next meeting date: 11 April, 2017 at 16:00 UTC
Meeting Materials (all posted at https://community.icann.org/x/sMLRAw)
.
<https://community.icann.org/download/attachments/64078512/Merged-ThinDataPu
rposes-v1.pdf?version=1&modificationDate=1491326385242&api=v2>
Merged-ThinDataPurposes-v1.pdf (initial rough draft displayed during call)
.
<https://community.icann.org/download/attachments/64076964/Sullivan-Suggesti
onForPurposeInDetail.pdf?version=1&modificationDate=1490583766000&api=v2>
Sullivan-SuggestionForPurposeInDetail.pdf and
<https://community.icann.org/download/attachments/64076964/Sullivan-Suggesti
onForPurposeInDetail.docx?version=1&modificationDate=1490583779000&api=v2>
doc
.
<https://community.icann.org/download/attachments/56986791/KeyConceptsDelibe
ration-WorkingDraft-7March2017.pdf?version=3&modificationDate=1489036968927&
api=v2> KeyConceptsDeliberation-WorkingDraft-7March2017.pdf and
<https://community.icann.org/download/attachments/56986791/KeyConceptsDelibe
ration-WorkingDraft-7March2017.docx?version=3&modificationDate=1489036982656
&api=v2> doc
.
<https://community.icann.org/download/attachments/64078512/EWG-AnnexD-ThinDa
taOnly.pdf?version=1&modificationDate=1491328937473&api=v2> Annex D of the
EWG final report (thin data only) - excerpted from full
<https://www.icann.org/en/system/files/files/final-report-06jun14-en.pdf>
EWG Final Report
.
<https://community.icann.org/download/attachments/56986784/RDS%20PDP%20WG%20
Work%20Plan%20-%20Clean%203%20April%202017.docx?version=1&modificationDate=1
491239583533&api=v2> Latest RDS PDP WG Phase 1 Work Plan - as of April 2017
(posted 3 April 2017)
. 28MarchCall Poll on Purpose -
o Link to participate: Poll closed on 1 April
o PDF of Poll Questions:
<https://community.icann.org/download/attachments/64076964/Poll-on-Purpose-f
rom-28MarCall.pdf?version=1&modificationDate=1490794620000&api=v2>
Poll-on-Purpose-from-28MarCall.pdf
o SurveyMonkey PDF of Summary Poll Results:
<https://community.icann.org/download/attachments/64078512/SummaryResults-Po
ll-on-Purpose-from-28MarchCall.pdf?version=1&modificationDate=1491150106000&
api=v2> SummaryResults-Poll-on-Purpose-from-28MarchCall.pdf
o SurveyMonkey Zip of Poll Raw Results:
<https://community.icann.org/download/attachments/64078512/RawData-Poll-on-P
urpose-from-28MarCall.zip?version=1&modificationDate=1491150124000&api=v2>
RawResults-Poll-on-Purpose-from-28MarchCall.zip
o Annotated Results:
<https://community.icann.org/download/attachments/64078512/AnnotatedResultsF
orACDisplay-Poll-28MarchCall.pdf?version=1&modificationDate=1491257793000&ap
i=v2> AnnotatedResultsForACDisplay-Poll-28MarchCall.pdf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-rds-pdp-wg/attachments/20170404/af86af5d/attachment-0001.html>
More information about the gnso-rds-pdp-wg
mailing list