| Number | Files | Title | Authors | Date | More Info | Status |
|---|---|---|---|---|---|---|
| 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 | ObsoletesRFC 3427, UpdatesRFC 3265,RFC 3969, Updated byRFC 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 | UpdatesRFC 5727 | Best Current Practice |
This memo documents a process intended to organize the futuredevelopment of the Session Initiation Protocol (SIP) and related workin the Real-time Applications and Infrastructure (RAI) Area. As theenvironments in which SIP is deployed grow more numerous and diverse,modifying or extending SIP in certain ways may threaten theinteroperability and security of the protocol; however, the IETFprocess must also cater to the realities of existing deployments andserve the needs of the implementers working with SIP. This documenttherefore defines the functions of two long-lived working groups inthe RAI Area that are, respectively, responsible for the maintenanceof the core SIP specifications and the development of new efforts toextend and apply work in this space. This document obsoletes RFC3427. This memo documents an Internet Best Current Practice.
RFC 5727 defined several processes for the former Real-timeApplications and Infrastructure (RAI) area. These processes includethe evolution of the Session Initiation Protocol (SIP) and relatedprotocols, as well as the operation of the DISPATCH and SIPCOREworking groups. This document updates RFC 5727 to allow flexibilityfor the area and working group structure, while preserving the SIPchange processes. It also generalizes the DISPATCH working groupprocesses so that they can be easily adopted by other working groups.
For the definition ofStatus,seeRFC 2026.
For the definition ofStream, seeRFC 8729.