Change Process for the Session Initiation Protocol and the Real-time Applications and Infrastructure Area
RFC 5727, “Change Process for the Session Initiation Protocol and the Real-time Applications and Infrastructure Area”, is a Best Current Practice document published in March 2010 by J. Peterson, C. Jennings, R. Sparks. It updates RFC 3265, RFC 3969. It obsoletes RFC 3427. It has since been updated by RFC 7957. The canonical text is published by the RFC Editor.
Abstract
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.
What “Best Current Practice” means
Documents the IETF community's recommended operational or procedural practice rather than a protocol specification.
The canonical text of RFC 5727 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 5726 Mobile IPv6 Location Privacy Solutions
- RFC 5728 The SatLabs Group DVB-RCS MIB
- RFC 5725 Post-Repair Loss RLE Report Block Type for RTP Control Protocol Extended Reports
- RFC 5724 URI Scheme for Global System for Mobile Communications Short Message Service
- RFC 5723 Internet Key Exchange Protocol Version 2 Session Resumption
- RFC 5721 POP3 Support for UTF-8
- RFC 5720 Routing and Addressing in Networks with Global Enterprise Recursion
- RFC 5719 Updated IANA Considerations for Diameter Command Code Allocations