<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Dec 17, 2013 at 9:24 AM, <a href="mailto:kirk_hall@trendmicro.com">kirk_hall@trendmicro.com</a> <span dir="ltr"><<a href="mailto:kirk_hall@trendmicro.com" target="_blank">kirk_hall@trendmicro.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div lang="EN-US" link="blue" vlink="purple">
<div>
<p>So would it work to amend the definition of ISN and of Registered Domain Name to read as follows?<u></u><u></u></p><div class="im">
<p><u></u> <u></u></p>
<p style="margin-left:0.5in">Internal Server Name: A Server Name that is an Unregistered Domain Name.<u></u><u></u></p>
<p style="margin-left:0.5in"><u></u> <u></u></p>
</div><p style="margin-left:0.5in">Registered Domain Name: A Domain Name that has been registered with an ICANN-assigned Domain Name Registrar.<u></u><u></u></p><div class="im">
<p style="margin-left:0.5in"><u></u> <u></u></p>
<p style="margin-left:0.5in">[Unregistered Domain Name: A Domain Name that is not a Registered Domain Name.]<u></u><u></u></p>
<p><u></u> </p></div></div></div></blockquote><div><br></div><div>Looks like we're mixing top and bottom posts again.</div><div><br></div><div>I tried to make a distinction between Registry (that is, a party duly recognized and contracted with ICANN to a TLD within the valid list maintained by IANA) and a Registrar (an ICANN-accredited organization to interact with registrants)</div>
<div><br></div><div>The goal of the wording should be two-fold</div><div>1) Ensure that Registered Domain Names means it is a name that is a valid TLD according to IANA</div><div>2) Ensure that the domain has been registered by a registrant with an ICANN-accredited registrar, for</div>
<div><br></div><div>For what it's worth, here's the definition of "Registered Name" taken from the ICANN 2013 Registrar Accreditation Agreement ( <a href="http://www.icann.org/en/resources/registrars/raa/approved-with-specs-27jun13-en.htm">http://www.icann.org/en/resources/registrars/raa/approved-with-specs-27jun13-en.htm</a> )</div>
<br>"</div>1.11 "gTLD" or "gTLDs" refers to the top-level domain(s) of the DNS delegated by ICANN pursuant to a registry agreement that is in full force and effect, other than any country code TLD (ccTLD) or internationalized domain name (IDN) country code TLD.</div>
<div class="gmail_extra"><br></div><div class="gmail_extra"><snip></div><div class="gmail_extra"><br><div class="gmail_quote">1.15 "Registered Name" refers to a domain name within the domain of a gTLD, whether consisting of two (2) or more (e.g., <a href="http://john.smith.name">john.smith.name</a>) levels, about which a gTLD Registry Operator (or an Affiliate or subcontractor thereof engaged in providing Registry Services) maintains data in a Registry Database, arranges for such maintenance, or derives revenue from such maintenance. A name in a Registry Database may be a Registered Name even though it does not appear in a zone file (e.g., a registered but inactive name).<br>
<br>1.16 "Registered Name Holder" means the holder of a Registered Name.<br><br>1.17 The word "registrar," when appearing without an initial capital letter, refers to a person or entity that contracts with Registered Name Holders and with a Registry Operator and collects registration data about the Registered Name Holders and submits registration information for entry in the Registry Database."</div>
<div class="gmail_quote"><br></div><div class="gmail_quote"><br></div><div class="gmail_quote">The above language doesn't quite handle the ccTLD case, but the IANA Root Zone Database does cover these - <a href="http://www.iana.org/domains/root/db">http://www.iana.org/domains/root/db</a></div>
<div class="gmail_quote"><br></div><div class="gmail_quote">Sorry for the nit-picking here, but I am hoping to avoid future questions.</div><div class="gmail_quote"><br></div><div class="gmail_quote">"Registered Domain Name: A Domain Name that contains as the final level a valid domain according to the IANA Root Zone Database. For domains that end in a gTLD, the Domain Name MUST be registered with an ICANN-accredited Registrar that is authorized to register domains with the ICANN-assigned gTLD Registry Operator (or an Affiliate or subtractor thereof engaged in providing Registry Surfaces). For domains that end in a country-code or sponsored TLD, the Domain Name MUST be registered with a duly-authorized entity recognized by the Sponsoring Organization of the appropriate ccTLD. No other forms of Root Zones are permitted to appear within a Registered Domain Name"</div>
<div class="gmail_quote"><br></div><div class="gmail_quote">I realize this is a significant expansion on the original language, and may be best suited by multiple additions to the glossary (to cover generic TLD, country-code TLD, and sponsored TLD), and while it should be plainly obvious as common sense, it avoids any ambiguity - and avoids any risk of alternate registries being used and there being naming collisions.</div>
<div class="gmail_quote"><br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div lang="EN-US" link="blue" vlink="purple">
<div><div class="im"><p><br> <u></u></p>
</div><div><div class="h5"><p>-----Original Message-----<br>
From: Gervase Markham [mailto:<a href="mailto:gerv@mozilla.org" target="_blank">gerv@mozilla.org</a>] <br>
Sent: Tuesday, December 17, 2013 4:28 AM<br>
To: Ryan Sleevi; Kirk Hall (RD-US)<br>
Cc: CABFPub (<a href="mailto:public@cabforum.org" target="_blank">public@cabforum.org</a>)<br>
Subject: Re: [cabfpub] Proposal for change of definition of Internal Server Name in the BRs</p>
<p><u></u> <u></u></p>
<p>On 17/12/13 02:02, Ryan Sleevi wrote:<u></u><u></u></p>
<p>> Within Chromium's implementation, we've long interpreted Internal
<u></u><u></u></p>
<p>> Server Name exactly as you describe, and that has been our primary
<u></u><u></u></p>
<p>> concern with the deprecation of such names.<u></u><u></u></p>
<p>> <u></u><u></u></p>
<p>> The one caveat I would propose that, as we seek to improve wording, we
<u></u><u></u></p>
<p>> also ensure that the name that has been registered with a Domain Name
<u></u><u></u></p>
<p>> Registar authorized by the ICANN-assigned Registry for that domain
<u></u><u></u></p>
<p>> name space.<u></u><u></u></p>
<p><u></u> <u></u></p>
<p>This sounds good to me, with Ryan's caveat taken note of. The alternate domain names space has multiple competing instances of the same TLD, and they will no doubt clash with the new ICANN ones. I think we have to be ICANN-only.<u></u><u></u></p>
<p><u></u> <u></u></p>
<p>Gerv<u></u><u></u></p>
<p><u></u> <u></u></p>
</div></div></div>
</div>
<table><tbody><tr><td bgcolor="#ffffff"><font color="#000000"><pre><table><tbody><tr><td><pre>TREND MICRO EMAIL NOTICE
The information contained in this email and any attachments is confidential
and may be subject to copyright or other intellectual property protection.
If you are not the intended recipient, you are not authorized to use or
disclose this information, and we request that you notify us by reply mail or
telephone and delete the original message from your mail system.
</pre></td></tr></tbody></table></pre></font></td></tr></tbody></table></blockquote></div><br></div></div>