< draft-campbell-art-rfc5727-update-01.txt   draft-campbell-art-rfc5727-update-02.txt >
Internet Engineering Task Force B. Campbell, Ed. Internet Engineering Task Force B. Campbell, Ed.
Internet-Draft Oracle Internet-Draft Oracle
Updates: 5727 (if approved) A. Cooper Updates: 5727 (if approved) A. Cooper
Intended status: Best Current Practice Cisco Intended status: Best Current Practice Cisco
Expires: November 30, 2015 B. Leiba Expires: December 21, 2015 B. Leiba
Huawei Huawei
May 29, 2015 June 19, 2015
Improving the Organizational Flexibility of the SIP Change Process. Improving the Organizational Flexibility of the SIP Change Process.
draft-campbell-art-rfc5727-update-01 draft-campbell-art-rfc5727-update-02
Abstract Abstract
RFC 5727 defines several processes for the Real-time Applications and RFC 5727 defines several processes for the Real-time Applications and
Infrastructure (RAI) area. These processes include the evolution of Infrastructure (RAI) area. These processes include the evolution of
the Session Initiation Protocol (SIP) and related protocols, as well the Session Initiation Protocol (SIP) and related protocols, as well
as the operation of the DISPATCH and SIPCORE working groups. This as the operation of the DISPATCH and SIPCORE working groups. This
document updates RFC 5727 to allow flexibility for the area and document updates RFC 5727 to allow flexibility for the area and
working group structure, while preserving the SIP change processes. working group structure, while preserving the SIP change processes.
It also generalizes the DISPATCH working group processes so that they It also generalizes the DISPATCH working group processes so that they
skipping to change at page 1, line 40 skipping to change at page 1, line 40
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on November 30, 2015. This Internet-Draft will expire on December 21, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 18 skipping to change at page 2, line 18
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Dispatch-Style Working Groups . . . . . . . . . . . . . . . . 3 2. Dispatch-Style Working Groups . . . . . . . . . . . . . . . . 3
3. Decoupling the SIP-Change Process from the RAI Area . . . . . 4 3. Decoupling the SIP-Change Process from the RAI Area . . . . . 4
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
5. Security Considerations . . . . . . . . . . . . . . . . . . . 4 5. Security Considerations . . . . . . . . . . . . . . . . . . . 4
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 5 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 5
7.1. Normative References . . . . . . . . . . . . . . . . . . 5 7.1. Normative References . . . . . . . . . . . . . . . . . . 5
7.2. Informative Reverences . . . . . . . . . . . . . . . . . 5 7.2. Informative Reverences . . . . . . . . . . . . . . . . . 5
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5
1. Introduction 1. Introduction
[RFC5727] describes processes for evolving and maintaining the [RFC5727] describes processes for evolving and maintaining the
Session Initiation Protocol (SIP) [RFC3261] and related technologies Session Initiation Protocol (SIP) [RFC3261] and related technologies
in the Real-time Application and Infrastructure (RAI) area. These in the former Real-time Application and Infrastructure (RAI) area.
processes are collectively known as the "SIP Change Process". 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 Internet Engineering Steering Group At the time of this writing, the RAI area recently merged with the
(IESG) expects to reorganize the RAI area. While areas do not Applications (APP) area to form a new Applications and Real-Time
normally have "charters" per se, RFC 5727 has effectively served as a (ART) area. This document updates RFC 5727 to remove its dependency
charter for RAI. The language in RFC 5727 is tightly bound to the on RAI and its working group structure.
area and to the the DISPATCH and SIPCORE working groups. 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 RFC 5727 specifies that the DISPATCH working group assesses potential
new work for the area, and determines where such work should occur. new work for the area, and determines where such work should occur.
DISPATCH does not itself take on such new work. The SIPCORE working DISPATCH does not itself take on such new work. The SIPCORE working
group is responsible for maintenance of SIP. Other RAI working group is responsible for maintenance of SIP. Other RAI working
groups develop extensions to SIP that do not change the core groups develop extensions to SIP that do not change the core
protocol, new applications of SIP, and other technologies for protocol, new applications of SIP, and other technologies for
interactive communication among humans. This document further interactive communication among humans. This document further
generalizes the processes of the DISPATCH working group so that they generalizes the processes of the DISPATCH working group so that they
can be applied to other areas, or to clusters of technologies within can be applied to other areas, or to clusters of technologies within
 End of changes. 7 change blocks. 
14 lines changed or deleted 15 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/