draft-ietf-sipping-pending-additions-01.txt   draft-ietf-sipping-pending-additions-02.txt 
SIPPING G. Camarillo SIPPING G. Camarillo
Internet-Draft Ericsson Internet-Draft Ericsson
Expires: May 29, 2007 November 25, 2006 Intended status: Standards Track April 2, 2007
Expires: October 4, 2007
The Session Initiation Protocol (SIP) Pending Additions Event Package The Session Initiation Protocol (SIP) Pending Additions Event Package
draft-ietf-sipping-pending-additions-01.txt draft-ietf-sipping-pending-additions-02.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 32 skipping to change at page 1, line 34
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on May 29, 2007. This Internet-Draft will expire on October 4, 2007.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2006). Copyright (C) The IETF Trust (2007).
Abstract Abstract
This document defines the SIP Pending Additions event package. This This document defines the SIP Pending Additions event package. This
event package is used by SIP relays to inform user agents about the event package is used by SIP relays to inform user agents about the
consent-related status of the entries to be added to a resource list. consent-related status of the entries to be added to a resource list.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Overview of Operation . . . . . . . . . . . . . . . . . . . . 3 3. Overview of Operation . . . . . . . . . . . . . . . . . . . . 3
4. XML Schema Definition . . . . . . . . . . . . . . . . . . . . 4 4. XML Schema Definition . . . . . . . . . . . . . . . . . . . . 3
5. Pending Additions Event Package Definition . . . . . . . . . . 5 5. Pending Additions Event Package Definition . . . . . . . . . . 5
5.1. Event Package Name . . . . . . . . . . . . . . . . . . . . 5 5.1. Event Package Name . . . . . . . . . . . . . . . . . . . . 5
5.1.1. Event Package Parameters . . . . . . . . . . . . . . . 5 5.1.1. Event Package Parameters . . . . . . . . . . . . . . . 5
5.1.2. SUBSCRIBE Bodies . . . . . . . . . . . . . . . . . . . 5 5.1.2. SUBSCRIBE Bodies . . . . . . . . . . . . . . . . . . . 5
5.1.3. Subscription Duration . . . . . . . . . . . . . . . . 5 5.1.3. Subscription Duration . . . . . . . . . . . . . . . . 5
5.1.4. NOTIFY Bodies . . . . . . . . . . . . . . . . . . . . 6 5.1.4. NOTIFY Bodies . . . . . . . . . . . . . . . . . . . . 5
5.1.5. Notifier Processing of SUBSCRIBE Requests . . . . . . 6 5.1.5. Notifier Processing of SUBSCRIBE Requests . . . . . . 6
5.1.6. Notifier Generation of NOTIFY Requests . . . . . . . . 6 5.1.6. Notifier Generation of NOTIFY Requests . . . . . . . . 6
5.1.7. Subscriber Processing of NOTIFY Requests . . . . . . . 6 5.1.7. Subscriber Processing of NOTIFY Requests . . . . . . . 6
5.1.8. Handling of Forked Requests . . . . . . . . . . . . . 6 5.1.8. Handling of Forked Requests . . . . . . . . . . . . . 6
5.1.9. Rate of Notifications . . . . . . . . . . . . . . . . 7 5.1.9. Rate of Notifications . . . . . . . . . . . . . . . . 7
5.1.10. State Agents . . . . . . . . . . . . . . . . . . . . . 7 5.1.10. State Agents . . . . . . . . . . . . . . . . . . . . . 7
5.1.11. Example . . . . . . . . . . . . . . . . . . . . . . . 7 5.1.11. Example . . . . . . . . . . . . . . . . . . . . . . . 7
6. Usage of the Pending Additions Event Package with the XCAP 6. Usage of the Pending Additions Event Package with the XCAP
Diff Format . . . . . . . . . . . . . . . . . . . . . . . . . 8 Diff Format . . . . . . . . . . . . . . . . . . . . . . . . . 7
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
7.1. SIP Event Package Registration . . . . . . . . . . . . . . 9 7.1. SIP Event Package Registration . . . . . . . . . . . . . . 9
7.2. URN Sub-Namespace Registration . . . . . . . . . . . . . . 9 7.2. URN Sub-Namespace Registration . . . . . . . . . . . . . . 9
7.3. XML Schema Registration . . . . . . . . . . . . . . . . . 10 7.3. XML Schema Registration . . . . . . . . . . . . . . . . . 10
8. Security Considerations . . . . . . . . . . . . . . . . . . . 10 8. Security Considerations . . . . . . . . . . . . . . . . . . . 10
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 10 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 10
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11
10.1. Normative References . . . . . . . . . . . . . . . . . . . 11 10.1. Normative References . . . . . . . . . . . . . . . . . . . 11
10.2. Informative References . . . . . . . . . . . . . . . . . . 11 10.2. Informative References . . . . . . . . . . . . . . . . . . 11
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 12 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 11
Intellectual Property and Copyright Statements . . . . . . . . . . 13 Intellectual Property and Copyright Statements . . . . . . . . . . 12
1. Introduction 1. Introduction
The framework for consent-based communications in SIP [8] identifies The framework for consent-based communications in SIP [8] identifies
the need for users manipulating the translation logic at a relay the need for users manipulating the translation logic at a relay
(e.g., adding a new recipient) to be informed about the consent- (e.g., adding a new recipient) to be informed about the consent-
related status of the recipients of a given translation. That is, related status of the recipients of a given translation. That is,
the user manipulating the translation logic needs to know which the user manipulating the translation logic needs to know which
recipients have given the relay permission to send them SIP requests. recipients have given the relay permission to send them SIP requests.
This document defines a SIP event package whereby user agents can This document defines a SIP event package whereby user agents can
subscribe to the consent-related state of the resources that are subscribe to the consent-related state of the resources that are
being added to a resource list that defines a translation. being added to a resource list that defines a translation.
2. Terminology 2. Terminology
In this document, the key words "MUST", "MUST NOT", "REQUIRED", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
RECOMMENDED", "MAY", and "OPTIONAL" are to be interpreted as document are to be interpreted as described in RFC 2119 [1].
described in BCP 14, RFC 2119 [1] and indicate requirement levels for
compliant implementations.
Relay: Any SIP server, be it a proxy, B2BUA (Back-to-Back User Relay: Any SIP server, be it a proxy, B2BUA (Back-to-Back User
Agent), or some hybrid, that receives a request, translates its Agent), or some hybrid, that receives a request, translates its
Request-URI into one or more next-hop URIs (i.e., recipient URIs), Request-URI into one or more next-hop URIs (i.e., recipient URIs),
and delivers the request to those URIs. and delivers the request to those URIs.
3. Overview of Operation 3. Overview of Operation
A user agent subscribes to a relay using the Pending Additions event A user agent subscribes to a relay using the Pending Additions event
package. NOTIFY requests within this event package can carry an XML package. NOTIFY requests within this event package can carry an XML
skipping to change at page 11, line 21 skipping to change at page 11, line 21
Peterson, J., Sparks, R., Handley, M., and E. Schooler, "SIP: Peterson, J., Sparks, R., Handley, M., and E. Schooler, "SIP:
Session Initiation Protocol", RFC 3261, June 2002. Session Initiation Protocol", RFC 3261, June 2002.
[3] Roach, A., "Session Initiation Protocol (SIP)-Specific Event [3] Roach, A., "Session Initiation Protocol (SIP)-Specific Event
Notification", RFC 3265, June 2002. Notification", RFC 3265, June 2002.
[4] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [4] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
January 2004. January 2004.
[5] Rosenberg, J., "The Extensible Markup Language (XML) [5] Rosenberg, J., "The Extensible Markup Language (XML)
Configuration Access Protocol (XCAP)", draft-ietf-simple-xcap-11 Configuration Access Protocol (XCAP)", draft-ietf-simple-xcap-12
(work in progress), May 2006. (work in progress), October 2006.
[6] Rosenberg, J., "Extensible Markup Language (XML) Formats for [6] Rosenberg, J., "Extensible Markup Language (XML) Formats for
Representing Resource Lists", Representing Resource Lists",
draft-ietf-simple-xcap-list-usage-05 (work in progress), draft-ietf-simple-xcap-list-usage-05 (work in progress),
February 2005. February 2005.
[7] Rosenberg, J., "An Extensible Markup Language (XML) Document [7] Rosenberg, J., "An Extensible Markup Language (XML) Document
Format for Indicating A Change in XML Configuration Access Format for Indicating A Change in XML Configuration Access
Protocol (XCAP) Resources", draft-ietf-simple-xcap-diff-03 (work Protocol (XCAP) Resources", draft-ietf-simple-xcap-diff-04 (work
in progress), March 2006. in progress), October 2006.
[8] Rosenberg, J., Camarillo, G., and D. Willis, "A Framework for [8] Rosenberg, J., "A Framework for Consent-Based Communications in
Consent-Based Communications in the Session Initiation Protocol the Session Initiation Protocol (SIP)",
(SIP)", draft-ietf-sip-consent-framework-00 (work in progress), draft-ietf-sip-consent-framework-01 (work in progress),
September 2006. November 2006.
10.2. Informative References 10.2. Informative References
Author's Address Author's Address
Gonzalo Camarillo Gonzalo Camarillo
Ericsson Ericsson
Hirsalantie 11 Hirsalantie 11
Jorvas 02420 Jorvas 02420
Finland Finland
Email: Gonzalo.Camarillo@ericsson.com Email: Gonzalo.Camarillo@ericsson.com
Intellectual Property Statement Full Copyright Statement
Copyright (C) The IETF Trust (2007).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
skipping to change at page 13, line 29 skipping to change at page 12, line 45
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at this standard. Please address the information to the IETF at
ietf-ipr@ietf.org. ietf-ipr@ietf.org.
Disclaimer of Validity
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement
Copyright (C) The Internet Society (2006). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights.
Acknowledgment Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is provided by the IETF
Internet Society. Administrative Support Activity (IASA).
 End of changes. 16 change blocks. 
40 lines changed or deleted 40 lines changed or added

This html diff was produced by rfcdiff 1.33. The latest version is available from http://tools.ietf.org/tools/rfcdiff/