ObsoletedBEST CURRENT PRACTICELegacy stream

RFC 3427: Change Process for the Session Initiation Protocol (SIP)

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 5727.

Current version: RFC 5727 — Change Process for the Session Initiation Protocol (SIP) and the Real-time Applications and Infrastructure Area

In plain English — editorial summary, not part of the RFC

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.

Document record

Document ID: RFC3427
Published: December 2002
Authors: A. Mankin; S. Bradner; R. Mahy; D. Willis; J. Ott; B. Rosen
Status: BEST CURRENT PRACTICE
Stream: Legacy
Area: —
Pages: 12
Also known as: —

Obsoleted by:: RFC 5727
Updated by:: RFC 3968, RFC 3969

Topics

sipping

Referenced by

3 later RFCs formally update or obsolete part of this document.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on 23 August 2026. RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?