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

Congratulations to the whole Working Group and to everybody involved
(including the IEEE 802.3 colleagues).=20

Dan


=20
=20

> -----Original Message-----
> From: Edward Beili [mailto:[email protected]]=20
> Sent: Tuesday, May 01, 2007 5:05 PM
> To: Wijnen, Bert (Bert)
> Cc: C. M. Heard; Romascanu, Dan (Dan); John Flick; Hub Mib
> Subject: RE: [Hubmib] RFC 4836 on Definitions of Managed=20
> Objects for IEEE802.3Medium Attachment Units (MAUs)
>=20
> Thank you Bert. I would also like to express my gratitude to=20
> Mike Heard, John Flick and Dan Romascanu for their help.
>=20
> Regards,
> -E.
>=20
> > -----Original Message-----
> > From: Wijnen, Bert (Bert) [mailto:[email protected]]
> > Sent: Tuesday, May 01, 2007 11:56
> > To: Hub Mib
> > Subject: FW: [Hubmib] RFC 4836 on Definitions of Managed=20
> Objects for=20
> > IEEE802.3Medium Attachment Units (MAUs)
> >=20
> > Congrats and many thanks (specifically to the editor and=20
> 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=20
> Objects for IEEE=20
> > 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 Internet=20
> > community.  In particular, it defines objects for managing=20
> IEEE 802.3=20
> > Medium Attachment Units (MAUs).  This document obsoletes RFC 3636.
> > It amends that specification by moving MAU type OBJECT-IDENTITY=20
> > definitions and relevant textual conventions into a=20
> separate Internet=20
> > Assigned Number Authority (IANA) maintained MIB module.  In=20
> addition,=20
> > management information is added to enable support for=20
> Ethernet in the=20
> > First Mile
> > (EFM) and 10GBASE-CX4 MAUs.  [STANDARDS TRACK]
> >=20
> > This document is a product of the Ethernet Interfaces and Hub MIB=20
> > Working Group of the IETF.
> >=20
> > This is now a Proposed Standard Protocol.
> >=20
> > STANDARDS TRACK: This document specifies an Internet=20
> standards track=20
> > protocol for the Internet community,and requests discussion and=20
> > suggestions for improvements.Please refer to the current edition of=20
> > the Internet Official Protocol Standards (STD 1) for the=20
> > standardization state and status of this protocol.  Distribution of=20
> > 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 list=20
> > should be sent to [email protected].  Requests to be=20
> added to or=20
> > deleted from the RFC-DIST distribution list should be sent to=20
> > [email protected].
> >=20
> > Details on obtaining RFCs via FTP or EMAIL may be obtained=20
> by sending=20
> > an EMAIL message to [email protected] with the message body
> >=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 either the=20
> > author of the RFC in question, or to [email protected]. =20
> > Unless specifically noted otherwise on the RFC itself, all RFCs are=20
> > for unlimited distribution.
> >=20
> > Submissions for Requests for Comments should be sent to=20
> > [email protected].  Please consult RFC 2223,=20
> Instructions to=20
> > 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
>=20