IETF 80 Proceedings

Introduction  |  Area, Working Goup & BoF Reports  |  Plenaries  |  Training  |  Internet Research Task Force

Dispatch (dispatch) (WG)

Minutes  | Audio Archives  |  Jabber Logs  |  Mailing List Archives

Additional information is available at tools.ietf.org/wg/dispatch

Chair(s): Mary Barnes Cullen Jennings Real-time Applications and Infrastructure Area Director(s): Gonzalo Camarillo Robert Sparks * The Real-time Applications and Infrastructure Area Directors were seated during the IETF 65. Real-time Applications and Infrastructure Area Advisor: Gonzalo Camarillo

Meeting Slides

• 1-Agenda-status-chairs
• Dispatch-agenda-audio
• 2-Reason-header-in-responses
• dispatch-reason-response-audio
• 3-q4s
• dispatch-q4s-audio
• RTCWeb agenda
• RTCWeb - problems

No Current Internet-Drafts

No Request For Comments

Charter (as of 2010-04-16)

The Dispatch working group is chartered to consider proposals for
new work in the RAI area and identify, or help create, an appropriate
venue for the work. Options for handling new work include:

- Directing the work to an existing WG.
- Developing a proposal for a BOF.
- Developing a charter and establishing consensus for a new WG
or Exploratory Group. This option will primarily be used with
fairly mature and well-defined efforts.
- Rejecting and deferring work.

A major objective of the DISPATCH WG is to provide timely, clear
dispositions of new efforts. Where there is consensus to take
on new work, the WG will strive to quickly find a home for it.
Reconsideration of proposals which have failed to gather consensus
will be prioritized behind proposals for new work which have not
yet been considered. In general, requests for reconsideration
should only be made once a proposal has been significantly
revised.

Guiding principles will include:

1. Providing a clear problem statement for proposed new work.

2. Prioritizing new efforts so that RAI does not take on more work
than it can effectively complete.

3. Looking for commonalities among ongoing development efforts.
Such commonalities may indicate the need to develop more
general, reusable components.

4. Protecting the architectural integrity of RAI protocols and
ensuring that work has general applicability.

If the group decides that a particular topic needs to be addressed by
a new or existing WG, the normal IETF chartering process will be
followed, including, for instance, IETF-wide review of the proposed
changes. Proposal for large work efforts SHOULD lead to a BOF where
the topic can be discussed in front of the entire IETF community.

Prior experience in RAI, particularly in SIPPING, indicates that the
activities described here are significantly hindered when trying to
complete the identified protocol work items in the same venue. The
DISPATCH working group will not direct protocol work to itself.

Goals and Milestones:

Aug 2009		Proposed charter for SIP Overload WG
Aug 2009		Proposed disposition for SIP Common Log Format
Sep 2009		Proposed charter for SIP Configuration WG
Sep 2009		Proposed disposition for SAML for SIP