Why are we spending time on a RDS Purpose statement?
Some of us, myself included, have been getting impatient because of the time we have been spending on a RDS purpose statement. In that regard, Lisa reminded me of why it is important to do that and I want to forward her comments to the full WG. The following is a direct quote from her message. "We are attempting to be responsive to the board and SSAC request for this PDP to address up front this question: "Resolved (2015.04.26.10), the Board reaffirms its request for a Board-initiated GNSO policy development process to define the purpose of collecting, maintaining and providing access to gTLD registration data, and consider safeguards for protecting data, using the recommendations in the Final Report<https://www.icann.org/en/system/files/files/final-report-06jun14-en.pdf> [PDF, 5.12 MB] as an input to, and, if appropriate, as the foundation for a new gTLD policy." In SAC055, WHOIS: Blind Men and an Elephant<https://www.icann.org/en/system/files/files/sac-055-en.pdf>, [1] the SSAC found that further work should be undertaken prior to implementation of the WHOIS Policy Review Team?s recommendations, concluding: "1. It is critical that ICANN should develop a policy defining the purpose of domain name registration data; 2. ICANN should create a committee to develop a registration data policy that defines the purpose of domain name registration data; and 3. ICANN should defer other activity directed at finding a ?solution? to ?the WHOIS problem? until the registration data policy identified in (1) and (2) has been developed and accepted." This is why this WG must examine not just policies that pertain to access, and not just a system that provides that access, but the entire purpose of collecting, maintaining, and providing access to data. This applies whether that system is a new next-gen system or an updated WHOIS system. If we cannot make some headway on the question of purpose, as SAC055 pointed out and the board agreed, then we are unlikely to make headway on specific policies intended to support each stakeholder's varying and sometimes divergent views about what the purpose should be. Chuck
+1. You could have added the ALAC's position - coming on a decade now! - to those quoted. Get the purpose right and everything else, arguments hither and thither, fall in place. Here's the takeaway though. You can depend on Lisa to keep the essence of the deal top of mind! I don't get weary reminding all she was a tower of strength working with the EWG for the same reasons. -Carlton ============================== *Carlton A Samuels* *Mobile: 876-818-1799Strategy, Planning, Governance, Assessment & Turnaround* ============================= On Fri, Sep 30, 2016 at 4:28 PM, Gomes, Chuck <cgomes@verisign.com> wrote:
Some of us, myself included, have been getting impatient because of the time we have been spending on a RDS purpose statement. In that regard, Lisa reminded me of why it is important to do that and I want to forward her comments to the full WG. The following is a direct quote from her message.
“We are attempting to be responsive to the board and SSAC request for this PDP to address up front this question:
*"Resolved (2015.04.26.10)*
*, the Board reaffirms its request for a Board-initiated GNSO policy development process to define the purpose of collecting, maintaining and providing access to gTLD registration data, and consider safeguards for protecting data, using the recommendations in the Final Report <https://www.icann.org/en/system/files/files/final-report-06jun14-en.pdf> [PDF, 5.12 MB] as an input to, and, if appropriate, as the foundation for a new gTLD policy." *In SAC055, WHOIS: Blind Men and an Elephant <https://www.icann.org/en/system/files/files/sac-055-en.pdf>, [1] the SSAC found that further work should be undertaken prior to implementation of the WHOIS Policy Review Team?s recommendations, concluding:
*"1. It is critical that ICANN should develop a policy defining the purpose of domain name registration data; 2. ICANN should create a committee to develop a registration data policy that defines the purpose of domain name registration data; and 3. ICANN should defer other activity directed at finding a ?solution? to ?the WHOIS problem? until the registration data policy identified in (1) and (2) has been developed and accepted." *This is why this WG must examine not just policies that pertain to access, and not just a system that provides that access, but the entire purpose of collecting, maintaining, and providing access to data. This applies whether that system is a new next-gen system or an updated WHOIS system. If we cannot make some headway on the question of purpose, as SAC055 pointed out and the board agreed, then we are unlikely to make headway on specific policies intended to support each stakeholder's varying and sometimes divergent views about what the purpose should be.
Chuck
_______________________________________________ gnso-rds-pdp-wg mailing list gnso-rds-pdp-wg@icann.org https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg
Thanks Chuck. This history and background helps focus our discussion. Looking at the Board resolution, I think the following purpose seems to fit the bill and I’d like to suggest we include this on our list. “The purpose of collecting, maintaining and providing access to gTLD registration data is to provide a record of domain name ownership”. Note I suspect the word “ownership” isn’t quite appropriate here - so some word-smithing may be required. Alex On Sep 30, 2016, at 5:28 PM, Gomes, Chuck <cgomes@verisign.com<mailto:cgomes@verisign.com>> wrote: Some of us, myself included, have been getting impatient because of the time we have been spending on a RDS purpose statement. In that regard, Lisa reminded me of why it is important to do that and I want to forward her comments to the full WG. The following is a direct quote from her message. “We are attempting to be responsive to the board and SSAC request for this PDP to address up front this question: "Resolved (2015.04.26.10), the Board reaffirms its request for a Board-initiated GNSO policy development process to define the purpose of collecting, maintaining and providing access to gTLD registration data, and consider safeguards for protecting data, using the recommendations in the Final Report<https://www.icann.org/en/system/files/files/final-report-06jun14-en.pdf> [PDF, 5.12 MB] as an input to, and, if appropriate, as the foundation for a new gTLD policy." In SAC055, WHOIS: Blind Men and an Elephant<https://www.icann.org/en/system/files/files/sac-055-en.pdf>, [1] the SSAC found that further work should be undertaken prior to implementation of the WHOIS Policy Review Team?s recommendations, concluding: "1. It is critical that ICANN should develop a policy defining the purpose of domain name registration data; 2. ICANN should create a committee to develop a registration data policy that defines the purpose of domain name registration data; and 3. ICANN should defer other activity directed at finding a ?solution? to ?the WHOIS problem? until the registration data policy identified in (1) and (2) has been developed and accepted." This is why this WG must examine not just policies that pertain to access, and not just a system that provides that access, but the entire purpose of collecting, maintaining, and providing access to data. This applies whether that system is a new next-gen system or an updated WHOIS system. If we cannot make some headway on the question of purpose, as SAC055 pointed out and the board agreed, then we are unlikely to make headway on specific policies intended to support each stakeholder's varying and sometimes divergent views about what the purpose should be. Chuck _______________________________________________ gnso-rds-pdp-wg mailing list gnso-rds-pdp-wg@icann.org<mailto:gnso-rds-pdp-wg@icann.org> https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg
Does "assignment" work? Stephanie Perrin On 2016-10-04 08:41, Deacon, Alex wrote:
Thanks Chuck.
This history and background helps focus our discussion.
Looking at the Board resolution, I think the following purpose seems to fit the bill and I’d like to suggest we include this on our list.
“The purpose of collecting, maintaining and providing access to gTLD registration data is to provide a record of domain name ownership”.
Note I suspect the word “ownership” isn’t quite appropriate here - so some word-smithing may be required.
Alex
On Sep 30, 2016, at 5:28 PM, Gomes, Chuck <cgomes@verisign.com <mailto:cgomes@verisign.com>> wrote:
Some of us, myself included, have been getting impatient because of the time we have been spending on a RDS purpose statement. In that regard, Lisa reminded me of why it is important to do that and I want to forward her comments to the full WG. The following is a direct quote from her message. “We are attempting to be responsive to the board and SSAC request for this PDP to address up front this question:
*/"Resolved (2015.04.26.10)/*/, the Board reaffirms its request for a Board-initiated GNSO policy development process to define the purpose of collecting, maintaining and providing access to gTLD registration data, and consider safeguards for protecting data, using the recommendations in theFinal Report <https://www.icann.org/en/system/files/files/final-report-06jun14-en.pdf>[PDF, 5.12 MB] as an input to, and, if appropriate, as the foundation for a new gTLD policy."
/InSAC055, WHOIS: Blind Men and an Elephant <https://www.icann.org/en/system/files/files/sac-055-en.pdf>,[1] the SSAC found that further work should be undertaken prior to implementation of the WHOIS Policy Review Team?s recommendations, concluding:
/"1. It is critical that ICANN should develop a policy defining the purpose of domain name registration data;
2. ICANN should create a committee to develop a registration data policy that defines the purpose of domain name registration data; and
3. ICANN should defer other activity directed at finding a ?solution? to ?the WHOIS problem? until the registration data policy identified in (1) and (2) has been developed and accepted."
/This is why this WG must examine not just policies that pertain to access, and not just a system that provides that access, but the entire purpose of collecting, maintaining, and providing access to data. This applies whether that system is a new next-gen system or an updated WHOIS system. If we cannot make some headway on the question of purpose, as SAC055 pointed out and the board agreed, then we are unlikely to make headway on specific policies intended to support each stakeholder's varying and sometimes divergent views about what the purpose should be. Chuck
_______________________________________________ gnso-rds-pdp-wg mailing list gnso-rds-pdp-wg@icann.org <mailto:gnso-rds-pdp-wg@icann.org> https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg
_______________________________________________ gnso-rds-pdp-wg mailing list gnso-rds-pdp-wg@icann.org https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg
What about 'registrations'? Then it would read "The purpose of collecting, maintaining and providing access to gTLD registration data is to provide a record of domain name registrations." Chuck From: gnso-rds-pdp-wg-bounces@icann.org [mailto:gnso-rds-pdp-wg-bounces@icann.org] On Behalf Of Stephanie Perrin Sent: Tuesday, October 04, 2016 9:17 AM To: gnso-rds-pdp-wg@icann.org Subject: Re: [gnso-rds-pdp-wg] Why are we spending time on a RDS Purpose statement? Does "assignment" work? Stephanie Perrin On 2016-10-04 08:41, Deacon, Alex wrote: Thanks Chuck. This history and background helps focus our discussion. Looking at the Board resolution, I think the following purpose seems to fit the bill and I'd like to suggest we include this on our list. "The purpose of collecting, maintaining and providing access to gTLD registration data is to provide a record of domain name ownership". Note I suspect the word "ownership" isn't quite appropriate here - so some word-smithing may be required. Alex On Sep 30, 2016, at 5:28 PM, Gomes, Chuck <cgomes@verisign.com<mailto:cgomes@verisign.com>> wrote: Some of us, myself included, have been getting impatient because of the time we have been spending on a RDS purpose statement. In that regard, Lisa reminded me of why it is important to do that and I want to forward her comments to the full WG. The following is a direct quote from her message. "We are attempting to be responsive to the board and SSAC request for this PDP to address up front this question: "Resolved (2015.04.26.10), the Board reaffirms its request for a Board-initiated GNSO policy development process to define the purpose of collecting, maintaining and providing access to gTLD registration data, and consider safeguards for protecting data, using the recommendations in the Final Report<https://www.icann.org/en/system/files/files/final-report-06jun14-en.pdf> [PDF, 5.12 MB] as an input to, and, if appropriate, as the foundation for a new gTLD policy." In SAC055, WHOIS: Blind Men and an Elephant<https://www.icann.org/en/system/files/files/sac-055-en.pdf>, [1] the SSAC found that further work should be undertaken prior to implementation of the WHOIS Policy Review Team?s recommendations, concluding: "1. It is critical that ICANN should develop a policy defining the purpose of domain name registration data; 2. ICANN should create a committee to develop a registration data policy that defines the purpose of domain name registration data; and 3. ICANN should defer other activity directed at finding a ?solution? to ?the WHOIS problem? until the registration data policy identified in (1) and (2) has been developed and accepted." This is why this WG must examine not just policies that pertain to access, and not just a system that provides that access, but the entire purpose of collecting, maintaining, and providing access to data. This applies whether that system is a new next-gen system or an updated WHOIS system. If we cannot make some headway on the question of purpose, as SAC055 pointed out and the board agreed, then we are unlikely to make headway on specific policies intended to support each stakeholder's varying and sometimes divergent views about what the purpose should be. Chuck _______________________________________________ gnso-rds-pdp-wg mailing list gnso-rds-pdp-wg@icann.org<mailto:gnso-rds-pdp-wg@icann.org> https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg _______________________________________________ gnso-rds-pdp-wg mailing list gnso-rds-pdp-wg@icann.org<mailto:gnso-rds-pdp-wg@icann.org> https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg
+1 to Chuck. That is the most in line with the actual facts. Am 04.10.2016 um 16:22 schrieb Gomes, Chuck:
What about ‘registrations’? Then it would read “The purpose of collecting, maintaining and providing access to gTLD registration data is to provide a record of domain name registrations.”
Chuck
*From:*gnso-rds-pdp-wg-bounces@icann.org [mailto:gnso-rds-pdp-wg-bounces@icann.org] *On Behalf Of *Stephanie Perrin *Sent:* Tuesday, October 04, 2016 9:17 AM *To:* gnso-rds-pdp-wg@icann.org *Subject:* Re: [gnso-rds-pdp-wg] Why are we spending time on a RDS Purpose statement?
Does "assignment" work?
Stephanie Perrin
On 2016-10-04 08:41, Deacon, Alex wrote:
Thanks Chuck.
This history and background helps focus our discussion.
Looking at the Board resolution, I think the following purpose seems to fit the bill and I’d like to suggest we include this on our list.
“The purpose of collecting, maintaining and providing access to gTLD registration data is to provide a record of domain name ownership”.
Note I suspect the word “ownership” isn’t quite appropriate here - so some word-smithing may be required.
Alex
On Sep 30, 2016, at 5:28 PM, Gomes, Chuck <cgomes@verisign.com <mailto:cgomes@verisign.com>> wrote:
Some of us, myself included, have been getting impatient because of the time we have been spending on a RDS purpose statement. In that regard, Lisa reminded me of why it is important to do that and I want to forward her comments to the full WG. The following is a direct quote from her message.
“We are attempting to be responsive to the board and SSAC request for this PDP to address up front this question:
*/"Resolved (2015.04.26.10)/*/, the Board reaffirms its request for a Board-initiated GNSO policy development process to define the purpose of collecting, maintaining and providing access to gTLD registration data, and consider safeguards for protecting data, using the recommendations in theFinal Report <https://www.icann.org/en/system/files/files/final-report-06jun14-en.pdf>[PDF, 5.12 MB] as an input to, and, if appropriate, as the foundation for a new gTLD policy."
/InSAC055, WHOIS: Blind Men and an Elephant <https://www.icann.org/en/system/files/files/sac-055-en.pdf>,[1] the SSAC found that further work should be undertaken prior to implementation of the WHOIS Policy Review Team?s recommendations, concluding:
/"1. It is critical that ICANN should develop a policy defining the purpose of domain name registration data;
2. ICANN should create a committee to develop a registration data policy that defines the purpose of domain name registration data; and
3. ICANN should defer other activity directed at finding a ?solution? to ?the WHOIS problem? until the registration data policy identified in (1) and (2) has been developed and accepted."
/This is why this WG must examine not just policies that pertain to access, and not just a system that provides that access, but the entire purpose of collecting, maintaining, and providing access to data. This applies whether that system is a new next-gen system or an updated WHOIS system. If we cannot make some headway on the question of purpose, as SAC055 pointed out and the board agreed, then we are unlikely to make headway on specific policies intended to support each stakeholder's varying and sometimes divergent views about what the purpose should be.
Chuck
_______________________________________________ gnso-rds-pdp-wg mailing list gnso-rds-pdp-wg@icann.org <mailto:gnso-rds-pdp-wg@icann.org> https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg
_______________________________________________
gnso-rds-pdp-wg mailing list
gnso-rds-pdp-wg@icann.org <mailto:gnso-rds-pdp-wg@icann.org>
https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg
_______________________________________________ gnso-rds-pdp-wg mailing list gnso-rds-pdp-wg@icann.org https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg
-- Bei weiteren Fragen stehen wir Ihnen gerne zur Verfügung. Mit freundlichen Grüßen, Volker A. Greimann - Rechtsabteilung - Key-Systems GmbH Im Oberen Werk 1 66386 St. Ingbert Tel.: +49 (0) 6894 - 9396 901 Fax.: +49 (0) 6894 - 9396 851 Email: vgreimann@key-systems.net Web: www.key-systems.net / www.RRPproxy.net www.domaindiscount24.com / www.BrandShelter.com Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook: www.facebook.com/KeySystems www.twitter.com/key_systems Geschäftsführer: Alexander Siffrin Handelsregister Nr.: HR B 18835 - Saarbruecken Umsatzsteuer ID.: DE211006534 Member of the KEYDRIVE GROUP www.keydrive.lu Der Inhalt dieser Nachricht ist vertraulich und nur für den angegebenen Empfänger bestimmt. Jede Form der Kenntnisgabe, Veröffentlichung oder Weitergabe an Dritte durch den Empfänger ist unzulässig. Sollte diese Nachricht nicht für Sie bestimmt sein, so bitten wir Sie, sich mit uns per E-Mail oder telefonisch in Verbindung zu setzen. -------------------------------------------- Should you have any further questions, please do not hesitate to contact us. Best regards, Volker A. Greimann - legal department - Key-Systems GmbH Im Oberen Werk 1 66386 St. Ingbert Tel.: +49 (0) 6894 - 9396 901 Fax.: +49 (0) 6894 - 9396 851 Email: vgreimann@key-systems.net Web: www.key-systems.net / www.RRPproxy.net www.domaindiscount24.com / www.BrandShelter.com Follow us on Twitter or join our fan community on Facebook and stay updated: www.facebook.com/KeySystems www.twitter.com/key_systems CEO: Alexander Siffrin Registration No.: HR B 18835 - Saarbruecken V.A.T. ID.: DE211006534 Member of the KEYDRIVE GROUP www.keydrive.lu This e-mail and its attachments is intended only for the person to whom it is addressed. Furthermore it is not permitted to publish any content of this email. You must not use, disclose, copy, print or rely on this e-mail. If an addressing or transmission error has misdirected this e-mail, kindly notify the author by replying to this e-mail or contacting us by telephone.
participants (5)
-
Carlton Samuels -
Deacon, Alex -
Gomes, Chuck -
Stephanie Perrin -
Volker Greimann