Re: [MEDIACTRL] Mixer Control Package

James Rafferty <James.Rafferty@dialogic.com> Tue, 06 September 2011 18:29 UTC

Return-Path: <James.Rafferty@dialogic.com>
X-Original-To: mediactrl@ietfa.amsl.com
Delivered-To: mediactrl@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B051B21F8D19 for <mediactrl@ietfa.amsl.com>; Tue, 6 Sep 2011 11:29:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.367
X-Spam-Level:
X-Spam-Status: No, score=-2.367 tagged_above=-999 required=5 tests=[AWL=0.232, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 96sboxEXkeym for <mediactrl@ietfa.amsl.com>; Tue, 6 Sep 2011 11:29:15 -0700 (PDT)
Received: from outbound.dialogic.com (outbound.dialogic.com [173.210.122.27]) by ietfa.amsl.com (Postfix) with ESMTP id 7F80D21F8D13 for <mediactrl@ietf.org>; Tue, 6 Sep 2011 11:29:15 -0700 (PDT)
Received: from MBX.dialogic.com ([fe80::bd56:b76c:8d2c:437b]) by pysxht02.dialogic.com ([::1]) with mapi; Tue, 6 Sep 2011 14:30:58 -0400
From: James Rafferty <James.Rafferty@dialogic.com>
To: Eric Burger <eburger@standardstrack.com>, "mediactrl@ietf.org" <mediactrl@ietf.org>
Date: Tue, 6 Sep 2011 14:29:56 -0400
Thread-Topic: [MEDIACTRL] Mixer Control Package
Thread-Index: AcxstpTvLx7NQOi1QtSBok8VuDVH1wADERMA
Message-ID: <54633A5E61DC84429CB9FE3D9143C72109B90DAB@MBX.dialogic.com>
References: <57534C79-D34A-4C8C-AD49-A7AF503D0660@standardstrack.com>
In-Reply-To: <57534C79-D34A-4C8C-AD49-A7AF503D0660@standardstrack.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [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 18:29:16 -0000

I agree with the proposal to make it an informative reference.  

James

-----Original Message-----
From: mediactrl-bounces@ietf.org [mailto:mediactrl-bounces@ietf.org] On Behalf Of Eric Burger
Sent: Tuesday, September 06, 2011 1:01 PM
To: mediactrl@ietf.org
Subject: [MEDIACTRL] Mixer Control Package

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 4.2.1.4.2.1, 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.

Thoughts?