idnits 2.17.1 draft-ietf-snmpv3-update-mib-07.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 STD 62 4 RFC 3418 6 Title: Management Information Base (MIB) for the Simple 7 Network Management Protocol (SNMP) 8 Author(s): R. Presuhn, Ed. 9 Status: Standards Track 10 Date: December 2002 11 Mailbox: randy_presuhn@bmc.com 12 Pages: 26 13 Characters: 49096 14 Obsoletes: 1907 15 See Also: STD 62 17 I-D Tag: draft-ietf-snmpv3-update-mib-07.txt 19 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3418.txt 21 This document defines managed objects which describe the behavior of 22 a Simple Network Management Protocol (SNMP) entity. This document 23 obsoletes RFC 1907, Management Information Base for Version 2 of the 24 Simple Network Management Protocol (SNMPv2). 26 This document is a product of the SNMPv3 Working Group of the IETF. 28 This is now a Standard Protocol. 30 This document specifies an Internet standards track protocol for 31 the Internet community, and requests discussion and suggestions 32 for improvements. Please refer to the current edition of the 33 "Internet Official Protocol Standards" (STD 1) for the 34 standardization state and status of this protocol. Distribution 35 of this memo is unlimited. 37 This announcement is sent to the IETF list and the RFC-DIST list. 38 Requests to be added to or deleted from the IETF distribution list 39 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 40 added to or deleted from the RFC-DIST distribution list should 41 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 43 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 44 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 45 help: ways_to_get_rfcs. For example: 47 To: rfc-info@RFC-EDITOR.ORG 48 Subject: getting rfcs 50 help: ways_to_get_rfcs 52 Requests for special distribution should be addressed to either the 53 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 54 specifically noted otherwise on the RFC itself, all RFCs are for 55 unlimited distribution.echo 56 Submissions for Requests for Comments should be sent to 57 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 58 Authors, for further information.