143 lines
6.0 KiB
HTML
143 lines
6.0 KiB
HTML
<html>
|
|
|
|
<head>
|
|
<meta http-equiv="Content-Language" content="en-us">
|
|
<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
|
|
<meta name="GENERATOR" content="Microsoft FrontPage 4.0">
|
|
<meta name="ProgId" content="FrontPage.Editor.Document">
|
|
<title>BryanSt's Jihads</title>
|
|
<meta name="Microsoft Border" content>
|
|
</head>
|
|
|
|
<body background="../../paper5.jpg" bgproperties="fixed">
|
|
|
|
<h1 align="center">BryanSt's AutoDiscovery</h1>
|
|
<p>This is the "Automatically Discovery Settings" for software on a
|
|
per-user account bases. The account is tied to an email address. So
|
|
if the user has been identified as "<a href="mailto:joeBlow@foobar.com">JoeUser@foobar.com</a>",
|
|
we then contact the appropriate servers (??.foobar.com) and get the settings to
|
|
configure the appropriate software. This works really well to configure:
|
|
1) email accounts, 2) a Virtual Private Network connection, 3) Newsgroups, 4)
|
|
v-Card information, and 5) a LDAP URL for further information.</p>
|
|
<p> </p>
|
|
<h3>Links:</h3>
|
|
<ul>
|
|
<li>
|
|
<p align="left"><a href="AutoDiscovery.htm">AutoDiscovery Spec</a>
|
|
(Overview)</li>
|
|
<li>
|
|
<p align="left"><a href="rfc.htm">AutoDiscovery Network Protocol</a> (For
|
|
RFC)</li>
|
|
<li>
|
|
<p align="left"><a href="ADServiceProposal.htm">AutoDiscovery Service
|
|
Business Proposal</a></li>
|
|
<li>
|
|
<p align="left"><a href="internal.htm">Internal Notes</a> (My Notes)</li>
|
|
</ul>
|
|
<p> </p>
|
|
<h3>Contacts:</h3>
|
|
<ul>
|
|
<li>
|
|
<p align="left"><b>Shell Dev:</b> <a href="mailto:bryanst@microsoft.com">BryanSt</a>
|
|
(contact first)</li>
|
|
<li>
|
|
<p align="left"><b>Outlook Express:</b> <a href="mailto:csager@microsoft.com">CSager</a>
|
|
(PM) and <a href="mailto:yst@microsoft.com">YSt</a> (Dev)</li>
|
|
<li>
|
|
<p align="left"><b>autodiscovery.windows.com:</b> Operations: <a href="mailto:DougSa@microsoft.com">Doug
|
|
Stamper</a>, PM: <a href="mailto:EugeneH@microsoft.com">Eugene Ho</a>.</li>
|
|
<li>
|
|
<p><b>Referal Server:</b> PM: <a href="mailto:ScotJohn@microsoft.com">Scott
|
|
Johnson</a>, Dev: <a href="mailto:vYung@microsoft.com">Vincent Yung</a>.</li>
|
|
<li>
|
|
<p align="left"><b>Outlook:</b> Accounts PM: <a href="mailto:taddg@microsoft.com">Tadd
|
|
Giles</a>, Marketting Stats/Product Manager: <a href="mailto:daviddel@microsoft.com">David
|
|
Delisi</a>, PSS Stats: <a href="mailto:toddDo@microsoft.com">Todd Dooley</a>,
|
|
Accounts Dev Lead: <a href="mailto:Radub@microsoft.com">Radu Bacioiu</a>,
|
|
Dev: <a href="mailto:JuliaC@microsoft.com">Julia Cai</a>.</li>
|
|
<li>
|
|
<p align="left"> </li>
|
|
<li>
|
|
<p align="left">IEAK: <a href="mailto:rfanco@microsoft.com">RFanco</a></li>
|
|
<li>
|
|
<p align="left">UI and PM: <a href="mailto:gsierra@microsoft.com">GSierra</a></li>
|
|
<li>
|
|
<p align="left">RFC Spec & Standards PM: <a href="mailto:JoshCo@microsoft.com">JoshCo</a></li>
|
|
<li>
|
|
<p align="left">VPN UI: RaoS (Rao Salapaka) is probably the dev for the
|
|
wizard. DavidEi is the PM. PMay (Paul Mayfield)
|
|
\nt\private\net\routing\ras\ui\rasdlg\.</li>
|
|
</ul>
|
|
<p> </p>
|
|
|
|
<h3> </h3>
|
|
<h3>Open Concerns:</h3>
|
|
<p align="left"><b>Shell Team:</b>
|
|
<ul>
|
|
<li>
|
|
<p align="left"><b>Question:</b> Who will maintain server? <b>Answer:</b>
|
|
See microsoft.com. </li>
|
|
<li>
|
|
<p align="left"><b>Question:</b> Who will buy the servers? <b>Answer:</b>
|
|
The shell team's cost center. Office would also almost certainly be
|
|
willing to pay for it. Estimated Cost: $45k. </li>
|
|
<li>
|
|
<p align="left"><b>Question:</b> Who will maintain the content? <b>Answer:</b>
|
|
Officially, Tadd Giles. We will probably do a one time list of the top
|
|
30 servers and not change it much or at all after that. </li>
|
|
<li>
|
|
<p align="left"><b>Question:</b> What % of users does the referal server not
|
|
handle? <b>Answer:</b> nnn%. Stats from David
|
|
Delisi. </li>
|
|
<li>
|
|
<p align="left"><b>Question:</b> Does the referal server team see any
|
|
problems? <b>Answer:</b> See Referal Server</li>
|
|
</ul>
|
|
<p> </p>
|
|
<p align="left"><b>microsoft.com:</b> (Doug Samper)
|
|
<ul>
|
|
<li>
|
|
<p align="left">They will own the server if Debrah Black signs off on the
|
|
Business Purposal.</li>
|
|
</ul>
|
|
<p> </p>
|
|
<p align="left"><b>Referal Server:</b> (Scott Johnson)
|
|
<ul>
|
|
<li>
|
|
<p align="left">Microsoft.com will run and maintain the servers.</li>
|
|
<li>
|
|
<p align="left"><b>Question:</b> Will 2 or 3 ISPs say that they will find it
|
|
find it useful and they are happy with the information being
|
|
provided? <b>Answer:</b> I'm going to meet with them.</li>
|
|
<li>
|
|
<p align="left"><b>Question:</b> Make sure the user is informed that email
|
|
associations won't configure accounts in legacy apps. <b>Answer:</b>
|
|
Easy to add to UI.</li>
|
|
<li>
|
|
<p align="left">Scott says that this solution will definitely cover
|
|
significate cases that the referal server won't cover today.</li>
|
|
</ul>
|
|
<p> </p>
|
|
<h3> </h3>
|
|
<h3>Status:</h3>
|
|
<ul>
|
|
<li>
|
|
<p align="left">Design & Implemenation: The design is finished and the
|
|
API is implemented. TODO: 1) We can write high level automation
|
|
interfaces for each of the AutoDiscovery specific users (VPN, vCard,
|
|
etc.). Currently, we only have email. Callers can use low level
|
|
API if we don't do the high level API. 2) Clean up the caching of
|
|
data. 3) Change implementation to use final XML format (from RFC).</li>
|
|
<li>
|
|
<p align="left">XML Format After RFC suggestions: BryanSt needs to clean up
|
|
the spec. JoshCo will then send it around for suggestions and
|
|
submission to as an RFC.</li>
|
|
<li>
|
|
<p align="left">UI & Products: GSierra needs to find out which products
|
|
(e-mail in sepcific) are going to use the API.</li>
|
|
</ul>
|
|
|
|
</body>
|
|
|
|
</html>
|