<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Texte brut Car";
margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
span.TextebrutCar
{mso-style-name:"Texte brut Car";
mso-style-priority:99;
mso-style-link:"Texte brut";
font-family:"Calibri","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=FR link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoPlainText><span lang=EN-US>Hello Shane, <o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p><p class=MsoPlainText><span lang=EN-US>You said : <o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p><p class=MsoPlainText><span lang=EN-US style='color:#C00000'>>> One thing that I am curious about is whether there are requirements for how access is delivered, as well as transparency and auditing of access to data.<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p><p class=MsoPlainText><span lang=EN-US>Indeed, these requirements are already associated with some charter questions (Gated Access, Users/Purposes, Compliance & accountability, etc.), and many "possible requirements" within the list are dealing with those issues in different ways.<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p><p class=MsoPlainText><span lang=EN-US>Actually, most of your concerns are already taken into account in the list of possible requirements. However, if you have any new concern or requirement and you want to ensure it is taken into account, you really need to read the RDS PDP list I sent alongside with the outreach message, check whether it is already duplicated or not, and, accordingly, rise it up using the response template. <o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p><p class=MsoPlainText><span lang=EN-US>Strictly speaking, I cannot read between your lines and just say that we already include your views or not. You need to show your position specifically with one or more requirements, and I can help you on that.<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p><p class=MsoPlainText><span lang=EN-US>For your information, the GNSO PDP WG weekly meeting of yesterday provide actions items to study how to group the “possible” requirements and remove possible duplicate. Then further discussions will focus on the way to find and reach consensus. So don’t worry just formulate any new requirement that isn’t already listed and the WG will do the rest. <o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p><p class=MsoPlainText><span lang=EN-US>--ff--<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US>Best regards<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US>------------------------------------------------------------------------------<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US>Farell FOLLY<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US>Africa 2.0 Foundation<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US>Chapter Head - Technology Champion<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p><p class=MsoPlainText><span lang=EN-US>t: +22997 248100<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US>s : Skype: farellf<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US>m: farell@benin2point0.org<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US>w :www.africa2point0.org <o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US>l : www.linkedin.com/in/farellf<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US>tt : www.twitter.com/__f_f__<o:p></o:p></span></p><p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p><p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p><p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p><p class=MsoPlainText><span style='mso-fareast-language:FR'>-----Message d'origine-----<br>De : NCSG-Discuss [mailto:NCSG-DISCUSS@LISTSERV.SYR.EDU] De la part de Shane Kerr<br>Envoyé : mercredi 15 juin 2016 12:57<br>À : NCSG-DISCUSS@LISTSERV.SYR.EDU<br>Objet : Re: Request for additional "possible" requirements for Next Generation RDS</span></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Ayden,<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>I haven't gone through the (780) possible requirements - apologies.<o:p></o:p></p><p class=MsoPlainText>Your mail sparked some thoughts that I mentioned earlier on-list, but I'll bring up again.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>----<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>One thing that I am curious about is whether there are requirements for how access is delivered, as well as transparency and auditing of access to data.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>I am thinking of the case where a law-enforcement agency (LEA) gains access to private data (like phone numbers). Ideally the LEA would have to impose controls over who within the LEA has access to the data. For example, it would be nice to know if a police officer was using RDS data for extortion of stalking or the like - which can only be done if the LEA has unique access credentials with strong authentication. I'm not sure how this could be best made into a policy, but I think that it is important (surely ICANN has experience with related cross-organizational privacy restrictions from the registry/registrar model).<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Likewise, it would be good to know if an LEA (or anyone else) was mining the data for mass-surveillance purposes or the like. While registries may not be legally permitted to report such information, there are good models that can be encouraged, such as:<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText><a href="https://en.wikipedia.org/wiki/Transparency_report"><span style='color:windowtext;text-decoration:none'>https://en.wikipedia.org/wiki/Transparency_report</span></a><o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>----<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>In a related topic, both registrars and registrants may want to know when information about the registrant is accessed. (This is certainly technologically possible. LinkedIn tells me how many people have looked at my page when I log in.) As a registrant, I probably also want context... if my basic data was shown 10 times in a month and my full data was shown 2 times, is that less or more than average?<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>On the other hand, registrants may NOT want information stored about access to their data, as any information that is stored can presumably be accessed by LEA. That implies some sort of way for registrants and/or registrars to specify preferences for the handling of meta-information about who has accessed what records.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>----<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Again, sorry for not going through the possible requirements to see if they are listed. I am being lazy and hoping that since you have put in so much work on this that you will know roughly what is contained. ;)<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Cheers,<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>--<o:p></o:p></p><p class=MsoPlainText>Shane<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>At 2016-06-15 11:27:55 +0000<o:p></o:p></p><p class=MsoPlainText>Ayden Férdeline <<a href="mailto:icann@FERDELINE.COM"><span style='color:windowtext;text-decoration:none'>icann@FERDELINE.COM</span></a>> wrote:<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>> One gap that I see among the (780) possible requirements is to do with <o:p></o:p></p><p class=MsoPlainText>> under what conditions transfers of data to foreign jurisdictions is permitted.<o:p></o:p></p><p class=MsoPlainText>> [CM-D30-R10] does talk about Privacy Shield and the transfer of data <o:p></o:p></p><p class=MsoPlainText>> between the US and EU, but it doesn't seem sufficient to me. Does <o:p></o:p></p><p class=MsoPlainText>> anyone know of any resources we can turn to re: restrictions on the <o:p></o:p></p><p class=MsoPlainText>> overseas transfer of personally identifiable information? Would also <o:p></o:p></p><p class=MsoPlainText>> be great if we had some case studies or costly judgements to include <o:p></o:p></p><p class=MsoPlainText>> which make it clear that the data controller has legal liability for <o:p></o:p></p><p class=MsoPlainText>> any breaches of privacy… I think we need to turn this debate into one <o:p></o:p></p><p class=MsoPlainText>> about $$$ and less about privacy rights, because to come up with a <o:p></o:p></p><p class=MsoPlainText>> wishlist of so many pieces of data to collect (and we are not yet even <o:p></o:p></p><p class=MsoPlainText>> looking to consolidate this - just to expand it even further) seems <o:p></o:p></p><p class=MsoPlainText>> not only unwise, but scandalously expensive. Particularly so if we go down the path of gated access and there are breaches - which there inevitably will be.<o:p></o:p></p><p class=MsoPlainText>> - Ayden<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> On Wed, Jun 15, 2016 10:06 AM, Farell FOLLY <a href="mailto:farell@BENIN2POINT0.ORG"><span style='color:windowtext;text-decoration:none'>farell@BENIN2POINT0.ORG</span></a> wrote:<o:p></o:p></p><p class=MsoPlainText>> Dear all,<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> In addition to my previous e-mail, I think it would be nice to recall <o:p></o:p></p><p class=MsoPlainText>> a brief history about the next-gen RDS. You can either read this <o:p></o:p></p><p class=MsoPlainText>> e-mail for brevity or download the attached presentation (from which I withdrew the information).<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> 1. Why this PDP Working ?<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> WHOIS was created in the 80s to identify & contact those responsible <o:p></o:p></p><p class=MsoPlainText>> for operation of Internet network resources. After nearly 15 years of <o:p></o:p></p><p class=MsoPlainText>> GNSO task forces, working groups, workshops, surveys & studies, the <o:p></o:p></p><p class=MsoPlainText>> ICANN community has been unable to reach consensus on comprehensive <o:p></o:p></p><p class=MsoPlainText>> WHOIS policy reforms. In response to the 2012 WHOIS Policy Review <o:p></o:p></p><p class=MsoPlainText>> Team’s Final Report, the ICANN Board launched the RDS PDP & the Expert <o:p></o:p></p><p class=MsoPlainText>> Working Group (EWG) to inform it The EWG was tasked with taking a <o:p></o:p></p><p class=MsoPlainText>> fresh approach by redefining the purpose of gTLD registration data & <o:p></o:p></p><p class=MsoPlainText>> then proposing a new model for gTLD Registration Directory Services to address accuracy, privacy & access issues.<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> 2. What is WHOIS<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <<WHOIS is an overloaded term, it could mean:<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> ü Registration data<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> ü Access protocol (WHOIS protocol)<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> ü Directory Service<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> ü It is best to use individual terms<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> It was created in 1982, but as the Internet grew, WHOIS began to serve <o:p></o:p></p><p class=MsoPlainText>> the needs of different stakeholders such as registrants, law <o:p></o:p></p><p class=MsoPlainText>> enforcement, intellectual property & trademark owners, businesses & <o:p></o:p></p><p class=MsoPlainText>> individual users - but the protocol remained largely unchanged. <o:p></o:p></p><p class=MsoPlainText>> Through the Affirmation of Commitments (AOC), ICANN is committed to <o:p></o:p></p><p class=MsoPlainText>> “enforcing its existing policy relating to WHOIS, subject to <o:p></o:p></p><p class=MsoPlainText>> applicable laws. Such existing policy requires that ICANN implement <o:p></o:p></p><p class=MsoPlainText>> measures to maintain timely, unrestricted & public access to accurate <o:p></o:p></p><p class=MsoPlainText>> & complete WHOIS information, including registrant, technical, <o:p></o:p></p><p class=MsoPlainText>> billing, & administrative contact information.”>><o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> 3. What is Next-Gen RDS<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> << In 2012, the ICANN Board resolved to<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> ü launch a new effort to redefine the purpose of collecting, <o:p></o:p></p><p class=MsoPlainText>> maintaining, & providing access to gTLD registration data, & consider <o:p></o:p></p><p class=MsoPlainText>> safeguards for protecting data, as a foundation for a new gTLD policy <o:p></o:p></p><p class=MsoPlainText>> & contractual negotiations, as appropriate<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> ü Prepare an Issue Report on the purpose of collecting & maintaining <o:p></o:p></p><p class=MsoPlainText>> gTLD registration data & on solutions to improve accuracy & access to <o:p></o:p></p><p class=MsoPlainText>> gTLD registration data, as part of a Board-initiated GNSO PDP<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> ü These efforts are collectively known as the: Next-Generation gTLD <o:p></o:p></p><p class=MsoPlainText>> Registration Directory Services to Replace WHOIS (Next-Gen RDS)>><o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> This RDS is described by 180 principles and should address the <o:p></o:p></p><p class=MsoPlainText>> following questions :<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> i. Users & Purposes<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> ii. Gated Access<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> iii. Privacy & Data Protection<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> iv. Data Quality<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> v. Data Elements<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> vi. Compliance & Accountability<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> vii. Implementation Model<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> viii. Cost<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> ix. Risks & Benefits<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> I hope this will help you understand more and stimulate your contribution.<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> --ff--<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> Best regards<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> ----------------------------------------------------------------------<o:p></o:p></p><p class=MsoPlainText>> --------<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> Farell FOLLY<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> Africa 2.0 Foundation<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> Chapter Head - Technology Champion<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> t: +22997 248100<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> s : Skype: farellf<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> m: <a href="mailto:farell@benin2point0.org"><span style='color:windowtext;text-decoration:none'>farell@benin2point0.org</span></a><o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> w :www.africa2point0.org<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> l : <a href="http://www.linkedin.com/in/farellf"><span style='color:windowtext;text-decoration:none'>www.linkedin.com/in/farellf</span></a><o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> tt : <a href="http://www.twitter.com/__f_f__"><span style='color:windowtext;text-decoration:none'>www.twitter.com/__f_f__</span></a><o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> -----Message d'origine-----<o:p></o:p></p><p class=MsoPlainText>> De : NCSG-Discuss [<a href="mailto:NCSG-DISCUSS@LISTSERV.SYR.EDU"><span style='color:windowtext;text-decoration:none'>mailto:NCSG-DISCUSS@LISTSERV.SYR.EDU</span></a>] De la part de <o:p></o:p></p><p class=MsoPlainText>> Farell FOLLY Envoyé : lundi 13 juin 2016 17:13 À : <o:p></o:p></p><p class=MsoPlainText>> <a href="mailto:NCSG-DISCUSS@LISTSERV.SYR.EDU"><span style='color:windowtext;text-decoration:none'>NCSG-DISCUSS@LISTSERV.SYR.EDU</span></a> Objet : Re: Request for additional <o:p></o:p></p><p class=MsoPlainText>> “possible” requirements for Next Generation RDS<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> (Sorry to have forwarded an unfinished e-mail, This is the final <o:p></o:p></p><p class=MsoPlainText>> response)<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> @Shane, and all<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> The RDS PDP WG has the job to gather all “possible” requirements for <o:p></o:p></p><p class=MsoPlainText>> the next-gen RDS to replace the WHOIS protocol. So many documents has <o:p></o:p></p><p class=MsoPlainText>> been found useful / relevant to provide insightful issues to serve as <o:p></o:p></p><p class=MsoPlainText>> inputs for the characteristics of the next-Gen RDS. However, WG found <o:p></o:p></p><p class=MsoPlainText>> it impossible to read all documents together as a team and agree on <o:p></o:p></p><p class=MsoPlainText>> what can be a “possible” requirement and what can/should not be a requirement (one by one, document per document).<o:p></o:p></p><p class=MsoPlainText>> Then it was proposed and adopted that group members volunteer to read <o:p></o:p></p><p class=MsoPlainText>> the docs and extract as many as inputs as possible. Then the ICANN <o:p></o:p></p><p class=MsoPlainText>> staff worked hard and concatenated all these requirements by naming <o:p></o:p></p><p class=MsoPlainText>> them appropriately without no change to the requirements themselves<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> Therefore the word “possible” means that the stated requirement may be <o:p></o:p></p><p class=MsoPlainText>> removed at the end of the current phase if it is judged so. However, <o:p></o:p></p><p class=MsoPlainText>> it is not yet time to make this decision.<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> Consequently, if you find any bogus or meaningless information <o:p></o:p></p><p class=MsoPlainText>> (according to you), please just make a comment to me offline and I <o:p></o:p></p><p class=MsoPlainText>> will forward to the staff as necessary. At this stage, we just need to propose new “possible”<o:p></o:p></p><p class=MsoPlainText>> requirements, so if you think you have a new requirement for the <o:p></o:p></p><p class=MsoPlainText>> next-gen RDS that is not already in the RDS PDP list I previously sent <o:p></o:p></p><p class=MsoPlainText>> (or by discarding all inputs you classify as bogus or legalese), please send it/them through.<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> Finally for other members I would to clarify that each requirement has <o:p></o:p></p><p class=MsoPlainText>> been given a specific annotation in the form of [QQ-R#-D#], for <o:p></o:p></p><p class=MsoPlainText>> instance in [UP-D26-R06] : the first two letters identify the <o:p></o:p></p><p class=MsoPlainText>> associated charter question (Users Purposes, in this case), the D26 <o:p></o:p></p><p class=MsoPlainText>> identifies the input document (Annex A) from which the requirement has <o:p></o:p></p><p class=MsoPlainText>> been extracted, and R06 means is the 6th “possible” requirement).<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> I suggest to anyone in this group to read (in priority, iteratively) a <o:p></o:p></p><p class=MsoPlainText>> sub-list of all these “possible” requirements depending or based on <o:p></o:p></p><p class=MsoPlainText>> his/her expertise or background. For instance, If you have experience <o:p></o:p></p><p class=MsoPlainText>> in data privacy, you can quickly check all “possible” requirements <o:p></o:p></p><p class=MsoPlainText>> starting by [PR-Dxx-Ryy] and a new one if any. For any new “possible” <o:p></o:p></p><p class=MsoPlainText>> requirement, don’t forget to add the source document.<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> --ff--<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> Best regards<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> ----------------------------------------------------------------------<o:p></o:p></p><p class=MsoPlainText>> --------<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> Farell FOLLY<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> Africa 2.0 Foundation<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> Chapter Head - Technology Champion<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> t: +22997 248100<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> s : Skype: farellf<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> m: <a href="mailto:farell@benin2point0.org"><span style='color:windowtext;text-decoration:none'>farell@benin2point0.org</span></a><o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> w :www.africa2point0.org<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> l : <a href="http://www.linkedin.com/in/farellf"><span style='color:windowtext;text-decoration:none'>www.linkedin.com/in/farellf</span></a><o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> tt : <a href="http://www.twitter.com/__f_f__"><span style='color:windowtext;text-decoration:none'>www.twitter.com/__f_f__</span></a><o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> -----Message d'origine-----<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> De : Shane Kerr [ <a href="mailto:shane@time-travellers.org"><span style='color:windowtext;text-decoration:none'>mailto:shane@time-travellers.org</span></a> ]<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> Envoyé : lundi 13 juin 2016 15:37<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> À : Farell FOLLY<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> Cc : <a href="mailto:NCSG-DISCUSS@LISTSERV.SYR.EDU"><span style='color:windowtext;text-decoration:none'>NCSG-DISCUSS@LISTSERV.SYR.EDU</span></a><o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> Objet : Re: Request for additional “possible” requirements for Next <o:p></o:p></p><p class=MsoPlainText>> Generation RDS<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> Farell,<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> At 2016-06-13 11:30:10 +0100<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> Farell FOLLY < <a href="mailto:farell@BENIN2POINT0.ORG"><span style='color:windowtext;text-decoration:none'>farell@BENIN2POINT0.ORG</span></a> > wrote:<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> > Few months ago I decided to join the NCSG in order to serve and <o:p></o:p></p><p class=MsoPlainText>> > defend<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> > the interest of the community regarding Internet resources use. <o:p></o:p></p><p class=MsoPlainText>> > Before<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> > that, I started working with the GNSO Policy Development Process<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> > Working Group (PDP<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> > WG) to contribute in the development process of the Next Generation<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> > Registration Directory Services (Next-Gen RDS). Time comes now that <o:p></o:p></p><p class=MsoPlainText>> > I<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> > engage more and participate within this stakeholder Group. <o:p></o:p></p><p class=MsoPlainText>> > Therefore,<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> > I volunteer to serve as a liaison/point of contact between NCSG and<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> > GNSO PDP WG as far as the attached documents are concerned. <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> Cool, thanks for this!<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> > 1. Read the outreach message 2 in attach<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> > <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> > 2. Read and check the RDS PDP list of possible requirements, also in<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> > attach<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> > <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> > 3. Reply to this mail by asking any questions to me or adding<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> > additional requirement<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> > <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> > Please before replying to this e-mail to add a “new” requirement, <o:p></o:p></p><p class=MsoPlainText>> > make<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> > sure you read the entire document and check whether this requirement<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> > was not duplicated already. Also, ensure that you send your contact<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> > details (name, first name, e-mail) if not explicitly included in <o:p></o:p></p><p class=MsoPlainText>> > your mail<o:p></o:p></p><p class=MsoPlainText>> signature.<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> [ Apologies if the following reads as a rant. It kind of is. Probably<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> my own fault for looking at policy stuff. ]<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> Is there a summary of the PDF, or any kind of specific issues that <o:p></o:p></p><p class=MsoPlainText>> seem contentious that one would look at?<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> I ask because the PDF alone is over 100 pages. Is this a typical ICANN document?<o:p></o:p></p><p class=MsoPlainText>> I was going to have a look since I'm somewhat technical and was <o:p></o:p></p><p class=MsoPlainText>> involved with WHOIS in the distant past, but honestly I don't really <o:p></o:p></p><p class=MsoPlainText>> have the many days time that would be necessary to make any sense out <o:p></o:p></p><p class=MsoPlainText>> of this. :(<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> ------<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> I did skim a bit, and while parts of it are pretty clear:<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> [UP-D01-R17] – Since it is likely that further [permissible<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> purposes] will be identified over time, any [gTLD registration<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> directory service] must be designed with extensibility in mind.<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> (This is a bogus requirement, BTW. Without specific descriptions of <o:p></o:p></p><p class=MsoPlainText>> the expected changes then it is impossible to implement. It's like <o:p></o:p></p><p class=MsoPlainText>> someone saying “prepare for the weather tomorrow” without telling you <o:p></o:p></p><p class=MsoPlainText>> what the weather will be. Better to leave this out and let people make <o:p></o:p></p><p class=MsoPlainText>> their own design decisions.)<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> Other parts are complete legalese:<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> [UP-D26-R06] – According to the Directive (30), whereas, in order<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> to be lawful, the processing of personal data must in addition be<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> carried out with the consent of the data subject or be necessary<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> for the conclusion or performance of a contract binding on the data<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> subject, or as a legal requirement, or for the performance of a<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> task carried out in the public interest or in the exercise of<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> official authority, or in the legitimate interests of a natural or<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> legal person, provided that the interests or the rights and<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> freedoms of the data subject are not overriding....subject to the<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> provisions allowing a data subject to object to the processing of<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> data regarding him, at no cost and without having to state his<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> reasons;<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> I mean, really, the last person to use “whereas” in English outside of <o:p></o:p></p><p class=MsoPlainText>> legal documents died before the invention of the telephone. ;) (The <o:p></o:p></p><p class=MsoPlainText>> Wikipedia article on plain English suggests “because” or “since”, as <o:p></o:p></p><p class=MsoPlainText>> does the “ <a href="http://www.plainlanguage.gov"><span style='color:windowtext;text-decoration:none'>www.plainlanguage.gov</span></a> ” site, although in this particular <o:p></o:p></p><p class=MsoPlainText>> case I'd say just leave it out.)<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> I don't even know what the requirement is here. I read it 4 times and <o:p></o:p></p><p class=MsoPlainText>> can't figure it out. I feel sorry for the poor software engineer that <o:p></o:p></p><p class=MsoPlainText>> has to try to convert this to running code. :P<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> Given the many hundreds of possible requirements, many of which are <o:p></o:p></p><p class=MsoPlainText>> written like this, I don't see any way that anyone who has anything <o:p></o:p></p><p class=MsoPlainText>> else to do for before the deadline can possibly hope to help properly <o:p></o:p></p><p class=MsoPlainText>> review this work, at least without some coordinated plan such as <o:p></o:p></p><p class=MsoPlainText>> “please review the following 10 requirements” for<o:p></o:p></p><p class=MsoPlainText>> 50 volunteers.<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> Sorry for ranting. :(<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> Cheers,<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> --<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> Shane<o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> <o:p></o:p></p><p class=MsoPlainText>> Ayden Férdeline Statement of Interest<o:p></o:p></p></div></body></html>