<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=us-ascii"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Cambria;
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;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"Franklin Gothic Medium";
panose-1:2 11 6 3 2 1 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:361323565;
mso-list-template-ids:8810958;}
@list l0:level1
{mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Hey, Michele. You mean registrars must VERIFY phone or email. The RAA says that registrars must VALIDATE presence of data in the street field, and VALIDATE that postal addresses are in a proper format for the applicable country, and VALIDATE that all postal address fields are consistent across fields (for example: street exists in city).<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I’m using the terms as per the RAA WHOIS Accuracy Program Spec.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>All best,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>--Greg<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Michele Neylon - Blacknight [mailto:michele@blacknight.com] <br><b>Sent:</b> Tuesday, November 25, 2014 11:18 AM<br><b>To:</b> Greg Aaron<br><b>Cc:</b> Gould, James; Gustavo Lozano; gtld-tech@icann.org<br><b>Subject:</b> Re: [gtld-tech] Whois advisory feedback meeting @IETF91<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>Greg<o:p></o:p></p></div><div><p class=MsoNormal>Registrars do not have to validate street<o:p></o:p></p></div><div><p class=MsoNormal>It's phone OR email<o:p></o:p></p></div><div><p class=MsoNormal>Regards<o:p></o:p></p></div><div><p class=MsoNormal>Michele<br><br>Mr Michele Neylon <o:p></o:p></p><div><p class=MsoNormal>Blacknight Hosting & Domains<o:p></o:p></p></div><div><p class=MsoNormal><a href="http://www.blacknight.host/">http://www.blacknight.host/</a><o:p></o:p></p></div><div><p class=MsoNormal><a href="http://www.mneylon.social">http://www.mneylon.social</a><o:p></o:p></p></div></div><div><p class=MsoNormal style='margin-bottom:12.0pt'><br>On 25 Nov 2014, at 17:09, Greg Aaron <<a href="mailto:greg@illumintel.com">greg@illumintel.com</a>> wrote:<o:p></o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Question #8: It is permissible for the registry contracts or the RAA to specify fields that are mandatory above and beyond those in the EPP specification. The EPP spec is a baseline as far as data fields, and allows registries (or in this case ICANN) to have policy authority and make fields such as Street #1 mandatory. The 2013 RAA requires that registrars collect, validate, and provision street and phone info … so I don’t see how there’s any open question for discussion here. Besides, I can’t see how ICANN could ever allowed registrations that do not include a street address or phone number – it would make WHOIS accuracy efforts impossible. </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Question #9 might be addressed in the registry contract. Does Spec 4 paragraph 1.3 allow the association of two Admin contacts to one domain, for example? </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Question #10: go back to the Applicant Guidebook Question 26, and also look at contract Spec 4 paragraph 1.10. It is the Searchable WHOIS service that allows wildcarding. The registry contract says that registries are not required to offer searchable WHOIS; those who want to can offer it. The contract also says that if it is offered, Searchable WHOIS must be provided on the Web-based WHOIS service ONLY, not on port 43 (see Spec 3 paragraph 1.10.1). If ICANN is stating that port 43 output must return only one record at a time, that seems to be in keeping with the contract and is an FYI clarification, not a new requirement.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>All best,</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>--Greg</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><o:p></o:p></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> <a href="mailto:gtld-tech-bounces@icann.org">gtld-tech-bounces@icann.org</a> [<a href="mailto:gtld-tech-bounces@icann.org">mailto:gtld-tech-bounces@icann.org</a>] <b>On Behalf Of </b>Gould, James<br><b>Sent:</b> Tuesday, November 25, 2014 8:49 AM<br><b>To:</b> Gustavo Lozano<br><b>Cc:</b> <a href="mailto:gtld-tech@icann.org">gtld-tech@icann.org</a><br><b>Subject:</b> Re: [gtld-tech] Whois advisory feedback meeting @IETF91</span><o:p></o:p></p></div></div><p class=MsoNormal> <o:p></o:p></p><div style='border:solid #D4D4D4 1.5pt;border-bottom:solid #D4D4D4 1.0pt;padding:4.0pt 4.0pt 4.0pt 4.0pt'><p class=MsoNormal style='background:#E5E5E5'><span style='font-size:10.0pt;font-family:"Franklin Gothic Medium","sans-serif";color:black'>> Old - S/MIME Signed by an unverified key: 11/25/2014 at 8:49:12 AM</span><o:p></o:p></p></div><div style='border-top:1.0pt;border-left:1.5pt;border-bottom:1.0pt;border-right:1.5pt;border-color:#D4D4D4;border-style:solid;padding:14.0pt 14.0pt 14.0pt 17.0pt'><p class=MsoNormal>Gustavo,<o:p></o:p></p><div><p class=MsoNormal> <o:p></o:p></p></div><div><p class=MsoNormal>Below are the notes that I took from the meeting. Hopefully others have additional notes to add or update to these. <o:p></o:p></p></div><div><ol start=1 type=1><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1'><span style='font-size:10.0pt;font-family:"Helvetica","sans-serif"'>Gustavo started the meeting by defining the purpose of the WHOIS Clarifications in clarifying items in Specification 4 of the New gTLD Registry Agreement and the 2013 Registrar Accreditation Agreement (RAA), based on questions posted to ICANN. The goal was to not create new requirements. </span><o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1'><span style='font-size:10.0pt;font-family:"Helvetica","sans-serif"'>Gustavo described changes between Version 1 and 2 of the WHOIS Clarifications. </span><o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1'><span style='font-size:10.0pt;font-family:"Helvetica","sans-serif"'>Gustavo stated that new fields require the use of an RSEP. </span><o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1'><span style='font-size:10.0pt;font-family:"Helvetica","sans-serif"'>The new target date for enforcing the WHOIS Clarifications is March 31, 2015 instead of February 12, 2015. ICANN asked whether there is a more reasonable date and the feedback was “as late as possible”. </span><o:p></o:p></li></ol><ol start=4 type=1><ol start=1 type=1><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level2 lfo1'><span style='font-size:10.0pt;font-family:"Helvetica","sans-serif"'>There was the recommendation to enable registries to test the PDT testing validation ahead of enforcing it. </span><o:p></o:p></li></ol></ol><ol start=5 type=1><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1'><span style='font-size:10.0pt;font-family:"Helvetica","sans-serif"'>Question - Can we wait for RDAP? RDAP will take time and we cannot wait.</span><o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1'><span style='font-size:10.0pt;font-family:"Helvetica","sans-serif"'>Question - Why return non-existent fields using a key and empty value? </span><o:p></o:p></li></ol><ol start=6 type=1><ol start=1 type=1><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level2 lfo1'><span style='font-size:10.0pt;font-family:"Helvetica","sans-serif"'>To stay in line with Specification 4 of the Registry Agreement</span><o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level2 lfo1'><span style='font-size:10.0pt;font-family:"Helvetica","sans-serif"'>It was brought up that there is a mix of including non-existent fields and also support for optional fields. </span><o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level2 lfo1'><span style='font-size:10.0pt;font-family:"Helvetica","sans-serif"'>Excluding non-existent fields could also support Specification 4 of the Registry Agreement, since Specification 4 of the Registry Agreement did not include any empty fields. </span><o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level2 lfo1'><span style='font-size:10.0pt;font-family:"Helvetica","sans-serif"'>Action Item - ICANN to bring the feedback back for internal discussion and provide a response to the gtld-tech list. </span><o:p></o:p></li></ol></ol><ol start=7 type=1><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1'><span style='font-size:10.0pt;font-family:"Helvetica","sans-serif"'>Question - Why is the contact name optional, since it’s required in EPP?</span><o:p></o:p></li></ol><ol start=7 type=1><ol start=1 type=1><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level2 lfo1'><span style='font-size:10.0pt;font-family:"Helvetica","sans-serif"'>ICANN believed that it was either name or organization, but that is not the case. </span><o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level2 lfo1'><span style='font-size:10.0pt;font-family:"Helvetica","sans-serif"'>Action Item - ICANN took note of this to address. The recommendation is update it to “Registrant/Admin/Tech[/Billing] Name and Organization - Name is required and Organization is optional"</span><o:p></o:p></li></ol></ol><ol start=8 type=1><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1'><span style='font-size:10.0pt;font-family:"Helvetica","sans-serif"'>Question - Why is the contact phone and contact street required? </span><o:p></o:p></li></ol><ol start=8 type=1><ol start=1 type=1><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level2 lfo1'><span style='font-size:10.0pt;font-family:"Helvetica","sans-serif"'>Contact phone and street is a required field in the RAA. </span><o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level2 lfo1'><span style='font-size:10.0pt;font-family:"Helvetica","sans-serif"'>Contact phone and street is not required in EPP and is not required for the registries, so therefore it should not be required in the Registry WHOIS. Cascading a Registrar requirement in the RAA that is not a Registry or EPP requirement through to a Registry WHOIS requirement must not be done.</span><o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level2 lfo1'><span style='font-size:10.0pt;font-family:"Helvetica","sans-serif"'>Action Item - ICANN took note of this to address.</span><o:p></o:p></li></ol></ol><ol start=9 type=1><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1'><span style='font-size:10.0pt;font-family:"Helvetica","sans-serif"'>Question - How to handle multiple contacts of the same type (Admin, Tech, Billing)</span><o:p></o:p></li></ol><ol start=9 type=1><ol start=1 type=1><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level2 lfo1'><span style='font-size:10.0pt;font-family:"Helvetica","sans-serif"'>Specification 4 of the Registry Agreement only supports a single contact per type, so the Registry must select only one to display. </span><o:p></o:p></li></ol></ol><ol start=10 type=1><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1'><span style='font-size:10.0pt;font-family:"Helvetica","sans-serif"'>Question - Why include the requirement that WHOIS queries for domain name data MUST return only one record per WHOIS query? </span><o:p></o:p></li></ol><ol start=10 type=1><ol start=1 type=1><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level2 lfo1'><span style='font-size:10.0pt;font-family:"Helvetica","sans-serif"'>Multiple registries support wildcard queries in WHOIS, where if more than one object (domain or host) matches the query name ( with or without TLD ), a list of matching names is returned instead of a single record. This is a useful feature that would need to be removed based on the Clarifications requirement. As earlier stated, the goal of the Clarifications was to not create new requirements. </span><o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level2 lfo1'><span style='font-size:10.0pt;font-family:"Helvetica","sans-serif"'>Action Item - ICANN took note of this to address. </span><o:p></o:p></li></ol></ol></div><div><div><p class=MsoNormal>Can ICANN respond with a status and update on the action items? <o:p></o:p></p></div><div><p class=MsoNormal> <o:p></o:p></p></div><div><p class=MsoNormal>Thanks,<o:p></o:p></p></div><div><p class=MsoNormal> <o:p></o:p></p></div><div><div><p style='margin:0in;margin-bottom:.0001pt'><span style='font-size:11.5pt;font-family:"Calibri","sans-serif";color:black'>—</span><o:p></o:p></p><p style='margin:0in;margin-bottom:.0001pt;-webkit-text-stroke-width: 0px;word-spacing:0px'><span style='font-size:9.0pt;font-family:"Verdana","sans-serif";color:black'> </span><o:p></o:p></p><p style='mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:0in;-webkit-text-stroke-width: 0px;word-spacing:0px'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'>JG</span><o:p></o:p></p></div><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana","sans-serif";color:black'><br><image001.png></span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'><br></span><span style='color:black'><br></span><b><span style='font-size:10.0pt;font-family:"Helvetica","sans-serif";color:#006AAA'>James Gould<br></span></b><span style='font-size:10.0pt;font-family:"Helvetica","sans-serif";color:#6B6D71'>Distinguished Engineer<br><a href="jgould@Verisign.com">jgould@Verisign.com</a><br><br>703-948-3271<br>12061 Bluemont Way<br>Reston, VA 20190<br><br></span><span style='font-size:10.0pt;font-family:"Helvetica","sans-serif";color:#006AAA'><a href="http://VerisignInc.com">VerisignInc.com</a></span><span style='font-size:9.0pt;font-family:"Verdana","sans-serif";color:black'> </span><o:p></o:p></p></div><p class=MsoNormal> <o:p></o:p></p><div><div><p class=MsoNormal>On Nov 14, 2014, at 3:41 PM, Gustavo Lozano <<a href="mailto:gustavo.lozano@icann.org">gustavo.lozano@icann.org</a>> wrote:<o:p></o:p></p></div><p class=MsoNormal><br><br><br><o:p></o:p></p><div><div><div><p class=MsoNormal><span style='font-family:"Calibri","sans-serif"'>Hello Colleagues,</span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-family:"Cambria","serif"'> </span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-family:"Calibri","sans-serif"'>Attached the slides that I used during this meeting.</span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-family:"Calibri","sans-serif"'> </span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:#101010'>Please note that some of the clarifications / updates presented in the slides may change based on the feedback obtained during the meeting.</span><o:p></o:p></p></div></div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana","sans-serif"'> </span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana","sans-serif"'>Regards,</span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana","sans-serif"'>Gustavo</span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif"'> </span><o:p></o:p></p></div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>From:<span class=apple-converted-space> </span></span></b><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Gustavo Lozano <<a href="mailto:gustavo.lozano@icann.org">gustavo.lozano@icann.org</a>><br><b>Date:<span class=apple-converted-space> </span></b>Thursday, November 13, 2014 at 10:07<br><b>To:<span class=apple-converted-space> </span></b>"<a href="mailto:gtld-tech@icann.org">gtld-tech@icann.org</a>" <<a href="mailto:gtld-tech@icann.org">gtld-tech@icann.org</a>><br><b>Subject:<span class=apple-converted-space> </span></b>Re: Whois advisory feedback meeting @IETF91</span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif"'> </span><o:p></o:p></p></div><blockquote style='border:none;border-left:solid #B5C4DF 4.5pt;padding:0in 0in 0in 4.0pt;margin-left:3.75pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt' id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE"><div><div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif"'>Hello Colleagues,</span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif"'> </span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif"'>The room has enough capacity for all of you interested in assisting physically based on the emails that I received.</span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif"'> </span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif"'>Adobe Connect will be used for remote participation. Please log into<span class=apple-converted-space> </span><a href="https://icann.adobeconnect.com/tech-services">https://icann.adobeconnect.com/tech-services</a><span class=apple-converted-space> </span>at the time of the meeting (<a href="http://www.timeanddate.com/worldclock/converted.html?iso=20141113T15&p1=103&p2=1440"><span style='color:purple'>http://www.timeanddate.com/worldclock/converted.html?iso=20141113T15&p1=103&p2=1440</span></a>).</span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif"'> </span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif"'>The dial-in bridge will not be available, we will use Adobe Connect for audio. If possible, please use a headset for remote participation.</span><o:p></o:p></p></div></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif"'> </span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif"'>Regards,</span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif"'>Gustavo</span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif"'> </span><o:p></o:p></p></div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>From:<span class=apple-converted-space> </span></span></b><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Gustavo Lozano <<a href="mailto:gustavo.lozano@icann.org">gustavo.lozano@icann.org</a>><br><b>Date:<span class=apple-converted-space> </span></b>Tuesday, November 11, 2014 at 10:42<br><b>To:<span class=apple-converted-space> </span></b><<a href="mailto:gtld-tech@icann.org">gtld-tech@icann.org</a>><br><b>Subject:<span class=apple-converted-space> </span></b>Whois advisory feedback meeting @IETF91</span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif"'> </span><o:p></o:p></p></div><blockquote style='border:none;border-left:solid #B5C4DF 4.5pt;padding:0in 0in 0in 4.0pt;margin-left:3.75pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt' id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE"><div><div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif"'>Hello Colleagues,</span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif"'> </span><o:p></o:p></p></div><div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif"'>If you are at the IETF91, an informal meeting to get feedback about the Whois advisory published by ICANN (i.e. </span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif"'> <a href="https://www.icann.org/resources/pages/registry-agreement-spec4-raa-rdds-2014-09-12-en">https://www.icann.org/resources/pages/registry-agreement-spec4-raa-rdds-2014-09-12-en</a>), will take place at Tapa Tower - Iolani 3 on Thursday (15.00 to 16.30 local time). </span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif"'> </span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif"'>Please send me a email if you are planing to assist in order to validate that the capacity of the room is sufficient.</span><o:p></o:p></p></div></div></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif"'> </span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif"'>Regards,</span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif"'>Gustavo</span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Calibri","sans-serif"'>ICAN</span><o:p></o:p></p></div></div></blockquote></div></blockquote><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana","sans-serif"'><whois_advisory.pdf></span><o:p></o:p></p></div></div><p class=MsoNormal> <o:p></o:p></p></div></div><div style='border:solid #D4D4D4 1.5pt;border-top:solid #D4D4D4 1.0pt;padding:4.0pt 4.0pt 4.0pt 4.0pt'><p class=MsoNormal style='background:#E5E5E5'><span style='font-size:10.0pt;font-family:"Franklin Gothic Medium","sans-serif";color:black'>* Gould, James <<a href="mailto:JGould@verisign.com">JGould@verisign.com</a>><br>* Issuer: Symantec Corporation - Unverified</span><o:p></o:p></p></div><p class=MsoNormal> <o:p></o:p></p></div></blockquote></div></body></html>