idnits 2.17.1 draft-ietf-atommib-rfc2558bis-01.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 3592 5 Title: Definitions of Managed Objects for the 6 Synchronous Optical Network/Synchronous Digital 7 Hierarchy (SONET/SDH) Interface Type 8 Author(s): K. Tesink 9 Status: Standards Track 10 Date: September 2003 11 Mailbox: kaj@research.telcordia.com 12 Pages: 73 13 Characters: 143588 14 Obsoletes: 2558 16 I-D Tag: draft-ietf-atommib-rfc2558bis-01.txt 18 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3592.txt 20 This memo defines a portion of the Management Information Base (MIB) 21 for use with network management protocols in TCP/IP-based internets. 22 In particular, it defines objects for managing Synchronous Optical 23 Network/Synchronous Digital Hierarchy (SONET/SDH) interfaces. This 24 document is a companion to the documents that define Managed Objects 25 for the DS1/E1/DS2/E2 and DS3/E3 Interface Types. 27 This memo replaces RFC 2558. Changes relative to RFC 2558 are 28 summarized in the MIB module's REVISION clause. 30 This document is a product of the AToM MIB Working Group of the IETF. 32 This is now a Draft Standard Protocol. 34 This document specifies an Internet standards track protocol for 35 the Internet community, and requests discussion and suggestions 36 for improvements. Please refer to the current edition of the 37 "Internet Official Protocol Standards" (STD 1) for the 38 standardization state and status of this protocol. Distribution 39 of this memo is unlimited. 41 This announcement is sent to the IETF list and the RFC-DIST list. 42 Requests to be added to or deleted from the IETF distribution list 43 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 44 added to or deleted from the RFC-DIST distribution list should 45 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 47 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 48 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 49 help: ways_to_get_rfcs. For example: 51 To: rfc-info@RFC-EDITOR.ORG 52 Subject: getting rfcs 54 help: ways_to_get_rfcs 56 Requests for special distribution should be addressed to either the 57 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 58 specifically noted otherwise on the RFC itself, all RFCs are for 59 unlimited distribution.echo 60 Submissions for Requests for Comments should be sent to 61 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 62 Authors, for further information.