FW: [Hubmib] RFC 4837 on Managed Objects of Ethernet Passive OpticalNetworks (EPON)
"Romascanu, Dan (Dan)" <dromasca@avaya.com> Wed, 11 July 2007 14:47 UTC
Return-path: <hubmib-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I8dTW-0000IN-Sj; Wed, 11 Jul 2007 10:47:30 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I8dTV-0000II-Lw for hubmib@ietf.org; Wed, 11 Jul 2007 10:47:29 -0400
Received: from nj300815-nj-outbound.net.avaya.com ([198.152.12.100] helo=nj300815-nj-outbound.avaya.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I8dTR-0002BA-CN for hubmib@ietf.org; Wed, 11 Jul 2007 10:47:29 -0400
Received: from 14.140.64.135.in-addr.arpa (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by nj300815-nj-outbound.avaya.com with ESMTP; 11 Jul 2007 10:47:24 -0400
X-IronPort-AV: i="4.16,527,1175486400"; d="scan'208"; a="37706689:sNHT11999970"
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: FW: [Hubmib] RFC 4837 on Managed Objects of Ethernet Passive OpticalNetworks (EPON)
Date: Wed, 11 Jul 2007 16:47:24 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04215A96@307622ANEX5.global.avaya.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Hubmib] RFC 4837 on Managed Objects of Ethernet Passive OpticalNetworks (EPON)
Thread-Index: AcfDUruKVDq4sznGQlWhQ43s4D/pzgAd3ghg
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: hubmib@ietf.org
X-Spam-Score: 0.1 (/)
X-Scan-Signature: d2b46e3b2dfbff2088e0b72a54104985
Cc: stds-802-3@ieee.org
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
Congratulations to Lior and to the whole Working Group on the publication of the EPON MIB. Dan -----Original Message----- From: rfc-editor@rfc-editor.org [mailto:rfc-editor@rfc-editor.org] Sent: Wednesday, July 11, 2007 3:28 AM To: ietf-announce@ietf.org; rfc-dist@rfc-editor.org Cc: hubmib@ietf.org; rfc-editor@rfc-editor.org Subject: [Hubmib] RFC 4837 on Managed Objects of Ethernet Passive OpticalNetworks (EPON) A new Request for Comments is now available in online RFC libraries. RFC 4837 Title: Managed Objects of Ethernet Passive Optical Networks (EPON) Author: L. Khermosh Status: Standards Track Date: July 2007 Mailbox: lior_khermosh@pmc-sierra.com Pages: 91 Characters: 206726 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-hubmib-efm-epon-mib-06.txt URL: http://www.rfc-editor.org/rfc/rfc4837.txt 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. [STANDARDS TRACK] This document is a product of the Ethernet Interfaces and Hub MIB Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements.Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute _______________________________________________ Hubmib mailing list Hubmib@ietf.org https://www1.ietf.org/mailman/listinfo/hubmib
- FW: [Hubmib] RFC 4837 on Managed Objects of Ether… Romascanu, Dan (Dan)
- FW: [Hubmib] RFC 4837 on Managed Objects of Ether… Wijnen, Bert (Bert)