[MEDIACTRL] Mixer Control Package

Eric Burger <eburger@standardstrack.com> Tue, 06 September 2011 16:59 UTC

Return-Path: <eburger@standardstrack.com>
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 AF12321F8C31 for <mediactrl@ietfa.amsl.com>; Tue, 6 Sep 2011 09:59:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.11
X-Spam-Status: No, score=-101.11 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id LhvpPwB7GE68 for <mediactrl@ietfa.amsl.com>; Tue, 6 Sep 2011 09:59:40 -0700 (PDT)
Received: from biz104.inmotionhosting.com (biz104.inmotionhosting.com []) by ietfa.amsl.com (Postfix) with ESMTP id 07AA721F8C1D for <mediactrl@ietf.org>; Tue, 6 Sep 2011 09:59:39 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=standardstrack.com; h=Received:From:Content-Type:Subject:Date:Message-Id:To:Mime-Version:X-Mailer:X-Source:X-Source-Args:X-Source-Dir; b=qTzy5FS8CMXcR4Bn/s7xVfUJPbERZ0Z9oEDKpqi1V2LKxR+M1+Vbp6UWxlMLDwIh7reD1Fk71v/a2ZIdaB8NtUo7GFwLMwKejMc/2We13OTUvH2OLnkjY5Z0lRI9lRtT;
Received: from [] (helo=[]) by biz104.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <eburger@standardstrack.com>) id 1R0z1Z-00052j-G3 for mediactrl@ietf.org; Tue, 06 Sep 2011 10:01:26 -0700
From: Eric Burger <eburger@standardstrack.com>
Content-Type: multipart/signed; boundary=Apple-Mail-77--133650584; protocol="application/pkcs7-signature"; micalg=sha1
Date: Tue, 6 Sep 2011 13:01:21 -0400
Message-Id: <57534C79-D34A-4C8C-AD49-A7AF503D0660@standardstrack.com>
To: mediactrl@ietf.org
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz104.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - standardstrack.com
Subject: [MEDIACTRL] Mixer Control Package
X-BeenThere: mediactrl@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
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, 06 Sep 2011 16:59:40 -0000

The Mixer Control Package, the second to last normative document the work group needs to publish, has been on hold for nine months waiting for the XCON common data model.  That document has been stuck in the XCON work group for over three months.

Do we need this to be a normative reference?  We refer to the document in two places.  The first is in, where we enumerate the entire list of video layouts. By the way, that reference is a MAY, not a MUST or even a SHOULD.  The second is in 4.4.1, where we say we take the <codec> element from the data model, but then we go ahead and define the element, anyway.

I would offer that reading, understanding, and conforming to the data model is a nice thing.  However, it is not mandatory for creating an interoperable mediactrl implementation.  Therefore, I would propose we ask the RFC Editor move this reference from the Normative References to the Informative References, at which point this document will publish.