Current Meeting Report

2.7.2 General Switch Management Protocol (gsmp)

NOTE: This charter is a snapshot of the 54th IETF Meeting in Yokohama, Japan. It may now be out-of-date.

Last Modifield: 06/25/2002

G Kullgren <>
Kenneth Sundell <>
Sub-IP Area Director(s):
Scott Bradner <>
Bert Wijnen <>
Sub-IP Area Advisor:
Scott Bradner <>
Technical Advisor(s):
A. Mankin <>
Mailing Lists:
General Discussion:
To Subscribe:
In Body: subscribe (unsubscribe)
Description of Working Group:
The base General Switch Management Protocol (GSMPv3) protocol has been submitted to the IESG with the request that it become a proposed standard. Currently the GSMP protocol provides switch configuration control and reporting, port management, connection control, QoS and traffic engineering control and the reporting of statistics and asynchronous events for MPLS label switch devices, all either from or to a third party controller.

The working group is responsible for completing the standardization of the GSMP protocol by responding to protocol issues that arise during implementation of the current specifications.

Additionally, the working group is responsible for augmenting the protocol as follows:

- Support for Optical and Other Extensions and CCAMP Features

The architecture of some optical, TDM, spatial and other switch types makes the ability to remotely control the connection state of a switch important. GSMP has been designed especially for such remote control operations. GSMP is, however, currently lacking in the specific semantics necessary for switches with some new technologies, especially in the optical space. The WG will collect requirements and define solutions to support optical and other new switching technologies, compatibly with the common control and measurement protocols WG (CCAMP) work. This work will be done in cooperation with the other Sub IP Working groups involved in this area.

The extensions will include definition of new instances of "labels" (for instance lambda identifiers) as needed, to support the usage in the new technologies. They will also include definitions of port types, of service definitions and of traffic parameters.

- Switch Partitioning

The current version of GSMP is designed to work with a static switch partition. Recently, some regulatory environments (on multiple continents) have mandated multi-provider access to the same physical infrastructure. Therefore, this work should allow network operators to dynamically open their forwarders (optical, TDM, and other switch types) to multiple administrative domains of control. As a result, the WG will analyze requirements for dynamic switch partioning with GSMP and determine if GSMP should be extended to support them. This work would be to adapt GSMP to work with multiple partitions in which resource allocation is dynamic and variable between the switch partitions. This would be achieved by using available management tools, e.g. MIBs (possibly PIBs), as well as potential extensions to GSMP.

- Relationship to Forwarding and Control Element Separation

The WG will conduct a brief (one-meeting) analysis of the potential use of GSMP in mechanisms that allow third party network processors in switch architectures. The output will be an agreement of the likely scope for a distinct WG that might be using GSMP for this purpose.

Goals and Milestones:
Done  Define an IP encapsulation for GSMP messages
Done  Extend GSMP message types to allow support of non-ATM Label Switch devices
Done  Refine the support for QoS models in GSMP
Done  Define an approved GSMP MIB
Done  Define approved mechanisms for security and authentication in GSMP
Done  Produce a version of the GSMP which has the consensus required for entry onto the standards track.
Done  Analyze role of GSMP for control element separation and make recommendation as to a separate WG for extending GSMP for this
MAY 02  Document requirements for control of switches supporting optical, TDM and other CCAMP features
MAY 02  Document requirements for switch partitioning and determine whetherto recharter to extend GSMP capabilities to meet these
SEP 02  If requirements process has convinced ADs/IESG, produce GSMP extensions and MIBs to support dynamic switch partitioning
DEC 02  Submit GSMPv3 extensions to include control of switches supporting optical, TDM and other CCAMP features and any updates of the base spec for Proposed Standard
JUN 03  Submit GSMPv3, its extensions and MIBs for Draft Standard
JUN 03  Conclude Working Group
  • - draft-ietf-gsmp-dyn-part-reqs-01.txt
  • - draft-ietf-gsmp-reqs-02.txt
  • Request For Comments:
    RFC3292 PS General Switch Management Potocol(GSMP) V3
    RFC3293 PS GSMP Packet Encapsulations for ATM, Ethernet and TCP
    RFC3294 I General Switch Management Protocol Applicability
    RFC3295 PS Definitions of Managed Objects for the General Switch Management Protocol (GSMP)

    Current Meeting Report

    The GSMP meeting was chaired by Avri Doria and minutes were taken by Kohei Shiomoto 1. The agenda was reviewed and was approved by the meeting attendants.2. Requirements for adding optical support to GSMPv3 - draft-ietf-gsmp-reqs-02.txt was presented by Avri DoriaThe changes from 01 version include:- Sections are rearranged to fit the RFC format.- List of issues in Section 4 is detailed in appropriate part of document.- Switching capability information is addressed. ITU-T G.805 model is referenced to model transport signal multiplex hierarchy. G.803 for SDT/SONET, G.705 for PDH, G.872 for OTN.- Port location identifier is extended. Bay/Shelf/Slot/Port is encoded.- Encapsulation. Non raw-IP encapsulation should be supported to meet G.ASTN CCI-interface requirements.- Bi-directional connection replacement should be done. Add Branch message must be changed to allow B and R flags be used in at the same time.There was no objection against issuing a last call on the requirements doucment. Everyone was encouraged to read the draft and to send comments to the list if something is missing for the last call.3. Extensions for optical burst switch - draft-choi-gsmp-optical-extension-00.txt was presented by Jun Kyun ChoiThis was a proposal for: - Extensions for GSMP for burst switching in optical domain - Reservation Message is extended - New service identifier OBS service ID with parameters of offset time and burst lengthThese changes are motivated by: - Data optical burst switching using on-the-fly resource reservation. - Real-time on-demand reservation. - Limitation optical device (buffer, tuning delay, switch size, switch delay)Avri asked the floor whether (1) this draft should be merged into draft-ietf-gsmp-reqs-02.txt? or(2) this draft should be adapted as WG document? or(3) this draft should not be adapted as WG document?The floor response was (1). The Requirements design team and the authors need to work together to incorpate the new requirements into the draft so that it can then be submitted for WG last call as was discussed earlier in the meeting.4. A MIB proposal - draft-cha-gsmp-management-00.txt was presented by Young Wook ChaThis draft proposed extensions to the GSMP MIB for control of switch control in the GSMP master controller.As the charter does not include this work item, the WG needs to ask the IESG for an extension to the charter for this work to be undertaken.Avri asked the floor whether we should ask the IESG to modify the charter to include this issue. The floor consensus was that it is good idea to change the charter.Avri asked the authors to rework the draft to better explain its motivations. Avri will work with the authors in developing a proposal for the IESG. This proposal will need to be reviewed by the WG before being forwarded to the IESG for consideration.5. Dynamic partitioning draft was presented by Avri DoriaWhile there was still a last edit to be contributed by Jonathan Sadler on the ability of one virtual switch to provide a service to another virtual switch, the meeting conditionally approved sending the draft to the WG list for last call as soon as it was reissued with the additonal content.6. A discussion on the structure of GSMP Specification was presented by Avri Doria The GSMP specification document is already very complex and would become too complex if all of the material mandated by the new requirements were to be included into a single document (ATM, FR, TDM, Lambda, Fiber, Optical burst switch).The proposal was made to divide the specification into several drafts.Specifically: - Basic messages and protocol function - Generic Switch - Layer 2 switch (ATM, FR) - TDM compatible switch - Lambda compatible switch - Fiber compatible switchAvri asked the floor whether the organization is reasonable or not?The answer is that it is reasonable. Volunteers should contact the chairs to be involved into the DTs. DT will start the task next month.A call was made for design team to volunteer for each of the documents. 7. Other IssuesForces requirements document is complete. Avri asked the floor whether there is any interest in implementing the Forces requirements in GSMP. The floor response was positive. The floor also asked whether the Forces chair agrees or not. The Forces chair attending the GSMP meeting answered tha yes, GSMP could present a solution proposal for consideration to the FORCES WG. A design team will be formed. Anyone intersted should contact the WG chairs.


    GSMP Requirements Draft
    Extension of GSMP for Optical Burst Switching
    Network Management for GSMP Interface