DISPATCH-Style Working Groups and the SIP Change Process

A. Feder Cooper, Barry Leiba2016 · DOI

TL;DR

This paper updates the "SIP-Change Process," a set of procedures for evolving the Session Initiation Protocol (SIP) and related technologies. It decouples these processes from a specific IETF area (RAI) and generalizes the "DISPATCH-style" working group model, making it adaptable for managing new work in other IETF areas or technology clusters.

What Problem Does This Paper Address?

The Internet Engineering Task Force (IETF) has established processes for managing the evolution of protocols and technologies. One such process, the "SIP-Change Process," was originally defined in RFC 5727 for the Real-time Applications and Infrastructure (RAI) area. This process included specific roles for working groups like DISPATCH (evaluating new work) and SIPCORE (maintaining SIP). However, organizational changes within the IETF, specifically the merger of the RAI area into the Applications and Real-Time (ART) area, rendered the original RFC's strict adherence to the RAI structure outdated. The problem is that the existing SIP-Change Process was too tightly coupled to a specific organizational structure, hindering its adaptability to evolving IETF landscapes. This paper aims to update RFC 5727 to ensure the SIP-Change Process remains relevant and flexible for future organizational changes.

Methods

The paper's approach is primarily one of clarification and generalization. It doesn't introduce new technical algorithms or experimental methods. Instead, it:

  • Decouples from Specific Areas: It reinterprets references to the "RAI area" in RFC 5727 to mean "the cluster of SIP and closely related application and infrastructure technologies, as well as other technologies designed primarily for interactive communication." This makes the process applicable beyond the former RAI area.
  • Generalizes the "DISPATCH-Style" Model: The core of the update is to describe the "DISPATCH-Style" working group model in a way that can be adopted by other working groups or areas. This model is characterized by:
  • Evaluation and Filtering: The group evaluates proposals for new work, acting as a filter to determine if a proposal is a reasonable fit for the area or cluster.
  • Venue Determination: It decides on the appropriate venue for the work, which could be an existing working group, a new BoF, a new working group, an exploratory group, or even an AD-sponsored individual draft.
  • Non-Execution of Work: Crucially, the dispatch-style group does not perform the proposed work itself. It focuses on the "dispatching" aspect.
  • Preserves Core Processes: The document emphasizes that the fundamental rules and procedures for changing SIP and related protocols, as defined in RFC 5727, remain the same unless updated by future documents.

Datasets

Not discussed in the paper.

Key Insights and Ideas

  • Organizational Agility is Key: The IETF's structure is dynamic. Processes for protocol evolution need to be robust enough to withstand organizational mergers and reassignments.
  • The "DISPATCH" Model as a Blueprint: The DISPATCH working group's success in managing new work for the RAI area provides a valuable template. Generalizing this model allows other areas to benefit from a structured approach to intake and routing of new proposals without needing to reinvent the wheel.
  • Separation of Concerns: The "DISPATCH-Style" model highlights the importance of separating the evaluation and routing of new work from the execution of that work. This allows specialized groups to focus on their core responsibilities.
  • Future-Proofing: By abstracting away specific area names and focusing on the function of the process, the authors aim to create a more enduring framework for managing protocol evolution.

Key Results

This document is not about experimental results but rather a procedural update. The "key results" are the updated definitions and guidelines for the SIP-Change Process and the DISPATCH-Style working group model. The primary outcome is a more flexible and adaptable framework for managing new work within the IETF, particularly concerning SIP and related technologies.

Limitations and Future Work

  • No Recommendation for Universal Adoption: The authors explicitly state that this document does not recommend dispatch-style groups for any specific IETF area other than ART. The decision to adopt such a model rests with the community and Area Directors, as different areas have different needs.
  • Potential for Bottlenecks: The paper acknowledges a potential security consideration: a dispatch-style working group could concentrate control of work, potentially creating bottlenecks or reducing decision quality. The proposed mitigation is active participation from the community.
  • Future Reorganizations: The document implicitly suggests that future reorganizations might necessitate further updates to the SIP-Change Process, though the generalized nature of this update aims to minimize the need for frequent revisions. The document itself is an "Internet-Draft" and will expire, indicating the ongoing nature of such updates.

Summary updated

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.
BibTeX
@misc{cooper2016dispatch,
  author = {A. Feder Cooper and Barry Leiba},
  title = {{DISPATCH-Style Working Groups and the SIP Change Process}},
  year = {2016},
  doi = {10.17487/rfc7957},
}

Loading related content...

Figure