attachment
<div dir="ltr"><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">---------- Forwarded message ---------<br>From: <b class="gmail_sendername" dir="auto">Salz, Rich</b> <span dir="auto"><rsalz=<a href="mailto:40akamai.com@dmarc.ietf.org">40akamai.com@dmarc.ietf.org</a>></span><br>Date: Thu, Feb 4, 2021 at 10:44 AM<br>Subject: [Secdispatch] Requesting agenda time for draft-rsalz-use-san<br>To: <a href="mailto:secdispatch@ietf.org">secdispatch@ietf.org</a> <<a href="mailto:secdispatch@ietf.org">secdispatch@ietf.org</a>><br></div><br><br>I would like to present <a href="https://datatracker.ietf.org/doc/draft-rsalz-use-san/" rel="noreferrer" target="_blank">https://datatracker.ietf.org/doc/draft-rsalz-use-san/</a><br>
<br>
This updates RFC 6125 to remove commonName as a way to identify the server; just use subjectAltName. It also limits where the "*" can go in wildcard certificates. This is a simplification of widely implemented existing practice. It may even be de facto what's mostly done. Perhaps the wildcard limitation is controversial and I'd be willing to remove it.<br>
<br>
6125 was AD-sponsored. I think this could also be, or perhaps it could go to UTA. I would not present any slides, and think 10-15 minutes would be enough time.<br>
<br>
<br>
_______________________________________________<br>
Secdispatch mailing list<br>
<a href="mailto:Secdispatch@ietf.org" target="_blank">Secdispatch@ietf.org</a><br>
<a href="https://www.ietf.org/mailman/listinfo/secdispatch" rel="noreferrer" target="_blank">https://www.ietf.org/mailman/listinfo/secdispatch</a><br>
</div></div>