One document matched: draft-rfced-info-ipsilon-gsmp2-00.txt

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


        RFC 2297:
 
        Title:      Ipsilon's General Switch Management Protocol
                    Specification Version 2.0
        Author(s):  P. Newman, W. Edwards, R. Hinden, E. Hoffman,
                    F. Ching Liaw, T. Lyon, G. Minshall
        Status:     Informational
        Date:       March 1998
        Mailbox:    pn@ipsilon.com, texas@sprintcorp.com,
                    hinden@ipsilon.com, hoffman@ipsilon.com,
                    fong@coppercom.com, pugs@ipsilon.com,
                    minshall@fiberlane.com
        Pages:      109
        Characters: 280484
        Updates:    2297

        URL:        ftp://ftp.isi.edu/in-notes/rfc2297.txt


This memo specifies enhancements to the General Switch Management
Protocol (GSMP) [RFC1987]. The major enhancement is the addition of
Quality of Service (QoS) messages. Other improvements have been made
to the protocol resulting from operational experience. GSMP is a
general purpose protocol to control an ATM switch. It allows a
controller to establish and release connections across the switch; add
and delete leaves on a multicast connection; manage switch ports;
request configuration information; and request statistics.

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@ISI.EDU.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@ISI.EDU with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@ISI.EDU
        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@ISI.EDU.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@ISI.EDU.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Alegre Ramos
USC/Information Sciences Institute