Re: [MEDIACTRL] Mixer Control Package

["Henry Lum" <[e-mail]>]

+1

-----Original Message-----
From: [e-mail] [mailto:[e-mail]] On
Behalf Of Eric Burger
Sent: Tuesday, September 06, 2011 1:01 PM
To: [e-mail]
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?

					
-------------------------------------------------------------------------------------------------------------------
CONFIDENTIALITY NOTICE: This e-mail and any files attached may contain confidential and proprietary information of Alcatel-Lucent and/or its affiliated entities. Access by the intended recipient only is authorized. Any liability arising from any party acting, or refraining from acting, on any information contained in this e-mail is hereby excluded. If you are not the intended recipient, please notify the sender immediately, destroy the original transmission and its attachments and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Copyright in this e-mail and any attachments belongs to Alcatel-Lucent and/or its affiliated entities.