Following the advice, Please find in attach the updated versions of the three files submitted previously. Le mar. 31 mai 2016 à 16:35, Gomes, Chuck <cgomes@verisign.com> a écrit :
I want to support Lisa’s guidance regarding ‘breaking the clause apart into shorter pieces that each map to one question’. It will make it a lot easier on all of us if the ‘possible requirements’ are clear and concise and mapped to one of the questions where possible.
Chuck
*From:* gnso-rds-pdp-wg-bounces@icann.org [mailto: gnso-rds-pdp-wg-bounces@icann.org] *On Behalf Of *Lisa Phifer *Sent:* Tuesday, May 31, 2016 9:56 AM *To:* Farell Folly; RDS PDP WG *Subject:* Re: [gnso-rds-pdp-wg] List of Possible requirements from Green Paper: Improvement of Technical Management of Internet Names and Addresses (1998)
Hi Farell,
Thank you for extracting this material from the NTIA Green Paper: Improvement of Technical Management of Internet Names and Addresses (1998) <https://www.ntia.doc.gov/legacy/ntiahome/domainname/022098fedreg.htm>
All, staff will copy all of the possible requirements identified by WG members into the next draft of the WG's list of possible requirements. During that process, staff will assign document numbers and sequentially number all possible requirements under each charter question. So don't worry about filling in those numbers [DE-xx-yy] etc - just identify the associated charter question (UP, GA, DA, DE, PR, etc). When quoting a lengthy complex clause that spans several questions, consider breaking the clause apart into shorter pieces that each map to one question - while this is not always possible, doing so where it is will reduce duplication of text and future effort.
Best, Lisa
At 06:12 AM 5/31/2016, Farell Folly wrote:
Hello All,
In attach three files containing three categories (registries, registrars, Trademarks and dispute resolution) of requirements. I must add that the document was created in 1998 when US government intended to transfer the mangement of the database from IANA to a new private not-for-profit organization (I think this is now ICANN, right?) and may be most of the requirements have been taken into account somewhere between 1998 and 2012, before the EWG report. I just want to bring your attention on that.
@Lisa, I Haven't named all the requirements yet. What I've just done is, for instance, to writeÂ
*[DE-xx-yy] , [DP-xx-yy] for requirements which address Data Elements and Data Privacy. I will update xx as soon as the document cited in the mail object is added to Annex A. *Best regards,
@__f_f__ Content-Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document; name="RaR_Telecom_improvment_requirements.docx" Content-Disposition: attachment; filename="RaR_Telecom_improvment_requirements.docx" Content-ID: <15506b8edcff79007ae1> X-Attachment-Id: 15506b8edcff79007ae1
Content-Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document; name="RyR_Technical Improvment of Internet Management.docx" Content-Disposition: attachment; filename="RyR_Technical Improvment of Internet Management.docx" Content-ID: <15506b8ede3a9cb20772> X-Attachment-Id: 15506b8ede3a9cb20772
Content-Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document; name="Append_II_Telecom_Improvment.docx" Content-Disposition: attachment; filename="Append_II_Telecom_Improvment.docx" Content-ID: <15506b91d1c1243f4013> X-Attachment-Id: 15506b91d1c1243f4013
_______________________________________________ gnso-rds-pdp-wg mailing list gnso-rds-pdp-wg@icann.org https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg
-- Best regards, @__f_f__