<html 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="Title" content="">
<meta name="Keywords" content="">
<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:DengXian;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@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:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-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.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.MsoNoSpacing, li.MsoNoSpacing, div.MsoNoSpacing
{mso-style-priority:1;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri",sans-serif;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle23
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle24
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle25
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle26
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle27
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle28
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle30
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.msoIns
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:underline;
color:teal;}
.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;}
--></style>
</head>
<body bgcolor="white" lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNoSpacing" style="margin:0in;margin-bottom:.0001pt"><span style="color:black">Dear all,</span><o:p></o:p></p>
<p class="MsoNoSpacing" style="margin:0in;margin-bottom:.0001pt"><span style="color:#1F497D"> </span><o:p></o:p></p>
<div>
<div>
<p class="MsoNoSpacing" style="margin:0in;margin-bottom:.0001pt"><span style="color:black">Please find the attendance of the call attached to this email, and the Adobe Connect chat, MP3 & Adobe Connect recording below for the Next-Gen RDS PDP Working group
call held on Wednesday, 29 November 2017 at 06:00 UTC </span><o:p></o:p></p>
<p class="MsoNormal" style="line-height:15.6pt"><b><span style="color:black">Mp3: </span></b><span style="color:black">
<a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__mailer.samanage.com_wf_click-3Fupn-3DBicbgE3FNUxHuHwOPdgXp7PxnHhpBITaBzfgAxdndi-2D2BfJ-2D2FMroolDGxniegGuHcfnPRT3ufG8PNO99SNd2qyk2rkEqs76N5zA8uOynvJKG7M-2D3D-5FQuA5zZR9ZZ7J1F2FeF-2D2FOsgm1hgIDcBrAX2P7Ezxmql7ckJc4ios1-2D2BxObAoz2rzLSI3c4QB1NGo7bw7XrBjpRCbz74w4vzk48UxZMFoBBQBQaQ0ePdiOjdJ30sQNHkokOf-2D2F2p-2D2FBvMgKvMhzp-2D2B4u8fP-2D2BRrSytHe2KCf2HpQmtSbpezMgNTUG57PiORAPesOotpHA-2D2BC4pSmXJRsVmpbNaLqzo84sKCQAVW1sKuEbbLMZrxVlMNH3zAq6baOLiaL8tiLkTqwavJFOvbFuROyjhdHPQAWJHqieUR1wiANNaRdQcEHzT2aSwLgEj-2D2B5MkmCNmKshD4V89InNC7tyILJ4LUAPfLly3vJksECzrimYwKwZS-2D2F4GUkyYyGiUxutnjxSIb6pK6-2D2F40UbziJNFLzBPghR0L8eyEjG9YqpFHpPVxLjdGDkg9gsDhqvPaNbYhN5srH7v5Yg86kGonejPC2bvWvk5RcYwz6S51NyA8BvQEBXEOvZEjIsVrpB5vUGPdRmsAY5-2D2F&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=PDd_FX3f4MVgkEIi9GHvVoUhbecsvLhgsyXrxgtbL10DTBs0i1jYiBM_uTSDzgqG&m=aTTPJ1JSmkbDALFlh28CvpS9_NlBtlImm_w12wTaO_s&s=VcMPUKdDFf4E1iGmG_dRFFRMSScWS_7SKPkbWke8taQ&e=">
https://audio.icann.org/gnso/gnso-nextgen-rds-pdp-29nov17-en.mp3[mailer.samanage.com]</a> <o:p></o:p></span></p>
<p style="line-height:15.6pt"><b><span style="color:black">AC recording:</span></b><span style="color:black">
<a href="https://participate.icann.org/p3uyaxlp6q3/?OWASP_CSRFTOKEN=da98784bd396b38e57f1d982b189a0a8f647aa1f7e8f2c7c1c2566602aaf4d91">
https://participate.icann.org/p3uyaxlp6q3/</a><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNoSpacing" style="margin:0in;margin-bottom:.0001pt"><span style="color:black">The recordings and transcriptions of the calls are posted on the GNSO Master Calendar page:</span><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_en_group-2Dactivities_calendar-23nov&d=DwMF-g&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=PDd_FX3f4MVgkEIi9GHvVoUhbecsvLhgsyXrxgtbL10DTBs0i1jYiBM_uTSDzgqG&m=GJMkY4Fbi9sry9Z53DaSWJm-mHxMfFxg7MEVDf2JU90&s=FI3QJYH6DWWCDQir6NDMSjPkzdqfTTUmf9Ua-AYpc14&e="><span style="color:purple">http://gnso.icann.org/en/group-activities/calendar</span></a><o:p></o:p></p>
</div>
<div>
<p class="MsoNoSpacing" style="margin:0in;margin-bottom:.0001pt"><span style="color:black"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNoSpacing" style="margin:0in;margin-bottom:.0001pt"><span style="color:black">** Please let me know if your name has been left off the list **</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNoSpacing" style="margin:0in;margin-bottom:.0001pt"><span style="color:black"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNoSpacing" style="margin:0in;margin-bottom:.0001pt"><span style="color:black">Mailing list archives:</span><a href="http://mm.icann.org/pipermail/gnso-rds-pdp-wg/"><span style="color:purple">http://mm.icann.org/pipermail/gnso-rds-pdp-wg/</span></a><o:p></o:p></p>
</div>
<div>
<p class="MsoNoSpacing" style="margin:0in;margin-bottom:.0001pt"><span style="color:black"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNoSpacing" style="margin:0in;margin-bottom:.0001pt"><span style="color:black">Wiki agenda page:<b> </b>
<a href="https://community.icann.org/x/LgByB">https://community.icann.org/x/LgByB</a>
</span><o:p></o:p></p>
<p class="MsoNoSpacing" style="margin:0in;margin-bottom:.0001pt"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNoSpacing" style="margin:0in;margin-bottom:.0001pt"><span style="color:black">Thank you.</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNoSpacing" style="margin:0in;margin-bottom:.0001pt"><span style="color:black">Kind regards,</span><o:p></o:p></p>
<p class="MsoNoSpacing" style="margin:0in;margin-bottom:.0001pt"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNoSpacing" style="margin:0in;margin-bottom:.0001pt">Nathalie<o:p></o:p></p>
</div>
<div>
<p class="MsoNoSpacing" style="margin:0in;margin-bottom:.0001pt"><span style="color:black"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNoSpacing" style="margin:0in;margin-bottom:.0001pt"><span style="color:black">———————————————</span><o:p></o:p></p>
<p class="MsoNoSpacing" style="margin:0in;margin-bottom:.0001pt"><span style="color:black"> </span><o:p></o:p></p>
<p class="MsoNoSpacing" style="margin:0in;margin-bottom:.0001pt"><b><u><span style="color:black">AC Chat Next-Gen RDS PDP WG Wednesday 29</span></u></b><b><u> November<span style="color:black"> 2017</span></u></b><o:p></o:p></p>
<p class="MsoNoSpacing"> Nathalie Peregrine:Dear all, welcome to the GNSO Next-Gen RDS PDP Working Group teleconference on Wednesday 29 November 2017 at 06:00 UTC<o:p></o:p></p>
<p class="MsoNoSpacing"> Nathalie Peregrine:Meeting agenda page: <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_LgByB&d=DwICaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=PDd_FX3f4MVgkEIi9GHvVoUhbecsvLhgsyXrxgtbL10DTBs0i1jYiBM_uTSDzgqG&m=DHPX0nKd-MdnsjkMfGWZqUteWPXbl9aTII6XcfESUNQ&s=BYRv0i8oN2flUBHM2sS8XKfD5ZBq2KYMHhScF08YpSM&e=">https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_LgByB&d=DwICaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=PDd_FX3f4MVgkEIi9GHvVoUhbecsvLhgsyXrxgtbL10DTBs0i1jYiBM_uTSDzgqG&m=DHPX0nKd-MdnsjkMfGWZqUteWPXbl9aTII6XcfESUNQ&s=BYRv0i8oN2flUBHM2sS8XKfD5ZBq2KYMHhScF08YpSM&e=</a><o:p></o:p></p>
<p class="MsoNoSpacing"> Maxim Alzoba (FAITID):Hello All<o:p></o:p></p>
<p class="MsoNoSpacing"> Nathalie Peregrine:Welcome all!<o:p></o:p></p>
<p class="MsoNoSpacing"> Tomslin Samme-Nlar:thanks and hello all<o:p></o:p></p>
<p class="MsoNoSpacing"> Lisa Phifer:Call Handout: <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_download_attachments_74580014_Handout-2D29Nov-2DRDSWGCall.pdf&d=DwICaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=PDd_FX3f4MVgkEIi9GHvVoUhbecsvLhgsyXrxgtbL10DTBs0i1jYiBM_uTSDzgqG&m=DHPX0nKd-MdnsjkMfGWZqUteWPXbl9aTII6XcfESUNQ&s=igCSpcrtks16p1WpgFRsWsafJWTLPgMIp8W68Hw0mN4&e=">https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_download_attachments_74580014_Handout-2D29Nov-2DRDSWGCall.pdf&d=DwICaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=PDd_FX3f4MVgkEIi9GHvVoUhbecsvLhgsyXrxgtbL10DTBs0i1jYiBM_uTSDzgqG&m=DHPX0nKd-MdnsjkMfGWZqUteWPXbl9aTII6XcfESUNQ&s=igCSpcrtks16p1WpgFRsWsafJWTLPgMIp8W68Hw0mN4&e=</a><o:p></o:p></p>
<p class="MsoNoSpacing"> Tim OBrien:hello all<o:p></o:p></p>
<p class="MsoNoSpacing"> Lisa Phifer:We are now on slide 4<o:p></o:p></p>
<p class="MsoNoSpacing"> Maxim Alzoba (FAITID):in cases where domain can not be resolved due to RBL which lists WHOIS servers of a registrar - it will not help <o:p></o:p></p>
<p class="MsoNoSpacing"> <span lang="PT-BR">Kal Feher:no audio for jim<o:p></o:p></span></p>
<p class="MsoNoSpacing"><span lang="PT-BR"> </span>James Galvin (Afilias):sorry have to reconnect...<o:p></o:p></p>
<p class="MsoNoSpacing"> Nathalie Peregrine:Jim, can you please provide your number privately and I can dial out to you<o:p></o:p></p>
<p class="MsoNoSpacing"> Maxim Alzoba (FAITID):i.e. DNS server of a registrar (THIN whois) is not reachable - knowing contact does not help<o:p></o:p></p>
<p class="MsoNoSpacing"> Kal Feher:agree with marc. the second is derived from the first. we dont really need to elaborate on the same principle<o:p></o:p></p>
<p class="MsoNoSpacing"> Maxim Alzoba (FAITID):+1<o:p></o:p></p>
<p class="MsoNoSpacing"> GZ Kabir:Agreed<o:p></o:p></p>
<p class="MsoNoSpacing"> Maxim Alzoba (FAITID):I am not sure broadening the scope to unlimited services list will be a good idea<o:p></o:p></p>
<p class="MsoNoSpacing"> Tim OBrien:since we are talking with lawyers, we should call both out seperate a<o:p></o:p></p>
<p class="MsoNoSpacing"> GZ Kabir:we are only talking about names and not the services on top of it<o:p></o:p></p>
<p class="MsoNoSpacing"> Kal Feher:I know a few of us have said this before: once we've agreed on a reason to collect (and maybe publish) data, we don't need to enumerate every possible purpose and trying to do so may result in strange outcomes<o:p></o:p></p>
<p class="MsoNoSpacing"> James Galvin (Afilias):I confess I don't recall who was advocating for services.<o:p></o:p></p>
<p class="MsoNoSpacing"> Maxim Alzoba (FAITID):formally delivering of a plain jokes gifts to a contact named in RDS is a service <o:p></o:p></p>
<p class="MsoNoSpacing"> Tomslin Samme-Nlar:I think that technical issues related or found to be related to Domain Names are inclusive of services mentioned in the second purpose<o:p></o:p></p>
<p class="MsoNoSpacing"> Maxim Alzoba (FAITID):so I am not sure it goes well with privacy <o:p></o:p></p>
<p class="MsoNoSpacing"> Maxim Alzoba (FAITID):so at least the list of services should be more narrow (potentially described, but not listed)<o:p></o:p></p>
<p class="MsoNoSpacing"> Maxim Alzoba (FAITID):+1 Marc<o:p></o:p></p>
<p class="MsoNoSpacing"> Maxim Alzoba (FAITID):Registrant ID is enough for a technical (non criminal) investigation<o:p></o:p></p>
<p class="MsoNoSpacing"> Tomslin Samme-Nlar:For technical contact, I think Email address and phone number is needed to resolve technical issues. I don't see the need for a physical address in resolving technical issues.<o:p></o:p></p>
<p class="MsoNoSpacing"> Maxim Alzoba (FAITID):and Tech contact<o:p></o:p></p>
<p class="MsoNoSpacing"> Kal Feher:agree with Jim. both client and server statuses are relevant<o:p></o:p></p>
<p class="MsoNoSpacing"> Maxim Alzoba (FAITID):such as e-mail & phone<o:p></o:p></p>
<p class="MsoNoSpacing"> Maxim Alzoba (FAITID):Company name/name in tech contact might be needed - to avoid confusion (at least to write/call them politely)<o:p></o:p></p>
<p class="MsoNoSpacing"> Krishna Seeburn - Kris:i think tech contact should be made available<o:p></o:p></p>
<p class="MsoNoSpacing"> Krishna Seeburn - Kris:+ 1 <o:p></o:p></p>
<p class="MsoNoSpacing"> Michele Neylon:It's in there<o:p></o:p></p>
<p class="MsoNoSpacing"> Benny Samuelsen / Nordreg AB:Will just point out that there are several ccTLDS that do not even need a tech contact at all<o:p></o:p></p>
<p class="MsoNoSpacing"> Michele Neylon:"Sponsoring Registrar" etc<o:p></o:p></p>
<p class="MsoNoSpacing"> Michele Neylon:TBH I tend to use the "host" command to work out where the domain / hostname is pointing and take it from there <o:p></o:p></p>
<p class="MsoNoSpacing"> Michele Neylon:DNS records => hosting provider <o:p></o:p></p>
<p class="MsoNoSpacing"> Benny Samuelsen / Nordreg AB:In light of GDPR there are ccTLD's limiting the info on tech contact if they want any at all<o:p></o:p></p>
<p class="MsoNoSpacing"> Krishna Seeburn - Kris:that is already happening in the many EU countries<o:p></o:p></p>
<p class="MsoNoSpacing"> Maxim Alzoba (FAITID):@Benny, I do not think ccTLDs are going to use RDS in full if at all<o:p></o:p></p>
<p class="MsoNoSpacing"> Michele Neylon:Expiry dates aren't included in a lot of ccTLDs<o:p></o:p></p>
<p class="MsoNoSpacing"> Michele Neylon:TBH some ccTLDs don't consider "expiry" to be a valid concept<o:p></o:p></p>
<p class="MsoNoSpacing"> Kal Feher:@michele, they are certainly useful for technical resolution. I'm of course ignoring the confusion around registrar and registry exp dates<o:p></o:p></p>
<p class="MsoNoSpacing"> Benny Samuelsen / Nordreg AB:@Maxim no I am aware of that but the point was that it's not a NEED to have domains working and resolve problems<o:p></o:p></p>
<p class="MsoNoSpacing"> James Galvin (Afilias):Just domain status: as shown in the example<o:p></o:p></p>
<p class="MsoNoSpacing"> Lisa Phifer:See notes pod - doing so now<o:p></o:p></p>
<p class="MsoNoSpacing"> Kal Feher:statuses are either server or client. client in this context is the registrar and server is the registry. its useful to know who applied what status<o:p></o:p></p>
<p class="MsoNoSpacing"> Kal Feher:client hold and server hold result in the same thing, but the cause might be very different.<o:p></o:p></p>
<p class="MsoNoSpacing"> Fabricio Vayra:+1 Susan<o:p></o:p></p>
<p class="MsoNoSpacing"> Kal Feher:ICANN has a reasonably good website explaining statuses<o:p></o:p></p>
<p class="MsoNoSpacing"> Krishna Seeburn - Kris:that works<o:p></o:p></p>
<p class="MsoNoSpacing"> Kal Feher:check out this page for a quick rundown: <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__icann.org_epp&d=DwICaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=PDd_FX3f4MVgkEIi9GHvVoUhbecsvLhgsyXrxgtbL10DTBs0i1jYiBM_uTSDzgqG&m=DHPX0nKd-MdnsjkMfGWZqUteWPXbl9aTII6XcfESUNQ&s=2lgs7IlmRUeFEVvhZ5YDfa26rlkPJtoonr4fLjN6pGc&e=">https://urldefense.proofpoint.com/v2/url?u=https-3A__icann.org_epp&d=DwICaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=PDd_FX3f4MVgkEIi9GHvVoUhbecsvLhgsyXrxgtbL10DTBs0i1jYiBM_uTSDzgqG&m=DHPX0nKd-MdnsjkMfGWZqUteWPXbl9aTII6XcfESUNQ&s=2lgs7IlmRUeFEVvhZ5YDfa26rlkPJtoonr4fLjN6pGc&e=</a><o:p></o:p></p>
<p class="MsoNoSpacing"> James Galvin (Afilias):There is also this: <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resources_pages_epp-2Dstatus-2Dcodes-2D2014-2D06-2D16-2Den&d=DwICaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=PDd_FX3f4MVgkEIi9GHvVoUhbecsvLhgsyXrxgtbL10DTBs0i1jYiBM_uTSDzgqG&m=DHPX0nKd-MdnsjkMfGWZqUteWPXbl9aTII6XcfESUNQ&s=yN7n_7rcYXZrJxzJI4Ug_oiwZULq_I2ASjkAPDEYj_c&e=">https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resources_pages_epp-2Dstatus-2Dcodes-2D2014-2D06-2D16-2Den&d=DwICaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=PDd_FX3f4MVgkEIi9GHvVoUhbecsvLhgsyXrxgtbL10DTBs0i1jYiBM_uTSDzgqG&m=DHPX0nKd-MdnsjkMfGWZqUteWPXbl9aTII6XcfESUNQ&s=yN7n_7rcYXZrJxzJI4Ug_oiwZULq_I2ASjkAPDEYj_c&e=</a><o:p></o:p></p>
<p class="MsoNoSpacing"> James Galvin (Afilias):Which is the same thing :-)<o:p></o:p></p>
<p class="MsoNoSpacing"> James Galvin (Afilias):It is not "server status" it is "domain status"<o:p></o:p></p>
<p class="MsoNoSpacing"> Krishna Seeburn - Kris:shouldbe domain status<o:p></o:p></p>
<p class="MsoNoSpacing"> Maxim Alzoba (FAITID):actually this example is using an old format: after CL&D policy Sponsoring Registrar is Registrar e.t.c.<o:p></o:p></p>
<p class="MsoNoSpacing"> James Galvin (Afilias):No, not EPP status<o:p></o:p></p>
<p class="MsoNoSpacing"> Kal Feher:I think domain status might be more intuitive to non industry participants<o:p></o:p></p>
<p class="MsoNoSpacing"> Maxim Alzoba (FAITID):it is domain status<o:p></o:p></p>
<p class="MsoNoSpacing"> Benny Samuelsen / Nordreg AB:Domain status<o:p></o:p></p>
<p class="MsoNoSpacing"> James Galvin (Afilias):@maxim - :-)<o:p></o:p></p>
<p class="MsoNoSpacing"> Maxim Alzoba (FAITID):I'd suggested Marc's approach - we need to identify needs , and not to revise the old lists of info bits<o:p></o:p></p>
<p class="MsoNoSpacing"> Lisa Phifer:@Maxim, what information is needed for a Technical Contact?<o:p></o:p></p>
<p class="MsoNoSpacing"> Maxim Alzoba (FAITID):I think Tech ID, name , e-mail , phone<o:p></o:p></p>
<p class="MsoNoSpacing"> Maxim Alzoba (FAITID):rarely postal address used (due to more than 2 weeks of letter delivery sometimes = one way)<o:p></o:p></p>
<p class="MsoNoSpacing"> Benny Samuelsen / Nordreg AB:Name?<o:p></o:p></p>
<p class="MsoNoSpacing"> Benny Samuelsen / Nordreg AB:It will be only a role<o:p></o:p></p>
<p class="MsoNoSpacing"> Benny Samuelsen / Nordreg AB:You done really need a name on a person<o:p></o:p></p>
<p class="MsoNoSpacing"> Maxim Alzoba (FAITID):name/company name - to start phone conversation properly (insted of "hey, TechID _____ we have an issue"<o:p></o:p></p>
<p class="MsoNoSpacing"> Benny Samuelsen / Nordreg AB:done = only<o:p></o:p></p>
<p class="MsoNoSpacing"> Tomslin Samme-Nlar:I agree with Benny we don't need a name <o:p></o:p></p>
<p class="MsoNoSpacing"> Benny Samuelsen / Nordreg AB:Sorry to little coffee here, should be, You don't really need a name on a person<o:p></o:p></p>
<p class="MsoNoSpacing"> Lisa Phifer:@James G, one contact method enabling real-time contact?<o:p></o:p></p>
<p class="MsoNoSpacing"> Maxim Alzoba (FAITID):@Benny, how then to address the person ? and to avoid confusion (in case where similar Tech ID was used by mistake)?<o:p></o:p></p>
<p class="MsoNoSpacing"> Maxim Alzoba (FAITID):+1 Jim (postal info rarely needed for tech investigation)<o:p></o:p></p>
<p class="MsoNoSpacing"> Krishna Seeburn - Kris:yes am also in agreement with jim<o:p></o:p></p>
<p class="MsoNoSpacing"> Krishna Seeburn - Kris:any technical problem needs a quick access and resolution<o:p></o:p></p>
<p class="MsoNoSpacing"> Maxim Alzoba (FAITID):cicle of letters (sending, having one back) takes a month, which is more than usual time for tech issue resolution <o:p></o:p></p>
<p class="MsoNoSpacing"> Benny Samuelsen / Nordreg AB:@Maxim as of today we already today tell people to use a role as name instead of having outdated info on persons no longer available<o:p></o:p></p>
<p class="MsoNoSpacing"> Maxim Alzoba (FAITID):@Benny, unfortunately some of them still using it , despite recommendation to use "Domain Tech Support" e.t.c<o:p></o:p></p>
<p class="MsoNoSpacing"> Benny Samuelsen / Nordreg AB:We need a contact which respond on issues and that doesn't need a persons name<o:p></o:p></p>
<p class="MsoNoSpacing"> Michele Neylon:Email isn't published for *any* .uk domains<o:p></o:p></p>
<p class="MsoNoSpacing"> Lisa Phifer:WG Agreement #32: At a minimum, one or more e-mail addresses must be collected for every domain name included in the RDS, for contact roles that require an e-mail address for contactability<o:p></o:p></p>
<p class="MsoNoSpacing"> Susan Kawaguchi:but you can request it <o:p></o:p></p>
<p class="MsoNoSpacing"> Krishna Seeburn - Kris:the importance is having a workable contact<o:p></o:p></p>
<p class="MsoNoSpacing"> Maxim Alzoba (FAITID):what we have in case of a physical person in Tech contact? I do not think we can avoid name there<o:p></o:p></p>
<p class="MsoNoSpacing"> Michele Neylon:email address collection does not mean email publication<o:p></o:p></p>
<p class="MsoNoSpacing"> Maxim Alzoba (FAITID):on the other hand, it might be "hello , you are listed as a Tech ID ___ contact for domain ____" , and it might work over time<o:p></o:p></p>
<p class="MsoNoSpacing"> Maxim Alzoba (FAITID):+1 Michele, collection and storage of e-mail<o:p></o:p></p>
<p class="MsoNoSpacing"> Lisa Phifer:In case it is relevant: WG Agreement #41: In the interest of maximizing contactability, additional contact methods MUST be supported by the RDS as an open-ended list and be optional for Registrants to provide. This does
not preclude agreements on requirements to include other contact methods<o:p></o:p></p>
<p class="MsoNoSpacing"> James Galvin (Afilias):@susan - I think that the efficacy of a particular contact method is a separate discussion.<o:p></o:p></p>
<p class="MsoNoSpacing"> Lisa Phifer:Also, with respect to roles: WG Agreement #36: Purpose-based contact (PBC) types identified (Admin, Legal, Technical, Abuse, Proxy/Privacy, Business) must be supported by the RDS but optional for registrants to provide.<o:p></o:p></p>
<p class="MsoNoSpacing"> Maxim Alzoba (FAITID):people just tend to forget things e.t.c.<o:p></o:p></p>
<p class="MsoNoSpacing"> James Galvin (Afilias):+1 - michele<o:p></o:p></p>
<p class="MsoNoSpacing"> Maxim Alzoba (FAITID):if they do not uspdate tech info - the worst thing happens is they loose the domain<o:p></o:p></p>
<p class="MsoNoSpacing"> James Galvin (Afilias):ensuring that contact methods work is important but as a practical matter you should have TOS that says if it doesn't work then the default action is you simply lose the domain name. :-)<o:p></o:p></p>
<p class="MsoNoSpacing"> Susan Kawaguchi:+1 Jim <o:p></o:p></p>
<p class="MsoNoSpacing"> Lisa Phifer:Note that we have a charter question on Data Accuracy which we'll address after we agree on data elements<o:p></o:p></p>
<p class="MsoNoSpacing"> Maxim Alzoba (FAITID):so the warning to have it updated is enough , and we are not going to be a police of tracking changes the people make in their lifes (it is way too far )<o:p></o:p></p>
<p class="MsoNoSpacing"> Fabricio Vayra:+1 Chuck<o:p></o:p></p>
<p class="MsoNoSpacing"> Krishna Seeburn - Kris:+ 1 Jim<o:p></o:p></p>
<p class="MsoNoSpacing"> Lisa Phifer:@Jim, for technical issue resolution, at least one method of real-time contact must be provided for either the Tech Contact, or if no Tech Contact is provide, the registrant?<o:p></o:p></p>
<p class="MsoNoSpacing"> Krishna Seeburn - Kris:@ It make logical sense<o:p></o:p></p>
<p class="MsoNoSpacing"> Maxim Alzoba (FAITID):it might work<o:p></o:p></p>
<p class="MsoNoSpacing"> Krishna Seeburn - Kris:someone needs to resolve the issue<o:p></o:p></p>
<p class="MsoNoSpacing"> Krishna Seeburn - Kris:he is in between<o:p></o:p></p>
<p class="MsoNoSpacing"> Lisa Phifer:WG Agreement #36: Purpose-based contact (PBC) types identified (Admin, Legal, Technical, Abuse, Proxy/Privacy, Business) must be supported by the RDS but optional for registrants to provide.<o:p></o:p></p>
<p class="MsoNoSpacing"> James Galvin (Afilias):@lisa - yes<o:p></o:p></p>
<p class="MsoNoSpacing"> Krishna Seeburn - Kris:so implicitly if none provided it pushes the registrant to abide to being responsible<o:p></o:p></p>
<p class="MsoNoSpacing"> James Galvin (Afilias):@kris - +1<o:p></o:p></p>
<p class="MsoNoSpacing"> Maxim Alzoba (FAITID):it could be IANA ID #9998 - the registry<o:p></o:p></p>
<p class="MsoNoSpacing"> Krishna Seeburn - Kris:@maxim +1<o:p></o:p></p>
<p class="MsoNoSpacing"> Krishna Seeburn - Kris:+ James<o:p></o:p></p>
<p class="MsoNoSpacing"> Fabricio Vayra:+1 Michelle<o:p></o:p></p>
<p class="MsoNoSpacing"> Kal Feher:@maxim in those instances the registry is responsible so they are the people you want to contact. it's still relevant<o:p></o:p></p>
<p class="MsoNoSpacing"> James Galvin (Afilias):@michele - +1 add the registrar web site link<o:p></o:p></p>
<p class="MsoNoSpacing"> Maxim Alzoba (FAITID):just notice<o:p></o:p></p>
<p class="MsoNoSpacing"> Maxim Alzoba (FAITID):and having a link would be really good idea (not many people know how to google for IANA ID Registrar list)<o:p></o:p></p>
<p class="MsoNoSpacing"> Krishna Seeburn - Kris:i like that as well<o:p></o:p></p>
<p class="MsoNoSpacing"> Maxim Alzoba (FAITID):it is already public<o:p></o:p></p>
<p class="MsoNoSpacing"> Michele Neylon:Registrar information should be public etc etc<o:p></o:p></p>
<p class="MsoNoSpacing"> Maxim Alzoba (FAITID):old hand<o:p></o:p></p>
<p class="MsoNoSpacing"> Maxim Alzoba (FAITID):sorry<o:p></o:p></p>
<p class="MsoNoSpacing"> Maxim Alzoba (FAITID):URLs could be found using <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_registrar-2Dreports_accredited-2Dlist.html&d=DwICaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=PDd_FX3f4MVgkEIi9GHvVoUhbecsvLhgsyXrxgtbL10DTBs0i1jYiBM_uTSDzgqG&m=DHPX0nKd-MdnsjkMfGWZqUteWPXbl9aTII6XcfESUNQ&s=34FIL9p-8THGWUJb3sh5kTfRiMVYqhZz-Ev0utPBIv8&e=">https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_registrar-2Dreports_accredited-2Dlist.html&d=DwICaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=PDd_FX3f4MVgkEIi9GHvVoUhbecsvLhgsyXrxgtbL10DTBs0i1jYiBM_uTSDzgqG&m=DHPX0nKd-MdnsjkMfGWZqUteWPXbl9aTII6XcfESUNQ&s=34FIL9p-8THGWUJb3sh5kTfRiMVYqhZz-Ev0utPBIv8&e=</a> and <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.iana.org_assignments_registrar-2Dids_registrar-2Dids.xhtml&d=DwICaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=PDd_FX3f4MVgkEIi9GHvVoUhbecsvLhgsyXrxgtbL10DTBs0i1jYiBM_uTSDzgqG&m=DHPX0nKd-MdnsjkMfGWZqUteWPXbl9aTII6XcfESUNQ&s=wHynkxy-e1hrfotFtUSep7ccGMHZ1ARJl0QmquCUECo&e=">https://urldefense.proofpoint.com/v2/url?u=https-3A__www.iana.org_assignments_registrar-2Dids_registrar-2Dids.xhtml&d=DwICaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=PDd_FX3f4MVgkEIi9GHvVoUhbecsvLhgsyXrxgtbL10DTBs0i1jYiBM_uTSDzgqG&m=DHPX0nKd-MdnsjkMfGWZqUteWPXbl9aTII6XcfESUNQ&s=wHynkxy-e1hrfotFtUSep7ccGMHZ1ARJl0QmquCUECo&e=</a> combined<o:p></o:p></p>
<p class="MsoNoSpacing"> Krishna Seeburn - Kris:i think we are closer<o:p></o:p></p>
<p class="MsoNoSpacing"> Lisa Phifer:The list: Tech Contacts, Registrant contact, nameservers, domain status, expiry date, sponsoring registrar<o:p></o:p></p>
<p class="MsoNoSpacing"> Krishna Seeburn - Kris:@lisa can we get a sample agreeement that goes to the registrar just for more understanding<o:p></o:p></p>
<p class="MsoNoSpacing"> Lisa Phifer:@Kris, can you please clarify what you are asking for?<o:p></o:p></p>
<p class="MsoNoSpacing"> Krishna Seeburn - Kris:between ICANN and Registrar what is specifically stipulated.... what data is required etc><o:p></o:p></p>
<p class="MsoNoSpacing"> Michele Neylon:That's in the RAA<o:p></o:p></p>
<p class="MsoNoSpacing"> Kal Feher:<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resources_pages_approved-2Dwith-2Dspecs-2D2013-2D09-2D17-2Den&d=DwICaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=PDd_FX3f4MVgkEIi9GHvVoUhbecsvLhgsyXrxgtbL10DTBs0i1jYiBM_uTSDzgqG&m=DHPX0nKd-MdnsjkMfGWZqUteWPXbl9aTII6XcfESUNQ&s=p-tq9xlPnlkeRwmUiXleelL3uPyQsuEQaUxBNdqODg0&e=">https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resources_pages_approved-2Dwith-2Dspecs-2D2013-2D09-2D17-2Den&d=DwICaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=PDd_FX3f4MVgkEIi9GHvVoUhbecsvLhgsyXrxgtbL10DTBs0i1jYiBM_uTSDzgqG&m=DHPX0nKd-MdnsjkMfGWZqUteWPXbl9aTII6XcfESUNQ&s=p-tq9xlPnlkeRwmUiXleelL3uPyQsuEQaUxBNdqODg0&e=</a><o:p></o:p></p>
<p class="MsoNoSpacing"> Krishna Seeburn - Kris:ok<o:p></o:p></p>
<p class="MsoNoSpacing"> Michele Neylon:<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resources_pages_approved-2Dwith-2Dspecs-2D2013-2D09-2D17-2Den&d=DwICaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=PDd_FX3f4MVgkEIi9GHvVoUhbecsvLhgsyXrxgtbL10DTBs0i1jYiBM_uTSDzgqG&m=DHPX0nKd-MdnsjkMfGWZqUteWPXbl9aTII6XcfESUNQ&s=p-tq9xlPnlkeRwmUiXleelL3uPyQsuEQaUxBNdqODg0&e=">https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resources_pages_approved-2Dwith-2Dspecs-2D2013-2D09-2D17-2Den&d=DwICaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=PDd_FX3f4MVgkEIi9GHvVoUhbecsvLhgsyXrxgtbL10DTBs0i1jYiBM_uTSDzgqG&m=DHPX0nKd-MdnsjkMfGWZqUteWPXbl9aTII6XcfESUNQ&s=p-tq9xlPnlkeRwmUiXleelL3uPyQsuEQaUxBNdqODg0&e=</a><o:p></o:p></p>
<p class="MsoNoSpacing"> Krishna Seeburn - Kris:thanks michele<o:p></o:p></p>
<p class="MsoNoSpacing"> Michele Neylon:Maxim - having to play "hunt the website" is not my idea of fun<o:p></o:p></p>
<p class="MsoNoSpacing"> Lisa Phifer:The slide in the deck also shows what is required of the registry<o:p></o:p></p>
<p class="MsoNoSpacing"> Maxim Alzoba (FAITID):@Michele, I agree with that, I meant not many people can play that game and URL is needed<o:p></o:p></p>
<p class="MsoNoSpacing"> Fabricio Vayra:thanks all! <o:p></o:p></p>
<p class="MsoNoSpacing"> Sam Lanfranco:Thanks to all<o:p></o:p></p>
<p class="MsoNoSpacing"> Maxim Alzoba (FAITID):bye all<o:p></o:p></p>
<p class="MsoNoSpacing"> Kal Feher:thanks. alternate times are the best times!<o:p></o:p></p>
<p class="MsoNoSpacing"> Susan Kawaguchi:Thanks Chuck <o:p></o:p></p>
<p class="MsoNoSpacing"> Krishna Seeburn - Kris:thanks<o:p></o:p></p>
<p class="MsoNoSpacing"> Krishna Seeburn - Kris:thanks chuck and all<o:p></o:p></p>
<p class="MsoNoSpacing"> Daniel K. Nanghaka:Thanks Chuck <o:p></o:p></p>
<p class="MsoNoSpacing"> Daniel K. Nanghaka:Bye all <o:p></o:p></p>
<p class="MsoNoSpacing"> Tim OBrien:good day everyone<o:p></o:p></p>
<p class="MsoNoSpacing"> GZ Kabir:thanks and bye all<o:p></o:p></p>
<p class="MsoNoSpacing"><o:p> </o:p></p>
<p class="MsoNoSpacing" style="margin:0in;margin-bottom:.0001pt"><o:p> </o:p></p>
</div>
</div>
</div>
</body>
</html>