Browse Prior Art Database

DISPATCH-Style Working Groups and the SIP Change Process (RFC7957)

IP.com Disclosure Number: IPCOM000247336D
Original Publication Date: 2016-Aug-01
Included in the Prior Art Database: 2016-Aug-25
Document File: 12 page(s) / 12K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

B. Campbell: AUTHOR [+4]

Abstract

[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.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 23% of the total text.

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....