RE: RFC 3621 on Power Ethernet MIB

The Power Ethernet MIB RFC was released! A nice holidays present, completing the previous stage of the WG Charter. 

I would like to extend my specials thanks and congratulations to Avi Berger, who was the main editor of the MIB, and brought a tremendous contribution to the successful completion of this work.

Dan

Dan Romascanu,
Chair, IETF Ethernet Interfaces and Hub MIB WG


> -----Original Message-----
> From: [email protected] [mailto:[email protected]]On 
> Behalf Of [email protected]
> Sent: 24 December, 2003 10:48 PM
> To: IETF-Announce; @[email protected]
> Cc: [email protected]; [email protected]
> Subject: [Hubmib] RFC 3621 on Power Ethernet MIB
> 
> 
> 
> A new Request for Comments is now available in online RFC libraries.
> 
> 
>         RFC 3621
> 
>         Title:      Power Ethernet MIB
>         Author(s):  A. Berger, D. Romascanu
>         Status:     Standards Track
>         Date:       December 2003
>         Mailbox:    [email protected], [email protected]
>         Pages:      20
>         Characters: 37294
>         Updates/Obsoletes/SeeAlso:    None
> 
>         I-D Tag:    draft-ietf-hubmib-power-ethernet-mib-08.txt
> 
>         URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3621.txt
> 
> 
> This memo defines a portion of the Management Information Base (MIB)
> for use with network management protocols in the Internet community.
> This document proposes an extension to the Ethernet-like Interfaces
> MIB with a set of objects for managing Power Sourcing Equipment
> (PSE).
> 
> This document is a product of the Ethernet Interfaces and Hub MIB
> Working Group of the IETF.
> 
> This is now a Proposed Standard Protocol.
> 
> 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 [email protected].  Requests to be
> added to or deleted from the RFC-DIST distribution list should
> be sent to [email protected].
> 
> Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
> an EMAIL message to [email protected] with the message body 
> help: ways_to_get_rfcs.  For example:
> 
>         To: [email protected]
>         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 
> [email protected].  Unless
> specifically noted otherwise on the RFC itself, all RFCs are for
> unlimited distribution.echo 
> Submissions for Requests for Comments should be sent to
> [email protected].  Please consult RFC 2223, 
> Instructions to RFC
> Authors, for further information.
> 
> 
> Joyce K. Reynolds and Sandy Ginoza
> USC/Information Sciences Institute
> 
> ...
> 
> Below is the data which will enable a MIME compliant Mail Reader 
> implementation to automatically retrieve the ASCII version
> of the RFCs.
>