<html xmlns:v="urn:schemas-microsoft-com:vml" 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=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@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;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal">Hi guys,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">One idea we’ve been kicking around to enable discovery for hosted domains is using a specific domain prefix in cases where writing a .well-known file into the root of the hosted domain is inconvenient/impossible. So for instance, rather
than doing Simple Web Discovery at:<o:p></o:p></p>
<p class="MsoNormal"> <a href="https://example.com/.well-known/simple-web-discovery">
https://example.com/.well-known/simple-web-discovery</a><o:p></o:p></p>
<p class="MsoNormal">one might fall back to (or start with)<o:p></o:p></p>
<p class="MsoNormal"> <a href="https://simple-web-discovery.example.com/.well-known/simple-web-discovery">
https://simple-web-discovery.example.com/.well-known/simple-web-discovery</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Then, rather than having to create a file in the domain root to do discovery, instead one could create a DNS record pointing to a hosted SWD service. This is logically no harder than creating a DNS record for other domains such as www.example.com
or mail.example.com.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">First, what are your thoughts about that possible approach? It may be easier to widely deploy than approaches that rely on DNS SRV records, for instance.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The one hesitation we’ve discussed is that just because you have a certificate for example.com, that doesn’t necessarily make it easy to create a certificate for simple-web-discovery.example.com. Do any of you have an experience with SSL
certificates for subdomains? Do any of your services presently use them? And if so, how are they created/managed?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Your thoughts would be greatly appreciated.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> Thanks,<o:p></o:p></p>
<p class="MsoNormal"> -- Mike<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>