Definitions of Managed Objects for Synchronous Optical Network (SONET) Linear Automatic Protection Switching (APS) Architectures
draft-ietf-atommib-sonetaps-mib-10
The information below is for an old version of the document that is already published as an RFC.
| Document | Type |
This is an older version of an Internet-Draft that was ultimately published as RFC 3498.
|
|
|---|---|---|---|
| Authors | Jeff T. Johnson , Jim Kuhfeld , Michael A. Thatcher | ||
| Last updated | 2015-10-14 (Latest revision 2002-11-21) | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | Proposed Standard | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | (None) | |
| Document shepherd | (None) | ||
| IESG | IESG state | Became RFC 3498 (Proposed Standard) | |
| Action Holders |
(None)
|
||
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | Erik Nordmark | ||
| IESG note | |||
| Send notices to | <fayely98@hotmail.com> |
draft-ietf-atommib-sonetaps-mib-10
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.