RFC 3427
Change Process for the Session Initiation Protocol (SIP), December 2002
- File formats:
- Status:
- BEST CURRENT PRACTICE
- Obsoleted by:
- RFC 5727
- Updated by:
- RFC 3968, RFC 3969
- Authors:
- A. Mankin
S. Bradner
R. Mahy
D. Willis
J. Ott
B. Rosen - Stream:
- [Legacy]
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC3427
Discuss this RFC: Send questions or comments to the mailing list iesg@ietf.org
Other actions: Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 3427
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. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.