[GSMP] RFC 3604 on Requirements for Adding Optical Support to the General Switch Management Protocol version 3 (GSMPv3)

rfc-editor@rfc-editor.org Wed, 08 October 2003 07:05 UTC

Message-Id: <200310071811.h97IBFO07165@gamma.isi.edu>
To: IETF-Announce: ;
Cc: rfc-editor@rfc-editor.org, gsmp@ietf.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary=NextPart
Date: Tue, 07 Oct 2003 11:11:15 -0700
Subject: [GSMP] RFC 3604 on Requirements for Adding Optical Support to the General Switch Management Protocol version 3 (GSMPv3)
Sender: gsmp-admin@ietf.org
Errors-To: gsmp-admin@ietf.org
Precedence: bulk

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


        RFC 3604

        Title:      Requirements for Adding Optical Support to
                    the General Switch Management Protocol version 3
                    (GSMPv3)
        Author(s):  H. Khosravi, G. Kullgren, S. Shew, J. Sadler,
                    A. Watanabe
        Status:     Informational
        Date:       October 2003
        Mailbox:    hormuzd.m.khosravi@intel.com,
                    geku@nortelnetworks.com,
                    sdshew@nortelnetworks.com,
                    Jonathan.Sadler@tellabs.com,
                    atsushi@exa.onlab.ntt.co.jp
        Pages:      16
        Characters: 30805
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-gsmp-reqs-06.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3604.txt


This memo provides requirements for adding optical switching support
to the General Switch Management Protocol (GSMP).  It also contains
clarifications and suggested changes to the GSMPv3 specification.

This document is a product of the General Switch Management Protocol
Working Group of the IETF.

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  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/rfc3604.txt"><ftp://ftp.isi.edu/in-notes/rfc3604.txt>

[GSMP] RFC 3604 on Requirements for Adding Optica… rfc-editor