Internet Engineering Task Force SIP WG Internet Draft G. Camarillo Ericsson draft-camarillo-sip-parameter-registry-00.txt December 19, 2002 Expires: June 2003 The Internet Assigned Number Authority Header Field and Universal Resource Identifier Parameter Registry for the Session Initiation Protocol STATUS OF THIS MEMO This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026. 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 To view the list Internet-Draft Shadow Directories, see http://www.ietf.org/shadow.html. Abstract This document creates an IANA registry for SIP header field, SIP URI and SIPS URI parameters. It also lists the already existing parameters to be used as initial values for that registry. G. Camarillo [Page 1] Internet Draft SIP December 19, 2002 Table of Contents 1 Introduction ........................................ 3 2 Use of the Registry ................................. 3 3 IANA Considerations ................................. 3 3.1 Header Field Parameters Sub-Registry ................ 3 3.2 SIP and SIPS URI Parameters Sub-Registry ............ 3 4 TODO list ........................................... 4 5 Security Considerations ............................. 5 6 Acknowledgements .................................... 5 7 Authors' Addresses .................................. 5 8 Normative References ................................ 5 G. Camarillo [Page 2] Internet Draft SIP December 19, 2002 1 Introduction RFC3261 [1] allows new header field, SIP URI and SIPS URI parameters to be defined. However, RFC3261 omitted an IANA registry for them. This document creates such a registry. 2 Use of the Registry Any RFC that defines a new header field, SIP URI or SIPS URI parameter, MUST include an IANA registration for it, as described below. Note that this includes RFCs that define parameters for P- headers. 3 IANA Considerations Section 27 of RFC 3261 [1] creates an IANA registry for method names, header field names, warning codes, status codes, and option tags. This specification instructs the IANA to create two new sub- registries under http://www.iana.org/assignments/sip-parameters: o Header Field Parameters o SIP/SIPS URI Parameters 3.1 Header Field Parameters Sub-Registry The majority of the SIP header fields can be extended by defining new parameters. New SIP header field parameters are registered by the IANA when they are published in an RFC. The IANA considerations section of the RFC MUST include the following information, which appears in the IANA registry along with the RFC number of the publication. o Name of the parameter. o Header fields in which the parameter can appear. Parameters that can appear in different header fields MAY have the same name. However, parameters that can appear in the same header field MUST have different names. Table 1 contains the initial values for this sub-registry. 3.2 SIP and SIPS URI Parameters Sub-Registry New SIP and SIPS URI parameters are registered by the IANA when they are published in standards track RFCs. The IANA considerations G. Camarillo [Page 3] Internet Draft SIP December 19, 2002 Parameter Name Header Fields Reference ______________________________________________________________ ttl Via RFC 3261 maddr Via RFC 3261 q Accept, Accept-Encoding, RFC 3261 Accept-Language, Contact purpose Call-Info RFC 3261 expires Contact RFC 3261 handling Content-Disposition RFC 3261 tag From, To RFC 3261 duration Retry-After RFC 3261 received Via RFC 3261 branch Via RFC 3261 comp Via [compression] rport Via [symmetric-response] Table 1: IANA SIP header field parameter sub-registry section of the RFC MUST include the following information, which appears in the IANA registry along with the RFC number of the publication. o Name of the parameter. Table 2 contains the initial values for this sub-registry. Parameter Name Reference _____________________________ transport RFC 3261 user RFC 3261 method RFC 3261 ttl RFC 3261 maddr RFC 3261 lr RFC 3261 comp [compression] Table 2: IANA SIP and SIPS URI parameter sub-registry 4 TODO list Add media feature tags from draft-ietf-sip-callerprefs-07.txt. That draft will be revised next week, and based on that revision we will add the parameters to the registry. We may have to define a prefix for some of them. G. Camarillo [Page 4] Internet Draft SIP December 19, 2002 Check timeframe of draft-garcia-sipping-3gpp-p-headers-02.txt. It will probably have to define its own entries in this registry. Check whether there are more specs that define parameters in addition to RFC 3261, draft-ietf-sip-compression-02.txt, draft-ietf-sip- symmetric-response-00.txt, draft-ietf-sip-callerprefs-07.txt and draft-garcia-sipping-3gpp-p-headers-02.txt. 5 Security Considerations There are no security considerations associated to this document. 6 Acknowledgements Jonathan Rosenberg provided useful comments. 7 Authors' Addresses Gonzalo Camarillo Ericsson Advanced Signalling Research Lab. FIN-02420 Jorvas Finland electronic mail: Gonzalo.Camarillo@ericsson.com 8 Normative References [1] J. Rosenberg, H. Schulzrinne, G. Camarillo, A. Johnston, J. Peterson, R. Sparks, M. Handley, and E. Schooler, "SIP: session initiation protocol," RFC 3261, Internet Engineering Task Force, June 2002. The IETF takes no position regarding the validity or scope of any intellectual property 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; neither does it represent that it has made any effort to identify any such rights. Information on the IETF's procedures with respect to rights in standards-track and standards-related documentation can be found in BCP-11. Copies of claims of rights made available for publication 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 implementors or users of this specification can G. Camarillo [Page 5] Internet Draft SIP December 19, 2002 be obtained from the IETF Secretariat. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to practice this standard. Please address the information to the IETF Executive Director. Full Copyright Statement Copyright (c) The Internet Society (2002). All Rights Reserved. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English. The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns. This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS 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. G. Camarillo [Page 6]