[rfc-dist] RFC 4878 on Definitions and Managed Objects for Operations, Administration, and Maintenance (OAM) Functions on Ethernet-Like Interfaces

[rfc-editor@rfc-editor.org]

A new Request for Comments is now available in online RFC libraries.

        
        RFC 4878

        Title:      Definitions and Managed Objects for 
                    Operations, Administration, and Maintenance (OAM)
                    Functions on Ethernet-Like Interfaces 
        Author:     M. Squire
        Status:     Standards Track
        Date:       June 2007
        Mailbox:    msquire at hatterasnetworks.com
        Pages:      58
        Characters: 130067
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-hubmib-efm-mib-06.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4878.txt

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 the
Simple Network Management Protocol (SNMP) 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.  [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

...