[rfc-dist] RFC 4837 on Managed Objects of Ethernet Passive Optical Networks (EPON)

rfc-editor@rfc-editor.org rfc-editor at rfc-editor.org
Tue Jul 10 17:28:22 PDT 2007


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 at 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 at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at 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 at 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 at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...




More information about the rfc-dist mailing list