Technology and engineering · 2002
RFC 3427: Change Process for the Session Initiation Protocol (SIP)
by A. Mankin, S. Bradner, R. Mahy et al.
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.
Anyone can see what's on the shelves. Open a book with a free account, and stay in touch with its book club.
- First published
- 2002
- Status
- Best Current Practice
- Pages
- 12
- Obsoleted by
- RFC 5727
- Copyright
- ✓ Free to read · Copied in full, as published
Where it comes from
RFC Editor · IETF Datatracker · IETF Trust Legal Provisions
Copied in full and unchanged from the RFC Editor, with the RFC's own notices. © IETF Trust and the persons identified as the document authors. The IETF Trust allows copying and distributing an RFC in full and without modification, so Micwyn shows it exactly as published and makes no study guide, audio or other version of it.
Discuss a passage
Select any passage in the reader and press Discuss to talk about it in public.