RFC - 3427

Change Process for the Session Initiation Protocol (SIP)

Original:	ftp://ftp.isi.edu/in-notes/rfc3427.txt
Authors:	A. Mankin [Bell Labs, Lucent Corporation], S. Bradner [Harvard University], R. Mahy [Cisco], D. Willis [dynamicsoft], J. Ott [ipDialog / Uni Bremen TZI], B. Rosen [Marconi]
Date:	December 2002
Category:	Best Current Practice [ BCP-67 ]

---

Updated by:
RFC-3969 [BCP 99]	The Internet Assigned Number Authority (IANA) Uniform Resource Identifier (URI) Parameter Registry for the Session Initiation Protocol (SIP)
RFC-3968 [BCP 98]	The Internet Assigned Number Authority (IANA) Header Field Parameter Registry for the Session Initiation Protocol (SIP)

Referred by:	14 RFC
Refers to:	5 RFC

---

Status

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 (2002). All Rights Reserved.

Abstract

This memo documents a process intended to apply architectural discipline to the future development of the Session Initiation Protocol (SIP). There have been concerns with regards to new SIP proposals. Specifically, that the addition of new SIP features can be damaging towards security and/or greatly increase the complexity of the protocol. The Transport Area directors, along with the SIP and Session Initiation Proposal Investigation (SIPPING) working group chairs, have provided suggestions for SIP modifications and extensions.

---