September 2017 - RDS-WHOIS2-RT

RDS-WHOIS2 Review Team Plenary Call #2 13 July 2017 - 13:00 UTC
by Jean-Baptiste Deroulez Nov. 26, 2017

Nov. 26, 2017

Dear Review Team Members, In preparation for your call #02<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…>, scheduled for Thursday, 13 July – 13:00-14:00 UTC (timezone converter here<https://www.timeanddate.com/worldclock/fixedtime.html?msg=RDS%2FWHOIS2+Revi…>), please find below a suggested agenda: 1. Welcome and opening remarks (Karen Mulberry) 2. ICANN59 Recap (Jean-Baptiste Deroulez) 3. Review Team leadership structure, responsibilities (RDS-WHOIS2-RT members) 4. Plenary call schedule and topics (Karen Mulberry) 5. Consider process and how the Review Team wishes to include Observers (Karen Mulberry) 6. First face-to-face meeting: Dates & Topics (Karen Mulberry) 7. ICANN60 meeting (Karen Mulberry) 8. Board Resolution (RDS-WHOIS2-RT members) (Lisa Phifer) 9. A.O.B Attached to this email you will find slides we invite you to read. You should all have received dial-in details to join this call. If not, please contact us off list at rds-whois2-staff(a)icann.org<mailto:rds-whois2-staff@icann.org> and we will make sure to send you a copy. Please feel free to join 20 minutes early to confirm your Adobe Connect and audio connections, if you wish. We would also like to remind you with some key links for your information: * This mailing-list is being publicly archived at: http://mm.icann.org/pipermail/rds-whois2-rt/ * https://community.icann.org/display/WHO/RDS-WHOIS2+Review[community.icann.o…<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_di…> is the URL to your work space, which we have started populating with information. It will be the main repository for your documents and activities. We would like to call your attention to the Background Materials page where we have started compiling documents we would encourage you to read: https://community.icann.org/display/WHO/Background+Materials[community.ican…<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_di…> As always, feel free to contact us should you have any questions or concerns. Kind regards, Jean-Baptiste Deroulez

11 19

Statement of Interest Form / Conflict of Interest Policy
by Alice Jansen Oct. 4, 2017

Oct. 4, 2017

Dear Review Team, Follow up on action item #11 in the tracker<https://community.icann.org/display/WHO/Tracking+Tool>, please find attached to this email: * A conflict of interest policy * The statement of interest form We invite you to review these two forms in anticipation of your face-to-face meeting and suggest discussing these documents on day 1 under agenda item #2. As a reminder, if you need more information to prepare for the Brussels meeting – please refer to the dedicated wiki page: https://community.icann.org/display/WHO/Meeting+%23+9+-+2-3+October+2017 Have a safe journey and see you all in Brussels! Best regards Alice

1 1

RDS-WHOIS2-RT: Plenary Action items, Face-to-Face Meeting Reading list & Final Agenda
by Jean-Baptiste Deroulez Oct. 1, 2017

Oct. 1, 2017

Dear Review Team members, Following yesterday’s plenary call, please find below the identified action items and decisions reached: Decisions Reached Face-to-face meeting #1 agenda is approved. (note on informal dinner and meet-up in the hotel lobby at 6:45 PM will be added) Action Items: * ICANN org to send list of questions to RT list - Leaders to confirm list of questions on set of briefings #2. * Susan to propose criteria for determining effectiveness by Brussels meeting. * ICANN org to reach out to CCT Review Team to see if they have a working definition of consumer trust this RT might use, and also any research relevant to consumer trust and WHOIS * ICANN org to update scope table in light of today's plenary discussion. * RT members to fill in the ICANN 60 doodle (http://doodle.com/poll/q35x2qxtipnyna9h) by COB today and/or confirm planning to attend. If no quorum, the meeting will be cancelled. Regarding the third action item listed above, we have contacted the CCT Review Team leadership and are expecting an answer, however we can already confirm that consumer trust was defined as follows in the CCT Review Team terms of reference: Consumer trust: The confidence Consumers have in the function, reliability, safety, security, and authenticity of the domain name system. This includes (i) trust in the consistency of name resolution; (ii) confidence by Internet users that they can safely navigate to a domain name to find and safely use the site they intend to reach; (iii) confidence that a TLD registry operator is fulfilling the Registry’s stated purpose; and (iv) confidence by a Registrant in a domain’s registration process and life cycle. Regarding the fourth action item, we have attached an updated version of the scope and objectives document based on your discussions from the last plenary call, with highlighted changes to ease your review. Attached to this email, you will also find the list of questions raised on plenary call #7 and #8 on the implementation of recommendations 4, 5, 8, 10, 11, 12, 13 and 14. As determined on the call, any supplementary questions you may have must be sent through this list. Alan, Susan, Cathrin – please confirm by this Sunday, 23:59 UTC, that the attached list captures all questions raised during the implementation briefings given during those plenary calls. We look forward meeting you in Brussels on October 2 & 3, and would like to confirm that we started populating the reading list on the dedicated face-to-face meeting wiki page: https://community.icann.org/display/WHO/Meeting+%23+9+-+2-3+October+2017. You will also find the final version of the agenda of the face-to-face meeting in attachment of this email, and the security sheet that was shared previously. Until then, safe travels to you all! Kind regards, Jean-Baptiste

2 1

Selecting meeting time(s)
by Alan Greenberg Sept. 30, 2017

Sept. 30, 2017

In looking at meeting times, we have noted what we think are everyone's time zones, both before and after the ICANN60 meeting (which happens to fall on top of the summer time shift in both Europe and North America) If the time zones noted below are incorrect, please let me know. We are also trying to ensure that no meetings occur from midnight until 6 am. If you don't mind late nights or early mornings, please let me know which 6-hour period you would prefer to block out. If we can find one slot that works for everyone, great. If not, then we will find two slots and rotate. Alan ========== Before ICANN60 Alan Greenberg -4 Carlton Samuels -5 Dmitry Belyavsky +3 Cathrin Bauer-Bulst +2 Lili Sun +8 Erika Mann +2 Stephanie Perrin -4 Susan Kawaguchi -7 Thomas Walden Jr -4 Volker Greimann +2 Chris Disspain +1 After ICANN60 Alan Greenberg -5 Carlton Samuels -5 Dmitry Belyavsky +3 Cathrin Bauer-Bulst +1 Lili Sun +8 Erika Mann +1 Stephanie Perrin -5 Susan Kawaguchi -8 Thomas Walden Jr -5 Volker Greimann +1 Chris Disspain 0

2 1

Re: [RDS-WHOIS2-RT] RDS-WHOIS2 Review Team Plenary Call #8 28 September 2017 - 11:00 UTC
by Alan Greenberg Sept. 28, 2017

Sept. 28, 2017

Thanks Dmitry. Yes, I am well aware of using non-ASCII characters to the left of the @ sign. My recollection is that for translation/transliteration, the new version would not replace the old one, but be in addition to it. And we are still some way from actually implementing it due to unresolved issues (who will pay for it, whether to use translation or transliteration in any given case (and it is FAR from obvious, since there are plenty of examples where one makes sense and the other is simply meaningless, and vice versa). Moreover, again my recollection is that the action to be taken is field specific, and I would presume that e-mail addresses are fields where it may not make a lot of sense to even provide T/T versions alongside (although the fact that my left-of-at-sign is "alan.greenberg" DOES convey information, so perhaps there is some reason). But regardless, I think the current work does address the issue. But of course, my recollection could be in error, so we need to verify. Alan At 28/09/2017 11:18 AM, Dmitry Belyavsky wrote: >Hello, > >The mentioned RFCs describe using addresses with >non-ascii symbols in left part. >There is an interest to use it as widely as >currently we use ASCII email addresses. > >The Rec 12 designed to cover the cases of >transliteration is not usable for the case of international email addresses. >But they are already used as part of WHOIS data >in some countries and we should expect that they >will be used in gTLDs relatively soon. > >On Thu, Sep 28, 2017 at 2:03 PM, Alan Greenberg ><<mailto:alan.greenberg@mcgill.ca>alan.greenberg(a)mcgill.ca> wrote: >Thanks Dmitry, > >Without our reading the RFCs, can you explain >exactly what the problem is and how it relates to WHOIS and Rec 12? > >Alan > >At 28/09/2017 03:28 AM, Dmitry Belyavsky wrote: > >>Hello, >> >>It's worth mentioning a significant change that happened after 2012. >> >>The International Email (EAI) was standartized (RFC 6530-6533), >>and at least some ccTLD registries from Asia (I definitely know about .TH) >>accept such email addresses as domain >>adminstrator's email. A lot of registries >>(mostly in Asia) organize more or less active research in this area. >> >>Though it is not acceptable by gTLDs registries >>yet, I suspect that it will be done soon. >> >>Recommendation #12 is not applicable for the International Email Addresses, >>so I think that we should deal with this problem. >> >>I think it can be a short mention or (better) >>recommendation to study this case by an appropriate ICANN working group. >> >>Thank you! >> >>On Wed, Sep 27, 2017 at 7:35 PM, Jean-Baptiste >>Deroulez >><<mailto:jean-baptiste.deroulez@icann.org> >>jean-baptiste.deroulez(a)icann.org> wrote: >>Dear Review Team Members, >> >>In preparation for your call >><https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…>#08, >>scheduled for Thursday, 28 September 2017 >>11:00 UTC, pleease findd below a suggested agenda: >> >>Welcome, roll-call >>Implementation Briefings on WHOIS Recommendations 4, 12, 13, 14 >>Scope >>Face-to-Face meeting #1 Agenda >>ICANN60 informal meeting >>A.O.B. >> >>In anticipation of the meeting, we invite you >>to read the attached slides, the scope and >>objectives document, and the draft face-to-face meeting agenda. >> >>You should all have received dial-in details to >>join this call. If not, please contact us off >>list at >><mailto:rds-whois2-staff@icann.org>rds-whois2-staff(a)icann.org >>and we will make sure to send you a copy. If >>need be, you may join the call up to 20 minutes >>prior to the scheduled start to test your audio. >> >>As always, feel free to contact us should you have any questions or concerns. >> >>Kind regards, >> >>Jean-Baptiste Deroulez >> >> >>_______________________________________________ >>RDS-WHOIS2-RT mailing list >><mailto:RDS-WHOIS2-RT@icann.org>RDS-WHOIS2-RT(a)icann.org >>https://mm.icann.org/mailman/listinfo/rds-whois2-rt >> >> >> >> >>-- >>SY, Dmitry Belyavsky >>Content-Type: text/plain; charset="us-ascii" >>Content-Transfer-Encoding: 7bit >>Content-Disposition: inline >>X-Microsoft-Exchange-Diagnostics: >> >>1;DM5PR03MB2714;27:QpaHfL8HWeRFwXoJRUdJiOH5sX9VYdwcqQuGVWCTF+18BaVV99w9ytfTLLQTyEfmXybGukANFzEPALYmod/8UumTop1rSSi8ELRJD+6TzdzKVzlf3X/b49naMH6LMW+n >>X-Microsoft-Antispam-Mailbox-Delivery: >> >>ex:0;auth:0;dest:I;ENG:(400001000128)(400125000095)(20160514016)(750103)(520002050)(400001001223)(400125100095)(61617095)(400001002128)(400125200095); >> >>_______________________________________________ >>RDS-WHOIS2-RT mailing list >><mailto:RDS-WHOIS2-RT@icann.org>RDS-WHOIS2-RT(a)icann.org >>https://mm.icann.org/mailman/listinfo/rds-whois2-rt > > > > >-- >SY, Dmitry Belyavsky

2 1

Re: [RDS-WHOIS2-RT] RDS-WHOIS2 Review Team Plenary Call #8 28 September 2017 - 11:00 UTC
by Alan Greenberg Sept. 28, 2017

Sept. 28, 2017

Thanks Dmitry, Without our reading the RFCs, can you explain exactly what the problem is and how it relates to WHOIS and Rec 12? Alan At 28/09/2017 03:28 AM, Dmitry Belyavsky wrote: >Hello, > >It's worth mentioning a significant change that happened after 2012. > >The International Email (EAI) was standartized (RFC 6530-6533), >and at least some ccTLD registries from Asia (I definitely know about .TH) >accept such email addresses as domain >adminstrator's email. A lot of registries >(mostly in Asia) organize more or less active research in this area. > >Though it is not acceptable by gTLDs registries >yet, I suspect that it will be done soon. > >Recommendation #12 is not applicable for the International Email Addresses, >so I think that we should deal with this problem. > >I think it can be a short mention or (better) >recommendation to study this case by an appropriate ICANN working group. > >Thank you! > >On Wed, Sep 27, 2017 at 7:35 PM, Jean-Baptiste >Deroulez ><<mailto:jean-baptiste.deroulez@icann.org>jean-baptiste.deroulez(a)icann.org> >wrote: > >Dear Review Team Members, > > > >In preparation for your call ><https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…>#08, >scheduled for Thursday, 28 September 2017 >11:00 UTC, please findd below a suggested agenda: > > >Welcome, roll-call >Implementation Briefings on WHOIS Recommendations 4, 12, 13, 14 >Scope >Face-to-Face meeting #1 Agenda >ICANN60 informal meeting >A.O.B. > > >In anticipation of the meeting, we invite you to >read the attached slides, the scope and >objectives document, and the draft face-to-face meeting agenda. > > > >You should all have received dial-in details to >join this call. If not, please contact us off >list at ><mailto:rds-whois2-staff@icann.org>rds-whois2-staff(a)icann.org >and we will make sure to send you a copy. If >need be, you may join the call up to 20 minutes >prior to the scheduled start to test your audio. > > > >As always, feel free to contact us should you have any questions or concerns. > > > >Kind regards, > > > >Jean-Baptiste Deroulez > > > > > >_______________________________________________ >RDS-WHOIS2-RT mailing list ><mailto:RDS-WHOIS2-RT@icann.org>RDS-WHOIS2-RT(a)icann.org >https://mm.icann.org/mailman/listinfo/rds-whois2-rt > > > > >-- >SY, Dmitry Belyavsky >Content-Type: text/plain; charset="us-ascii" >Content-Transfer-Encoding: 7bit >Content-Disposition: inline >X-Microsoft-Exchange-Diagnostics: > >1;DM5PR03MB2714;27:QpaHfL8HWeRFwXoJRUdJiOH5sX9VYdwcqQuGVWCTF+18BaVV99w9ytfTLLQTyEfmXybGukANFzEPALYmod/8UumTop1rSSi8ELRJD+6TzdzKVzlf3X/b49naMH6LMW+n >X-Microsoft-Antispam-Mailbox-Delivery: > >ex:0;auth:0;dest:I;ENG:(400001000128)(400125000095)(20160514016)(750103)(520002050)(400001001223)(400125100095)(61617095)(400001002128)(400125200095); > >_______________________________________________ >RDS-WHOIS2-RT mailing list >RDS-WHOIS2-RT(a)icann.org >https://mm.icann.org/mailman/listinfo/rds-whois2-rt

2 1

RDS-WHOIS2 - Face-to-Face Meeting: Brussels Security Sheet
by Jean-Baptiste Deroulez Sept. 28, 2017

Sept. 28, 2017

Dear Review Team members, In anticipation of your first face-to-face meeting in Brussels, the ICANN meetings team has prepared the attached Security sheet which includes information on: • Office location • Foreign embassies • Transportation details • ICANN & Emergency contacts • ISOS Recommended Hospital • General Security Recommendations When landing at Brussels airport, we recommend taking a taxi to your hotel. The taxi company - Autolux -has fixed prices (with a 20% discount for round-trip journeys). If you prefer taking the train, a train station is located within the airport (Brussels Airport – Zaventem). You can catch a train to Bruxelles-Schuman, which is the closest train station (a 5 min walk from the office and your hotel). If you wish to take the bus from the airport, more information is available here https://www.stib-mivb.be/article.html?l=en&_guid=d07b4e96-1283-3410-f08c-e0…. We also attached for your convenience a map with metro, train and bus stations located close by the ICANN office, and the hotel. Kind regards, Jean-Baptiste Deroulez

1 0

Meeting today
by Erika Mann Sept. 28, 2017

Sept. 28, 2017

Quick question: is the meeting today at 11 AM UTC or 11 PM UTC? PM will be hard for me! Greetings, Erika Sent from my iPhone

4 4

RDS-WHOIS2 Review Team Plenary Call #8 28 September 2017 - 11:00 UTC
by Jean-Baptiste Deroulez Sept. 28, 2017

Sept. 28, 2017

Dear Review Team Members, In preparation for your call #08<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…>, scheduled for Thursday, 28 September 2017 – 11:00 UTC, please find below a suggested agenda: 1. Welcome, roll-call 2. Implementation Briefings on WHOIS Recommendations 4, 12, 13, 14 3. Scope 4. Face-to-Face meeting #1 Agenda 5. ICANN60 informal meeting 6. A.O.B. In anticipation of the meeting, we invite you to read the attached slides, the scope and objectives document, and the draft face-to-face meeting agenda. You should all have received dial-in details to join this call. If not, please contact us off list at rds-whois2-staff(a)icann.org<mailto:rds-whois2-staff@icann.org> and we will make sure to send you a copy. If need be, you may join the call up to 20 minutes prior to the scheduled start to test your audio. As always, feel free to contact us should you have any questions or concerns. Kind regards, Jean-Baptiste Deroulez

4 3

RDS-WHOIS2-RT: Follow-up on Plenary Call #7 action items
by Jean-Baptiste Deroulez Sept. 26, 2017

Sept. 26, 2017

Dear Review Team members, Following the last plenary call, we have prepared the below items for your review and input: 1. Implementation Briefings questions Attached to this email, you will find the list of questions raised on the last plenary call on the implementation of recommendations 5, 8, 10 and 11. As determined on the call, any supplementary questions you may have must be sent through this list. Alan, Susan, Cathrin – please confirm by this Friday, 23:59 UTC, that you validate the attached list of questions. 1. Terms of Reference As requested on the call, sections of Terms of Reference that remain to be addressed before the ToR can be finalized are listed below. Note: you may also choose to add to the ToR or modify other existing sections as the list only flags existing sections. Mission and Scope (pages 6-7) Bullet list of Objectives to be inserted following the text: "In line with the Bylaws, and after considering the limited scope proposal and feedback, the Review Team agreed by consensus to define the scope of the Review to address the following objectives." As noted in the template, each bullet to include (a) description of objective and (b) relationship to specific review requirement and ICANN's mission. Objectives to be prioritized by the Review Team, using prioritization criteria to be inserted below the bullet list. Definitions (pages 7-9) Additional definitions (if any) to be inserted here as needed to reflect terms appropriate for agreed-scope. For example, see definition sources provided at end of section. Review team may wish to review those sources for applicable definitions. If no further definitions are to be added at this time, highlighted placeholders can be deleted. Deliverables and Timeframes (page 9) After work plan is agreed, milestone timeline given here to be updated with target dates extracted from work plan. Membership (page 11) After scope is agreed, ccNSO placeholders to be deleted or replaced to reflect ccNSO decision, and closing paragraph on interim review team leadership to be updated. Reporting (pages 17-18) Highlighted example requirements to be replaced with agreed reporting requirements for this review. The highlighted example from the CCT1 ToR may be adopted as-is, modified, or entirely replaced, at the team's discretion. 1. ICANN60 – Availability In anticipation of your ICANN60 informal meeting, we kindly invite you to fill in the doodle (http://doodle.com/poll/q35x2qxtipnyna9h) with your availability on given dates by Friday 22 September COB. We will confirm the date of the informal meeting on our next plenary call. Kind regards, Jean-Baptiste

1 3

RDS-WHOIS2 Plenary Meeting #8: Briefing on WHOIS Recommendations 4, 12, 13, 14
by Jean-Baptiste Deroulez Sept. 25, 2017

Sept. 25, 2017

Dear Review Team members, In anticipation of Thursday’s plenary meeting, please find attached the slides for the briefing on WHOIS Recommendations 4, 12, 13, 14. We kindly invite you to address your questions to Subject Matter Experts in advance of the plenary meeting in reply to this email including the rds-whois2-rt(a)icann.org<mailto:rds-whois2-rt@icann.org> email list. Kind regards, Jean-Baptiste

1 0

Help to promote the upcoming F2F meeting
by Jean-Baptiste Deroulez Sept. 25, 2017

Sept. 25, 2017

Dear Review Team members and Observers, A meeting description and information about how to join the first RDS-WHOIS2 face-to-face meeting, 2-3 October in Brussels is live on the meeting wiki page<https://community.icann.org/display/WHO/Meeting+%23+9+-+2-3+October+2017>. As you know, community engagement is critical to a successful review. We would like to promote this opportunity for community members to observe this meeting. Could you help us by sharing this opportunity to participate with your networks? Below is a short email you can copy and paste and send to those who may be interested in attending. There is also a social post you may wish to share. Thanks in advance for your help. Kind regards, Jean-Baptiste Email for sharing with your networks: Hi, I wanted to invite you to attend the first face-to-face meeting of the ICANN Registration Directory Services Review Team (RDS-WHOIS2), on 2-3 October. As you may know, I am a member of the RDS-WHOIS2 Review Team. The Review Team is assessing the effectiveness of the current RDS (formerly known as WHOIS) and its ability to meet legitimate needs for general top-level domain registration data while safeguarding that data. We would like to invite you to observe the upcoming meeting, remotely or in-person, and share your input and questions as the Review Team finalizes and approves the terms of reference, scope, and work plan. You can learn more about the meeting, which will be held in Brussels, and how to attend by clicking the link below, or getting in touch with me. More information about the upcoming RDS-WHOIS2 face-to-face meeting: https://community.icann.org/display/WHO/Meeting+%23+9+-+2-3+October+2017 Social: Save the date! #ICANN RDS-WHOIS2 Review Team first face-to-face meeting, 2-3 October. More info & how to attend: https://community.icann.org/display/WHO/Meeting+%23+9+-+2-3+October+2017

1 0

Apologies for upcoming call
by Volker Greimann Sept. 22, 2017

Sept. 22, 2017

Dear fellow review team members, dear staff, please note my apologies for the upcoming RT call next week, Thu the 28th. A conflict has sudenly arisen due to an important internal meeting having to be moved ahead. -- 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(a)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(a)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.

1 0

ACTION ITEMS - Plenary call #7
by Alice Jansen Sept. 15, 2017

Sept. 15, 2017

Dear Review Team Members, Many thanks for attending plenary call #7 – archives are posted here<https://community.icann.org/display/WHO/Meeting+%237+-+14+September+2017>. Please see below action Items identified on the call: * ICANN org to produce list of ToR items to be addressed. * Review Team Members to send follow-up questions on briefings to the mailing-list. * ICANN org to capture RT members' detailed questions on briefings and circulate to Review Team list for leadership's confirmation prior to providing answers in writing. * Alan and ICANN org to pull scope issues together in a simple document. Attached to this email you will find the slides that were presented. As requested, see below names and titles of your SME presenters: Recommendation # 5 = Trang Nguyen<https://www.icann.org/profiles/dai-trang-nguyen> & Roger Lim<https://www.icann.org/profiles/roger-lim> Recommendation # 8 = Negar Farzinnia<https://www.icann.org/profiles/negar-farzinnia> Recommendation # 10 = Amy Bivins<https://www.icann.org/profiles/amy-bivins> Recommendation # 11 = Trang Nguyen<https://www.icann.org/profiles/dai-trang-nguyen> & Negar Farzinnia<https://www.icann.org/profiles/negar-farzinnia> Many thanks, Kind regards Alice

1 0

Re: [RDS-WHOIS2-RT] Reminder: Implementation Briefings
by Stephanie Perrin Sept. 14, 2017

Sept. 14, 2017

Sorry to be late with this question, but I cannot seem to find the terms of reference for the last WHOIS Review Team. Could you please point me to that document? Thanks. I am afraid that I am unable to travel to the Brussels face to face, it is too much travel in one month with the Abu Dhabi meeting. I do hope that I can connect via Adobe. Kind regards Stephanie Perrin On 2017-09-08 04:41, Jean-Baptiste Deroulez wrote:

3 2

apologies
by Erika Mann Sept. 13, 2017

Sept. 13, 2017

Dear Alan, dear All - apologies but I won't be able to join the call (11 UTC) tomorrow. Kind regards, Erika Erika Mann +32 498 121354

1 0

My apologize for possible absence for Plenary Call #7
by Dmitry Belyavsky Sept. 11, 2017

Sept. 11, 2017

Dear all, I am not sure whether I am able to participate in the Plenary Call #7 because I'm at the APTLD conference that day. I'll do my best to join at least in listen-only mode if agenda permits. Please apologize my possible absence. -- SY, Dmitry Belyavsky

1 0

Reminder: Implementation Briefings
by Jean-Baptiste Deroulez Sept. 8, 2017

Sept. 8, 2017

Please find below an email sent on behalf of the RDS-WHOIS2 leadership. Dear Team, This is to inform you that ICANN org will be providing you with a schedule of implementation briefings shortly. We would like to take this opportunity to kindly remind you that we have a go-to person for any implementation related briefing and questions: Negar Farzinnia. Negar manages all ICANN organization task forces that are compiling information for briefings and coordinates with Subject Matter Experts (SMEs) to ensure our questions are answered. As we start developing our draft recommendations, Negar will also be the member of the support team who will provide us with some guidance on how to build SMART recommendations (Specific, Measurable, Achievable, Realistic, Timebound). Briefings will involve SMEs who are responsible for implementation of various recommendations across different departments (Global Domains Division (GDD), Office of the Chief Technology Officer (OCTO), compliance, etc.). It is important, as a result, that we be prepared. We invite you to read the process below which will help ICANN organization and SMEs shape briefings in the most relevant and helpful way for us: 1. Thoroughly read documentation and implementation reports available on our background materials page:https://community.icann.org/display/WHO/Background+Materials.)[communi…<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_di…> 2. ICANN organization sends briefing materials in writing no later than 3-5 days prior to the presentation 3. Review Team reads materials and sends questions to the mailing-list prior to the presentation 4. SME delivers presentation and addresses questions 5. Review Team sends any follow-up questions/asks to mailing-list 6. Briefings coordinator advises on anticipated completion dates for follow-up questions/asks Our initial deadline for questions on the WHOIS implementation report was August 31st. Please send any questions you may to have to the list by the end of this week so SMEs may prepare their materials and answers accordingly. Thank you. Kind regards, Alan, Cathrin, Susan

1 0

Fact Sheet: Question addressed on plenary call #6
by Jean-Baptiste Deroulez Sept. 6, 2017

Sept. 6, 2017

Dear Review Team members, We would like to follow up on Alan’s question assigned to ICANN organization from the last plenary call #6<https://community.icann.org/display/WHO/Meeting+%236+-+31+August> on the Fact Sheet and how percentages were assigned on milestones listed. Four milestones were identified by ICANN org in the Fact Sheet at the time the call for volunteers was published. - Review Planning: 20% - Research and Studies: 20% - Draft Report: 35% - Final Report: 25% We heard on the plenary call that there were concerns with the percentages allocation and would like to invite you to review these. As this version was already approved by the leadership, we will implement your approved changes in the September 2017 version scheduled for posting in November. We kindly remind you that the Fact Sheet captures attendance of review team members, costs associated with professional services and travel to attend face-to-face meetings, and milestones. The Fact Sheet will be updated and posted on a quarterly basis as follows: Quarter End Date of Financials Posting Date FY17 Q4 June 2017 10 August 2017 FY18 Q1 September 2017 10 November 2017 FY18 Q2 December 2017 10 February 2018 Kind regards, Jean-Baptiste

1 0

Fwd: ICANN News Alert -- Registration Data Access Protocol (RDAP) Pilot Program Launches
by Alan Greenberg Sept. 6, 2017

Sept. 6, 2017

-- Sent from my mobile. Please excuse brevity and typos. -------- Original Message -------- From: ICANN News Alert <no-reply(a)external.icann.org> Sent: September 5, 2017 9:26:38 PM EDT To: alan.greenberg(a)mcgill.ca Subject: ICANN News Alert -- Registration Data Access Protocol (RDAP) Pilot Program Launches [1]ICANN News Alert [2]https://www.icann.org/news/announcement-2017-09-05-en ______________________________________________________________________ Registration Data Access Protocol (RDAP) Pilot Program Launches 5 September 2017 The Internet Corporation for Assigned Names and Numbers (ICANN) today announced a voluntary Registration Data Access Protocol (RDAP) pilot program, which will begin on 5 September 2017 and conclude on 31 July 2018. RDAP enables users to access current registration data and was created as a replacement for the WHOIS protocol. The goal of the pilot program is to develop a baseline profile (or profiles) to guide implementation, establish an implementation target date, and develop a plan for the implementation of an RDAP-based solution. Proceeding with a pilot program will provide an opportunity for Registration Data Services (RDS) operators to gain operational experience and for producers and consumers of RDS data to participate and provide valuable feedback. The voluntary RDAP pilot program was initiated at the [3]request [PDF, 93 KB] of the gTLD Registries Stakeholder Group, with the support of the Registrar Stakeholder Group. Interested parties can participate in the pilot as described in the [4]community wiki workspace. About RDAP Some of RDAP advantages over WHOIS protocol include: * Standardized query, response and error messages. * Secure access to data (i.e., over HTTPS). * Extensibility (e.g., makes it easy to add output elements). * A bootstrapping mechanism that makes it easy to find the authoritative server for a given query. * Redirection/reference mechanism (e.g., from a thin registry to a registrar). * Builds on top of the well-known web protocol HTTP. * Internationalization support for registration data. * Provides the option to enable differentiated access (e.g., limited access for anonymous users and full access for authenticated users). For more information, send an email to [5]globalsupport(a)icann.org with "RDAP Pilot Program" in the subject line. About ICANN ICANN's mission is to help ensure a stable, secure and unified global Internet. To reach another person on the Internet, you need to type an address – a name or a number – into your computer or other device. That address must be unique so computers know where to find each other. ICANN helps coordinate and support these unique identifiers across the world. ICANN was formed in 1998 as a not-for-profit public-benefit corporation with a community of participants from all over the world. References 1. http://www.icann.org/ 2. https://www.icann.org/news/announcement-2017-09-05-en 3. https://www.icann.org/en/system/files/correspondence/diaz-to-atallah-01aug1… 4. https://community.icann.org/display/RP/RDAP+Pilot 5. mailto:globalsupport@icann.org This message was sent to alan.greenberg(a)mcgill.ca from no-reply(a)external.icann.org ICANN News Alert | ICANN | 12025 Waterfront Drive Suite 300 | Los Angeles, CA 90094-2536 Manage Your Subscription: http://app.icontact.com/icp/mmail-mprofile.pl?r=11810893&l=6333&s=8IU3&m=10…

1 0