RFC 3592 on Definitions of Managed Objects for the Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Interface Type
rfc-editor@rfc-editor.org Wed, 03 September 2003 23:35 UTC
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17022 for <ietf-announce-web-archive@odin.ietf.org>; Wed, 3 Sep 2003 19:35:11 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14) id 19uh5r-0002pO-2J for ietf-announce-list@asgard.ietf.org; Wed, 03 Sep 2003 19:31:19 -0400
Received: from ietf.org ([10.27.2.28]) by asgard.ietf.org with esmtp (Exim 4.14) id 19uh4l-0002iS-4J for all-ietf@asgard.ietf.org; Wed, 03 Sep 2003 19:30:11 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16525 for <all-ietf@ietf.org>; Wed, 3 Sep 2003 19:30:05 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19uh4j-0005CR-00 for all-ietf@ietf.org; Wed, 03 Sep 2003 19:30:09 -0400
Received: from gamma.isi.edu ([128.9.144.145]) by ietf-mx with esmtp (Exim 4.12) id 19uh4i-0005CN-00 for all-ietf@ietf.org; Wed, 03 Sep 2003 19:30:08 -0400
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6p2/8.11.2) with ESMTP id h83NU8N09000; Wed, 3 Sep 2003 16:30:08 -0700 (PDT)
Message-Id: <200309032330.h83NU8N09000@gamma.isi.edu>
To: IETF-Announce:;
Subject: RFC 3592 on Definitions of Managed Objects for the Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Interface Type
Cc: rfc-editor@rfc-editor.org, atommib@research.telcordia.com
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Wed, 03 Sep 2003 16:30:08 -0700
Sender: owner-ietf-announce@ietf.org
Precedence: bulk
A new Request for Comments is now available in online RFC libraries. RFC 3592 Title: Definitions of Managed Objects for the Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Interface Type Author(s): K. Tesink Status: Standards Track Date: September 2003 Mailbox: kaj@research.telcordia.com Pages: 73 Characters: 143588 Obsoletes: 2558 I-D Tag: draft-ietf-atommib-rfc2558bis-01.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3592.txt This memo 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 Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) interfaces. This document is a companion to the documents that define Managed Objects for the DS1/E1/DS2/E2 and DS3/E3 Interface Types. This memo replaces RFC 2558. Changes relative to RFC 2558 are summarized in the MIB module's REVISION clause. This document is a product of the AToM MIB Working Group of the IETF. This is now a Draft 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 IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG 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 RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. 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.