[eman] SCTE and EMAN: requesting a presentation slot.
Benoit Claise <bclaise@cisco.com> Wed, 27 February 2013 19:13 UTC
Return-Path: <bclaise@cisco.com>
X-Original-To: eman@ietfa.amsl.com
Delivered-To: eman@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9DF5721F8AB4 for <eman@ietfa.amsl.com>; Wed, 27 Feb 2013 11:13:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.547
X-Spam-Level:
X-Spam-Status: No, score=-10.547 tagged_above=-999 required=5 tests=[AWL=0.051, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ARsnoA6dTcXE for <eman@ietfa.amsl.com>; Wed, 27 Feb 2013 11:13:01 -0800 (PST)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfa.amsl.com (Postfix) with ESMTP id A24B821F8611 for <eman@ietf.org>; Wed, 27 Feb 2013 11:13:01 -0800 (PST)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r1RJCr49012622; Wed, 27 Feb 2013 20:12:53 +0100 (CET)
Received: from [10.60.67.84] (ams-bclaise-8913.cisco.com [10.60.67.84]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r1RJC3Qv012148; Wed, 27 Feb 2013 20:12:13 +0100 (CET)
Message-ID: <512E5A82.30102@cisco.com>
Date: Wed, 27 Feb 2013 20:12:02 +0100
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3
MIME-Version: 1.0
To: eman mailing list <eman@ietf.org>
Content-Type: multipart/alternative; boundary="------------060506000908070507040403"
Cc: "Frank_Sandoval@cable.comcast.com" <Frank_Sandoval@cable.comcast.com>
Subject: [eman] SCTE and EMAN: requesting a presentation slot.
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Discussions about the Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Feb 2013 19:13:02 -0000
Dear all, I had a call with SCTE yesterday. Frank, in the copy list, sent me this SCTE description, and could add some more information if needed: The Society of Cable Telecommunications Engineers (SCTE) is addressing energy management topics for the cable industry through its Smart Energy Management Initiative (SEMI). There are several sub-committees and working groups within SEMI, one of which is addressing energy measurement and management communications protocols. The scope of this group is to describe a logical Information Model that articulates the entities, attributes, and relationships supported by a wide variety of devices used within the cable environment, define a number of encoding and transport protocols that may be used to support the model, and provide a mapping between a specific protocol definition and the Information Model. There is a lot of overlap between this activity and the work of the IETF EMAN group. It is the hope of the SCTE working group to leverage the work occurring within the IETF to the greatest degree practical. Specifically, we hope to adopt the Information Model defined within the IETF. Members of the working group plan to participate in the IETF to further refine the information model. We discussed the EMAN and SCTE scopes and agreed that the two groups want to solve the same problem (as described by http://tools.ietf.org/html/draft-ietf-eman-requirements-12). The IETF EMAN charter mentions MIB modules (data model), but we all understand that what is key is the information model definition (see RFC 3444), and that future data models could exist in the future (NETCONF, IPFIX, you name it). And the EMAN framework contains precisely an information model, which is used as input for the MIB module specifications. See http://tools.ietf.org/html/draft-ietf-eman-framework-07#section-5 Brian, also in the copy list, reverse-engineering our MIB modules to create an UML based information model. SCTE was not aware of the information model definition in the EMAN framework. To tell the truth, it's true that it is a little hidden in the series of EMAN documents. It will be very valuable for EMAN to see Brian 's UML based information model, to understand if the object semantics are correctly defined, the information model shortcomings, and finally if we lack objects or use the wrong ones. The good news is that Brian will be attending the IETF. Nevil, Bruce, can you please organize a slot for Brian to present. Based on the discussion I had with the SCTE group, that discussion will be very valuable. Regards, Benoit
- [eman] SCTE and EMAN: requesting a presentation s… Benoit Claise
- Re: [eman] SCTE and EMAN: requesting a presentati… Benoit Claise
- Re: [eman] SCTE and EMAN: requesting a presentati… Brian Hedstrom