Re: [BLISS] SIP SIMPLE: "do not disturb" interoperability

Shida Schubert <shida@ntt-at.com> Tue, 06 September 2011 00:31 UTC

Return-Path: <shida@ntt-at.com>
X-Original-To: bliss@ietfc.amsl.com
Delivered-To: bliss@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 7A4411B60B19 for <bliss@ietfc.amsl.com>; Mon, 5 Sep 2011 17:31:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.664
X-Spam-Level:
X-Spam-Status: No, score=-99.664 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gZU6VzPi2PWn for <bliss@ietfc.amsl.com>; Mon, 5 Sep 2011 17:31:03 -0700 (PDT)
Received: from gator465.hostgator.com (gator465.hostgator.com [69.56.174.130]) by ietfc.amsl.com (Postfix) with ESMTP id 9F2201B60B17 for <bliss@ietf.org>; Mon, 5 Sep 2011 17:31:00 -0700 (PDT)
Received: from [122.135.156.233] (port=52815 helo=[192.168.1.139]) by gator465.hostgator.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <shida@ntt-at.com>) id 1R0jZ2-00014O-Tx; Mon, 05 Sep 2011 19:30:57 -0500
Mime-Version: 1.0 (Apple Message framework v1244.3)
Content-Type: multipart/alternative; boundary="Apple-Mail=_1A7743EE-EF91-42E6-8A4E-591343471984"
From: Shida Schubert <shida@ntt-at.com>
In-Reply-To: <9B7CB52192C7EA4C931088F28A51177C011D878E0EE1@hermelin.estos.de>
Date: Tue, 6 Sep 2011 09:30:57 +0900
Message-Id: <10B8E8B2-AAB7-4EE2-A76A-6B18779A6A84@ntt-at.com>
References: <9B7CB52192C7EA4C931088F28A51177C011D878E0EE1@hermelin.estos.de>
To: Raphael Bossek <raphael.bossek@estos.de>
X-Mailer: Apple Mail (2.1244.3)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - gator465.hostgator.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - ntt-at.com
X-BWhitelist: no
X-Source:
X-Source-Args:
X-Source-Dir:
X-Source-Sender: fl1-122-135-156-233.tky.mesh.ad.jp ([192.168.1.139]) [122.135.156.233]:52815
X-Source-Auth: shida@agnada.com
X-Email-Count: 2
X-Source-Cap: c3NoaWRhO3NzaGlkYTtnYXRvcjQ2NS5ob3N0Z2F0b3IuY29t
Cc: "bliss@ietf.org" <bliss@ietf.org>
Subject: Re: [BLISS] SIP SIMPLE: "do not disturb" interoperability
X-BeenThere: bliss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Basic Level of Interoperability for SIP Services \(BLISS\) BoF" <bliss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bliss>, <mailto:bliss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bliss>
List-Post: <mailto:bliss@ietf.org>
List-Help: <mailto:bliss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Sep 2011 00:31:05 -0000

Raphael;

 Although we discussed DND in the past here at 
BLISS, there wasn't sufficient interest to progress 
the work here. 

 As you are mainly looking at DND in the context 
of presence, I think you may get a better feedback by 
posting this question to SIMPLE mailing list. 

 Regards
  Shida

On Aug 25, 2011, at 9:36 PM, Raphael Bossek wrote:

> Dear IETF BLISS,
>  
> Just one sentence about me and ESTOS GmbH (http://www.estos.com) , the company I’m working for. I’m looking for a standard compliant solution for instant messaging exchange the “do not disturb”/DND presence information between clients – 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.
>  
> I’ve studied the RFC 4479 (http://tools.ietf.org/html/rfc4479#page-13 ) chapter “Reach Information” at page 13: “It is also possible for a presence document to contain a service that has no reach information at all.  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.”
>  
> The example from RFC 4480 (http://tools.ietf.org/html/rfc4480#page-19 ) chapter “Example” at page 13 describe a “do not disturb” case: “<contact priority="0.8">im:someone@mobile.example.net</contact>”
>  
> As conclusion we could say that “do not disturb” is set if
> n  Contact address for a <tuple> is missing (refer to RFC 4479) or
> n  The priority for the contact address within a service is less than 1.0 (refer to RFC 4480)
>  
> What do you thing about this interpretation?
>  
> I would like to fixating that officially but I’m not confirm with the IEFT process. Should this discussion be continued at https://lists.cs.columbia.edu/pipermail/sip-implementors/2008-April/018968.html ?
>  
> At the end I would like to make a publication athttp://stackoverflow.com/questions/6057830/sip-simple-pidf-convention-for-do-not-disturb-dnd-presence-extension 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.
>  
> Would appreciate to hear from you,
>  
> 
> 
> 
> i.A. Raphael Bossek
> Software Architect
> 
> ESTOS GmbH
> Petersbrunner Str. 3a
> 82319 Starnberg, Germany
> 
> Phone:	+49 (8151) 36856-153
> Fax:	+49 (8151) 36856-853
> Mobile:	+49 (151) 59177535
>  	
> E-Mail:	raphael.bossek@estos.de
> Web:	http://www.estos.de
> 
> 
> // Webinar: Facebook Killer Federation? 29. Sept 2011 um 10.00 Uhr.
> Jetzt anmelden!
> 
> <footer_110823_de.jpg>
> 
> // Wählen Sie ProCall!
> Sie finden ProCall ein tolles Produkt? Stimmen Sie jetzt bei der großen 
> Funkschau-Leserwahl für ESTOS. Hier geht's zum Voting...
> 
> <footer_110803_de.jpg>
> 
> 
> ---
> ESTOS GmbH
> Registered office: Starnberg, Germany
> Commercial registry Munich, HRB 133 670
> Managing Directors: Dipl.-Phys. Stephan Eckbauer, Dipl.-Ing. Stefan Hobratschk, Ing. Christoph Lösch, Florian Bock
> _______________________________________________
> BLISS mailing list
> BLISS@ietf.org
> https://www.ietf.org/mailman/listinfo/bliss