[Sip] Updated gruu I-D

Jonathan Rosenberg <jdrosen@dynamicsoft.com> Mon, 16 February 2004 01:44 UTC

Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA07471 for <sip-archive@odin.ietf.org>; Sun, 15 Feb 2004 20:44:45 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AsXo1-0006Rd-4Q for sip-archive@odin.ietf.org; Sun, 15 Feb 2004 20:44:17 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1G1iHH0024711 for sip-archive@odin.ietf.org; Sun, 15 Feb 2004 20:44:17 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AsXnm-0006MC-IE; Sun, 15 Feb 2004 20:44:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AsXne-0006L6-GZ for sip@optimus.ietf.org; Sun, 15 Feb 2004 20:43:54 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA07465 for <sip@ietf.org>; Sun, 15 Feb 2004 20:43:52 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AsXnc-00000W-00 for sip@ietf.org; Sun, 15 Feb 2004 20:43:52 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AsXmn-0007lr-00 for sip@ietf.org; Sun, 15 Feb 2004 20:43:02 -0500
Received: from [63.113.44.69] (helo=mail3.dynamicsoft.com) by ietf-mx with esmtp (Exim 4.12) id 1AsXmZ-0007if-00 for sip@ietf.org; Sun, 15 Feb 2004 20:42:47 -0500
Received: from dynamicsoft.com ([63.113.46.68]) by mail3.dynamicsoft.com (8.12.8/8.12.1) with ESMTP id i1G1gONr004824 for <sip@ietf.org>; Sun, 15 Feb 2004 20:42:25 -0500 (EST)
Message-ID: <40301FF8.40201@dynamicsoft.com>
Date: Sun, 15 Feb 2004 20:42:16 -0500
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: sip@ietf.org
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Subject: [Sip] Updated gruu I-D
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Folks,

I've just submitted an update to the GRUU specification. Until it 
appears in the archives, you can find it at:

http://www.jdrosen.net/papers/draft-ietf-sip-gruu-01.txt

The differences are:

* removed requirement that the gruu be constructed in such a way that
the contact and/or AOR can be determined from it

* indicate that a gruu can be obtained by the register mechanisms in
the specification, but that other mechanisms are also possible

* The gruu is now associated with the instance ID of the UA. The
instance ID is defined as a callee capability parameter. The
specification now includes a UML diagram showing the relationships
between GRUU, AOR, Contact URI and instance ID.

* Added registration of the sip.instance media feature tag



The biggest change is the third. Indeed, it seems like we have three 
drafts this round that discuss instance identifiers in SIP:

http://www.jdrosen.net/papers/draft-ietf-sip-gruu-01.txt
http://www.ietf.org/internet-drafts/draft-jennings-sipping-instance-id-00.txt
http://www.ietf.org/internet-drafts/draft-stucker-sip-guid-00.txt

all three are similar. Mine uses a contact header field parameter, and 
uses the callee capabilities framework to enable caller preferences 
routing based on instance iDs. Cullen also uses a contact parameter, but 
not within the callee caps framework. Brian defines a header field. I'll 
post a separate not starting a thread on the pros and cons of the 
various approaches.

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


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