Change Process for the Session Initiation Protocol (SIP) and the Real-time Applications and Infrastructure Area
RFC 5727
Document | Type |
RFC - Best Current Practice
(March 2010; Errata)
Updated by RFC 7957
Obsoletes RFC 3427
Also known as BCP 67
Was draft-peterson-rai-rfc3427bis (individual in rai area)
|
|
---|---|---|---|
Authors | Jon Peterson , Cullen Jennings , Robert Sparks | ||
Last updated | 2015-10-14 | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized bibtex | ||
Reviews | |||
Stream | WG state | (None) | |
Document shepherd | No shepherd assigned | ||
IESG | IESG state | RFC 5727 (Best Current Practice) | |
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | Russ Housley | ||
Send notices to | (None) |
Internet Engineering Task Force (IETF) J. Peterson Request for Comments: 5727 NeuStar, Inc. BCP: 67 C. Jennings Obsoletes: 3427 Cisco Systems Updates: 3265, 3969 R. Sparks Category: Best Current Practice Tekelec ISSN: 2070-1721 March 2010 Change Process for the Session Initiation Protocol (SIP) and the Real-time Applications and Infrastructure Area 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. Status of This Memo This memo documents an Internet Best Current Practice. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on BCPs is available in Section 2 of RFC 5741. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc5727. Peterson, et al. Best Current Practice [Page 1] RFC 5727 SIP Change March 2010 Copyright Notice Copyright (c) 2010 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it into languages other than English. Table of Contents 1. History and Development . . . . . . . . . . . . . . . . . . . 3 1.1. The IETF SIPCORE Working Group . . . . . . . . . . . . . . 3 1.2. The IETF DISPATCH Working Group . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5 3. Introducing New Work to RAI . . . . . . . . . . . . . . . . . 6 4. Extensibility and Architecture . . . . . . . . . . . . . . . . 7 4.1. SIP Event Packages . . . . . . . . . . . . . . . . . . . . 9 5. Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 6. Security Considerations . . . . . . . . . . . . . . . . . . . 11 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 7.1. Clarification of RFC 3969 . . . . . . . . . . . . . . . . 12 8. Overview of Changes to RFC 3427 . . . . . . . . . . . . . . . 12 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 12 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13 10.1. Normative References . . . . . . . . . . . . . . . . . . . 13 10.2. Informative References . . . . . . . . . . . . . . . . . . 13 Peterson, et al. Best Current Practice [Page 2] RFC 5727 SIP Change March 2010Show full document text