RFC 3427 (rfc3427) - Page 1 of 12
Change Process for the Session Initiation Protocol (SIP)
Alternative Format: Original Text Document
Network Working Group A. Mankin
Request for Comments: 3427 Bell Labs, Lucent Corporation
BCP: 67 S. Bradner
Category: Best Current Practice Harvard University
R. Mahy
Cisco
D. Willis
dynamicsoft
J. Ott
ipDialog / Uni Bremen TZI
B. Rosen
Marconi
December 2002
Change Process 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 (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.
1. Terminology
In this document, the key words "MAY", "MUST, "MUST NOT", "SHOULD",
and "SHOULD NOT", are to be interpreted as described in Keywords [1].
Mankin, et. al. Best Current Practice