[Docs] [txt|pdf] [Tracker] [Email] [Diff1] [Diff2] [Nits]

Versions: 00 01

Internet Engineering Task Force                                   SIP WG
Internet Draft                                              G. Camarillo
                                                                Ericsson
draft-camarillo-sip-parameter-registry-01.txt
June 17, 2003
Expires: December 2003


        The Internet Assigned Number Authority Header Field
       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
   parameters. It also lists the already existing parameters to be used
   as initial values for that registry.














G. Camarillo                                                  [Page 1]

Internet Draft                    SIP                      June 17, 2003





                           Table of Contents



   1          Introduction ........................................    3
   2          Use of the Registry .................................    3
   3          IANA Considerations .................................    3
   3.1        Header Field Parameters Sub-Registry ................    3
   4          Security Considerations .............................    4
   5          Acknowledgements ....................................    4
   6          Authors' Addresses ..................................    4
   7          Normative References ................................    5




































G. Camarillo                                                  [Page 2]

Internet Draft                    SIP                      June 17, 2003


1 Introduction

   RFC3261 [1] allows new header field parameters to be defined.
   However, RFC3261 omitted an IANA registry for them. This document
   creates such a registry.

2 Use of the Registry

   Both RFC defined and proprietary header field parameters MUST be
   registered with IANA as described below.

        Note that this includes header field 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 a new sub-
   registry under http://www.iana.org/assignments/sip-parameters:

        o Header Field 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 registering a new parameter for a header field, the
   following information MUST be provided.

        o Header field in which the parameter can appear.

        o Name of the parameter.

        o For proprietary parameters, a brief description of its
          semantics.

        o A reference to a further description, if available. For
          example, (in order of preference) an RFC, a published paper, a
          patent filing, a technical report, documented source code or a
          computer manual.

        o For proprietary parameters, contact information (postal and
          email address).

   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.



G. Camarillo                                                  [Page 3]

Internet Draft                    SIP                      June 17, 2003


   Table 1 contains the initial values for this sub-registry.


 Header Field                   Parameter Name   Description   Reference
 ________________________________________________________________________
 Accept                         q                              RFC 3261
 Accept-Encoding                q                              RFC 3261
 Accept-Language                q                              RFC 3261
 Call-Info                      purpose                        RFC 3261
 Contact                        expires                        RFC 3261
 Contact                        q                              RFC 3261
 Content-Disposition            handling                       RFC 3261
 From                           tag                            RFC 3261
 P-Charging-Function-Addresses  ccf                            RFC 3455
 P-Charging-Function-Addresses  ecf                            RFC 3455
 P-Charging-Vector              icid-value                     RFC 3455
 P-Charging-Vector              icid-generated-at              RFC 3455
 P-Charging-Vector              orig-ioi                       RFC 3455
 P-Charging-Vector              term-ioi                       RFC 3455
 Retry-After                    duration                       RFC 3261
 To                             tag                            RFC 3261
 Via                            branch                         RFC 3261
 Via                            comp                           RFC 3486
 Via                            maddr                          RFC 3261
 Via                            received                       RFC 3261
 Via                            rport                       [symmetric]
 Via                            ttl                            RFC 3261


   Table 1: IANA SIP header field parameter sub-registry


4 Security Considerations

   There are no security considerations associated to this document.

5 Acknowledgements

   Jonathan Rosenberg, Henning Schulzrinne, Rohan Mahy and Dean Willis
   provided useful comments.

6 Authors' Addresses

   Gonzalo Camarillo
   Ericsson
   Advanced Signalling Research Lab.
   FIN-02420 Jorvas
   Finland
   electronic mail:  Gonzalo.Camarillo@ericsson.com


G. Camarillo                                                  [Page 4]

Internet Draft                    SIP                      June 17, 2003


7 Normative References

   [1] J. Rosenberg, H. Schulzrinne, G. Camarillo, A. R. 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
   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 (2003). 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.



G. Camarillo                                                  [Page 5]

Internet Draft                    SIP                      June 17, 2003


   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]


Html markup produced by rfcmarkup 1.107, available from http://tools.ietf.org/tools/rfcmarkup/