Hi, This is not really a fatal objection, and I can accept the inclusion since people seem to think it important (and because ultimately it's our charter that limits our freedom of action), but I continue to wonder why we keep including "collect" in the description of the RDS ("RDS, i.e., the system that may collect, maintain, and provide or deny access to some or all of those data elements [and services related to them, if any]"). The RDS _does not_ collect the data. That is the responsibility of the SRSes underlying registrations. I recall spending some time making diagrams illustrating this some months ago (it was before I moved back to Toronto, so it was before the end of June, but I don't recall when exactly). The RDS provides _access_ to that registration data. The RDS policies might have implications for registration policies (i.e. what data must be collected), but I cannot see how expanding our scope to talk about what registration _may_ collect is helpful. And we keep tripping over this because people point to consensus policies sometimes that are in fact about registration and not publication of the data. I therefore think that item 2 under "specific purpose" is actually false: that's the purpose of the SRS, and _not_ the RDS. The RDS is for lookup, and we should concentrate on that. Nit under "Goals": item iv is poor parallel construction. It could be fixed with "To help articilate [clearly, if you want] …" Best regards, A On Wed, Sep 28, 2016 at 05:12:29PM +0000, Marika Konings wrote:
Dear All,
Please find attached for your review the updated statement of purpose which aims to reflect the changes discussed during yesterday’s meeting. You are all encouraged to review this version, especially the section ‘Specific Purposes for Registration Data and Registration Directory Services’, and share your input with the mailing list prior to next week’s meeting. Also note that a couple of WG members (Marc & Fabrizio) volunteered to provide updated language for two specific parts of the document which have been flagged accordingly, so please hold your comments on those parts until the proposed language has been circulated.
Best regards,
Marika
Marika Konings
Senior Policy Director & Team Leader for the GNSO, Internet Corporation for Assigned Names and Numbers (ICANN)
Email: marika.konings@icann.org
Follow the GNSO via Twitter @ICANN_GNSO
Find out more about the GNSO by taking our interactive courses and visiting the GNSO Newcomer pages.
_______________________________________________ gnso-rds-pdp-wg mailing list gnso-rds-pdp-wg@icann.org https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg
-- Andrew Sullivan ajs@anvilwalrusden.com