[Sipping] draft-ietf-sipping-gruu-reg-event-07 just posted
Paul Kyzivat <pkyzivat@cisco.com> Fri, 13 October 2006 22:16 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GYVJx-0000C6-8D; Fri, 13 Oct 2006 18:16:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GYVJv-0000C1-NK for sipping@ietf.org; Fri, 13 Oct 2006 18:15:59 -0400
Received: from sj-iport-4.cisco.com ([171.68.10.86]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GYVJu-0000by-0k for sipping@ietf.org; Fri, 13 Oct 2006 18:15:59 -0400
Received: from sj-dkim-6.cisco.com ([171.68.10.81]) by sj-iport-4.cisco.com with ESMTP; 13 Oct 2006 15:15:57 -0700
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138]) by sj-dkim-6.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id k9DMFvHd014318; Fri, 13 Oct 2006 15:15:57 -0700
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id k9DMFrOh016651; Fri, 13 Oct 2006 15:15:56 -0700 (PDT)
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); Fri, 13 Oct 2006 18:15:21 -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); Fri, 13 Oct 2006 18:15:20 -0400
Message-ID: <45300FF8.3080906@cisco.com>
Date: Fri, 13 Oct 2006 18:15:20 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: sipping@ietf.org
References: <E1GYT2g-0000zd-Hp@stiedprstage1.ietf.org>
In-Reply-To: <E1GYT2g-0000zd-Hp@stiedprstage1.ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 13 Oct 2006 22:15:20.0634 (UTC) FILETIME=[124289A0:01C6EF15]
DKIM-Signature: a=rsa-sha1; q=dns; l=5519; t=1160777757; x=1161641757; c=relaxed/simple; s=sjdkim6002; 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:draft-ietf-sipping-gruu-reg-event-07=20just=20posted; X=v=3Dcisco.com=3B=20h=3DQMBxP65igogkvV9YMJYab6FAdfA=3D; b=mTjvVGh4jqWVL453pSCCwaAahb8j8rEiw9fD3iSH6JRPOq+lTXOEYJ+QsVKfLIcJV2mYxzUm 2a62jmGxGNfQcF30rXboG/pKJu238QQOFOb2kl/ragK5abPtDAkO4UlT;
Authentication-Results: sj-dkim-6.cisco.com; header.From=pkyzivat@cisco.com; dkim=pass ( sig from cisco.com verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 093efd19b5f651b2707595638f6c4003
Cc: "Gray, Eric" <Eric.Gray@marconi.com>, Brian E Carpenter <brc@zurich.ibm.com>
Subject: [Sipping] draft-ietf-sipping-gruu-reg-event-07 just posted
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 revised draft-ietf-sipping-gruu-reg-event again. This was going to only have changes requested by the IESG. But then there have been some significant last minute changes in draft-ietf-sip-gruu-11 (not yet released the last I knew), that also required changes here. The following things have been done: - an incorrect reference (to RFC 3860 rather than 3680), spotted by Brian Carpenter, has been fixed. - the abstract has been reworded in an attempt to clarify confusing wording identified by the Gen-ART reviewer - Eric Gray. - in response to another review comment an example has been added to the security considerations section, showing how a proxy might control access for requests addressed to a GRUU. - some grammatical nits identified by reviewers have been fixed. - the plural usage of GRUU was changed from GRUU to GRUUs for consistency with draft-ietf-sip-gruu. (I changed it the other way for consistency a few revs back, but the pendulum swung again.) - the quoting conventions have been regularized when referring to the name of an event package. - the big semantic change is that now two there is provision for including both public and anonymous GRUUs, using <pub-gruu> and <anon-gruu>, rather than a single <gruu>. This is for alignment with gruu-11. This required changes in numerous places, including the examples. - extra normative language and security considerations have been added relative to the inclusion of an anonymous gruu in a notification. - gruu-11 renamed the URI parameters it uses from "gruu" to "gr, and from "opaque" to "aor-qual". While this has no normative effect on this draft, the examples were aligned with the change. - boilerplate was updated (automatically by xml2rfc). - the version number in the reference to draft-ietf-sip-gruu has been updated (by xml2rfc) from -07 to -10. Unfortunately it should be -11, but isn't because I submitted first. Sigh! I guess it doesn't matter because the RFC editor will have to change it to a reference to the RFC in any case. Hopefully this is the last revision of this! Paul Internet-Drafts@ietf.org wrote: > 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-07.txt > Pages : 14 > Date : 2006-10-13 > > 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-07.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-07.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-07.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 _______________________________________________ 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
- [Sipping] I-D ACTION:draft-ietf-sipping-gruu-reg-… Internet-Drafts
- [Sipping] draft-ietf-sipping-gruu-reg-event-07 ju… Paul Kyzivat