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. 29, 2017

Sept. 29, 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