[MEDIACTRL] Document Action: 'Media Control Channel Framework (CFW) Call Flow Examples' to Informational RFC (draft-ietf-mediactrl-call-flows-13.txt)

The IESG <iesg-secretary@ietf.org> Tue, 17 September 2013 00:58 UTC

Return-Path: <iesg-secretary@ietf.org>
X-Original-To: mediactrl@ietfa.amsl.com
Delivered-To: mediactrl@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id D778A11E8276; Mon, 16 Sep 2013 17:58:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.466
X-Spam-Status: No, score=-102.466 tagged_above=-999 required=5 tests=[AWL=0.134, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id nOJLKz6D+QAh; Mon, 16 Sep 2013 17:58:37 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 03DB511E8269; Mon, 16 Sep 2013 17:58:37 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 4.71.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20130917005836.13862.86395.idtracker@ietfa.amsl.com>
Date: Mon, 16 Sep 2013 17:58:36 -0700
Cc: mediactrl mailing list <mediactrl@ietf.org>, mediactrl chair <mediactrl-chairs@tools.ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: [MEDIACTRL] Document Action: 'Media Control Channel Framework (CFW) Call Flow Examples' to Informational RFC (draft-ietf-mediactrl-call-flows-13.txt)
X-BeenThere: mediactrl@ietf.org
X-Mailman-Version: 2.1.12
List-Id: Media Control WG Discussion List <mediactrl.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mediactrl>, <mailto:mediactrl-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mediactrl>
List-Post: <mailto:mediactrl@ietf.org>
List-Help: <mailto:mediactrl-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mediactrl>, <mailto:mediactrl-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Sep 2013 00:58:38 -0000

The IESG has approved the following document:
- 'Media Control Channel Framework (CFW) Call Flow Examples'
  (draft-ietf-mediactrl-call-flows-13.txt) as Informational RFC

This document is the product of the Media Server Control Working Group.

The IESG contact persons are Richard Barnes and Gonzalo Camarillo.

A URL of this Internet Draft is:

Technical Summary:

	Relevant content can frequently be found in the abstract
	and/or introduction of the document. If not, this may be an
	indication that there are deficiencies in the abstract or

This document presents a series of MEDIACTRL-related call flows,
presenting client/server state diagrams, message sequence diagrams,
and message contents. It is a reference for the whole MEDIACTRL
specification for implementers and protocol researchers alike, and all
the flows are modeled from an implementation of the framework and its
	Working Group Summary:

	Was there anything in WG process that is worth noting? For
	example, was there controversy about particular points or were
	there decisions where the consensus was particularly rough?

Several participants in the WG have advocated a call flows document.
The advocates included Jon Peterson, who was the AD at the time the
Mediactrl WG was chartered.

	Document Quality:

	Are there existing implementations of the protocol? Have a
	significant number of vendors indicated their plan to
	implement the specification? Are there any reviewers that
	merit special mention as having done a thorough review, e.g.,
	one that resulted in important changes or a conclusion that
	the document had no substantive issues? If there was a MIB
	Doctor, Media Type or other expert review, what was its course
	(briefly)? In the case of a Media Type review, on what date
	was the request posted?

Lorenzo Miniero reports that interoperability tests were carried out
at IETF73 (Minneapolis, Nov 2008) with implementations from HP (OCMP)
and Dialogic testing scenarios illustrated by this document.  The
minutes report other companies that were planning an implementation at
the time: "Stephan notes that implementation is be planned on
Broadsoft for the spring. Alan notes that Ditech is also planning an

As an examples document, the document does not specify any protocol.
All the contained examples were produced by running the scenarios
using an existing implementation of the MEDIACTRL specification by the
authors themselves. A thorough review was done by Dale Worley, who
helped tackle some relevant inconsistencies in the presented


	Who is the Document Shepherd? Who is the Responsible Area

The Document Shepherd is Dale Worley. The Responsible Area Director is
Richard Barnes.