idnits 2.17.1 draft-ietf-rmonmib-framework-05.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3577 5 Title: Introduction to the Remote Monitoring (RMON) 6 Family of MIB Modules 7 Author(s): S. Waldbusser, R. Cole, C. Kalbfleisch, 8 D. Romascanu 9 Status: Informational 10 Date: August 2003 11 Mailbox: waldbusser@nextbeacon.com, rgcole@att.com, 12 cwk@verio.net, dromasca@avaya.com 13 Pages: 31 14 Characters: 68551 15 Updates/Obsoletes/SeeAlso: None 17 I-D Tag: draft-ietf-rmonmib-framework-05.txt 19 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3577.txt 21 The Remote Monitoring (RMON) Framework consists of a number of 22 interrelated documents. This memo describes these documents and how 23 they relate to one another. 25 This document is a product of the Remote Network Monitoring Working 26 Group of the IETF. 28 This memo provides information for the Internet community. It does 29 not specify an Internet standard of any kind. Distribution of this 30 memo is unlimited. 32 This announcement is sent to the IETF list and the RFC-DIST list. 33 Requests to be added to or deleted from the IETF distribution list 34 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 35 added to or deleted from the RFC-DIST distribution list should 36 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 38 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 39 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 40 help: ways_to_get_rfcs. For example: 42 To: rfc-info@RFC-EDITOR.ORG 43 Subject: getting rfcs 45 help: ways_to_get_rfcs 47 Requests for special distribution should be addressed to either the 48 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 49 specifically noted otherwise on the RFC itself, all RFCs are for 50 unlimited distribution.echo 51 Submissions for Requests for Comments should be sent to 52 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 53 Authors, for further information.