RE: RFC 4878 on Definitions and Managed Objects for Operations, Administration, and Maintenance (OAM) Functions on Ethernet-Like Interfaces

Thanks and congratulations to Matt Squire and to the whole working
group.=20

Dan
=20

=20
=20

> -----Original Message-----
> From: [email protected] [mailto:[email protected]]=20
> Sent: Sunday, July 01, 2007 12:39 AM
> To: [email protected]; [email protected]
> Cc: [email protected]; [email protected]
> Subject: [Hubmib] RFC 4878 on Definitions and Managed Objects=20
> for Operations,Administration,and Maintenance (OAM) Functions=20
> on Ethernet-Like Interfaces
>=20
>=20
> A new Request for Comments is now available in online RFC libraries.
>=20
>=20
>=20
>        =20
>=20
>         RFC 4878
>=20
>=20
>=20
>         Title:      Definitions and Managed Objects for=20
>=20
>                     Operations, Administration, and Maintenance (OAM)
>=20
>                     Functions on Ethernet-Like Interfaces=20
>=20
>         Author:     M. Squire
>=20
>         Status:     Standards Track
>=20
>         Date:       June 2007
>=20
>         Mailbox:    [email protected]
>=20
>         Pages:      58
>=20
>         Characters: 130067
>=20
>         Updates/Obsoletes/SeeAlso:   None
>=20
>=20
>=20
>         I-D Tag:    draft-ietf-hubmib-efm-mib-06.txt
>=20
>=20
>=20
>         URL:        http://www.rfc-editor.org/rfc/rfc4878.txt
>=20
>=20
>=20
> This document defines objects for managing Operations,
>=20
> Administration, and Maintenance (OAM) capabilities on Ethernet-like
>=20
> interfaces conformant to the Ethernet OAM functionality defined in
>=20
> the Ethernet in the First Mile (EFM) clauses of the Ethernet
>=20
> standards.  The Ethernet OAM functionality is complementary to the
>=20
> Simple Network Management Protocol (SNMP) in that it is focused on a
>=20
> small set of link-specific functions for directly connected Ethernet
>=20
> interfaces.  This document defines objects for controlling those link
>=20
> OAM functions and for providing results and status of the OAM
>=20
> functions to management entities.  [STANDARDS TRACK]
>=20
>=20
>=20
> This document is a product of the Ethernet Interfaces and Hub MIB
>=20
> Working Group of the IETF
>=20
>=20
>=20
> This is now a Proposed Standard Protocol.
>=20
>=20
>=20
> STANDARDS TRACK: This document specifies an Internet standards track
>=20
> protocol for the Internet community,and requests discussion=20
> and suggestions
>=20
> for improvements.Please refer to the current edition of the Internet
>=20
>  Official Protocol Standards (STD 1) for the standardization state and
>=20
>  status of this protocol.  Distribution of this memo is unlimited.
>=20
>=20
>=20
> This announcement is sent to the IETF list and the RFC-DIST list.
>=20
> Requests to be added to or deleted from the IETF distribution list
>=20
> should be sent to [email protected].  Requests to be
>=20
> added to or deleted from the RFC-DIST distribution list should
>=20
> be sent to [email protected].
>=20
>=20
>=20
> Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
>=20
> an EMAIL message to [email protected] with the message body=20
>=20
>=20
>=20
> help: ways_to_get_rfcs. For example:
>=20
>=20
>=20
>         To: [email protected]
>=20
>         Subject: getting rfcs
>=20
>=20
>=20
>         help: ways_to_get_rfcs
>=20
>=20
>=20
> Requests for special distribution should be addressed to either the
>=20
> author of the RFC in question, or to=20
> [email protected].  Unless
>=20
> specifically noted otherwise on the RFC itself, all RFCs are for
>=20
> unlimited distribution.
>=20
>=20
>=20
> Submissions for Requests for Comments should be sent to
>=20
> [email protected].  Please consult RFC 2223,=20
> Instructions to RFC
>=20
> Authors, for further information.
>=20
>=20
>=20
>=20
>=20
> The RFC Editor Team
>=20
> USC/Information Sciences Institute
>=20
>=20
>=20
> ...
>=20
>=20
>=20
>=20
>=20
> _______________________________________________
> Hubmib mailing list
> [email protected]
> https://www1.ietf.org/mailman/listinfo/hubmib
>=20