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