Improving the Organizational Flexibility of the SIP Change Process.
draft-campbell-art-rfc5727-update-02

The information below is for an old version of the document
Document Type Active Internet-Draft (individual in art area)
Last updated 2016-01-05 (latest revision 2015-06-19)
Stream IETF
Intended RFC status Best Current Practice
Formats plain text pdf html bibtex
Stream WG state (None)
Document shepherd Mary Barnes
Shepherd write-up Show (last changed 2015-11-25)
IESG IESG state Waiting for Writeup
Consensus Boilerplate Unknown
Telechat date
Responsible AD Spencer Dawkins
Send notices to (None)
IANA IANA review state IANA OK - No Actions Needed
IANA action state None
Internet Engineering Task Force                         B. Campbell, Ed.
Internet-Draft                                                    Oracle
Updates: 5727 (if approved)                                    A. Cooper
Intended status: Best Current Practice                             Cisco
Expires: December 21, 2015                                      B. Leiba
                                                                  Huawei
                                                           June 19, 2015

  Improving the Organizational Flexibility of the SIP Change Process.
                  draft-campbell-art-rfc5727-update-02

Abstract

   RFC 5727 defines several processes for the 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 Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on December 21, 2015.

Copyright Notice

   Copyright (c) 2015 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

Campbell, et al.        Expires December 21, 2015               [Page 1]
Internet-Draft              SIP-Change Update                  June 2015

   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.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   5
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   5
     7.2.  Informative Reverences  . . . . . . . . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   [RFC5727] describes 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 has
   effectively served as a charter for RAI.  The language in RFC 5727 is
   tightly bound to the RAI area and to the the DISPATCH and SIPCORE
   working groups.

   At the time of this writing, the RAI area recently merged with the
   Applications (APP) area to form a new Applications and Real-Time
   (ART) area.  This document updates RFC 5727 to remove its dependency
   on RAI and its working group structure.

   RFC 5727 specifies 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
   group is responsible for maintenance of SIP.  Other RAI 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 within
   an area.

Campbell, et al.        Expires December 21, 2015               [Page 2]
Show full document text