Protocol Action: 'Definitions and Managed Objects for OAM Functions on Ethernet Like Interfaces' to Proposed Standard
The IESG <iesg-secretary@ietf.org> Mon, 12 March 2007 20:23 UTC
Return-path: <ietf-announce-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HQr2z-0005Zh-1d; Mon, 12 Mar 2007 16:23:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HQr2w-0005Yf-Ro; Mon, 12 Mar 2007 16:23:06 -0400
Received: from ns0.neustar.com ([156.154.16.158]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HQr2v-0001S1-K0; Mon, 12 Mar 2007 16:23:06 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id 8E9B532912; Mon, 12 Mar 2007 20:23:05 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1HQr2v-000097-FX; Mon, 12 Mar 2007 16:23:05 -0400
X-test-idtracker: no
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Message-Id: <E1HQr2v-000097-FX@stiedprstage1.ietf.org>
Date: Mon, 12 Mar 2007 16:23:05 -0400
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
Cc: hubmib mailing list <hubmib@ietf.org>, Internet Architecture Board <iab@iab.org>, hubmib chair <hubmib-chairs@tools.ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: Protocol Action: 'Definitions and Managed Objects for OAM Functions on Ethernet Like Interfaces' to Proposed Standard
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Errors-To: ietf-announce-bounces@ietf.org
The IESG has approved the following document: - 'Definitions and Managed Objects for OAM Functions on Ethernet Like Interfaces ' <draft-ietf-hubmib-efm-mib-06.txt> as a Proposed Standard This document is the product of the Ethernet Interfaces and Hub MIB Working Group. The IESG contact persons are Dan Romascanu and David Kessens. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-hubmib-efm-mib-06.txt Technical Summary This document defines objects for managing Operations, Administration, and Maintenance (OAM) capabilities on Ethernet like interfaces conformant to the Ethernet OAM functionality defined in the Ethernet in the First Mile (EFM) clauses of the Ethernet standards. The Ethernet OAM functionality is complementary to SNMP management in that it is focused on a small set of link-specific functions for directly connected Ethernet interfaces. This document defines objects for controlling those link OAM functions, and for providing results and status of the OAM functions to management entities. Working Group Summary The document met the Working Group consensus. Protocol Quality The document was reviewed by David Perkins as MIB Doctor and by Bert Wijnen and Dan Romascanu as successive Area Directors and WG Chairs. The last call version of the Internet-Draft was also sent for comments to the IEEE 802.3 Working Group and to the MIB Doctors list. Note to RFC Editor Please make the following editorial chamges: 1. pag. 16, DESCRIPTION clause of dot3OamFunctionsSupported OLD: operating in undirectional mode (traffic flowing in one NEW: operating in unidirectional mode (traffic flowing in one 2. pag 51, DESCRIPTION clause of dot3OamStatsBaseGroup: OLD: number of various transmit and recieve events for OAM on an NEW: number of various transmit and receive events for OAM on an 3. page 54, DESCRIPTION clause of dot3OamNotificationGroup: OLD: to a management entity that local or remote events have occured NEW: to a management entity that local or remote events have occurred 4. Section 7, page 55: OLD: if the network itself is secure (for example by using IPSec), even NEW: if the network itself is secure (for example by using IPsec), even _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce