[MEDIACTRL] AD review: draft-ietf-mediactrl-mixer-control package-09

Robert Sparks <rjsparks@nostrum.com> Tue, 12 January 2010 21:50 UTC

Return-Path: <rjsparks@nostrum.com>
X-Original-To: mediactrl@core3.amsl.com
Delivered-To: mediactrl@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 083B23A690A for <mediactrl@core3.amsl.com>; Tue, 12 Jan 2010 13:50:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, SPF_PASS=-0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LfOJFJbR7LvN for <mediactrl@core3.amsl.com>; Tue, 12 Jan 2010 13:50:26 -0800 (PST)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by core3.amsl.com (Postfix) with ESMTP id C987E3A67FB for <mediactrl@ietf.org>; Tue, 12 Jan 2010 13:50:25 -0800 (PST)
Received: from [192.168.2.2] (pool-173-71-49-137.dllstx.fios.verizon.net [173.71.49.137]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id o0CLoLkq042945 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 12 Jan 2010 15:50:21 -0600 (CST) (envelope-from rjsparks@nostrum.com)
Message-Id: <8D41072E-34C7-4332-9EC3-B39C4C1E2013@nostrum.com>
From: Robert Sparks <rjsparks@nostrum.com>
To: mediactrl@ietf.org
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Tue, 12 Jan 2010 15:50:21 -0600
X-Mailer: Apple Mail (2.936)
Received-SPF: pass (nostrum.com: 173.71.49.137 is authenticated by a trusted mechanism)
Cc: draft-ietf-mediactrl-mixer-control-package@tools.ietf.org, mediactrl-chairs@tools.ietf.org
Subject: [MEDIACTRL] AD review: draft-ietf-mediactrl-mixer-control package-09
X-BeenThere: mediactrl@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Media Control WG Discussion List <mediactrl.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 12 Jan 2010 21:50:30 -0000

This draft is essentially ready to go. I have two questions/comments  
for the group.

1) As written, the reference to the XCON datamodel document needs to  
be normative.
      (You have to know what's defined there to know when a prefix is  
required, and
        realistically, it's a must read to use any of the video  
layouts defined there).
      I'm expecting XCON to pubreq that document within a couple of  
weeks, so making
      the reference normative shouldn't slow down publication of this  
document.
      Would anyone object to making that reference normative?

2) I'm not easily finding where framework (or this document) says what  
happens
     when part of a command with multiple components fails. For  
instance, in section
     4.2.2, there's an example of a join command that operates two  
different volumes.
     If one of those fails for some reason, does the other one fail  
with it? Where is
     the text that says this is so?

Once we resolve those two, I expect to send framework, ivr-control,  
and mixer-control
into IETF LC.

RjS