DISPATCH-Style Working Groups and the SIP Change Process
draft-campbell-art-rfc5727-update-03

[Ballot comment]
This document is related to the DISPATCH charter, recently approved by the IESG.

For example, my feedback, which lead to the changes at
https://www.ietf.org/rfcdiff?url1=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fcharter-ietf-dispatch%2Fwithmilestones-02-01.txt&url2=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fcharter-ietf-dispatch%2Fwithmilestones-03.txt, is (I believe, different wording is used) covered under the following text.

  Nothing in this list prevents existing working groups from directly
  adopting new work that reasonably fits their charters, nor does it
  prevent new-work proposals from going directly to BoF meetings when
  appropriate.  For borderline cases, the decision whether new work
  should start in a dispatch-style group or elsewhere is made by the
  responsible Area Directors and chairs.

Even if the write-up doesn't mention the link with the DISPATCH charter, I trust the authors (current and past IESG members) have double-checked everything.

[Ballot comment]
I absolutely fine with this doc and understand that an update of RFC 5727 is needed (especially to update/decouple the SIP change process), but I have a question out of curiosity:
Why does ART need dispatch (and define the process in an BCP) while other areas have an area meeting that more or less performs the same task...?
I'm probably missing some history on this, but would be curious to learn more!

[Ballot comment]
I want to make sure that this doesn't prohibit direct chartering of WGs without BOFs and without going through DISPATCH. I intend to assume that is the case for some work I am planning.

(Via drafts-lastcall-comment@iana.org): IESG/Authors/WG Chairs:

IANA has reviewed draft-campbell-art-rfc5727-update-02.txt, which is currently in Last Call, and has the following comments:

We understand that this document doesn't require any IANA actions.

While it's often helpful for a document's IANA Considerations section to remain in place upon publication even if there are no actions, if the authors strongly prefer to remove it, IANA does not object.

If this assessment is not accurate, please respond as soon as possible.

Thank you,

Sabrina Tanamal
IANA Specialist
ICANN

The following Last Call announcement was sent out:

From: The IESG
To: "IETF-Announce"
CC: mary.ietf.barnes@gmail.com, draft-campbell-art-rfc5727-update@ietf.org, spencerdawkins.ietf@gmail.com
Reply-To: ietf@ietf.org
Sender:
Subject: Last Call:  (Improving the Organizational Flexibility of the SIP Change Process.) to Best Current Practice


The IESG has received a request from an individual submitter to consider
the following document:
- 'Improving the Organizational Flexibility of the SIP Change Process.'
  as Best Current Practice

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2016-01-05. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

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.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-campbell-art-rfc5727-update/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-campbell-art-rfc5727-update/ballot/


No IPR declarations have been submitted directly on this I-D.

Notification list changed to ben@nostrum.com, draft-campbell-art-rfc5727-update@ietf.org, alcoop@cisco.com, draft-campbell-art-rfc5727-update.ad@ietf.org, draft-campbell-art-rfc5727-update.shepherd@ietf.org, barryleiba@computer.org, "Mary Barnes" <mary.ietf.barnes@gmail.com> from ben@nostrum.com, draft-campbell-art-rfc5727-update@ietf.org, alcoop@cisco.com, draft-campbell-art-rfc5727-update.ad@ietf.org, draft-campbell-art-rfc5727-update.shepherd@ietf.org, barryleiba@computer.org