RFC 2558 on SONET/SDH Objects

RFC Editor <rfc-ed@ISI.EDU> Thu, 01 April 1999 01:25 UTC

Received: by ietf.org (8.9.1a/8.9.1a) id UAA06268 for ietf-123-outbound.10@ietf.org; Wed, 31 Mar 1999 20:25:02 -0500 (EST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA06107 for <all-ietf@ietf.org>; Wed, 31 Mar 1999 20:11:55 -0500 (EST)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id RAA04492; Wed, 31 Mar 1999 17:11:56 -0800 (PST)
Message-Id: <199904010111.RAA04492@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2558 on SONET/SDH Objects
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Wed, 31 Mar 1999 17:11:56 -0800
From: RFC Editor <rfc-ed@ISI.EDU>

A new Request for Comments is now available in online RFC libraries.


        RFC 2558: 

        Title:	    Definitions of Managed Objects
                    for the SONET/SDH Interface Type
	Author(s):  K. Tesink
        Status:     Proposed Standard
	Date:       March 1999
        Mailbox:    kaj@research.telcordia.com
	Pages:      74
        Characters: 138550
        Obsoletes:  1595
        I-D Tag:    draft-ietf-atommib-sonetng-05.txt

        URL:        ftp://ftp.isi.edu/in-notes/rfc2558.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 [24][25].

This document is a product of the AToM MIB Working Group of the IETF.

This is now a Proposed 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 Alegre Ramos
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.
ftp://ftp.isi.edu/in-notes/rfc2558.txt"><ftp://ftp.isi.edu/in-notes/rfc2558.txt>