Requirements for Adding Optical Support to the General Switch Management Protocol version 3 (GSMPv3) (RFC3604)
Original Publication Date: 2003-Oct-01
Included in the Prior Art Database: 2003-Oct-07
Internet Society Requests For Comment (RFCs)
H. Khosravi: AUTHOR [+5]
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.
Network Working Group H. Khosravi
Request for Comments: 3604 Intel
Category: Informational G. Kullgren
Requirements for Adding Optical Support to
the General Switch Management Protocol version 3 (GSMPv3)
Status of this Memo
This memo provides information for the Internet community. It does
not specify an Internet standard of any kind. Distribution of this
memo is unlimited.
Copyright (C) The Internet Society (2003). All Rights Reserved.
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.
Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in BCP 14, RFC 2119 .
This document details the changes to GSMP necessary for the support
of optical (non-transparent and all optical), SONET/SDH, and spatial
switching of IP packets, Layer 2 (L2) frames and TDM data. When
implemented, GSMP controllers will then be able to control: photonic
cross-connects (optical-optical), transparent optical cross connects
(optical-electrical-optical, frame independent), opaque cross
connects (optical-electrical-optical, SONET/SDH frames), and
Khosravi, et al. Informational [Page 1]
RFC 3604 Adding Optical Support to GSMPv3 October 2003
traditional TDM switches (all electrical). The resulting systems
could form IP based optical routers, optical label switches,
wavelength routers, and dynamic optical cross connects.
Several different generic models exist defining how to provide
control plane functionality in an optical network , , .
This document takes no position on which model is most appropriate
(e.g., single or multiple routing plane instances). The only
assumption is that the ability to separate the control mechanisms
from the data switching is as useful for the signaling of optical
paths (e.g., GMPLS) as it is for the signaling of L2 paths (e.g.,
MPLS). Therefore, the requirements contained within are focused only
on the separation of control functions from data functions in order
to provide a more flexible network architecture.
GSMPv3  is well suited for providing the control interface
necessary for allowing an IP based controller to direct the
activities of an optical switch. In order for GSMP to operate
between controllers and optical switches and cross connects, support
for optical labels and service and resource abstractions must be
added to GSMP.
This document also includes changes recommended by implementers that
will facilitate easier development of a GSMP implementation. These
changes consist of rearranging PDU formats, clarification of flags,
transaction identifiers, and response codes.
2. Requirements for Optical Support