<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Agree with this clarification - to put a finer point on it, many companies hire others to manage their large portfolios of domain names for them. That is actually covered in the definition that was quoted but is not covered by the subsequent term, “domain name holder” when translating that to the RDS space since a contracted management provider isn’t the holder itself. I did this kind of work in a long-ago life and there is quite a bit to it and in some use cases it may actually be interesting to provide some sort of explicit “management contact" - something we didn’t even surface out of the EWG, but now that I think about it could be really handy. In some cases the registrar (e.g. MarkMonitor, Iron Mountain, CSC) itself provides this service but in a management role that is supplemental to their registrar role. Some law firms also provide similar management services to adjunct their legal services around domain names. When I was doing this with my company, we were one of many such specialist providers that was neither a registrar nor a law firm. It sure would be handy for such non-registrar domain portfolio managers to be able to have a contact role like this that would allow them default control over many aspects of a domain without being the legal owner. You can kinda fudge it with “technical contact” in many cases, but having such and explicit contact name like this is more useful, since as a “manager” of a domain, I could do things to the contact records, renewals, and designated name servers, but couldn’t answer any domain-related problems like say misconfigured e-mail servers that a tech contact would. Was a real pain in the rear to get calls on these company-related issues when we got listed as a tech contact for many of these kinds of problems. I know that’s a bit tangental to the original question but I’d like others in the corporate domain management space to weigh in on the utility of such a contact. Obviously this would be optional, as only domain holders (registrants) who outsource this kind of thing would need such a thing.<div class=""><br class=""></div><div class="">Cheers,</div><div class=""><br class=""></div><div class="">Rod<br class=""><div class=""><br class=""></div><div class=""><div><blockquote type="cite" class=""><div class="">On Dec 7, 2017, at 12:44 PM, Susan Kawaguchi <<a href="mailto:susankpolicy@gmail.com" class="">susankpolicy@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Hi Sam, <div class=""><br class=""></div><div class="">Not sure I agree with that. We may have named the use case Domain Name Management but control is key verb in my opinion. A domain name manager may give control of a domain name to a third party or rely on the services of a third party to perform one of the roles required ex: admin or tech. </div><div class=""><br class=""></div><div class="">This use case encompasses all of the possible parties that may be involved with the control or management of the domain name. </div><div class=""><br class=""></div><div class="">Hope this helps to clarify. </div><div class=""><br class=""></div><div class="">Susan</div></div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Thu, Dec 7, 2017 at 9:55 AM, Sam Lanfranco <span dir="ltr" class=""><<a href="mailto:sam@lanfranco.net" target="_blank" class="">sam@lanfranco.net</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF" class=""><p class="">Management (as a verb) is normally taken to mean the active
engagement of the owner, or owner's contractually related parties,
in the organization and coordination of the activities of a
business in order to achieve defined objectives. Using the word
"management" here suggests that we are limiting ourselves to what
data elements are necessary to collect for the use of the domain
name holder, the registrar and the registry. There are no other
parties engaged in the "management" of the domain name. <br class="">
</p><p class=""> Correct?<br class="">
</p><p class="">ICANN's take on Domain Name Management: <a href="https://www.icann.org/resources/pages/management-2013-05-03-en" target="_blank" class="">
https://www.icann.org/<wbr class="">resources/pages/management-<wbr class="">2013-05-03-en</a><br class="">
</p>
Sam L. <br class="">
<br class="">
<div class="m_4431707524723424403moz-cite-prefix">On 12/7/2017 11:01 AM, Chuck wrote:<br class="">
</div>
<blockquote type="cite" class="">
<pre class="m_4431707524723424403moz-signature" cols="72">As Andrew suggests, it sure would be helpful if members discussed the
definition of Domain Name Management on this list as well as responding to
the poll that provides several options for that definition. The definition
will guide our deliberation as we discuss what data elements are necessary
to collect for the various aspects of Domain Name Management.
Chuck
------------------------------<wbr class="">------------------
"It is a disgrace to be rich and honoured
in an unjust state" -Confucius
邦有道，贫且贱焉，耻也。邦无道，富且贵焉，耻也
------------------------------<wbr class="">------------------
Dr Sam Lanfranco (Prof Emeritus & Senior Scholar)
Econ, York U., Toronto, Ontario, CANADA - M3J 1P3
email: <a class="m_4431707524723424403moz-txt-link-abbreviated" href="mailto:sam@lanfranco.net" target="_blank">sam@lanfranco.net</a> Skype: slanfranco
blog: <a class="m_4431707524723424403moz-txt-link-freetext" href="https://samlanfranco.blogspot.com/" target="_blank">https://samlanfranco.blogspot.<wbr class="">com</a>
Phone: <a href="tel:(613)%20476-0429" value="+16134760429" target="_blank" class="">+1 613-476-0429</a> cell: <a href="tel:(416)%20816-2852" value="+14168162852" target="_blank" class="">+1 416-816-2852</a></pre>
</blockquote>
</div>
<br class="">______________________________<wbr class="">_________________<br class="">
gnso-rds-pdp-wg mailing list<br class="">
<a href="mailto:gnso-rds-pdp-wg@icann.org" class="">gnso-rds-pdp-wg@icann.org</a><br class="">
<a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" rel="noreferrer" target="_blank" class="">https://mm.icann.org/mailman/<wbr class="">listinfo/gnso-rds-pdp-wg</a><br class=""></blockquote></div><br class=""></div>
_______________________________________________<br class="">gnso-rds-pdp-wg mailing list<br class=""><a href="mailto:gnso-rds-pdp-wg@icann.org" class="">gnso-rds-pdp-wg@icann.org</a><br class="">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</div></blockquote></div><br class=""></div></div></body></html>