idnits 2.17.1 

draft-ietf-sipping-gruu-reg-event-01.txt:

  Checking boilerplate required by RFC 5378 and the IETF Trust (see
  https://trustee.ietf.org/license-info):
  ----------------------------------------------------------------------------

  ** It looks like you're using RFC 3978 boilerplate.  You should update this
     to the boilerplate described in the IETF Trust License Policy document
     (see https://trustee.ietf.org/license-info), which is required now.

  -- Found old boilerplate from RFC 3978, Section 5.1 on line 14.

  -- Found old boilerplate from RFC 3978, Section 5.5 on line 456.

  -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 433.

  -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 440.

  -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 446.

  ** This document has an original RFC 3978 Section 5.4 Copyright Line,
     instead of the newer IETF Trust Copyright according to RFC 4748.

  ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead
     of the newer disclaimer which includes the IETF Trust according to RFC
     4748.


  Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt:
  ----------------------------------------------------------------------------

  == No 'Intended status' indicated for this document; assuming Proposed
     Standard


  Checking nits according to https://www.ietf.org/id-info/checklist :
  ----------------------------------------------------------------------------

  ** The abstract seems to contain references ([1]), which it shouldn't. 
     Please replace those with straight textual mentions of the documents in
     question.

  ** The document seems to lack a both a reference to RFC 2119 and the
     recommended RFC 2119 boilerplate, even if it appears to use RFC 2119
     keywords. 

     RFC 2119 keyword, line 113: '...   A notifier for the "reg" event package [1] SHOULD include the <gruu>...'
     RFC 2119 keyword, line 116: '...e <gruu> element MUST be be positioned...'
     RFC 2119 keyword, line 122: '...ing a <gruu>, it SHOULD use the gruu i...'
     RFC 2119 keyword, line 303: '...ML document that MUST be well-formed a...'
     RFC 2119 keyword, line 304: '...   SHOULD be valid.  Gruu documents MU...'


  Miscellaneous warnings:
  ----------------------------------------------------------------------------

  == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not
     match the current year

  -- The document seems to lack a disclaimer for pre-RFC5378 work, but may
     have content which was first submitted before 10 November 2008.  If you
     have contacted all the original authors and they are all willing to grant
     the BCP78 rights to the IETF Trust, then this is fine, and you can ignore
     this comment.  If not, you may need to add the pre-RFC5378 disclaimer. 
     (See the Legal Provisions document at
     https://trustee.ietf.org/license-info for more information.)

  -- The document date (November 22, 2005) is 6730 days in the past.  Is this
     intentional?


  Checking references for intended status: Proposed Standard
  ----------------------------------------------------------------------------

     (See RFCs 3967 and 4897 for information about using normative references
     to lower-maturity documents in RFCs)

  == Unused Reference: '4' is defined on line 397, but no explicit reference
     was found in the text

  == Unused Reference: '6' is defined on line 406, but no explicit reference
     was found in the text

  == Outdated reference: A later version (-15) exists of
     draft-ietf-sip-gruu-06

  -- Obsolete informational reference (is this intentional?): RFC 3455 (ref.
     '5') (Obsoleted by RFC 7315)


     Summary: 5 errors (**), 0 flaws (~~), 5 warnings (==), 8 comments (--).

     Run idnits with the --verbose option for more detailed information about
     the items above.

--------------------------------------------------------------------------------


2	Sipping                                                       P. Kyzivat
3	Internet-Draft                                       Cisco Systems, Inc.
4	Expires: May 26, 2006                                  November 22, 2005

6	                 Reg Event Package Extension for GRUUs
7	                  draft-ietf-sipping-gruu-reg-event-01

9	Status of this Memo

11	   By submitting this Internet-Draft, each author represents that any
12	   applicable patent or other IPR claims of which he or she is aware
13	   have been or will be disclosed, and any of which he or she becomes
14	   aware will be disclosed, in accordance with Section 6 of BCP 79.

16	   Internet-Drafts are working documents of the Internet Engineering
17	   Task Force (IETF), its areas, and its working groups.  Note that
18	   other groups may also distribute working documents as Internet-
19	   Drafts.

21	   Internet-Drafts are draft documents valid for a maximum of six months
22	   and may be updated, replaced, or obsoleted by other documents at any
23	   time.  It is inappropriate to use Internet-Drafts as reference
24	   material or to cite them other than as "work in progress."

26	   The list of current Internet-Drafts can be accessed at
27	   http://www.ietf.org/ietf/1id-abstracts.txt.

29	   The list of Internet-Draft Shadow Directories can be accessed at
30	   http://www.ietf.org/shadow.html.

32	   This Internet-Draft will expire on May 26, 2006.

34	Copyright Notice

36	   Copyright (C) The Internet Society (2005).

38	Abstract

40	   This draft defines an extension to RFC 3680 [1] for representing the
41	   GRUU associated with a Contact.

43	Table of Contents

45	   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
46	   2.  Description  . . . . . . . . . . . . . . . . . . . . . . . . .  3
47	   3.  Notifier Processing of SUBSCRIBE Requests  . . . . . . . . . .  3
48	   4.  Notifier Generation of NOTIFY Requests . . . . . . . . . . . .  4
49	   5.  Subscriber Processing of NOTIFY Requests . . . . . . . . . . .  4
50	   6.  Sample reginfo Document  . . . . . . . . . . . . . . . . . . .  4
51	   7.  Examples . . . . . . . . . . . . . . . . . . . . . . . . . . .  5
52	     7.1.  Example: Welcome Notice  . . . . . . . . . . . . . . . . .  5
53	     7.2.  Example: Implicit Registration . . . . . . . . . . . . . .  5
54	   8.  XML Schema Definition  . . . . . . . . . . . . . . . . . . . .  8
55	   9.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . .  8
56	     9.1.  URN Sub-Namespace Registration . . . . . . . . . . . . . .  8
57	     9.2.  XML Schema Registration  . . . . . . . . . . . . . . . . .  9
58	   10. Security Considerations  . . . . . . . . . . . . . . . . . . .  9
59	   11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . .  9
60	   12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 10
61	     12.1. Normative References . . . . . . . . . . . . . . . . . . . 10
62	     12.2. Informative References . . . . . . . . . . . . . . . . . . 10
63	   Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 11
64	   Intellectual Property and Copyright Statements . . . . . . . . . . 12

66	1.  Introduction

68	   The addition of GRUU (Globally Routable Unique URI) support to the
69	   REGISTER message, defined in [2], introduces another element of state
70	   to the registrar.  Subscribers to the registration event package [1]
71	   will sometimes have need for the new state.

73	   For example, the Welcome Notices example in [1] will only operate
74	   correctly if the contact address in the reg event notification is
75	   reachable by the sender of the welcome notice.  When the registering
76	   device is using the gruu extension, it is likely that the registered
77	   contact address will not be globally addressable, and the gruu should
78	   be used as the target address for the MESSAGE.

80	   Another case where this feature may be helpful is within the 3GPP IP
81	   Multimedia Subsystem (IMS).  IMS employs a technique where a REGISTER
82	   of a contact address to one Address of Record (AOR) causes the
83	   implicit registration of the same contact to other associated AORs.
84	   If a GRUU is requested and obtained as part of the registration
85	   request, then additional GRUUs will also be needed for the implicit
86	   registrations.  While assigning the additional GRUUs is
87	   straightforward, informing the registering UA of them is not.  In
88	   IMS, UAs typically subscribe to the 'reg' event, and subscriptions to
89	   the 'reg' event for an AOR result in notifications containing
90	   registration state for all the associated AORs.  The proposed
91	   extension provides a way to easily deliver the GRUUs for the
92	   associated AORs.

94	   The reg event package has provision for including extension elements
95	   within the <contact> element.  This document defines a new element
96	   that may be used in that context to deliver the GRUU corresponding to
97	   the contact.

99	2.  Description

101	   A new element (<gruu>) is defined which contains a GRUU.

103	   This optional element is included within the body of a NOTIFY for the
104	   "reg" event package when a GRUU is associated with the contact.  The
105	   contact URI and the GRUU are then both available to the watcher.

107	3.  Notifier Processing of SUBSCRIBE Requests

109	   Unchanged from RFC 3680 [1].

111	4.  Notifier Generation of NOTIFY Requests

113	   A notifier for the "reg" event package [1] SHOULD include the <gruu>
114	   element when a contact has an Instance ID and a GRUU is associated
115	   with the combination of the AOR and the Instance ID.  When present,
116	   the <gruu> element MUST be be positioned as an instance of the <any>
117	   element within the <contact> element.

119	5.  Subscriber Processing of NOTIFY Requests

121	   When a subscriber receives a "reg" event notification [1] with a
122	   <contact> containing a <gruu>, it SHOULD use the gruu in preference
123	   to the corresponding <uri> when sending SIP requests to the contact.

125	   Subscribers that are unaware of this extension will, as required by
126	   [1], ignore the <gruu> element.

128	6.  Sample reginfo Document

130	   The following is an example registration information document
131	   including the new element:

133	      <?xml version="1.0"?>
134	          <reginfo xmlns="urn:ietf:params:xml:ns:reginfo"
135	              xmlns:gr="urn:ietf:params:xml:ns:gruuinfo"
136	              xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
137	              version="0" state="full">
138	            <registration aor="sip:user@example.com" id="as9"
139	                 state="active">
140	              <contact id="76" state="active" event="registered"
141	                 duration-registered="7322"
142	                 q="0.8">
143	                   <uri>sip:user@192.0.2.1</uri>
144	                   <unknown-param name="+sip.instance">
145	                      "<urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6>"
146	                   </unknown-param>
147	                   <gr:gruu>
148	                      sip:user@example.com;opaque=hha9s8d-999a
149	                   </gruu>
150	              </contact>
151	            </registration>
152	          </reginfo>

154	7.  Examples

156	   Note: In the following examples the SIP messages have been
157	   simplified, removing headers that are not pertinent to the example.
158	   The conventions of [7] are used to describe representation of long
159	   message lines.

161	7.1.  Example: Welcome Notice

163	   Consider the Welcome Notices example in [1].  When the application
164	   server receives a notification of a new registration containing the
165	   reginfo shown in Section 6 it should address messages using the
166	   contained GRUU as follows:

168	      MESSAGE sip:user@example.com;opaque=hha9s8d-999a SIP/2.0
169	      To: <sip:user@example.com>
170	      From: "SIPland Notifier" <sip:notifier@example.com>
171	      Content-Type: text/plain
172	      Content-Length: ...

174	      Welcome to SIPland!
175	      Blah, blah, blah.

177	7.2.  Example: Implicit Registration

179	   In an 3GPP IMS setting, a UA may send a single register message,
180	   requesting assignment of a gruu, as follows:

182	      REGISTER sip:example.net SIP/2.0
183	      From: <sip:user_aor_1@example.net>;tag=5ab4
184	      To: <sip:user_aor_1@example.net>
185	      Contact: <sip:ua.example.com>
186	        ;expires=3600
187	        ;+sip.instance="<urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6>"
188	      Supported: path, gruu
189	      Content-Length: 0

191	   The response reports success of the registration and returns the GRUU
192	   assigned for the combination of AOR, Instance ID, and Contact.  It
193	   also indicates (via the P-Associated-URI header [5]) that there are
194	   two other associated AORs that may have been implicitly registered
195	   using the same contact.  But each of those implicitly registered AORs
196	   will have had a unique GRUU assigned, and there is no way defined to
197	   report that assignment in the response.

199	      SIP/2.0 200 OK
200	      From: <sip:user_aor_1@example.net>;tag=5ab4
201	      To: <sip:user_aor_1@example.net>;tag=373392
202	      Path: <sip:proxy.example.net;lr>
203	      Service-Route: <sip:proxy.example.net;lr>
204	      Contact: <sip:ua.example.com>
205	        ;expires=3600
206	        ;+sip.instance="<urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6>"
207	        ;gruu="sip:user_aor_1@example.net;opaque=hha9s8d-999a"
208	      P-Associated-URI: <sip:user_aor_2@example.net>,
209	        <sip:+358504821437@example.net;user=phone>
210	      Content-Length: 0

212	   The UA then subscribes to the 'reg' event package as follows:

214	      SUBSCRIBE sip:user_aor_1@example.net SIP/2.0
215	      From: <sip:user_aor_1@example.net>;tag=27182
216	      To: <sip:user_aor_1@example.net>
217	      Route: <sip:proxy.example.net;lr>
218	      Event: reg
219	      Expires: 3600
220	      Accept: application/reginfo+xml
221	      Contact: <sip:user_aor_1@example.net;opaque=hha9s8d-999a>
222	      Content-Length: 0

224	   (The successful response to the subscription is not shown.)  Once the
225	   subscription is established an initial notification is sent giving
226	   registration status.  In IMS deployments the response includes, in
227	   addition to the status for the requested URI, the status for the
228	   other associated URIs.

230	      NOTIFY sip:user_aor_1@example.net;opaque=hha9s8d-999a SIP/2.0
231	      From: <sip:user_aor_1@example.net>;tag=27182
232	      To: <sip:user_aor_1@example.net>;tag=262281
233	      Subscription-State: active;expires=3600
234	      Event: reg
235	      Content-Type: application/reginfo+xml
236	      Contact: <sip:registrar.example.net>
237	      Content-Length: (...)

239	      <?xml version="1.0"?>
240	          <reginfo xmlns="urn:ietf:params:xml:ns:reginfo"
241	              xmlns:gr="urn:ietf:params:xml:ns:gruuinfo"
242	              xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
243	              version="1" state="full">
244	            <registration aor="sip:user_aor_1@example.net" id="a7"
245	                 state="active">
246	              <contact id="92" state="active" event="registered"
247	                 duration-registered="1" expires="3599">
248	                   <uri>
249	                      sip:ua.example.com
250	                   </uri>
251	                   <unknown-param name="+sip.instance">
252	                      "<urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6>"
253	                   </unknown-param>
254	      <allOneLine>
255	                   <gr:gruu>sip:user_aor_1@example.net
256	      ;opaque=hha9s8d-999a</gruu>
257	      </allOneLine>
258	              </contact>
259	            </registration>
260	            <registration aor="sip:user_aor_2@example.net" id="a8"
261	                 state="active">
262	              <contact id="93" state="active" event="created"
263	                 duration-registered="1" expires="3599">
264	                   <uri>
265	                      sip:ua.example.com
266	                   </uri>
267	                   <unknown-param name="+sip.instance">
268	                      "<urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6>"
269	                   </unknown-param>
270	      <allOneLine>
271	                   <gr:gruu>sip:user_aor_2@example.net
272	      ;opaque=hha9s8d-999b</gruu>
273	      </allOneLine>
274	              </contact>
275	            </registration>
276	            <registration
277	                 aor="sip:+358504821437@example.net;user=phone"
278	                 id="a9"
279	                 state="active">
280	              <contact id="94" state="active" event="created"
281	                 duration-registered="1" expires="3599">
282	                   <uri>
283	                      sip:ua.example.com
284	                   </uri>
285	                   <unknown-param name="+sip.instance">
286	                      "<urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6>"
287	                   </unknown-param>
288	      <allOneLine>
289	                   <gr:gruu>sip:+358504821437@example.net;user=phone
290	      ;opaque=hha9s8d-999c</gruu>
291	      </allOneLine>
292	              </contact>
293	            </registration>
294	          </reginfo>

296	   The status indicates that the associated URIs all have the same
297	   contact registered.  It also includes the unique GRUU that has been
298	   assigned to each.  The UA may then retain those GRUUs for use when
299	   establishing dialogs using the corresponding AORs.

301	8.  XML Schema Definition

303	   A gruu document is an XML document that MUST be well-formed and
304	   SHOULD be valid.  Gruu documents MUST be based on XML 1.0 and MUST be
305	   encoded using UTF-8.  This specification makes use of XML namespaces
306	   for identifying gruu documents.  The namespace URI for elements
307	   defined for this purpose is a URN, using the namespace identifier
308	   'ietf'.  This URN is:
309	      urn:ietf:params:xml:ns:gruuinfo

311	   BEGIN
312	   <?xml version="1.0" encoding="UTF-8"?>
313	   <xs:schema targetNamespace="urn:ietf:params:xml:ns:gruuinfo"
314	     elementFormDefault="qualified"
315	     attributeFormDefault="unqualified"
316	     xmlns:xs="http://www.w3.org/2001/XMLSchema"
317	     xmlns:tns="urn:ietf:params:xml:ns:gruuinfo">
318	     <xs:element name="gruu" type="xs:anyURI"/>
319	   </xs:schema>
320	   END

322	9.  IANA Considerations

324	   There are two IANA considerations associated with this specification.

326	9.1.  URN Sub-Namespace Registration

328	   This section registers a new XML namespace, per the guidelines in
329	   [3].

331	   URI: The URI for this namespace is urn:ietf:params:xml:ns:gruuinfo

333	   Registrant Contact: IETF, SIPPING working group, <sipping@ietf.org>,
334	   Paul Kyzivat <pkyzivat@cisco.com>

336	   XML:

338	         BEGIN
339	         <?xml version="1.0"?>
340	         <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
341	                   "http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">
342	         <html xmlns="http://www.w3.org/1999/xhtml">
343	         <head>
344	           <meta http-equiv="content-type"
345	              content="text/html;charset=iso-8859-1"/>
346	           <title>Reg Information GRUU Extension Namespace</title>
347	         </head>
348	         <body>
349	            <h1>Namespace for Reg Information GRUU Extension</h1>
350	            <h2>urn:ietf:params:xml:ns:gruuinfo</h2>
351	            <p>See <a href="[URL of published RFC]">RFCXXXX [[NOTE
352	      TO RFC-EDITOR/IANA: Please replace XXXX with the RFC Number of
353	      this specification]]</a>.</p>
354	          </body>
355	         </html>
356	         END

358	9.2.  XML Schema Registration

360	   This section registers an XML schema per the procedures in [3].

362	   URI: urn:ietf:params:xml:schema:gruuinfo.

364	   Registrant Contact: IETF, SIPPING working group, <sipping@ietf.org>,
365	   Paul Kyzivat <pkyzivat@cisco.com>

367	   The XML for this schema can be found in Section 8.

369	10.  Security Considerations

371	   Security considerations for the registration event package is
372	   discussed in RFC 3680 [1], and those considerations apply here.

374	   The addition of gruu information does not impact security negatively
375	   because the gruu is less sensitive than the contact URI itself.

377	11.  Acknowledgements

379	   The author would like to thank Jonathan Rosenberg for encouraging
380	   this draft.

382	12.  References
383	12.1.  Normative References

385	   [1]  Rosenberg, J., "A Session Initiation Protocol (SIP) Event
386	        Package for Registrations", RFC 3680, March 2004.

388	   [2]  Rosenberg, J., "Obtaining and Using Globally Routable User Agent
389	        (UA) URIs (GRUU) in the  Session Initiation Protocol (SIP)",
390	        draft-ietf-sip-gruu-06 (work in progress), October 2005.

392	   [3]  Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
393	        January 2004.

395	12.2.  Informative References

397	   [4]  Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, A.,
398	        Peterson, J., Sparks, R., Handley, M., and E. Schooler, "SIP:
399	        Session Initiation Protocol", RFC 3261, June 2002.

401	   [5]  Garcia-Martin, M., Henrikson, E., and D. Mills, "Private Header
402	        (P-Header) Extensions to the Session Initiation Protocol (SIP)
403	        for the 3rd-Generation Partnership Project (3GPP)", RFC 3455,
404	        January 2003.

406	   [6]  Rosenberg, J., Schulzrinne, H., and P. Kyzivat, "Indicating User
407	        Agent Capabilities in the Session Initiation Protocol (SIP)",
408	        RFC 3840, August 2004.

410	   [7]  Sparks, R., "Session Initiation Protocol Torture Test Messages",
411	        draft-ietf-sipping-torture-tests-09 (work in progress),
412	        November 2005.

414	Author's Address

416	   Paul H. Kyzivat
417	   Cisco Systems, Inc.
418	   1414 Massachusetts Avenue
419	   Boxborough, MA  01719
420	   USA

422	   Email: pkyzivat@cisco.com

424	Intellectual Property Statement

426	   The IETF takes no position regarding the validity or scope of any
427	   Intellectual Property Rights or other rights that might be claimed to
428	   pertain to the implementation or use of the technology described in
429	   this document or the extent to which any license under such rights
430	   might or might not be available; nor does it represent that it has
431	   made any independent effort to identify any such rights.  Information
432	   on the procedures with respect to rights in RFC documents can be
433	   found in BCP 78 and BCP 79.

435	   Copies of IPR disclosures made to the IETF Secretariat and any
436	   assurances of licenses to be made available, or the result of an
437	   attempt made to obtain a general license or permission for the use of
438	   such proprietary rights by implementers or users of this
439	   specification can be obtained from the IETF on-line IPR repository at
440	   http://www.ietf.org/ipr.

442	   The IETF invites any interested party to bring to its attention any
443	   copyrights, patents or patent applications, or other proprietary
444	   rights that may cover technology that may be required to implement
445	   this standard.  Please address the information to the IETF at
446	   ietf-ipr@ietf.org.

448	Disclaimer of Validity

450	   This document and the information contained herein are provided on an
451	   "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
452	   OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
453	   ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
454	   INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
455	   INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
456	   WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

458	Copyright Statement

460	   Copyright (C) The Internet Society (2005).  This document is subject
461	   to the rights, licenses and restrictions contained in BCP 78, and
462	   except as set forth therein, the authors retain all their rights.

464	Acknowledgment

466	   Funding for the RFC Editor function is currently provided by the
467	   Internet Society.