[Videomgmt] RE: Overall thoughts on a standard Video Management MIB
"Ray, Robert" <RobertRay@pesa.com> Fri, 07 October 2005 14:27 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ENtBe-00038O-96; Fri, 07 Oct 2005 10:27:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ENtBd-00038J-CP for videomgmt@megatron.ietf.org; Fri, 07 Oct 2005 10:27:01 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21740 for <videomgmt@ietf.org>; Fri, 7 Oct 2005 10:26:58 -0400 (EDT)
Received: from mail.pesa.com ([216.180.38.252]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ENtKv-0000j0-11 for videomgmt@ietf.org; Fri, 07 Oct 2005 10:36:38 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 07 Oct 2005 09:26:48 -0500
Message-ID: <D9D369D05EDF2F498B0FB6357C3BB9972E11B9@exchange.hsv.pesa.com>
Thread-Topic: Overall thoughts on a standard Video Management MIB
Thread-Index: AcXKzYHZQs3A38+eQReMrPtdrA0NPQAeKeyQ
From: "Ray, Robert" <RobertRay@pesa.com>
To: videomgmt@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Content-Transfer-Encoding: quoted-printable
Subject: [Videomgmt] RE: Overall thoughts on a standard Video Management MIB
X-BeenThere: videomgmt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: MIB development for the Video Industry <videomgmt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/videomgmt>, <mailto:videomgmt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/videomgmt>
List-Post: <mailto:videomgmt@ietf.org>
List-Help: <mailto:videomgmt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/videomgmt>, <mailto:videomgmt-request@ietf.org?subject=subscribe>
Sender: videomgmt-bounces@ietf.org
Errors-To: videomgmt-bounces@ietf.org
-- The Entity MIB is useful for modeling chassis types of architectures. It appears to be the new and improved Chassis MIB (the chassis MIB working group closed in the early 90s, I think). Which is exactly what we need. Fans, power supplies, slots, etc. -- However the Entity MIB does not have Video-industry specific Textual -- Convention definitions (nor should it). Agree with that. The same mechanism works well for telecommunications gear, for example. -- Is there a need for a Video-Management-specific-entity-type MIB? As Mohit notted, the Entity MIB http://www.ietf.org/rfc/rfc4133.txt?number=4133 can certainly handle our world. I think a good first step might be to see how well we can fit a very simple thing into the framework. Like a fan. Would be a really simple thing: perhaps as few as four attributes, say: Operational Status - a bitmap of things such as: on, fixed-speed, rpm-controlled, voltage-controlled Rpm (0..10000) Voltage (0..240) Notification Flag - enables or disables notification generation Creating a very simple MIB for this and writing the text for how it integrates into the Entity MIB architecture would be a big step (IMHO), no? Adding Industry specific things such as power supplies, video conversion, audio conversion, audio gain, mixing, etc., would surely follow and could hopefully be kept small as well. Bob Ray _______________________________________________ Videomgmt mailing list Videomgmt@ietf.org https://www1.ietf.org/mailman/listinfo/videomgmt
- [Videomgmt] RE: Overall thoughts on a standard Vi… Larry R. Walsh
- [Videomgmt] RE: Overall thoughts on a standard Vi… Ray, Robert