[Sipping] New draft-ietf-sipping-gruu-reg-event-08.txt submitted

Paul Kyzivat <pkyzivat@cisco.com> Tue, 24 October 2006 14:01 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GcMqS-0000lV-Bw; Tue, 24 Oct 2006 10:01:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GcMqQ-0000lQ-Ty for sipping@ietf.org; Tue, 24 Oct 2006 10:01:30 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GcMqJ-0002wc-OB for sipping@ietf.org; Tue, 24 Oct 2006 10:01:30 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by rtp-iport-1.cisco.com with ESMTP; 24 Oct 2006 07:01:23 -0700
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-2.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id k9OE1NrI021049 for <sipping@ietf.org>; Tue, 24 Oct 2006 10:01:23 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id k9OE1NDM012552 for <sipping@ietf.org>; Tue, 24 Oct 2006 10:01:23 -0400 (EDT)
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 24 Oct 2006 10:01:23 -0400
Received: from [161.44.79.182] ([161.44.79.182]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 24 Oct 2006 10:01:23 -0400
Message-ID: <453E1CB2.6010903@cisco.com>
Date: Tue, 24 Oct 2006 10:01:22 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: sipping <sipping@ietf.org>
Content-Type: multipart/mixed; boundary="------------000501060906000403010608"
X-OriginalArrivalTime: 24 Oct 2006 14:01:23.0092 (UTC) FILETIME=[E373C540:01C6F774]
DKIM-Signature: a=rsa-sha1; q=dns; l=4427; t=1161698483; x=1162562483; c=relaxed/simple; s=rtpdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=pkyzivat@cisco.com; z=From:Paul=20Kyzivat=20<pkyzivat@cisco.com> |Subject:New=20draft-ietf-sipping-gruu-reg-event-08.txt=20submitted |To:sipping=20<sipping@ietf.org>; X=v=3Dcisco.com=3B=20h=3D3ywh6MRmpLV89iS7zqNhHT0k9pI=3D; b=t5woIP451R73hJFbjp2bFiISKTaq+wbRLe8UlXG12B5/lIsuct1kfHF7rvj5UHKJ2XPJcodL mPLa/ePdEJEtKxxGOWDkRCFBSyZM7uRE3UnwGpbqUDvbdaGvndX6Rlm+;
Authentication-Results: rtp-dkim-2.cisco.com; header.From=pkyzivat@cisco.com; dkim=pass ( 42 extraneous bytes; sig from cisco.com verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5ebbf074524e58e662bc8209a6235027
Subject: [Sipping] New draft-ietf-sipping-gruu-reg-event-08.txt submitted
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
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>
Errors-To: sipping-bounces@ietf.org

I got a final change to gruu-reg-event in before the deadline. The -07 
version attempted to anticipate what was going to be in gruu-11, but got 
it wrong due to last minute discussions by the design team. The -08 
version aligns with the submitted gruu-11. The differences between -07 
and -08 are all about syntax and terminology.

I *hope* gruu-11 and gruu-reg-event-08 are both now in final form.

	Paul

-------- Original Message --------
Subject: [Sipping] I-D ACTION:draft-ietf-sipping-gruu-reg-event-08.txt
Date: Mon, 23 Oct 2006 15:50:03 -0400
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
CC: sipping@ietf.org

A New Internet-Draft is available from the on-line Internet-Drafts
directories.
This draft is a work item of the Session Initiation Proposal 
Investigation Working Group of the IETF.

	Title		: Registration Event Package Extension for Session Initiation 
Protocol (SIP) Globally Routable User Agent URIs (GRUUs)
	Author(s)	: P. Kyzivat
	Filename	: draft-ietf-sipping-gruu-reg-event-08.txt
	Pages		: 14
	Date		: 2006-10-23
	
RFC 3680 defines a Session Initiation Protocol (SIP) event package
    for registration state.  This package allows a watcher to learn about
    information stored by a SIP registrar, including its registered
    contact.

    However, the registered contact is frequently unreachable and thus
    not useful for watchers.  The Globally Routable User Agent URI
    (GRUU), defined in RFC YYYY [3], is a URI that is capable of reaching
    a particular contact.  However this URI is not included in the
    document format defined in RFC 3680.  This specification defines an
    extension to the registration event package to include GRUUs assigned
    by the registrar.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sipping-gruu-reg-event-08.txt

To remove yourself from the I-D Announcement list, send a message to
i-d-announce-request@ietf.org with the word unsubscribe in the body of
the message.
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the
username "anonymous" and a password of your e-mail address. After
logging in, type "cd internet-drafts" and then
"get draft-ietf-sipping-gruu-reg-event-08.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-sipping-gruu-reg-event-08.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

_______________________________________________
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