draft-ietf-gsmp-applicability-02.txt   rfc3294.txt 
INTERNET DRAFT Avri Doria
GSMP Working Group Kenneth Sundell
Informational Track Nortel Networks
August 2001
General Switch Management Protocol Applicability Network Working Group A. Doria
Request for Comments: 3294 Lulea University of Technology
<draft-ietf-gsmp-applicability-02.txt> Category: Informational K. Sundell
Nortel Networks
June 2002
This document is an Internet-Draft and is in full conformance with General Switch Management Protocol (GSMP) Applicability
all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Status of this Memo
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six This memo provides information for the Internet community. It does
months and may be updated, replaced, or obsoleted by other not specify an Internet standard of any kind. Distribution of this
documents at any time. It is inappropriate to use Internet- memo is unlimited.
Drafts as reference material or to cite them other than as "work
in progress."
The list of current Internet-Drafts can be accessed at Copyright Notice
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at Copyright (C) The Internet Society (2002). All Rights Reserved.
http://www.ietf.org/shadow.html.
Abstract Abstract
This memo provides an overview of the GSMP protocol and includes This memo provides an overview of the GSMP (General Switch Management
information relating to its deployment in a IP network in an MPLS Protocol) and includes information relating to its deployment in a IP
environment. It does not discuss deployment in an ATM nework or network in an MPLS environment. It does not discuss deployment in an
in a raw ethernet configuration. ATM (Asynchronous Transfer Mode) network or in a raw ethernet
configuration.
1. Overview 1. Overview
The General Switch Management Protocol (GSMP) has been available The General Switch Management Protocol (GSMP) has been available to
to the IETF community for several years now as informational the IETF community for several years now as informational RFCs. Both
RFC's. Both GSMPv1.1 released in March 1996 as RFC1987 [2], and GSMPv1.1 (released in March 1996 as RFC 1987 [2]) and GSMPv2.0
GSMPv2.0 released in August 1998 as RFC2297 [3] are available. (released in August 1998 as RFC 2297 [3]) are available. Several
Several vendors have implemented GSMPv1.1. vendors have implemented GSMPv1.1.
In V1.1 and V2 GSMP was intended only for use with ATM switches. In V1.1 and V2 GSMP was intended only for use with ATM switches.
During the course of the last two years, the GSMP working group During the course of the last two years, the GSMP working group has
has decided to expand the purview of GSMP to the point where it decided to expand the purview of GSMP to the point where it can be
can be used to control a number of different kinds of switch and used to control a number of different kinds of switch and can thus
can thus live up to what its name indicates; a general switch live up to what its name indicates; a general switch management
management protocol. To do this, commands and arguments needed to protocol. To do this, commands and arguments needed to be
be generalised, with sections added discussing the manner in which generalised and sections needed to be added, discussing the manner in
the generalised protocol could be applied to specific kinds of which the generalised protocol could be applied to specific kinds of
switches and port types. In short the protocol has gone through switches and port types. In short, the protocol has gone through
major changes in the last 24 months. major changes in the last 24 months.
GSMP provides an interface that can be used to separate the data GSMP provides an interface that can be used to separate the data
forwarder from the routing and other control plane protocols such forwarder from the routing and other control plane protocols such as
as LDP. As such it allows service providers to move away from LDP. As such it allows service providers to move away from
monolithic systems that bundle control plane and data plane into a monolithic systems that bundle the control plane and the data plane
single tightly coupled system - usually in a single chassis. into a single tightly coupled system - usually in a single chassis.
Separating the control components from the forwarding components Separating the control components from the forwarding components and
and using GSMP for switch management, enables service providers to using GSMP for switch management, enables service providers to create
create multi-service systems composed of various vendors multi-service systems composed of various vendors equipment. It also
equipment. It also allows for a more dynamic means of adding allows for a more dynamic means of adding services to their networks.
services to their networks.
The IETF GSMP working group was established in the routing area The IETF GSMP working group was established in the routing area
because GSMP was being seen as an optional part of the MPLS because GSMP was being seen as an optional part of the MPLS solution.
solution. In a MPLS system, it is possible to run the routing In a MPLS system, it is possible to run the routing protocols and
protocols and label distribution protocols on one system while label distribution protocols on one system while passing data across
passing data across a generic switch, e.g. an ATM switch. GSMP a generic switch, e.g., an ATM switch. GSMP provides the switch
provides the switch resource management mechanism needed in such a resource management mechanism needed in such a scenario.
scenario.
GSMP has also been selected by the Multiservice Switching GSMP has also been selected by the Multiservice Switching Forum (MSF)
Forum(MSF) as its protocol of choice for the Switch Control as its protocol of choice for the Switch Control Interface identified
Interface identified in their architecture. The MSF is an in their architecture. The MSF is an industry forum which, among its
industry forum, which among its activities establishes their activities establishes their member's requirements and then works
member's requirements and then works with the appropriate with the appropriate standards bodies to foster their goals. In the
standards bodies to foster their goals. In the case of GSMP, the case of GSMP, the MSF presented the IETF GSMP Working Group with a
MSF presented the IETF GSMP Working Group with a set of set of requirements for GSMP. The working group has made a
requirements for GSMP. The working group has made a determined determined effort to comply with those requirements in its
effort to comply with those requirements in its specifications. specifications.
2. GSMP V3 Document Set 2. GSMP V3 Document Set
The current version of GSMP is documented in 3 documents: The current version of GSMP is documented in 3 documents:
- GSMP: General Switch Management protocol V3 [5] - GSMP: General Switch Management protocol V3 [5]
- GSMP-ENCAPS: GSMP Packet Encapsulations for ATM, Ethernet - GSMP-ENCAPS: General Switch Management Protocol (GSMP) Packet
and TCP[4] Encapsulations for Asynchronous Transfer Mode (ATM), Ethernet and
Transmission Control Protocol (TCP) [4]
- GSMP-MIB: Definitions of Managed Objects for the General - GSMP-MIB: Definitions of Managed Objects for the General Switch
Switch Management Protocol [1] Management Protocol [1]
3. General Description 3. General Description
The General Switch Management Protocol V3 (GSMPv3) [5], is a The General Switch Management Protocol V3 (GSMPv3) [5], is a general
general purpose protocol to control a label switch. GSMP allows purpose protocol to control a label switch. GSMP allows a
a controller to establish and release connections across the controller to establish and release connections across the switch;
switch; add and delete leaves on a multicast connection; add and delete leaves on a multicast connection; reserve
reserve resources; manage switch ports; request configuration resources; manage switch ports; request configuration information;
information; and request statistics. It also allows the switch and request statistics. It also allows the switch to inform the
to inform the controller of asynchronous events such as a link controller of asynchronous events such as a link going down. The
going down. The GSMPv3 protocol is asymmetric, the controller GSMPv3 protocol is asymmetric, the controller being the master and
being the master and the switch being the slave. the switch being the slave.
A physical switch can be partitioned into many virtual switches. A physical switch can be partitioned into many virtual switches.
GSMPv3 does not provide support for defining switch partitions. GSMPv3 does not provide support for defining switch partitions.
GSMPv3 treats a virtual switch as if it were a physical switch. GSMPv3 treats a virtual switch as if it were a physical switch.
GSMPv3 may be transported in three ways: GSMPv3 may be transported in three ways:
- GSMPv3 operation across an IP network is specified. - GSMPv3 operation across an IP network is specified.
- GSMPv3 operation across an ATM virtual channel is - GSMPv3 operation across an ATM virtual channel is specified.
specified.
- GSMPv3 operation across an Ethernet link is specified. - GSMPv3 operation across an Ethernet link is specified.
Other encapsulations are possible, but have not been defined. Other encapsulations are possible, but have not been defined.
Encapsulations are defined in [4]. Encapsulations are defined in [4].
A label switch is a frame or cell switch that supports connection A label switch is a frame or cell switch that supports connection
oriented switching using the exact match forwarding algorithm oriented switching using the exact match forwarding algorithm
based on labels attached to incoming cells or frames. based on labels attached to incoming cells or frames.
A label switch may support multiple label types, however, each
switch port can support only one label type. The label type
supported by a given port is indicated in a port configuration
message. Connections may be established between ports A label switch may support multiple label types. However, each
supporting different label types using the adaptation methods. switch port can support only one label type. The label type
GSMPv3 supports TLV labels similar to those defined in MPLS. supported by a given port is indicated in a port configuration
Examples of labels which are defined include ATM, Frame Relay, message. Connections may be established between ports supporting
DS1, DS3, E1, E3, MPLS Generic Labels and MPLS FECs. different label types using the adaptation methods. GSMPv3
supports TLV labels similar to those defined in MPLS. Examples of
labels which are defined include ATM, Frame Relay, DS1, DS3, E1,
E3, MPLS Generic Labels and MPLS FECs.
A connection across a switch is formed by connecting an incoming A connection across a switch is formed by connecting an incoming
labelled channel to one or more outgoing labelled channels. labelled channel to one or more outgoing labelled channels.
Connections are generally referenced by the input port on which Connections are generally referenced by the input port on which
they arrive and the label values of their incoming labelled they arrive and the label values of their incoming labelled
channel. In some messages connections are referenced by the channel. In some messages, connections are referenced by the
output port. output port.
GSMPv3 supports point-to-point and point-to-multipoint GSMPv3 supports point-to-point and point-to-multipoint connections.
connections. A multipoint-to-point connection is specified by A multipoint-to-point connection is specified by establishing
establishing multiple point-to-point connections each of which multiple point-to-point connections, each of which specifies the
specifies the same output label. A multipoint-to-multipoint same output label. A multipoint-to-multipoint connection is
connection is specified by establishing multiple point-to- specified by establishing multiple point-to-multipoint connections
multipoint connections each of which specifies a different each of which specifies a different input label with the same
input label with the same output labels. output labels.
In general a connection is established with a certain quality of In general a connection is established with a certain quality of
service (QoS). GSMPv3 includes a default QoS Configuration and service (QoS). GSMPv3 includes a default QoS Configuration and
additionally allows the negotiation of alternative, optional additionally allows the negotiation of alternative, optional QoS
QoS configurations. The default QoS Configuration includes configurations. The default QoS Configuration includes three QoS
three QoS Models: a default service model, a simple priority Models: a default service model, a simple priority model and a QoS
model and a QoS profile model. GSMPv3 also supports the profile model. GSMPv3 also supports the reservation of resources
reservation of resources when the labels are not yet known. when the labels are not yet known. This ability can be used in
This ability can be used in support of MPLS. support of MPLS.
GSMP contains an adjacency protocol. The adjacency protocol is GSMP contains an adjacency protocol. The adjacency protocol is used
used to synchronise state across the link, to negotiate which to synchronise states across the link, to negotiate which version
version of the GSMP protocol to use, to discover the identity of the GSMP protocol to use, to discover the identity of the
of the entity at the other end of a link, and to detect when it entity at the other end of a link, and to detect when it changes.
changes.
3.1 Switch Partitioning 3.1 Switch Partitioning
In GSMPv3 switch partitioning is static and occurs prior to In GSMPv3 switch partitioning is static and occurs prior to running
running the protocol. The partitions of a physical switch are the protocol. The partitions of a physical switch are isolated from
isolated from each other by the implementation and the controller each other by the implementation and the controller assumes that the
assumes that the resources allocated to a partition are at all resources allocated to a partition are at all times available to that
times available to that partition and only to that partition. A partition and only that partition. A partition appears to its
partition appears to its controller as a physical label switch. controller as a physical label switch. The resources allocated to a
The resources allocated to a partition appear to the controller as partition appear to the controller as if they were the actual
if they were the actual physical resources of a physical switch. physical resources of a physical switch. For example if the
For example if the bandwidth of a port is divided among several bandwidth of a port is divided among several partitions, each
partitions, each partition would appear to the controller to have partition would appear to the controller to have its own independent
its own independent port with its fixed set or resources. port with its fixed set of resources.
GSMPv3 controls a partitioned switch through the use of a GSMPv3 controls a partitioned switch through the use of a partition
partition identifier that is carried in every GSMPv3 message. Each identifier that is carried in every GSMPv3 message. Each partition
partition has a one-to-one control relationship with its own has a one-to-one control relationship with its own logical controller
logical controller entity (which in the remainder of the document entity (which in the remainder of the document is referred to simply
is referred to simply as a controller) and GSMPv3 independently as a controller) and GSMPv3 independently maintains adjacency between
maintains adjacency between each controller-partition pair. each controller-partition pair.
3.2 Switch and controller interactions 3.2 Switch and controller interactions
Multiple switches may be controlled by a single controller using Multiple switches may be controlled by a single controller using
multiple instantiations of the protocol over separate control multiple instantiations of the protocol over separate control
connections. connections.
Alternatively, multiple controllers can control a single switch. Alternatively, multiple controllers can control a single switch.
Each controller would establish a control connection to the switch Each controller would establish a control connection to the switch
using the adjacency protocol. The adjacency mechanism maintains a using the adjacency protocol. The adjacency mechanism maintains a
state table indicating the control connections that are being state table indicating the control connections that are being
maintained by the same partition. The switch provides information maintained by the same partition. The switch provides information to
to the controller group about the number and identity of the the controller group about the number and identity of the attached
attached controllers. It does nothing, however, to co-ordinate controllers. It does nothing, however, to co-ordinate the activities
the activities of the controllers, and will execute all commands of the controllers, and will execute all commands as they are
as they are received. It is the controller group's responsibility received. It is the controller group's responsibility to co-ordinate
to co-ordinate its use of the switch. This mechanism is most its use of the switch. This mechanism is most commonly used for
commonly used for controller redundancy and load sharing. controller redundancy and load sharing. Definition of the mechanism
Definition of the mechanism by which controllers use to co- by which controllers use to co-ordinate their control is not within
ordinate their control is not within GSMPv3's scope. GSMPv3's scope.
3.3 Service support 3.3 Service support
All GSMPv3 switches support the default QoS Configuration. A All GSMPv3 switches support the default QoS Configuration. A GSMPv3
GSMPv3 switch may additionally support one or more alternative QoS switch may additionally support one or more alternative QoS
Configurations. GSMP includes a negotiation mechanism that allows Configurations. GSMP includes a negotiation mechanism that allows a
a controller to select from the QoS configurations that a switch controller to select from the QoS configurations that a switch
supports. supports.
The default QoS Configuration includes three models: The default QoS Configuration includes three models:
The Service Model is based on service definitions found The Service Model is based on service definitions found external
external to GSMP such as in CR-LDP, Integrated Services or to GSMP such as in CR-LDP, Integrated Services or ATM Service
ATM Service Categories. Each connection is assigned a Categories. Each connection is assigned a specific service
specific service that defines the handling of the that defines the handling of the connection by the switch.
connection by the switch. Additionally, traffic parameters Additionally, traffic parameters and traffic controls may be
and traffic controls may be assigned to the connection assigned to the connection depending on the assigned service.
depending on the assigned service.
In the Simple Abstract Model a connection is assigned a In the Simple Abstract Model a connection is assigned a priority
priority when it is established. It may be assumed that for when it is established. It may be assumed that for connections
connections that share the same output port, an cell or that share the same output port, a cell or frame on a
frame on a connection with a higher priority is much more connection with a higher priority is much more likely to exit
likely to exit the switch before a cell or frame on a the switch before a cell or frame on a connection with a lower
connection with a lower priority if they are both in the priority if they are both in the switch at the same time.
switch at the same time.
The QoS Profile Model provides a simple mechanism that allows The QoS Profile Model provides a simple mechanism that allows QoS
QoS semantics defined externally to GSMP to be assigned to semantics defined externally to GSMP to be assigned to
connections. Each profile is an opaque indicator that has connections. Each profile is an opaque indicator that has been
been predefined in the controller and in the switch. predefined in the controller and in the switch.
4. Summary of Message Set 4. Summary of Message Set
The following table gives a summary of the messages defined in The following table gives a summary of the messages defined in this
this version of the specification. It also makes a recommendation version of the specification. It also makes a recommendation of the
of the minimal set of messages that should be supported in an MPLS minimal set of messages that should be supported in an MPLS
environment. These messages will be labelled as "Required", environment. These messages will be labelled as "Required", though
though the service provided by the other messages are essential the service provided by the other messages are essential for the
for the operation of carrier quality controller/ switch operation of carrier quality controller/switch operations. GSMPv1.1
operations. GSMPv1.1 or GSMPv2 commands that are no longer or GSMPv2 commands that are no longer support are marked as
support are marked as "Obsolete" and should no longer be used. "Obsolete" and should no longer be used.
4.1 Messages Table 4.1 Messages Table
Message Name Message Number Status Message Name Message Number Status
Connection Management Messages Connection Management Messages
Add Branch .......................16 Required Add Branch........................16 Required
ATM Specific - VPC............26 ATM Specific - VPC............26
Delete Tree.......................18 Delete Tree.......................18
Verify Tree.......................19 Obsoleted Verify Tree.......................19 Obsoleted
Delete All Input..................20 Delete All Input..................20
Delete All Output.................21 Delete All Output.................21
Delete Branches...................17 Required Delete Branches...................17 Required
Move Output Branch............... 22 Move Output Branch................22
ATM Specific - VPC............27 ATM Specific - VPC............27
Move Input Branch.................23 Move Input Branch.................23
ATM Specific - VPC............28 ATM Specific - VPC............28
Port Management Messages Port Management Messages
Port Management...................32 Required Port Management...................32 Required
Label Range.......................33 Label Range.......................33
State and Statistics Messages State and Statistics Messages
Connection Activity...............48 Connection Activity...............48
Port Statistics...................49 Required Port Statistics...................49 Required
Connection Statistics.............50 Connection Statistics.............50
QoS Class Statistics..............51 Reserved QoS Class Statistics..............51 Reserved
Report Connection State...........52 Report Connection State...........52
Configuration Messages Configuration Messages
Switch Configuration..............64 Required Switch Configuration..............64 Required
Port Configuration................65 Required Port Configuration................65 Required
All Ports Configuration...........66 Required All Ports Configuration...........66 Required
Service Configuration.............67 Service Configuration.............67
Reservation Messages Reservation Messages
Reservation Request.............. 70 Required Reservation Request...............70 Required
Delete Reservation................71 Required Delete Reservation................71 Required
Delete All Reservations...........72 Delete All Reservations...........72
Event Messages Event Messages
Port Up...........................80 Port Up...........................80
Port Down.........................81 Port Down.........................81
Invalid Label.....................82 Invalid Label.....................82
New Port..........................83 New Port..........................83
Dead Port.........................84 Dead Port.........................84
Abstract and Resource Model Extension Messages Abstract and Resource Model Extension Messages
Reserved.Message Range.............200-249 Reserved.Message Range.........200-249
Adjacency Protocol....................10 Required Adjacency Protocol.................10 Required
5. Security Considerations 5. Security Considerations
The security of GSMP's TCP/IP control channel has been addressed The security of GSMP's TCP/IP control channel has been addressed in
in [4]. For all uses of GSMP over an IP network it is REQUIRED [4]. For all uses of GSMP over an IP network, it is REQUIRED that
that GSMP be run over TCP/IP using the security considertaions GSMP be run over TCP/IP using the security considerations discussed
discussed in [4]. in [4].
References References
[1] [GSMP-MIB] Sjostrand, H., "Definitions of Managed Objects [1] Sjostrand, H., Buerkle, J. and B. Srinivasan, "Definitions of
for the General Switch Management Protocol Managed Objects for the General Switch Management Protocol
(GSMP)," Internet-Draft draft-ietf-gsmp-mib-02, (GSMP)", RFC 3295, June 2002.
July 2000. work in progress
[2] [GSMPv1.1] Newman, P, Edwards, W., Hinden, R., Hoffman, E. [2] Newman, P., Edwards, W., Hinden, R., Hoffman, E., Ching Liaw, F.,
Ching Liaw, F., Lyon, T. and Minshall, G., Lyon, T. and Minshall, G., "Ipsilon's General Switch Management
"Ipsilon's General Switch Management Protocol Protocol Specification Version 1.1", RFC 1987, August 1996.
Specification," Version 1.1, RFC 1987, August
1996.
[3] [GSMPv2] Newman, P, Edwards, W., Hinden, R., Hoffman, [3] Newman, P., Edwards, W., Hinden, R., Hoffman, E., Ching Liaw, F.,
E., Ching Liaw, F., Lyon, T. and Minshall, G., Lyon, T. and G. Minshall, "Ipsilon's General Switch Management
"Ipsilon's General Switch Management Protocol Protocol Specification Version 2.0", RFC 2297, March 1998.
Specification," Version 2.0, RFC 2397, March
1998.
[4] [GSMP-ENCAPS] T. Worster, "GSMP Packet Encapsulations for [4] Worster, T., Doria, A. and J. Buerkle, "General Switch Management
ATM, Ethernet and TCP," Internet-Draft draft- Protocol (GSMP) Packet Encapsulations for Asynchronous Transfer
ietf-gsmp-encaps-02, July 2000. work in Mode (ATM), Ethernet and Transmission Control Protocol (TCP)",
progress RFC 3293, June 2002.
[5] [GSMP] Doria, A, Sundell, K, Hellstrand, F, Worster, [5] Doria, A., Sundell, K., Hellstrand, F. and T. Worster, "General
T, "General switch Management Protocol V3," Switch Management Protocol (GSMP) V3", RFC 3292, June 2002.
Internet Draft draft-ietf-gsmp-06.txt, July
2000. work in progress
Authors' Addresses Authors' Addresses
Avri Doria Avri Doria
Nortel Networks Div. of Computer Communications
600 Technology Park Drive Lulea University of Technology
Billerica, MA S-971 87 Lulea
Phone: +1 401 663 5024 Sweden
avri@nortelnetworks.com
Kenneth Sundell Phone: +1 401 663 5024
Nortel Networks AB EMail: avri@acm.org
S:t Eriksgatan 115 A
P.O. Box 6701 Kenneth Sundell
SE-113 85 Stockholm Sweden Nortel Networks AB
ksundell@nortelnetworks.com S:t Eriksgatan 115 A
P.O. Box 6701
SE-113 85 Stockholm Sweden
EMail: sundell@nortelnetworks.com
Full Copyright Statement
Copyright (C) The Internet Society (2002). All Rights Reserved.
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.
 End of changes. 58 change blocks. 
260 lines changed or deleted 237 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/