DISPATCH-Style Working Groups and the SIP Change Process
RFC 7957
Document | Type |
RFC - Best Current Practice
(August 2016; No errata)
Updates RFC 5727
Was draft-campbell-art-rfc5727-update (individual in art area)
|
|
---|---|---|---|
Authors | Ben Campbell , Alissa Cooper , Barry Leiba | ||
Last updated | 2016-08-24 | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized bibtex | ||
Reviews | |||
Stream | WG state | (None) | |
Document shepherd | Mary Barnes | ||
Shepherd write-up | Show (last changed 2015-11-25) | ||
IESG | IESG state | RFC 7957 (Best Current Practice) | |
Consensus Boilerplate | Yes | ||
Telechat date | |||
Responsible AD | Spencer Dawkins | ||
Send notices to | (None) | ||
IANA | IANA review state | IANA OK - No Actions Needed | |
IANA action state | No IANA Actions |
Internet Engineering Task Force (IETF) B. Campbell, Ed. Request for Comments: 7957 Oracle BCP: 67 A. Cooper Updates: 5727 Cisco Category: Best Current Practice B. Leiba ISSN: 2070-1721 Huawei Technologies August 2016 DISPATCH-Style Working Groups and the SIP Change Process Abstract 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. 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 7841. 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/rfc7957. Campbell, et al. Best Current Practice [Page 1] RFC 7957 Update to SIP Change Process August 2016 Copyright Notice Copyright (c) 2016 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. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 2. DISPATCH-Style Working Groups . . . . . . . . . . . . . . . . 3 3. Decoupling the SIP Change Process from the RAI Area . . . . . 4 4. Security Considerations . . . . . . . . . . . . . . . . . . . 4 5. References . . . . . . . . . . . . . . . . . . . . . . . . . 5 5.1. Normative References . . . . . . . . . . . . . . . . . . 5 5.2. Informative References . . . . . . . . . . . . . . . . . 5 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 5 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6 1. Introduction [RFC5727] described processes for evolving and maintaining the Session Initiation Protocol (SIP) [RFC3261] and related technologies in the former Real-time Application and Infrastructure (RAI) area. These processes are collectively known as the "SIP Change Process". While areas do not normally have "charters" per se, RFC 5727 effectively served as a charter for RAI. The language in RFC 5727 was tightly bound to the RAI area and to the DISPATCH and SIPCORE working groups. In 2015, The RAI area merged with the Applications (APP) area to form the Applications and Real-Time (ART) area. This document updates RFC 5727 to remove its dependency on RAI and its working group structure. The updates in this document do not depend on the names of the new area, or any specific working group. Rather, the authors seek to future-proof the SIP Change Process against future reorganizations. RFC 5727 specified that the DISPATCH working group assesses potential new work for the area, and determines where such work should occur. DISPATCH does not itself take on such new work. The SIPCORE working Campbell, et al. Best Current Practice [Page 2] RFC 7957 Update to SIP Change Process August 2016 group is responsible for maintenance of SIP. Other historically RAI area working groups develop extensions to SIP that do not change the core protocol, new applications of SIP, and other technologies for interactive communication among humans. This document further generalizes the processes of the DISPATCH working group so that they can be applied to other areas, or to clusters of technologies withinShow full document text