RE: RFC 5066 on Ethernet in the First Mile Copper(EFMCu)Interfaces MIB

Bert,
Thanks for the guidance, comments and help you have provided during this =
long period.

I would also like to thank the hubmib group members, especially people =
mentioned in the Acknowledgments section of the rfc, namely (in =
alphabetical order):
    Udi Ashkenazi (Actelis)
    Mike Heard
    Alfred Hoenes (TR-Sys)
    Marina Popilov (Actelis)
    Mathias Riess (Infineon)
    Dan Romascanu (Avaya)
    Matt Squire (Hatteras)
    Bert Wijnen (Alcatel)

I'm now working on the G.Bond MIBs in ADSLMIB group =
(http://www.ietf.org/html.charters/adslmib-charter.html), providing =
management for the ITU-T G.998.x series xDSL bonding protocols. So, if =
you were unaware of this work, hop onto the adslmib mailing list.

Regards,
-E.

> -----Original Message-----
> From: WIJNEN, Bert (Bert) [mailto:[email protected]]=20
> Sent: Wednesday, November 21, 2007 10:59
> To: [email protected]
> Subject: FW: [Hubmib] RFC 5066 on Ethernet in the First Mile=20
> Copper(EFMCu)Interfaces MIB
>=20
> Congrats to the (now closed) WG for the final publication of=20
> our work. Special thanks to Edward Beili for his careful and=20
> meticulous work in the whole process and specifically in the=20
> final stages of the process.
>=20
> Bert Wijnen
> Chair of the IETF HUBMIB WG
>=20
> -----Original Message-----
> From: [email protected] [mailto:[email protected]]
> Sent: Wednesday, November 21, 2007 1:44 AM
> To: [email protected]; [email protected]
> Cc: [email protected]; [email protected]
> Subject: [Hubmib] RFC 5066 on Ethernet in the First Mile=20
> Copper (EFMCu)Interfaces MIB
>=20
>=20
> A new Request for Comments is now available in online RFC libraries.
>=20
>        =20
>         RFC 5066
>=20
>         Title:      Ethernet in the First Mile=20
>                     Copper (EFMCu) Interfaces MIB=20
>         Author:     E. Beili
>         Status:     Standards Track
>         Date:       November 2007
>         Mailbox:    [email protected]
>         Pages:      90
>         Characters: 193465
>         Updates/Obsoletes/SeeAlso:   None
>=20
>         I-D Tag:    draft-ietf-hubmib-efm-cu-mib-08.txt
>=20
>         URL:        http://www.rfc-editor.org/rfc/rfc5066.txt
>=20
> This document defines Management Information Base (MIB)=20
> modules for use
> with network management protocols in TCP/IP-based internets.
> This document describes extensions to the Ethernet-like Interfaces MIB
> and Medium Attachment Unit (MAU) MIB modules with a set of objects for
> managing Ethernet in the First Mile Copper (EFMCu) interfaces=20
> 10PASS-TS
> and 2BASE-TL, defined in IEEE Std 802.3ah-2004
> (note: IEEE Std 802.3ah-2004 has been integrated into IEEE Std 802.3-
> 2005).  In addition, a set of objects is defined, describing cross-
> connect capability of a managed device with multi-layer (stacked)
> interfaces, extending the stack management objects in the Interfaces
> Group MIB and the Inverted Stack Table MIB modules.  [STANDARDS TRACK]
>=20
> This document is a product of the Ethernet Interfaces and Hub MIB
> Working Group of the IETF.
>=20
> This is now a Proposed Standard Protocol.
>=20
> 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=20
> edition of the
> Internet  Official Protocol Standards (STD 1) for the standardization
> state and  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 list
> should be sent to [email protected].  Requests to be added to or
> deleted from the RFC-DIST distribution list 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 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 either the
> author of the RFC in question, or to=20
> [email protected].  Unless
> specifically noted otherwise on the RFC itself, all RFCs are for
> unlimited distribution.
>=20
> Submissions for Requests for Comments should be sent to
> [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
>=20
> _______________________________________________
> Hubmib mailing list
> [email protected]
> https://www1.ietf.org/mailman/listinfo/hubmib
>=20
>=20
> _______________________________________________
> Hubmib mailing list
> [email protected]
> https://www1.ietf.org/mailman/listinfo/hubmib
>=20