RE: RFC 4502 on Remote Network MonitoringManagement Information Base Version 2

Congratulations. This is indeed good work and an important standard. 

Dan

 
 

> -----Original Message-----
> From: Andy Bierman [mailto:[email protected]] 
> Sent: Tuesday, May 23, 2006 4:46 AM
> To: [email protected]
> Cc: [email protected]
> Subject: Re: [RMONMIB] RFC 4502 on Remote Network 
> MonitoringManagement Information Base Version 2
> 
> [email protected] wrote:
> > A new Request for Comments is now available in online RFC libraries.
> > 
> 
> Finally!!!!
> 
> I'd like to thank the WG, the RFC Editor staff, and 
> especially Steve Waldbusser for all the hard work it took to 
> publish this document.
> 
> thanks,
> Andy
> 
> 
> >         
> >         RFC 4502
> > 
> >         Title:      Remote Network Monitoring Management 
> Information 
> >                     Base Version 2 
> >         Author:     S. Waldbusser
> >         Status:     Standards Track
> >         Date:       May 2006
> >         Mailbox:    [email protected]
> >         Pages:      142
> >         Characters: 290816
> >         
> > 
> >         I-D Tag:    draft-ietf-rmonmib-rmon2-v2-05.txt
> > 
> >         URL:        http://www.rfc-editor.org/rfc/rfc4502.txt
> > 
> > This document defines a portion of the Management Information Base 
> > (MIB) for use with network management protocols in TCP/IP-based 
> > internets.  In particular, it defines objects for managing remote 
> > network monitoring devices.
> > 
> > This document obsoletes RFC 2021, updates RFC 3273, and 
> contains a new 
> > version of the RMON2-MIB module.  [STANDARDS TRACK]
> > 
> > This document is a product of the Remote Network Monitoring Working 
> > Group of the IETF.
> > 
> > This is now a Draft Standard Protocol.
> > 
> > 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 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.
> > 
> > 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
> > 
> > ...
> > 
> > 
> > 
> > _______________________________________________
> > RMONMIB mailing list
> > [email protected]
> > https://www1.ietf.org/mailman/listinfo/rmonmib
> > 
> > 
> 
> 
> _______________________________________________
> RMONMIB mailing list
> [email protected]
> https://www1.ietf.org/mailman/listinfo/rmonmib
>