[Hubmib] FW: Protocol Action: 'Managed Objects of Ethernet Passive Optical Networks (EPON)' to Proposed Standard
"Romascanu, Dan \(Dan\)" <dromasca@avaya.com> Tue, 05 December 2006 13:10 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gra41-0005Zi-UT; Tue, 05 Dec 2006 08:10:25 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gra41-0005Zb-3V for hubmib@ietf.org; Tue, 05 Dec 2006 08:10:25 -0500
Received: from co300216-ier2.net.avaya.com ([198.152.13.103]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gra3z-0003qz-PP for hubmib@ietf.org; Tue, 05 Dec 2006 08:10:25 -0500
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by co300216-ier2.net.avaya.com (Switch-3.1.8/Switch-3.1.7) with ESMTP id kB5DALMJ003770 for <hubmib@ietf.org>; Tue, 5 Dec 2006 08:10:22 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 05 Dec 2006 15:10:21 +0200
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F0BE0F340@is0004avexu1.global.avaya.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Protocol Action: 'Managed Objects of Ethernet Passive Optical Networks (EPON)' to Proposed Standard
Thread-Index: AccYAvxWqcz/Q6EHQ8GVZ4sysg2x3QAa7XIA
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Hubmib Mailing List (E-mail)" <hubmib@ietf.org>
X-Scanner: InterScan AntiVirus for Sendmail
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Subject: [Hubmib] FW: Protocol Action: 'Managed Objects of Ethernet Passive Optical Networks (EPON)' to Proposed Standard
X-BeenThere: hubmib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Ethernet Interfaces an Hub MIB WG <hubmib.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>, <mailto:hubmib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:hubmib@ietf.org>
List-Help: <mailto:hubmib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>, <mailto:hubmib-request@ietf.org?subject=subscribe>
Errors-To: hubmib-bounces@ietf.org
-----Original Message----- From: The IESG [mailto:iesg-secretary@ietf.org] Sent: Tuesday, December 05, 2006 2:19 AM To: IETF-Announce Cc: Internet Architecture Board; hubmib chair; RFC Editor Subject: Protocol Action: 'Managed Objects of Ethernet Passive Optical Networks (EPON)' to Proposed Standard The IESG has approved the following document: - 'Managed Objects of Ethernet Passive Optical Networks (EPON) ' <draft-ietf-hubmib-efm-epon-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-epon-mib-06.tx t Technical Summary This document defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP based Internets. In particular, it defines objects for managing interfaces that conform to the Ethernet Passive Optical Networks (EPON) standard as defined in the IEEE Std 802.3ah-2004, which are extended capabilities to the Ethernet like interfaces. Working Group Summary The working Group has consensus to publish this document as a Proposed Standard RFC. Protocol Quality The document has been reviewed by various WG members (and chairs) of the HUBMIB WG. IEEE802.3ah did various reviews and comments throughout the development of this document. MIB Doctor review was done by David Perkins. IETF Last Call also resulted in some comments. All review comments have been addressed. We are not aware of any current implementations. Bert Wijnen (WG chair of hubmib) is the PROTO SHEPHERD. Dan Romascanu is the Responsible Area Director. Note to RFC Editor 1. Page 99, pls move reference [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. from the informative to the normative section. 2. Replace all citations/references to rfc3636 and with the new rfc3636bis-to-be (which has been approved by IESG already, and which obsoletes RFC3636). _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib
- [Hubmib] FW: Protocol Action: 'Managed Objects of… Romascanu, Dan (Dan)