Browse Prior Art Database

The Internet Assigned Number Authority (IANA) Uniform Resource Identifier (URI) Parameter Registry for the Session Initiation Protocol (SIP) (RFC3969)

IP.com Disclosure Number: IPCOM000033612D
Original Publication Date: 2004-Dec-01
Included in the Prior Art Database: 2004-Dec-18
Document File: 7 page(s) / 12K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

G. Camarillo: AUTHOR

Abstract

This document creates an Internet Assigned Number Authority (IANA) registry for the Session Initiation Protocol (SIP) and SIPS Uniform Resource Identifier (URI) parameters, and their values. It also lists the already existing parameters to be used as initial values for that registry.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 23% of the total text.

Network Working Group                                       G. Camarillo

Request for Comments: 3969                                      Ericsson

Updates: 3427                                              December 2004

BCP: 99

Category: Best Current Practice

             The Internet Assigned Number Authority (IANA)

         Uniform Resource Identifier (URI) Parameter Registry

               for the Session Initiation Protocol (SIP)

Status of This Memo

   This document specifies an Internet Best Current Practices for the

   Internet Community, and requests discussion and suggestions for

   improvements.  Distribution of this memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (2004).

Abstract

   This document creates an Internet Assigned Number Authority (IANA)

   registry for the Session Initiation Protocol (SIP) and SIPS Uniform

   Resource Identifier (URI) parameters, and their values.  It also

   lists the already existing parameters to be used as initial values

   for that registry.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  2

   2.  Terminology. . . . . . . . . . . . . . . . . . . . . . . . . .  2

   3.  Use of the Registry. . . . . . . . . . . . . . . . . . . . . .  2

   4.  IANA Considerations. . . . . . . . . . . . . . . . . . . . . .  3

       4.1.  SIP and SIPS URI Parameters Sub-Registry . . . . . . . .  3

       4.2.  Registration Policy for SIP and SIPS URI Parameters. . .  4

   5.  Security Considerations. . . . . . . . . . . . . . . . . . . .  4

   6.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . .  4

   7.  Normative References . . . . . . . . . . . . . . . . . . . . .  5

       Author's Address . . . . . . . . . . . . . . . . . . . . . . .  5

       Full Copyright Statement . . . . . . . . . . . . . . . . . . .  6

Camarillo                Best Current Practice                  [Page 1]

RFC 3969          IANA URI Parameter Registry for SIP      December 2004

1.  Introduction

   RFC 3261 [1] allows new SIP URI and SIPS URI parameters, and new

   parameter values to be defined.  However, RFC 3261 omitted an IANA

   registry for them.  This document creates such a registry.

   RFC 3427 [2] documents the process to extend SIP.  This document

   updates RFC 3427 by specifying how to define and register new SIP and

   SIP URI parameters and their values.

2.  Terminology

   In this document, the key words "MUST", "MUST NOT", "REQUIRED",

   "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY",

   and "OPTIONAL" are to be interpreted as described in BCP 14, RFC 2119

   [3] and indicate requirement levels for compliant SIP

   implementation...