IETF Logo Mail Archive

[Sipping] Update to caller preferences use cases

Jonathan Rosenberg <jdrosen@dynamicsoft.com> Tue, 08 July 2003 07:29 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA12880 for <sipping-archive@odin.ietf.org>; Tue, 8 Jul 2003 03:29:32 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZmuN-0001va-Vf for sipping-archive@odin.ietf.org; Tue, 08 Jul 2003 03:29:03 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h687T3GZ007408 for sipping-archive@odin.ietf.org; Tue, 8 Jul 2003 03:29:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZmuN-0001vP-OS for sipping-web-archive@optimus.ietf.org; Tue, 08 Jul 2003 03:29:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA12861 for <sipping-web-archive@ietf.org>; Tue, 8 Jul 2003 03:29:01 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ZmuL-0007Cv-00 for sipping-web-archive@ietf.org; Tue, 08 Jul 2003 03:29:01 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19ZmuK-0007Cs-00 for sipping-web-archive@ietf.org; Tue, 08 Jul 2003 03:29:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZmuM-0001uQ-3E; Tue, 08 Jul 2003 03:29:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZmtN-0001sC-OJ for sipping@optimus.ietf.org; Tue, 08 Jul 2003 03:28:01 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA12816 for <sipping@ietf.org>; Tue, 8 Jul 2003 03:27:59 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ZmtL-0007CI-00 for sipping@ietf.org; Tue, 08 Jul 2003 03:27:59 -0400
Received: from [63.113.44.69] (helo=mail3.dynamicsoft.com) by ietf-mx with esmtp (Exim 4.12) id 19ZmtG-0007CA-00 for sipping@ietf.org; Tue, 08 Jul 2003 03:27:54 -0400
Received: from dynamicsoft.com ([63.113.46.11]) by mail3.dynamicsoft.com (8.12.8/8.12.1) with ESMTP id h687RNiB005521 for <sipping@ietf.org>; Tue, 8 Jul 2003 03:27:24 -0400 (EDT)
Message-ID: <3F0A7256.60900@dynamicsoft.com>
Date: Tue, 08 Jul 2003 03:27:18 -0400
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: sipping <sipping@ietf.org>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Sipping] Update to caller preferences use cases
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Folks,

You may have seen that I posted an update to the caller preferences 
use cases:

http://www.jdrosen.net/papers/draft-ietf-sipping-callerprefs-usecases-00.txt
http://www.jdrosen.net/papers/draft-ietf-sipping-callerprefs-usecases-00.html
http://www.ietf.org/internet-drafts/draft-ietf-sipping-callerprefs-usecases-00.txt

This is now a working item of SIPPING.

There are a bunch of changes since the previous version. Firstly, the 
use cases are now aligned with the -09 version of caller preferences. 
As a result of the changes in the caller preferences algorithms, 
several use cases no longer work. I've already documented those in a 
note to sip.

Some other changes:

* added a hearing impaired use case
* added a use case where the registered contact has an embedded 
Reject-Contact
* added a bunch of example registrations from various common devices, 
to show how to use caller prefs
* added a bunch of material up front to motivate caller prefs

And some other open issues:

* one of the use cases (section 3.14) is really better done with a CPL 
script than caller preferences. Should we eliminate this use case? I 
say yes.

* do we advise devices to register what they can't do, along with what 
they can do? THis makes the registrations a lot more bloated, but 
caller preferences tends to work better. I say no.

* do we want to include an example implementation of the matching 
procedure of rfc2533? The benefit is to help calrify the spec a lot. 
The drawback is - what happens if its not consistent with the 
normative algorithm in RFC2533? I say we should include it.


Comments and questions welcome.

Thanks,
Jonathan R.
-- 
Jonathan D. Rosenberg, Ph.D.                600 Lanidex Plaza
Chief Technology Officer                    Parsippany, NJ 07054-2711
dynamicsoft
jdrosen@dynamicsoft.com                     FAX:   (973) 952-5050
http://www.jdrosen.net                      PHONE: (973) 952-5000
http://www.dynamicsoft.com



_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP

v2.23.0 | Report a Bug | By Email