Cite this BCP: TXTBCP 67 contains the following RFCs:
|RFC 5727, BCP 67||Change Process for the Session Initiation Protocol (SIP) and the Real-time Applications and Infrastructure Area||J. Peterson, C. Jennings, R. Sparks||March 2010||Obsoletes RFC 3427, Updates RFC 3265, RFC 3969, Updated by RFC 7957, Errata||Best Current Practice|
|RFC 7957, BCP 67||DISPATCH-Style Working Groups and the SIP Change Process||B. Campbell, Ed., A. Cooper, B. Leiba||August 2016||Updates RFC 5727||Best Current Practice|
Abstract of RFC 5727
This memo documents a process intended to organize the future development of the Session Initiation Protocol (SIP) and related work in the Real-time Applications and Infrastructure (RAI) Area. As the environments in which SIP is deployed grow more numerous and diverse, modifying or extending SIP in certain ways may threaten the interoperability and security of the protocol; however, the IETF process must also cater to the realities of existing deployments and serve the needs of the implementers working with SIP. This document therefore defines the functions of two long-lived working groups in the RAI Area that are, respectively, responsible for the maintenance of the core SIP specifications and the development of new efforts to extend and apply work in this space. This document obsoletes RFC 3427. This memo documents an Internet Best Current Practice.
Abstract of RFC 7957
RFC 5727 defined several processes for the former Real-time Applications and Infrastructure (RAI) area. These processes include the evolution of the Session Initiation Protocol (SIP) and related protocols, as well as the operation of the DISPATCH and SIPCORE working groups. This document updates RFC 5727 to allow flexibility for the area and working group structure, while preserving the SIP change processes. It also generalizes the DISPATCH working group processes so that they can be easily adopted by other working groups.
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.