RE: RFC 4836 on Definitions of Managed Objects for IEEE802.3Medium Attachment Units (MAUs)

"Edward Beili" <[email protected]> Tue, 1 May 2007 17:04:59 +0300
Newsgroups gmane.ietf.hubmib
Message-ID <[email protected]>
Thank you Bert. I would also like to express my gratitude to Mike Heard, =
John Flick and Dan Romascanu for their help.

Regards,
-E.

> -----Original Message-----
> From: Wijnen, Bert (Bert) [mailto:[email protected]]=20
> Sent: Tuesday, May 01, 2007 11:56
> To: Hub Mib
> Subject: FW: [Hubmib] RFC 4836 on Definitions of Managed=20
> Objects for IEEE802.3Medium Attachment Units (MAUs)
>=20
> Congrats and many thanks (specifically to the editor and reviewers).=20
>=20
> Bert Wijnen
> Chair of the IETF HUBMIB WG
> -----Original Message-----
> From: [email protected] [mailto:[email protected]]
> Sent: Saturday, April 28, 2007 2:59 AM
> To: [email protected]; [email protected]
> Cc: [email protected]; [email protected]
> Subject: [Hubmib] RFC 4836 on Definitions of Managed Objects=20
> for IEEE 802.3Medium Attachment Units (MAUs)
>=20
>=20
> A new Request for Comments is now available in online RFC libraries.
>=20
>        =20
>         RFC 4836
>=20
>         Title:      Definitions of Managed Objects for=20
>                     IEEE 802.3 Medium Attachment Units (MAUs)=20
>         Author:     E. Beili
>         Status:     Standards Track
>         Date:       April 2007
>         Mailbox:    [email protected]
>         Pages:      67
>         Characters: 151012
>         Obsoletes:  RFC3636
>         See-Also:  =20
>=20
>         I-D Tag:    draft-ietf-hubmib-rfc3636bis-05.txt
>=20
>         URL:        http://www.rfc-editor.org/rfc/rfc4836.txt
>=20
> This document defines a portion of the Management Information Base
> (MIB) for use with network management protocols in the=20
> Internet community.  In particular, it defines objects for=20
> managing IEEE 802.3 Medium Attachment Units (MAUs).  This=20
> document obsoletes RFC 3636.
> It amends that specification by moving MAU type=20
> OBJECT-IDENTITY definitions and relevant textual conventions=20
> into a separate Internet Assigned Number Authority (IANA)=20
> maintained MIB module.  In addition, management information=20
> is added to enable support for Ethernet in the First Mile=20
> (EFM) and 10GBASE-CX4 MAUs.  [STANDARDS TRACK]
>=20
> This document is a product of the Ethernet Interfaces and Hub=20
> MIB Working Group of the IETF.
>=20
> This is now a Proposed Standard Protocol.
>=20
> STANDARDS TRACK: This document specifies an Internet=20
> standards track protocol for the Internet community,and=20
> requests discussion and suggestions for improvements.Please=20
> refer to the current edition of the Internet Official=20
> Protocol Standards (STD 1) for the standardization state and=20
> status of this protocol.  Distribution of this memo is unlimited.
>=20
> This announcement is sent to the IETF list and the RFC-DIST list.
> Requests to be added to or deleted from the IETF distribution=20
> list should be sent to [email protected].  Requests to be=20
> added to or deleted from the RFC-DIST distribution list=20
> should be sent to [email protected].
>=20
> Details on obtaining RFCs via FTP or EMAIL may be obtained by=20
> sending an EMAIL message to [email protected] with the=20
> message body=20
>=20
> help: ways_to_get_rfcs. For example:
>=20
>         To: [email protected]
>         Subject: getting rfcs
>=20
>         help: ways_to_get_rfcs
>=20
> Requests for special distribution should be addressed to=20
> either the author of the RFC in question, or to=20
> [email protected].  Unless specifically noted=20
> otherwise on the RFC itself, all RFCs are for unlimited distribution.
>=20
> Submissions for Requests for Comments should be sent to=20
> [email protected].  Please consult RFC 2223,=20
> Instructions to RFC Authors, for further information.
>=20
>=20
> The RFC Editor Team
> USC/Information Sciences Institute
>=20
> ...
>=20
>=20
>=20
> _______________________________________________
> Hubmib mailing list
> [email protected]
> https://www1.ietf.org/mailman/listinfo/hubmib
>=20
> _______________________________________________
> Hubmib mailing list
> [email protected]
> https://www1.ietf.org/mailman/listinfo/hubmib
>=20