SIPPING G. Camarillo Internet-Draft Ericsson Expires: August 29, 2006 February 25, 2006 Session Initiation Protocol (SIP) Registration Event Package Extension for Consent-Based Communications draft-camarillo-sipping-consent-reg-event-00.txt Status of this Memo By submitting this Internet-Draft, each author represents that any 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 aware will be disclosed, in accordance with Section 6 of BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. This Internet-Draft will expire on August 29, 2006. Copyright Notice Copyright (C) The Internet Society (2006). Abstract This document defines an extension to the SIP registration event package for communicating whether or not a registrar has obtained permission to perform a translation that was set up through a registration. This extension is used by registrars implementing the framework for consent-based communications in SIP. Camarillo Expires August 29, 2006 [Page 1] Internet-Draft Reg Event Consent Extension February 2006 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Description . . . . . . . . . . . . . . . . . . . . . . . . . . 3 4. Notifier Processing of SUBSCRIBE Requests . . . . . . . . . . . 3 5. Notifier Generation of NOTIFY Requests . . . . . . . . . . . . 3 6. Subscriber Processing of NOTIFY Requests . . . . . . . . . . . 4 7. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 8. XML Schema Definition . . . . . . . . . . . . . . . . . . . . . 4 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5 9.1. URN Sub-Namespace Registration . . . . . . . . . . . . . . 5 9.2. XML Schema Registration . . . . . . . . . . . . . . . . . . 6 10. Security Considerations . . . . . . . . . . . . . . . . . . . . 6 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 7 11.1. Normative References . . . . . . . . . . . . . . . . . . . 7 11.2. Informative References . . . . . . . . . . . . . . . . . . 7 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 8 Intellectual Property and Copyright Statements . . . . . . . . . . 9 Camarillo Expires August 29, 2006 [Page 2] Internet-Draft Reg Event Consent Extension February 2006 1. Introduction The framework for consent-based communications in SIP [5] identifies the need for registrars to inform user agents about the consent- related status of their registrations. That is, user agents need to know whether or not their registrar has obtained permission to perform a particular translation that was set up through a registration. User agents are kept informed about the status of their registrations using the SIP [2] registration event package [3]. This event package has provision for including extension elements within the element. This document defines a new element called that may be used to deliver the consent-related status of a registration. 2. Terminology In this document, the key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" are to be interpreted as described in BCP 14, RFC 2119 [1] and indicate requirement levels for compliant implementations. 3. Description A new element is defined which contains the consent- related status of a registration. This element can take the following values: 'pending', 'granted', or 'denied'. This optional element is included within the body of a NOTIFY for the "reg" event package when the framework for consent-communications in SIP is used. The contact URI and the consent-related status are then both available to the watcher. 4. Notifier Processing of SUBSCRIBE Requests Unchanged from RFC 3680 [3]. 5. Notifier Generation of NOTIFY Requests A notifier for the "reg" event package [3] SHOULD include the element when the framework for consent-based communications in SIP is used. When present, the Camarillo Expires August 29, 2006 [Page 3] Internet-Draft Reg Event Consent Extension February 2006 element MUST be positioned as an instance of the element within the element. 6. Subscriber Processing of NOTIFY Requests Subscribers receive information about the consent-related status of registrations in "reg" event notifications with elements containing elements. Subscribers that are unaware of this extension will, as required by [3], ignore the element. 7. Example The following is an example registration information document including the new element: sip:user@192.0.2.1 pending 8. XML Schema Definition A consent-status document is an XML document that MUST be well-formed and SHOULD be valid. Consent-status documents MUST be based on XML 1.0 and MUST be encoded using UTF-8. This specification makes use of XML namespaces for identifying consent-status documents. The namespace URI for elements defined for this purpose is a URN, using the namespace identifier 'ietf'. This URN is: Camarillo Expires August 29, 2006 [Page 4] Internet-Draft Reg Event Consent Extension February 2006 urn:ietf:params:xml:ns:consent-status BEGIN END 9. IANA Considerations There are two IANA considerations associated with this specification. 9.1. URN Sub-Namespace Registration This section registers a new XML namespace, per the guidelines in [4]. URI: The URI for this namespace is urn:ietf:params:xml:ns:consent-status Registrant Contact: IETF, SIPPING working group, , Gonzalo Camarillo Camarillo Expires August 29, 2006 [Page 5] Internet-Draft Reg Event Consent Extension February 2006 XML: BEGIN Consent-related Status Extension Namespace

Namespace for Consent-related Status Information Extension

urn:ietf:params:xml:ns:consent-status

See RFCXXXX [[NOTE TO RFC-EDITOR/IANA: Please replace XXXX with the RFC Number of this specification]].

END 9.2. XML Schema Registration This section registers an XML schema per the procedures in [4]. URI: urn:ietf:params:xml:schema:consent-status. Registrant Contact: IETF, SIPPING working group, , Gonzalo Camarillo The XML for this schema can be found in Section 8. 10. Security Considerations Security considerations for the registration event package are discussed in RFC 3680 [3], and those considerations apply here. The addition of consent-related information does not impact security negatively because that information is less sensitive than the contact URI itself. 11. References Camarillo Expires August 29, 2006 [Page 6] Internet-Draft Reg Event Consent Extension February 2006 11.1. Normative References [1] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [2] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, A., Peterson, J., Sparks, R., Handley, M., and E. Schooler, "SIP: Session Initiation Protocol", RFC 3261, June 2002. [3] Rosenberg, J., "A Session Initiation Protocol (SIP) Event Package for Registrations", RFC 3680, March 2004. [4] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, January 2004. [5] Rosenberg, J., "A Framework for Consent-Based Communications in the Session Initiation Protocol (SIP)", draft-ietf-sipping-consent-framework-03 (work in progress), October 2005. 11.2. Informative References Camarillo Expires August 29, 2006 [Page 7] Internet-Draft Reg Event Consent Extension February 2006 Author's Address Gonzalo Camarillo Ericsson Hirsalantie 11 Jorvas 02420 Finland Email: Gonzalo.Camarillo@ericsson.com Camarillo Expires August 29, 2006 [Page 8] Internet-Draft Reg Event Consent Extension February 2006 Intellectual Property Statement The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in 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 made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79. Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at 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 Funding for the RFC Editor function is currently provided by the Internet Society. Camarillo Expires August 29, 2006 [Page 9]