<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
On 11/16/2012 10:16 PM, From Ryan Sleevi:
<blockquote
cite="mid:CACvaWvZaY9DK3Q2z6=tVGQx6+pgNSzmKoOttoZYVMqdrDAAJLw@mail.gmail.com"
type="cite">
<div style="font-family: arial,helvetica,sans-serif; font-size:
10pt;">Thus, while we support this effort, it should be clear
our motivations, and that we'd not support measures to further
encourage, permit, or undeprecate internal names, regardless of
any additional validation checks that may be proposed in the
future.</div>
</blockquote>
<br>
Even though it's actually not directly effecting the web per se,
internal and unqualified host names and IP addresses are a risk to
the relying parties and not something CAs can verify anyway. If you
consider proposing a ballot to deprecate and disallow it on an
earlier date, I'd be happy to endorse it today.<br>
<br>
<br>
<div class="moz-signature">
<table border="0" cellpadding="0" cellspacing="0">
<tbody>
<tr>
<td colspan="2">Regards </td>
</tr>
<tr>
<td colspan="2"> </td>
</tr>
<tr>
<td>Signer: </td>
<td>Eddy Nigg, COO/CTO</td>
</tr>
<tr>
<td> </td>
<td><a href="http://www.startcom.org">StartCom Ltd.</a></td>
</tr>
<tr>
<td>XMPP: </td>
<td><a href="xmpp:startcom@startcom.org">startcom@startcom.org</a></td>
</tr>
<tr>
<td>Blog: </td>
<td><a href="http://blog.startcom.org">Join the Revolution!</a></td>
</tr>
<tr>
<td>Twitter: </td>
<td><a href="http://twitter.com/eddy_nigg">Follow Me</a></td>
</tr>
<tr>
<td colspan="2"> </td>
</tr>
</tbody>
</table>
</div>
<br>
</body>
</html>