RFC 3498 on Definitions of Managed Objects for Synchronous Optical Network (SONET) Linear Automatic Protection Switching (APS) Architectures

rfc-editor@rfc-editor.org Sat, 08 March 2003 00:34 UTC

Message-Id: <200303072302.h27N2IZ22820@gamma.isi.edu>
To: IETF-Announce:;
Subject: RFC 3498 on Definitions of Managed Objects for Synchronous Optical Network (SONET) Linear Automatic Protection Switching (APS) Architectures
Cc: rfc-editor@rfc-editor.org, atommib@research.telecordia.com
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Fri, 07 Mar 2003 15:02:18 -0800
Sender: owner-ietf-announce@ietf.org
Precedence: bulk

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


        RFC 3498

        Title:      Definitions of Managed Objects
                    for Synchronous Optical Network (SONET)
                    Linear Automatic Protection Switching (APS)
                    Architectures
        Author(s):  J. Kuhfeld, J. Johnson, M. Thatcher
        Status:     Standards Track
        Date:       March 2003
        Mailbox:    jkuhfeld@redback.com, jeff@redback.com,
                    thatcher@redback.com
        Pages:      43
        Characters: 78701
        Updates/Obsoletes/SeeAlso:  None

        I-D Tag:    draft-ietf-atommib-sonetaps-mib-10.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3498.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 networks using
Synchronous Optical Network (SONET) linear Automatic Protection
Switching (APS) architectures.

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 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.

ftp://ftp.isi.edu/in-notes/rfc3498.txt"><ftp://ftp.isi.edu/in-notes/rfc3498.txt>

RFC 3498 on Definitions of Managed Objects for Sy… rfc-editor