Basic Level of Interoperability for SIP Services

headers Raphael Bossek | 25 Aug 2011 14:36

<div>
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US">Dear IETF BLISS,<p></p></span></p>
<p class="MsoNormal"><span lang="EN-US"><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span lang="EN-US">Just one sentence about me and ESTOS GmbH (<a href="http://www.estos.com">http://www.estos.com</a>) , the company I&rsquo;m working for. I&rsquo;m looking for a standard compliant solution for instant messaging exchange the &ldquo;do not
 disturb&rdquo;/DND presence information between clients &ndash; if possible without introduction of new tags or values. ESTOS GmbH is a software manufacturer for unified communication and collaboration products and depends heavily on standards for interoperability with
 PBX and phone manufactures.<p></p></span></p>
<p class="MsoNormal"><span lang="EN-US"><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span lang="EN-US">I&rsquo;ve studied the RFC 4479 (<a href="http://tools.ietf.org/html/rfc4479#page-13">http://tools.ietf.org/html/rfc4479#page-13</a> ) chapter &ldquo;Reach Information&rdquo; at page 13: &ldquo;It is also possible for a presence document to
 contain a service that has no reach information at all.&nbsp; In such a case, the presentity is indicating that the service exists, but is electing not to offer the watcher the opportunity to connect to it.&rdquo;<p></p></span></p>
<p class="MsoNormal"><span lang="EN-US"><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span lang="EN-US">The example from RFC 4480 (<a href="http://tools.ietf.org/html/rfc4480#page-19">http://tools.ietf.org/html/rfc4480#page-19</a> ) chapter &ldquo;Example&rdquo; at page 13 describe a &ldquo;do not disturb&rdquo; case: &ldquo;&lt;contact priority="0.8"&gt;<a href="im:someone@...%3c/contact">im:someone <at> mobile.example.net&lt;/contact</a>&gt;&rdquo;<p></p></span></p>
<p class="MsoNormal"><span lang="EN-US"><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span lang="EN-US">As conclusion we could say that &ldquo;do not disturb&rdquo; is set if<p></p></span></p>
<p class="MsoListParagraph"><span lang="EN-US"><span>n<span>&nbsp;
</span></span></span><span lang="EN-US">Contact address for a &lt;tuple&gt; is missing (refer to RFC 4479) or<p></p></span></p>
<p class="MsoListParagraph"><span lang="EN-US"><span>n<span>&nbsp;
</span></span></span><span lang="EN-US">The priority for the contact address within a service is less than 1.0 (refer to RFC 4480)<p></p></span></p>
<p class="MsoNormal"><span lang="EN-US"><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span lang="EN-US">What do you thing about this interpretation?<p></p></span></p>
<p class="MsoNormal"><span lang="EN-US"><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span lang="EN-US">I would like to fixating that officially but I&rsquo;m not confirm with the IEFT process. Should this discussion be continued at
<a href="https://lists.cs.columbia.edu/pipermail/sip-implementors/2008-April/018968.html">
https://lists.cs.columbia.edu/pipermail/sip-implementors/2008-April/018968.html</a> ?<p></p></span></p>
<p class="MsoNormal"><span lang="EN-US"><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span lang="EN-US">At the end I would like to make a publication at
<a href="http://stackoverflow.com/questions/6057830/sip-simple-pidf-convention-for-do-not-disturb-dnd-presence-extension">
http://stackoverflow.com/questions/6057830/sip-simple-pidf-convention-for-do-not-disturb-dnd-presence-extension</a> and some open source projects about the way to do. I have also contact to SEN OpenStage phone people. Maybe they will join this discussion.<p></p></span></p>
<p class="MsoNormal"><span lang="EN-US"><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span lang="EN-US">Would appreciate to hear from you,<p></p></span></p>
<p class="MsoNormal"><span lang="EN-US"><p>&nbsp;</p></span></p>
</div>
<br>
<br><br><div align="left">
<span>i.A.  Raphael Bossek<br>Software Architect<br><br>ESTOS 
GmbH<br>Petersbrunner Str. 3a<br>82319 Starnberg, 
Germany<br><br></span>
<table bordercolor="#111111" cellspacing="0" cellpadding="0" width="100%" border="0">
<tr>
<td>Phone:</td>
    <td>+49 (8151) 36856-153</td>
</tr>
<tr>
<td>Fax:</td>
    <td>+49 (8151) 36856-853</td>
</tr>
<tr>
<td>Mobile:</td>
    <td>+49 (151) 59177535</td>
</tr>
<tr>
<td width="50">&nbsp;</td>
    <td></td>
</tr>
<tr>
<td>E-Mail:</td>
    <td>raphael.bossek@...</td>
</tr>
<tr>
<td>Web:</td>
    <td><a title="" href="http://www.estos.de/">http://www.estos.de</a></td>
</tr>
</table>
</div>
<br><br><div align="left"><span><span>// 
Webinar: Facebook Killer Federation? 29. Sept 2011 um 10.00 
Uhr.</span></span></div>
<div align="left"><span><a title="Funkschau Voting" href="http://www.estos.de/partner/webinare/webinar-facebook-killer-federation.html">Jetzt 
anmelden!</a></span></div>
<div align="left">
<span></span><br><a href="http://www.estos.de/partner/webinare/webinar-facebook-killer-federation.html"></a>
</div>
<br><div align="left">
<span><span>// 
W&auml;hlen Sie ProCall!<br>Sie finden ProCall ein tolles Produkt? Stimmen Sie jetzt 
bei der gro&szlig;en <br>Funkschau-Leserwahl f&uuml;r ESTOS. </span></span><span><a title="Funkschau Voting" href="http://www.funkschau.de/specials/itk2011/fragebogen/">Hier geht's zum 
Voting...</a></span>
</div>
<div align="left">
<span></span><br><a href="http://www.funkschau.de/specials/itk2011/fragebogen/"></a>
</div>
<br><br><div align="left"><span>---<br>ESTOS 
GmbH<br>Registered office: Starnberg, Germany<br>Commercial registry Munich, HRB 
133 670<br>Managing Directors: Dipl.-Phys. Stephan Eckbauer, Dipl.-Ing. Stefan 
Hobratschk, Ing. Christoph L&ouml;sch, Florian Bock</span></div>
</div>

SIP SIMPLE: "do not disturb" interoperability

Re: SIP SIMPLE: "do not disturb" interoperability

Phone:	+49 (8151) 36856-153
Fax:	+49 (8151) 36856-853
Mobile:	+49 (151) 59177535

E-Mail:	raphael.bossek-5CnTNc0ZioU@public.gmane.org
Web:	http://www.estos.de