draft-ietf-gsmp-optical-spec-01.txt   draft-ietf-gsmp-optical-spec-02.txt 
GSMP Working Group Internet Draft Jun Kyun Choi(ICU) GSMP Working Group Internet Draft Jun Kyun Choi(ICU)
Document: draft-ietf-gsmp-optical-spec-01.txt Min Ho Kang(ICU) Document: draft-ietf-gsmp-optical-spec-02.txt Min Ho Kang(ICU)
Expiration Date: August 2003 Jung Yul Choi(ICU) Expiration Date: December 2003 Jung Yul Choi(ICU)
Gyu Myoung Lee(ICU) Gyu Myoung Lee(ICU)
Joo Uk Um(KT) Young Wook Cha(ANU)
March 2003 June 2003
General Switch Management Protocol (GSMP) v3 for Optical Support General Switch Management Protocol (GSMP) v3 for Optical Support
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC-2026. all provisions of Section 10 of RFC-2026.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that other Task Force (IETF), its areas, and its working groups. Note that other
skipping to change at page 1, line 34 skipping to change at page 1, line 34
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
Abstract Abstract
This document describes the GSMPv3 for the support of optical switching. This document describes the General Switch Management Protocol version 3
GSMPv3 controller SHOULD control optical label switches and manage (GSMPv3) for the support of optical switching. GSMPv3 controller SHOULD
optical resources on them. This document describes the extended control optical label switches and manage optical resources on them.
functions of GSMPv3 for optical switching and explains operational This document describes the extended functions of GSMPv3 for optical
mechanisms to implement them. It SHOULD be referred with [1] for the switching and explains operational mechanisms to implement them. It
complete implementation. SHOULD be referred with [1] for the complete implementation.
Conventions Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC-2119. document are to be interpreted as described in RFC-2119.
GSMPv3 for Optical Support March 2003 GSMPv3 for Optical Support June 2003
Table of Contents Table of Contents
1. Introduction.....................................................3 1. Introduction.....................................................2
2. Common Definitions and Procedures for Optical Support............4 2. GSMP Packet Encapsulation........................................3
2.1 Labels.......................................................4 3. Common Definitions and Procedures for Optical Support............3
2.1.1 Labels for Fiber.........................................5 3.1 Labels..........................................................3
2.1.2 Labels for Waveband......................................5 3.1.1 Labels for Fiber..............................................5
2.1.3 Labels for Wavelength....................................6 3.1.2 Labels for Waveband...........................................5
2.1.4 Labels for optical burst switching.......................6 3.1.3 Labels for Wavelength.........................................6
2.1.5 Label Range..............................................7 3.1.4 Labels for optical burst......................................6
3. Connection Management Messages...................................8 4. Connection Management Messages...................................7
3.1 Add Branch Message...........................................8 4.1 Add Branch Message: Recovery Specific Block.....................7
3.2 Delete Tree Message..........................................9 5. Reservation Management Messages..................................8
3.3 Delete All Input Port Message................................9 5.1 Reservation Request Message: Recovery Specific Block............9
3.4 Delete All Output Port Message...............................9 5.2 Reservation Request Message: Optical Burst Specific Block.......9
3.5 Delete Branches Message......................................9 6. Management Message..............................................10
3.6 Move Output Branch Message...................................9 6.1 Label Range Message............................................10
3.7 Move Input Branch Message...................................10 6.1.1 Optical Label................................................11
4. Reservation Management Messages.................................10 7. Statistics Messages: Optical Signal Specific Block..............12
4.1 Reservation Request Message for optical burst...............10 8. Configuration Messages..........................................12
4.2 Delete Reservation Message..................................12 8.1 Switch Configuration Message: Optical Switch Specific Block....12
4.3 Delete All Reservations Message.............................12 8.2 Port Configuration Message.....................................13
5. Management Message..............................................12 8.2.1 PortType Specific Data for Optical Switching.................13
5.1 Port Management Message.....................................12 9. Event Messages..................................................15
5.2 Label Range Message.........................................12 9.1 Recovery Completion Message....................................16
5.2.1 Optical Label...........................................12 9.2 Fault Notification Message.....................................17
6. State and Statistics Messages...................................13 10. Service Model Definition.......................................18
6.1 Connection Activity Message.................................13 11. Failure Response Codes.........................................18
6.2 Statistics Messages.........................................13 12. Security Considerations........................................19
6.2.1 Optical signal statistics Message.......................13 Appendix I. Protection and Restoration Capability in GSMPv3........19
6.3 Report Connection State Message.............................14 1.1 1+1 dedicated recovery mechanism...............................20
7. Configuration Messages..........................................14 1.2 1:1 dedicated recovery mechanism...............................20
7.1 Optical Switch Configuration Message........................15 1.3 1:N/M:N shared recovery mechanism (M, N > 1, M <= N)...........21
7.2 Port Configuration Message..................................16 Appendix II. GSMPv3 support for optical cross-connect systems......21
7.2.1 PortType Specific Data for Optical Switching............16 References.........................................................22
7.3 All Ports Configuration Message.............................18 Acknowledgement....................................................23
7.4 Service Configuration Message...............................18 Author's Addresses.................................................23
7.4.1 Optical Service Configuration Message...................18 Full Copyright Statement...........................................24
8. Event Messages..................................................18
8.1 Restoration Completion Message..............................18
8.2 Fault Notification Message..................................19
9. Optical Service Model Definition................................20
10. Failure Response Codes.........................................20
11. Security Considerations........................................20
Appendix I. Protection and Restoration Capability in GSMPv3........21
1.1 1+1 dedicated recovery mechanism............................21
GSMPv3 for Optical Support March 2003
1.2 1:1 dedicated recovery mechanism............................22
1.3 1:N/M:N shared recovery mechanism...........................23
Appendix II. GSMPv3 support for optical cross-connect system.......23
References.........................................................24
Acknowledgement....................................................25
Author's Addresses.................................................25
Full Copyright Statement...........................................27
1. Introduction 1. Introduction
This document describes the extended functions and their mechanisms This document describes the extended functions and their mechanisms
of GSMPv3 for the support of optical switching. The GSMPv3 is an of the General Switch Management Protocol version 3 (GSMPv3) for the
asymmetric protocol to control and manage label switch. The label support of optical switching. GSMPv3 is an asymmetric protocol to
switches that are used for optical switching are all optical cross- control and manage label switch. The label switches that are used for
connects (optical-optical-optical), transparent optical cross GSMPv3 for Optical Support June 2003
connects (optical-electrical-optical, frame independent), and opaque
optical cross connects (optical-electrical-optical, SONET/SDH optical switching are all optical cross-connects (optical-optical-
frames).These OXC (optical cross connect) systems can be IP-based optical), transparent optical cross connects (optical-electrical-
optical routers which are dynamic wavelength routers, optical label optical, frame independent), and opaque optical cross connects
switches, or burst/packet-based optical cross connects, and so on[2]. (optical-electrical-optical, SONET/SDH frames).These optical cross
In this draft, we do not limit specific OXC systems, but aims to connect (OXC) systems can be IP-based optical routers which are
provide the general functions of optical switching and services for dynamic wavelength routers, optical label switches, or burst/packet-
connections in general optical switches. based optical cross connects [2]. In this draft, we do not limit
specific OXC systems, but aim to provide the general functions of
optical switching and services for connections in general optical
switches.
GSMPv3 is a label switch controller and provides a control interface GSMPv3 is a label switch controller and provides a control interface
to optical switches. Therefore, it SHOULD define and add services for to optical switches. The optical resources used in connection setup
optical switching and resource abstractions. The basic optical are different from those used in legacy networks. In optical
resources used in connection setup are different with them of legacy switching, basic connection units are a fiber, a wavelength, or a
networks. In optical switching, basic connection units are a fiber, a burst and they are assumed to be processed in optical domain without
wavelength, or a burst and they are assumed to be processed in optical/electrical/optical conversion. This specification defines the
optical domain without optical/electrical/optical conversion. It is services, traffic control, and QoS guarantee necessary at to support
impossible to define services, traffic control, and QoS guarantee in optical switches. This draft defines several sub-TLVs, parameters,
packet or cell level. New messages are needed to process optical and new messages to support optical services and optical connection
services, optical connection management, and so on, in real time management. This draft describes optical resources, connection
because optical switching requires real time process with low message management, optical services, and switch configuration which can be
processing overhead. This draft describes optical resources, applied in optical domain generally.
connection management, optical services, and switch configuration
which can be applied in optical domain generally.
One of the important OAM functions is protection and restoration One of the important OAM functions is protection and restoration
functions. In the current situation where a single fiber delivers function. In the current situation where a single fiber delivers
several Tb/s through several wavelengths, when even a single link several Tb/s through several wavelengths, when even a single link
gets cut it makes a huge turbulence. Therefore GSMPv3, as an optical gets cut it makes a huge turbulence. Therefore GSMPv3, as an optical
switch controller, MUST have protection and restoration capabilities switch controller, MUST have survivable capability of switches and
of switches and connections. By extending the management messages of connections. By extending the management messages of GSMPv3, this
GSMP, this function will be implemented. This draft also deals with function will be implemented.
several recovery capabilities of the GSMPv3.
GSMPv3 for Optical Support March 2003 [Note] For the complete implementation this document MUST be referred
with [1].
For the complete implementation this document MUST be referred with 2. GSMP Packet Encapsulation
[1].
2. Common Definitions and Procedures for Optical Support. GSMP Packets may be transported via any suitable medium. GSMP packet
encapsulation for optical support will be defined in separate
documents.
Common definitions and procedures which are not mentioned in this 3. Common Definitions and Procedures for Optical Support.
document follow [1].
2.1 Labels 3.1 Labels
Labels are the basic identifiers for connections. In order to setup Labels are the basic identifiers for connections. In order to setup
connections in optical switch, new labels MUST be defined. Newly connections in optical switch, new labels MUST be defined. Newly
defined labels identify entities that are to be switched in optical defined labels identify entities that are to be switched in optical
switches. GMPLS defines packet switching capable, TDM switching GSMPv3 for Optical Support June 2003
capable, lambdas switching capable, fiber switching capable
switches. Generalized Multi-Protocol Label Switching (GMPLS) defines
packet switching capable (PSC), Time-Division Multiplex Capable (TDM),
lambda switching capable (LSC), fiber switching capable (FSC)
interfaces, and it introduces needs of generalized labels to support interfaces, and it introduces needs of generalized labels to support
them [3][4]. So far, GMPLS does not defined labels to be used for them [3][4]. The following list is the labels to be supported in
optical switching (label formats and encoding schemes), but GSMPv3 GSMPv3 for optical support [2][3][4][7][8][10].
MUST support all types of label that to be defined in GMPLS. The
following lists, especially related to lambda/fiber switch capable
interfaces, are the labels to be supported in optical switching
[2][3][4][7][8][10].
- a single fiber in a bundle - a single fiber in a bundle
- a single waveband within a waveband (or )fiber - a single waveband within a waveband (or )fiber
- a single wavelength within a fiber - a single wavelength within a fiber
- an optical burst within a wavelength - an optical burst within a wavelength
These labels can be encoded in a common structure composed of three All labels are encoded in a common structure composed of three fields,
fields, a Type, a Length, and a Value [1]. TLV types for optical a Type, a Length, and a Value [1]. A label TLV is encoded as a 2-
support in GSMPv3 are not defined yet. octet field that uses 12 bits to specify a Type and four bits to
specify certain behavior specified below, followed by 2-octec Length
field, and followed by a variable length Value field.
A summary of TLV labels supported by the GSMPv3 extensions for
optical support defined in this document is listed below:
TLV Label Label Type
-------------------- -----------
Fiber Label 0x300
Waveband Label 0x301
Wavelength Label 0x302
Optical burst Label 0x303
All labels will be designated as follow: All labels will be designated as follow:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|S|x|x| Label Type | Label Length | |x|S|x|x| Label Type | Label Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
~ Label Value ~ ~ Label Value ~
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
S: Stacked Label Indicator X: Reserved Flags
S field is not used in this extended version of GSMPv3 because labels These are generally used by specific messages and will be defined in
for optical support only carry a single level of label [4]. those messages.
Label Type: 12 bit S
GSMPv3 for Optical Support March 2003 Stacked Label Indicator
Label type for optical support MAY be identified with the above four Label Type
types of optical switching. A 12-bit field indicating the type of label.
Label type for optical support is TBD.
Label value: Variable Label Length
Carries label information. The interpretation of this field depends GSMPv3 for Optical Support June 2003
on the type of the link (or the type of connection) over which the
label is used. Label value for optical support is TBD.
The other fields are defined in [1] and referred in it. A 16-bit field indicating the length of the Label Value field in
bytes.
2.1.1 Labels for Fiber Label value: Variable
A variable length field that is an integer number of 32 bit words
long. The interpretation of this field depends on the Label Type as
described in the following sections.
3.1.1 Labels for Fiber
This label indicates a fiber to be used for a connection This label indicates a fiber to be used for a connection
establishment in optical switching. The label value only has establishment in optical switching. The label value only has
significance between two neighbors, and the receiver MAY need to significance between two neighbors, and the receiver MAY need to
convert the received value into a value that has local significance. convert the received value into a value that has local significance.
If the label type = labels for fiber, the label MUST be interpreted If the label type = labels for fiber, the label MUST be interpreted
as labels for fiber and the label for fiber has the following format: as labels for fiber and it has the following format:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Label | | Label |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Label: 32 bits Label: 32 bits
Indicates a label for fiber to be used. Indicates a label for fiber to be used.
Label encoding is TBD.
2.1.2 Labels for Waveband 3.1.2 Labels for Waveband
A waveband is a set of contiguous wavelengths which can be switched A waveband is a set of contiguous wavelengths which can be switched
together to a new waveband [3][4]. It MAY be desirable for an optical together to a new waveband [3][4]. It MAY be desirable for an optical
cross connect to optically switch multiple wavelengths as a unit cross connect to optically switch multiple wavelengths as a unit
since it MAY reduce distortion on individual wavelengths and MAY since it MAY reduce distortion on individual wavelengths and MAY
allow tighter separation of individual wavelengths. Waveband allow tighter separation of individual wavelengths. Waveband
switching introduces another level of label hierarchy and as such the switching introduces another level of label hierarchy and as such the
waveband is treated the same way all other upper layer labels are waveband is treated the same way all other upper layer labels are
treated. The waveband label is defined to support such a waveband treated. The waveband label is defined to support such a waveband
switching. The waveband label can be encoded in three parts; waveband switching. The waveband label can be encoded in three parts; waveband
ID, start label, and end label. The start label and the end label ID, start label, and end label. The start label and the end label
represent the lowest value of wavelength and the highest value of represent the lowest value of wavelength and the highest value of
wavelengths. wavelength.
If the label type = labels for waveband, the label MUST be If the label type = labels for waveband, the label MUST be
interpreted as labels for waveband and the label for waveband has the interpreted as labels for waveband and it has the following format:
following format:
GSMPv3 for Optical Support March 2003
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Waveband Id | | Waveband Id |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
GSMPv3 for Optical Support June 2003
| Start Label | | Start Label |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| End Label | | End Label |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Waveband Id: 32 bits Waveband Id: 32 bits
A waveband identifier. The value is selected by a sender and reused A waveband identifier. The value is selected by a sender and reused
in all subsequent related messages. in all subsequent related messages.
Start Label: 32 bits Start Label: 32 bits
Indicates the lowest value of wavelength in the waveband. Indicates the lowest value of wavelength in the waveband.
End Label: 32 bits End Label: 32 bits
Indicates the highest value wavelength in the waveband. Indicates the highest value wavelength in the waveband.
The start/end label are established either by configuration or by The start/end label are established either by configuration or by
means of a protocol such as LMP [6]. They are normally used in the means of a protocol such as LMP [6]. They are normally used in the
label parameter of the Generalized Label one PSC and LSC [3][4]. label parameter of the Generalized Label one PSC and LSC [3][4].
2.1.3 Labels for Wavelength 3.1.3 Labels for Wavelength
The label indicates a single wavelength to be used for a connection The label indicates a single wavelength to be used for a connection
establishment in optical switching. The label value only has establishment in optical switching. The label value only has
significance between two neighbors, and the receiver MAY need to significance between two neighbors, and the receiver MAY need to
convert the received value into a value that has local significance. convert the received value into a value that has local significance.
If the label type = labels for wavelength, the label MUST be If the label type = labels for wavelength, the label MUST be
interpreted as labels for wavelength and a format of the label for interpreted as labels for wavelength and a format of the label for
wavelength is given as the below: wavelength is given as the below:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Label | | Label |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Label: 32 bits Label: 32 bits
Indicates label for wavelength to be used. Indicates label for wavelength to be used.
Label encoding is TBD.
2.1.4 Labels for optical burst switching 3.1.4 Labels for optical burst
The label for optical burst switching represents a label for
switching optical burst data.
GSMPv3 for Optical Support March 2003 The label for optical burst represents a label for switching data
burst in optical domain.
Optical data burst switching, which utilizes finer granularity in Optical data burst switching, which utilizes finer granularity in
time domain in a coarse granularity such as a wavelength, is a new time domain in a coarse granularity such as a wavelength, is a new
connection entity in optical domain [7][8]. Connection setup for connection entity in optical domain [7][8]. Connection setup for
optical burst includes reserving time on the transport medium for the optical burst includes reserving time on the transport medium for the
client. client.
GSMPv3 for Optical Support June 2003
This time is characterized by two parameters: start time and duration This time is characterized by two parameters: start time and duration
of data burst. These values define a fast one-way reservation. Upon a of data burst. These values define a fast one-way reservation. Upon a
request for setup of a burst connection, the GSMP controller MUST request for a connection setup for data burst, the GSMP controller
perform appropriate Connection Admission Control for the start time MUST perform appropriate Connection Admission Control for the start
and duration of data burst specified. If the connection is allowed, time and duration of data burst specified. If the connection is
it MUST signal these parameters to the burst switching device to allowed, it MUST signal these parameters to the burst switching
reserve the exact bandwidth required [7][8]. The burst switch MUST device to reserve the exact bandwidth required [7][8]. The burst
perform the switching operation autonomously, using the switch MUST perform switching operation autonomously, using
synchronization methods prescribed for the burst network it is synchronization methods prescribed for the burst network it is
operating in. operating in.
If the label type = labels for optical burst switching, the label If the label type = labels for optical burst, the label MUST be
MUST be interpreted as labels for burst switching and a format of the interpreted as labels for burst switching and a format of the label
label for optical burst switching is given as the below: for optical burst is given as the below:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Label | | Label |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Label: 32 bits Label: 32 bits
Indicates label for a burst level connection. Indicates label for a burst level connection.
Label encoding is TBD.
2.1.5 Label Range 4. Connection Management Messages
The basic label range to be used in each port is specified by the
Port Configuration or All Port Configuration message. The Label Range
message allows the range of labels supported by a specified port to
be changed. The controller MUST allocate the label range with
consideration of optical characteristics when assigning the labels
for a connection because a connection is established per optical
burst, wavelength, waveband, and fiber in optical domain. Since the
basic label range varies in switches and the labels for the
connections can be different due to the optical characteristics, GSMP
does not treat them. However, the following lists SHOULD be
considered and the available label ranges SHOULD be applied in the
Label Range message.
- When allocating a label for a wavelength, the label SHOULD be
allocated with consideration of wavelength continuity. For
satisfying requirement of wavelength continuity in a connection,
the label SHOULD be allocated to maintain the same wavelength for
GSMPv3 for Optical Support March 2003
it. The controller MUST manage the available labels and support
the constraint.
- The labels to be used for waveband switching MUST be contiguous,
because the waveband switching is possible only in a set of
contiguous wavelengths. The decision mechanism for the available
label range is out of scope of GSMPv3.
- GMPLS supports bi-directional symmetric LSPs setup [3][4]. To
setup a bi-directional LSP two unidirectional paths MUST be
independently established. For doing so, the presence of an
upstream label in the appropriate signaling message indicates the
bi-directional LSP setup and two labels are allocated for them.
The GSMPv3, therefore, SHOULD allow appropriate labels for them.
In order to avoid contention for labels, much care SHOULD be taken
in choosing the two labels. To choose the labels to avoid
contention is out of scope of GSMPv3.
3. Connection Management Messages
Connection management messages, which are used for establishing, Connection management messages, which are used for establishing,
releasing, modifying, and verifying connections across the switch by releasing, modifying, and verifying connections across the switch by
the controller, SHOULD operate for optical switching. Since the the controller, SHOULD operate for optical switching. Connection
GSMPv3 does not process each packet in optical domain, traffic management messages also SHOULD support recovery capabilities of
related fields used to specify connections in the messages are not optical switch and these are mainly dealt with in the following sub-
dealt with and then it makes possible to process the message faster. sections.
Connection management messages also SHOULD support restoration
capabilities of optical switch and these are mainly dealt with in the
following sub-sections.
The general message definition and semantics in this section follow The general message definition and semantics in this section follow
[1] and the other untouched items are dealt with in it. [1] and the other untouched items are dealt with in it.
3.1 Add Branch Message 4.1 Add Branch Message: Recovery Specific Block
The Add Branch message is used to setup a connection. Especially, it
SHOULD support restoration capability in optical switches. For 1+1
dedicated recovery, it is required to make an additional connection
as a backup connection to protect an original connection against a
failure. Additional fields are not required in the Add Branch message
to support the restoration capability since two connections are used
for delivering data traffic simultaneously and an egress node selects
one of them. Since the two connections are established for one
connection, connection-related fields, such as input port/label,
output port/label, SHUOLD be carefully set in order to distinguish
them. The controller SHOULD know the whole status of the switch and
manage the information base.
GSMPv3 for Optical Support March 2003
3.2 Delete Tree Message
The message format and semantics in this section follows [1].
3.3 Delete All Input Port Message
The message format and semantics in this section follows [1].
3.4 Delete All Output Port Message
The message format and semantics in this section follows [1].
3.5 Delete Branches Message
The message format and semantics in this section follows [1], and Recovery capability of optical switch is supported by Add Branch
optical switching related contents will be added. message by establishing recovery connection in order to protect
working connection. By using this message a recovery connection is
established for various types of recovery mechanism. The recovery
block defines a recovery type, connection type, and related
connection information for the purpose of recovery.
3.6 Move Output Branch Message The Add Branch message adds the following block for recovery
capability.
The Move Output Branch message is used to change the current output 0 1 2 3
port label to the new output port label for re-establishing the GSMPv3 for Optical Support June 2003
existing connection. It can be used to support restoration capability.
Since to re-establish output port of a switch at an ingress node is
to change a start point of the current connection, it can be used for
1:1 dedicated recovery or 1:N (M:N) shared recovery where an ingress
node begins a connection and it takes responsibility for recovery of
the connection. Upon a fault occurring, in order to setup a new
backup connection for the failed working connection, the new port in
upstream node SHOULD be connected to the current connection by using
this message.
For configuring a new backup connection, the following fields of Move 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
Input Branch message SHOULD be set as following. +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Recovery Type |Connection Type| Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Recovery Related Port 1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Recovery Related Label 1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| . . . |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| . . . |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Recovery Related Port N |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Recovery Related Label N |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
- Old Output Port = failed working connection's output port ID Recovery Type; 8 bits
- Old Output Label = failed working connection's output label ID This field provides the required information for various types of
- New Output Port = newly configured reserved backup connection's recovery mechanism when a recovery connection is established by using
output port ID Add Branch message. The Recovery Type has the following value for
- New Output Port = newly configured reserved backup connection's various types of recovery mechanism.
output label ID
This message is additionally used to move back to the original - 0: 0:1 unprotected
connection from the backup connection in revertible mode after a - 1: 1+1 dedicated protection
recovery completed. In this case, Old Output Port/Label are for the - 2: 1:1 protection
currently used backup connection, and New Output Port/Label are for - 3: 1:1 restoration
the restored working connection - 4: 1:N shared recovery
GSMPv3 for Optical Support March 2003 - 5: M:N shared recovery
3.7 Move Input Branch Message Connection Type: 8 bits
This field indicates which the message is for a working connection or
a recovery connection.
The Move Input Branch message is used to change the current input - 0: working connection
port label to the new input port label for re-establishing the - 1: recovery connection
existing connection. It is also used to support restoration
capability. For 1:1 dedicated recovery or 1:N (M:N) shared recovery,
the message can be used to configure backup connection at an egress
node. By setting Old Input Port/Label as a failed working connection
and New Input Port/Label as a reserved backup connection, recovery of
the failed working connections is achieved.
It is also used to move back to the original connection from a backup Recovery Related Connection
connection for the revertible mode after a recovery completed. The This field indicates the corresponding connection for recovery
new port/label in this message sets that of the restored original purpose. If the Add Branch message is used to setup a working
connection. connection the field implies the related recovery connection, and
vice versa. This information consists of the following two fields.
The other untouched items and fields in these messages are dealt with - Recovery Related Port
in [1] and referred in it. - Recovery Related Label
4. Reservation Management Messages 5. Reservation Management Messages
The GSMPv3 allows a switch to reserve resources for connections The GSMPv3 allows a switch to reserve resources for connections
before establishing them through Reservation Management messages. before establishing them through Reservation Management messages.
GSMPv3 for Optical Support June 2003
Reservable resources are bandwidth, buffers, queues, labels and etc. Reservable resources are bandwidth, buffers, queues, labels and etc.
In this extended version of GSMPv3 for optical support, the resources In this draft the resources imply optical resources, such as data
imply optical resources, such as data burst, wavelengths, fibers, and burst, wavelengths, fibers, and so on. In this section, recovery
so on. capability and data burst level switching are supported by using the
Reservation Management messages.
With these messages, restoration capabilities of a switch are 5.1 Reservation Request Message: Recovery Specific Block
supported. Especially, in 1:N (M:N) shared recovery scheme, a spare
connection is reserved for N working connections. The GSMPv3 SHOULD Reservation Request message is used to reserve a recovery connection
use the reservation request messages for reserving a backup for various types of recovery mechanisms. Especially, in 1:N (M:N)
connection. The GSMPv3 controller SHOULD have mapping information shared recovery scheme, a spare connection is reserved for N working
connections. In order to support recovery capability, a recovery
connection is configured by reserving backup resource for working
connections. The GSMPv3 controller SHOULD have mapping information
between a shared backup resource and N working connections. Whenever between a shared backup resource and N working connections. Whenever
the GSMPv3 uses the reserved resource for a failed working connection the GSMPv3 uses the reserved resource for a failed working connection,
Add Branch message is used to establish a new connection with New Add Branch message is used to establish a new connection with New
Port/Label of one of N working connections. Port/Label of one of N working connections.
Or any other cases, the reserved resources are used as followed in Reservation Request message adds the following block for recovery
[1]. The message format and semantics in this section follow [1] and capability.
the other untouched items are dealt with in it.
4.1 Reservation Request Message for optical burst 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Recovery Type |Connection Type| Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Recovery Related Port 1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Recovery Related Label 1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| . . . |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| . . . |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Recovery Related Port N |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Recovery Related Label N |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Reservation Request message SHOULD support new connections per data NOTE: Fields and parameters in the block refer to section 4.1.
burst, based on time-delayed reservation in optical domain. In order
to configure connection per burst, two parameters, offset time and
burst length, SHOULD be add on the message. When a controller
GSMPv3 for Optical Support March 2003
receives a request for a burst connection setup it sends a 5.2 Reservation Request Message: Optical Burst Specific Block
Reservation Request message with the two fields. The switch then
waits for offset time to establish the connection and then
automatically set it up. After burst length time, it releases the
connection.
Message type = TBA Reservation Request message also supports a new connection per data
burst in optical domain. Data burst is very short in huge bandwidth
of a wavelength and needs to process just in time. However, it takes
much time to reserve resource and setup a connection per data burst
by using the Reservation Request message. Therefore, a short form of
Reservation Request message is used to support data burst. The
GSMPv3 for Optical Support June 2003
The Reservation Request message for optical burst has the following original Reservation Request message tries to reserve resource for
format. data burst and the short form of the message is used to trigger the
resource to switch and transmit the data burst. This message only
contains information to identify the reservation as well as the
original message. In order to configure a connection per burst, two
parameters, offset time and burst length, are added on the message.
When a controller receives a request for a connection setup for data
burst it sends the message. According to the different switching
mechanisms for optical burst [7][8], the value of two fields in the
message are assigned. That is, by applying them, connection setup and
release are performed explicitly or implicitly. This draft does not
limit the usage of the block in a specific switching technology.
The following message is the short form of Reservation Request
message to support data burst.
Message type = TBA
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Message Type | Result | Code | | Version | Message Type | Result | Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID | Transaction Identifier | | Partition ID | Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|I| SubMessage Number | Length | |I| SubMessage Number | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port Session Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reservation ID | | Reservation ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Input Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Input Service Selector |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Output Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Output Service Selector |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|IQS|OQS|P|x|N|O| Adaptation Method |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|S|M|B| |
+-+-+-+-+ Input Label |
~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|S|M|x| |
+-+-+-+-+ Output Label |
~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Offset Time (T) | | Offset Time (T) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Burst Length (L) | | Burst Length (L) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Note: Fields and Parameters that have not been explained in the NOTE: Fields and parameters that have not been explained follow
Subsection follow [1]. [1].
Offset Time (T); TBD Offset Time (T); TBD
GSMPv3 for Optical Support March 2003
This field is the time between a connection request reception and the This field is the time between a connection request reception and the
start of the connection for the data burst. start of the connection for the data burst.
Burst Length (L); TBD Burst Length (L); TBD
This field is the time duration of data burst This field is the time duration of data burst
4.2 Delete Reservation Message 6. Management Message
The message format and semantics in this section follows [1].
4.3 Delete All Reservations Message
The message format and semantics in this section follows [1].
5. Management Message
5.1 Port Management Message
The message format and semantics in this section follows [1], and
optical switching related contents will be added.
5.2 Label Range Message 6.1 Label Range Message
The label range, which is specified for each port by the Port The label range, which is specified for each port by the Port
Configuration or the All Ports Configuration message, can be Configuration or the All Ports Configuration message, can be
specified to the range of label supported by a specified port and to specified to the range of label supported by a specified port and to
GSMPv3 for Optical Support June 2003
be changed by using Label Range message. Since the granularity of be changed by using Label Range message. Since the granularity of
each connection is different in optical domain each port SHOULD allow each connection is different in optical domain each port SHOULD allow
the label range changeable in ports. In addition, a port MAY have the label range changeable in ports. In addition, a port MAY have
wavelength converters with full or limited capability so that each wavelength converters with full or limited capability so that each
port MAY have different limited labels. In case of waveband switching, port MAY have different limited labels. In case of waveband switching,
a single label for waveband connection is used for a set of a single label for waveband connection is used for a set of
wavelengths in the band. To support these cases, the Label Range wavelengths in the band. To support these cases, the Label Range
message is used. message is used.
The general usage and massage format of this message follows [1]. The general usage and the format of this message follows [1].
5.2.1 Optical Label 6.1.1 Optical Label
If the Label Type is equal to optical label, the label range message If the Label Type is equal to optical label, the label range message
MUST be interpreted as an Optical Label. Label Range Message format MUST be interpreted as shown:
follows [1] and the Label Range Block has the following format:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
GSMPv3 for Optical Support March 2003
|x|x|V|C| Optical Label | Label Length | |x|x|V|C| Optical Label | Label Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Min Label | | Min Label |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Max Label | | Max Label |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Remaining Labels | | Remaining Labels |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
V: Label V: Label
The Label flag use is port type specific. The Label flag is not used.
TBD.
C: Multipoint Capable C: Multipoint Capable
Indicates label range that can be used for multipoint connections. Indicates label range that can be used for multipoint connections.
This field is not used in the draft. This field is not used in this document.
Min Label: TBD Optical Label
The optical label indicates the type of label for optical support and
is referred to the section 3.1 of this document.
Min Label:
The minimum label value in the range. The minimum label value in the range.
Max Label: TBD Max Label:
The maximum label value in the range. The maximum label value in the range.
Remaining Labels: TBD Remaining Labels:
The maximum number of remaining labels that could be requested for The maximum number of remaining labels that could be requested for
allocation on the specified port. allocation on the specified port.
6. State and Statistics Messages GSMPv3 for Optical Support June 2003
The State and Statistics messages allow a controller to request state
and statistics of connections of a switch. They SHOULD be extended to
monitor the statistics related to ports and connections for optical
transmission.
6.1 Connection Activity Message
The message format and semantics of the message follows [1], and
optical switching related contents will be added.
6.2 Statistics Messages
6.2.1 Optical signal statistics Message 7. Statistics Messages: Optical Signal Specific Block
The statistics messages are used to query the performance statistics The statistics messages are used to query the performance statistics
related to ports and connections for optical transmission. Since the related to ports and connections for optical transmission. The
current statistics messages in [1] report the statistics related to statistics contain optical transmission characteristics which specify
traffic states per cells, or frames, new fields SHOULD be added into transmission quality of connections. Transmission performance is
the message for querying optical support. The statistics contain typically defined in terms of signal performance with reference to
GSMPv3 for Optical Support March 2003 noise level, or by the signal-to-noise ratio (SNR), and spectral
occupancy requirement or signal power level. Optical Signal
optical transmission characteristics which specify transmission QoS Statistics message SHOULD contain Optical Signal Block which
of connections. Transmission performance is typically defined in specifies the transmission property of connections as shown in the
terms of signal performance with reference to noise level, or by the below.
signal-to-noise ratio (SNR), and spectral occupancy requirement or
signal power level. Optical Signal Statistics message SHOULD contain
Optical Signal Property which specifies the transmission property of
connections as shown in the below.
Optical Signal Statistics Message Type = TBA
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Message Type | Result | Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID | Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|I| SubMessage Number | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|S|x|x| |
+-+-+-+-+ Label |
~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
~ Optical Signal Property ~ ~ Optical Signal Block ~
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Optical Signal Property; variable Optical Signal Block; variable
This field implies quality of transmission signal in a connection so This field implies quality of transmission signal in a connection so
that it informs a controller signal degradation or loss of signal. that it informs a controller signal degradation or loss of signal.
This field MAY consist of several sub-TLVs which specify the optical This field MAY consist of several blocks which specify the optical
signal statistics in detail and they will be further added on this signal statistics in detail and they will be further added on this
message. This information MAY result in an alarm of link failure. message. This information MAY result in an alarm of link failure.
The format and semantics of Optical Signal Property is TBD. 8. Configuration Messages
The other statistics messages are not dealt with in the section
follow [1].
6.3 Report Connection State Message
The message format and usage in this section follows [1], and optical
switching related contents will be added.
7. Configuration Messages
GSMPv3 for Optical Support March 2003
The configuration messages allow a controller to discover a The configuration messages allow a controller to discover
capabilities of optical switch. Switch configuration, port capabilities of optical switch. Switch configuration, port
configuration, and service configuration messages are defined for configuration, and service configuration messages are defined for
these functions. these functions.
7.1 Optical Switch Configuration Message 8.1 Switch Configuration Message: Optical Switch Specific Block
Since an optical switch MAY be able to provide connection services at Since an optical switch MAY be able to provide connection services at
multiple transport layers, and not all switches are expected to multiple transport layers, and not all switches are expected to
support the same transport layers, the switch will need to notify the support the same transport layers, the switch will need to notify the
controller of the specific layers it can support. Therefore, the controller of the specific layers it can support. Therefore, the
switch configuration message MUST be extended to provide a list of switch configuration message MUST be extended to provide a list of
the transport layers for which an optical switch can perform the transport layers for which an optical switch can perform
switching. For supporting various types of switching capable switching. For supporting various types of switching capable
interfaces, Optical Switch Configuration Message SHOULD contain the interfaces, the following optical switch configuration blocks SHOULD
Switching Interface ID. be added in the Switch Configuration message.
Message Type = TBD
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
GSMPv3 for Optical Support June 2003
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Version | Message Type | Result | Code | | SW capable | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID | Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|I| SubMessage Number | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MType | MType | MType | MType |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Firmware Version Number | Window Size |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Switch Type | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +
| Switch Name |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Max Reservations |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Optical Switching Interface IDs ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Optical Switching Interface ID: variable Switching Capable Layer : 8 bits
TBD This field indicates the supported switching capable layers in an
optical switch. It has three flags which indicate the layers. The
The following lists are the possible switching capable layers. flags can be set at the same time when the optical switch contains
multiple transport layers.
- switching per optical burst X X X X X X F B L
- switching per a single wavelength -------------------
- switching per a waveband
GSMPv3 for Optical Support March 2003
- switching per a single fiber X: reserved field
- switching per a fiber bundle F: indicates the switching capable layer per a fiber
B: indicates the switching capable layer per a waveband
L: indicates the switching capable layer per a wavelength
7.2 Port Configuration Message 8.2 Port Configuration Message
The port configuration message informs a controller configuration The port configuration message informs a controller configuration
information related to a single port. Ports in optical switches information related to a single port. Ports in optical switches
differ from those in electrical switches. The ports defined in GSMPv3 differ from those in electrical switches. The ports defined in GSMPv3
imply a single physical link and several connections are specified imply a single physical link and several connections are specified
with labels in a port. However, a single port does not identify a with labels in a port. However, a single port does not identify a
single link in optical domain. A port can imply a set of fibers, a single link in optical domain. A port can imply a set of fibers, a
single fiber, or a single wavelength. Therefore different types of single fiber, or a single wavelength. Therefore different types of
port SHOULD be identified in GSMPv3. Moreover, OXC can have many bays port SHOULD be identified in GSMPv3.
which contain hundreds of shalves which have tens of thousands of
port. Therefore, physical bay and shelve identifiers also SHOULD be
defined and encoded in the port configuration message.
The basic format and usage of Port Configuration message follow [1]. The basic format and usage of Port Configuration message follow [1].
The following new port types are defined. In optical domain, PortType The following new port types are defined to support optical switch.
can be classified into per fiber bundle containing several fibers, a
single fiber containing several wavelengths, or a single wavelength.
PortType = optical switching (TBA by IANA)
This port type further can be classified into several types as Value PortType
following. ------ ---------
10 a fiber (wavelength)
PortType = fiber in optical switching When the value of PortType is in the above range, we call "PortType =
PortType = wavelength in optical switching Optical Switching" in the following section.
...
7.2.1 PortType Specific Data for Optical Switching 8.2.1 PortType Specific Data for Optical Switching
The format and usage of Port Specific Data in Port Configuration The format and usage of Port Specific Data in Port Configuration
message depends on the PortType value and the basic format of it is message depends on the PortType value and the basic format of it is
given as following [1]. given as following [1].
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|P|M|L|R|Q| Label Range Count | Label Range Length | |P|M|L|R|Q| Label Range Count | Label Range Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
GSMPv3 for Optical Support June 2003
~ Default Label Range Block ~ ~ Default Label Range Block ~
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Receive Data Rate | | Receive Data Rate |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Transmit Data Rate | | Transmit Data Rate |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
GSMPv3 for Optical Support March 2003
| Port Status | Line Type | Line Status | Priorities | | Port Status | Line Type | Line Status | Priorities |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Physical Slot Number | Physical Port Number | | Physical Slot Number | Physical Port Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Note: Fields and Parameters that have not been explained in the Note: Fields and Parameters that have not been explained in the
Subsection follow [1]. Subsection follow [1].
In this section, we specify some fields for supporting optical In this section, we specify some fields for supporting optical
switching as following. If PortType is equal to optical switching, switching as following. If PortType is equal to optical switching,
skipping to change at page 17, line 29 skipping to change at page 14, line 36
(interface) in; (interface) in;
Bits/sec for PortType = Optical Switching Bits/sec for PortType = Optical Switching
Transmit Data Rate Transmit Data Rate
The maximum rate of data that may depart from the output port The maximum rate of data that may depart from the output port
(interface) in; (interface) in;
Bits/sec for PortType = Optical Switching Bits/sec for PortType = Optical Switching
Port Status
Give the administrative state of the port. The new values of the Port
Status are defined to indicate recovery capability in port.
Recovery:
Port Status = 6. The port is reserved for recovery support. For
1+1 dedicated protection, this port is configured to transmit
traffic as a backup. On the other hand, for 1:1 protection, this
port is just configured to reserve the connection without
transmitting traffic.
Line Type Line Type
The type of physical transmission interface for this port. The line The type of physical transmission interface for this port. The line
type for optical support depends on switching interface for each type for optical support depends on switching interface for each
switching entity, such as for wavelength-related port or fiber- switching entity, such as for wavelength-related port or fiber-
related port. This field MAY define bit rate of wavelength, fiber related port. This field MAY define range of wavelength, fiber type,
type. The following values can be identified for optical support. and so on. For example,
PortType = Optical Switching: TBD Line Type for PortType = a fiber
------------------------
Single Mode Fiber
Multi Mode Fiber
GSMPv3 for Optical Support June 2003
Dispersion Shifted Fiber
Nonzero Dispersion Fiber
Line Type for PortType = a wavelength
------------------------
1300nm
1550nm
Physical Slot Number Physical Slot Number
The physical location of the slot in optical switching (or OXC). The physical location of the slot in optical switching (or OXC).
Since the OXC systems can have many bays which contain hundreds of Since the OXC systems can have many bays which contain hundreds of
shelf which have tens of thousands of port this field SHLOULD shelf which have tens of thousands of port this field SHLOULD
identify the slot. For doing so, the field MAY be partitioned into identify the slot. For doing so, the field MAY be partitioned into
several sub-fields to define bay, shelf, and slot. several sub-fields to define bay, shelf, and slot.
The default label range block for optical switching has the The default label range block for optical switching has the following
following format. format.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|x|x|x| Label Type | Label Length | |x|x|x|x| Label Type | Label Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
~ Label Value ~ ~ Label Value ~
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
GSMPv3 for Optical Support March 2003
Label Type: 12 bit Label Type: 12 bit
Label type for optical support. Each encoding type of the labels is Label type for optical support. Each encoding type of the labels is
TBD. TBD.
Label value: Variable Label value: Variable
Carries label information. The interpretation of this field depends Carries label information. The interpretation of this field depends
on the type of the link (or the type of connection) over which the on the type of the link (or the type of connection) over which the
label is used. Min Label and Max label value imply the range of label is used. Min Label and Max label value imply the range of
available optical labels. Each encoding type of the labels is TBD. available optical labels. Each encoding type of the labels is TBD.
7.3 All Ports Configuration Message 9. Event Messages
The message format and usage of it follows [1], and optical The Event messages allow a switch to inform a controller of certain
switching-related contents follow section 7.2. asynchronous events. This draft deals with recovery-related events.
The indication of these asynchronous events related to ports and
labels can inform failure of them to the controller and it can
initiate a fault recovery mechanism. In the following sub-sections,
two messages, Recovery Completion message and Fault Notification
message, are used to notify a controller fault-related events of a
switch.
7.4 Service Configuration Message GSMPv3 for Optical Support June 2003
The Service Configuration message requests an optical switch report Event messages for recovery-related events have the following format:
the configuration information of the supported services. The
requested services are identified in service ID in the Add Branch
message or the Reservation Management message. The service model is
defined with traffic parameter, QoS parameter, and traffic control
elements in [1], but these parameters can not be used to specify the
optical services. Therefore this message SHOULD be modified to
support optical services with newly defined capability sets. The
services supported at optical switches SHOULD be defined for dealing
with optical burst, wavelength, waveband, and fiber connection.
7.4.1 Optical Service Configuration Message 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Version| Sub | Message Type | Result| Code |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID | Transaction Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|I| SubMessage Number | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x x x x x x x x x x x x x x x x| Number of Blocks |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ Recovery-Related Blocks ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
TBD. [Note] Fields and Parameters that have not been explained SHOULD be
referred to [1].
8. Event Messages Number of Blocks
This field implies the total number of the recovery-related blocks.
By notifying the contents of the recovery-related blocks in a single
event message to the controller the recovery-related events can be
processed in very short time. The number of Blocks in a single Event
message for recovery-related events MUST NOT cause the packet length
to exceed toe maximum transmission unit defined by the encapsulation.
The Event messages allow a switch to inform a controller of certain Recovery-Related Blocks
asynchronous events. In this version of GSMPv3, asynchronous events This field contains several recovery-related blocks for the suitable
mainly deal with recovery-related events. The indication of these purpose of the messages. In this draft, these fields are used to
asynchronous events related to ports and switch elements can inform notify recovery completion or fault notification. More message
failure of them to the controller and it can initiate a fault specific contents are dealt with in the following sub-sections.
recovery mechanism. The basic message format and usage of it SHOULD
be referred to [1]. The two messages, Restoration Completion message
and Fault Notification message, are used to notify a controller
fault-related events of a switch.
8.1 Restoration Completion Message 9.1 Recovery Completion Message
GSMPv3 for Optical Support March 2003
For 1+1 dedicated recovery, a failed working connection is switched This message is used to notify the recovery completion to the
over to another dedicated connection without a controller's controller by the switch after the failed elements are restored. This
recognition. This message is used to inform the controller message contains restored connection information. Restored Connection
restoration completion of the switch. This message contains failed information implies restored Port IDs and Label IDs. By using this
working connection ID and restored backup connection ID. message, the recovery completion of several failed connections, which
consist of port and label, are notified to the controller at one time.
Message Type = TBA Message Type = TBA
If a message type is equal to Restoration Completion message the If a message type is equal to Recovery Completion message the
following sub-TLVs SHOULD be added on the message in order to notify following Recovery Completion Blocks SHOULD be added on the message
restoration completion to a controller. GSMPv3 for Optical Support June 2003
in order to notify the recovery completion of all failed ports and
all fault-affected labels to the controller.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | Restored Port ID |
~ Restored Port ID list ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | Restored Label ID |
~ Restored Switch Element ID list ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
8.2 Fault Notification Message Restored Port ID list; variable
This field describes the restored port IDs which contain different
types of port which indicate wavelength-related port, fiber-related
port, or fiber bundle-related port.
Restored Label ID list; variable
This field describes the restored label ID which comes to be used
again from a fault.
9.2 Fault Notification Message
This message is used to inform a controller a fault occurring in a This message is used to inform a controller a fault occurring in a
switch. The possible faults are link failure from cutting off switch. The possible faults are link failure from cutting off
(affecting wavelengths, fibers, fiber bundles), port failure, or (affecting wavelengths, fibers, fiber bundles), port failure, or
switch modules. For the notification purpose, the following sub-TLV switch modules. For the notification purpose, the following Fault
SHOULD be added in Event message. Notification blocks SHOULD be added in Event message.
Message type = TBA Message type = TBA
If a message type is equal to Fault Notification message the If a message type is equal to Fault Notification message the
following sub-TLV SHOULD be added on the message in order to notify a following Fault Notification blocks SHOULD be added on the message in
fault in a switch to a controller. order to notify all fault-affected ports and labels in a switch to a
controller.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Failed Port ID list | | Failed Port ID |
~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Failed Switch Element ID list | | Failed Label ID |
~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Failed Port ID list; variable Failed Port ID list; variable
This field describes the failed port ID which contains different This field describes the failed port ID which contains different
types of port which indicate wavelength-related port, fiber-related types of port which indicate wavelength-related port, fiber-related
port, or fiber bundle-related port. This field can consist of several port, or fiber bundle-related port.
sub-TLVs to indicate the failed elements.
Failed Switch Element ID list; variable Failed Label ID list; variable
GSMPv3 for Optical Support March 2003 This field describes the failed label ID which comes to not be used
from a connection failed.
This field describes the failed optical switch fabric such as, GSMPv3 for Optical Support June 2003
wavelength converters, cross connect elements, and so on. It depends
on the optical switching systems.
The encoding of Failed Switch Element is TBD 10. Service Model Definition
9. Optical Service Model Definition In the GSMP Service Model a controller may request the switch to
establish a connection with a given Service. The requested Service is
identified by including a Service ID in the Add Branch message or the
Reservation message. The Service ID refers to a Service Definition
(defined in chapter 10 of [1]). This chapter defines the various
Service ID for optical capable switches.
TBD The following Service Identifiers are defined for optical support.
10. Failure Response Codes ID Range Service Type
-------- ------------
128 - 191 Optical Switch Services
Service Identifier
The reference number used to identify the Service in GSMP.
Service Characteristics
A definition of the Service
Traffic Parameters
A definition of the Traffic Parameters used in connection management
messages.
QoS parameters
A definition of the QoS Parameters that are included in the
Capability Set for instances of the Service.
Traffic Controls
A definition of the Traffic Controls that may be supported by an
instance of the Service.
11. Failure Response Codes
This chapter describes the failure and warning states which can occur This chapter describes the failure and warning states which can occur
in setup optical connections. The following lists are the codes that in setup optical connections. The following lists are the codes that
SHOULD be defined and added in the Failure Response messages. These SHOULD be defined and added in the Failure Response messages. These
codes MAY be added more when the services for optical switching are codes MAY be added more when the services for optical switching are
defined. defined.
If the switch issues a failure response it MUST choose the most If the switch issues a failure response it MUST choose the most
specific failure code according to the following precedence. The code specific failure code according to the following precedence. The code
numbers will be assigned in IANA. numbers will be assigned in IANA.
Optical Connection Failure Optical Connection Failure
GSMPv3 for Optical Support June 2003
- recovery failure - recovery failure
Due the limitation of available resource for backup connection, Due the limitation of available resource for recovery connection,
for example, multiple links failure, the switch can not be for example, multiple links failure, the switch can not be
succeeded the recovery procedure for shared protected connection. succeeded the recovery procedure for shared protected connection.
- waveband connection setup failure - waveband connection setup failure
There are not available wavelengths which belong to the range of There are not available wavelengths which belong to the range of
min and max limits of the waveband min and max limits of the waveband
- reservation failure for optical burst - reservation failure for optical burst
In case of delayed reservation in time is not exactly matched, In case of delayed reservation in time is not exactly matched,
the reservation of optical burst can be failed. the reservation of optical burst can be failed.
The following list gives a summary of the failure codes defined for The following list gives a summary of the failure codes defined for
failure response messages: failure response messages:
- no available label for shortage of available wavelengths - no available label for shortage of available wavelengths
- no available resource for recovery - no available resource for recovery
- no available resource for waveband connection setup - no available resource for waveband connection setup
- no match for the delayed reservation for optical burst connection - no match for the delayed reservation for optical burst connection
11. Security Considerations 12. Security Considerations
GSMPv3 for Optical Support March 2003
This document does not have any security concerns. The security This document does not have any security concerns. The security
requirements using this document are describes in the referenced requirements using this document are described in the referenced
documents. documents.
Appendix I. Protection and Restoration Capability in GSMPv3 Appendix I. Protection and Restoration Capability in GSMPv3
The GSMP controller MUST support the protection and restoration The GSMP controller MUST support the protection and restoration
capabilities because the optical switch delivers several Gbps data capabilities because the optical switch delivers several Gbps data
traffic in a single wavelength. To achieve fast protection and traffic in a single wavelength. To achieve fast protection and
restoration, the optical switch is capable of taking an action restoration, the optical switch MAY be capable of taking an action
independent of the GSMP controller, then it informs the controller independent of the GSMP controller, then it informs the controller
after completing the restoration [2]. This differs from the master- after completing the restoration [2]. This differs from the master-
slave relationship in GSMP. slave relationship in GSMP.
Recovery mechanisms do not distinguish path (end-to-end) and link Recovery mechanisms do not distinguish path (end-to-end) and link
recovery in GSMPv3. The difference of them is considered in signaling recovery in GSMPv3. The difference of them is considered in signaling
protocol. In case of dynamically calculating the backup link after a protocol. In case of dynamically calculating the recovery connection
fault occurs, GSMPv3 establishes a new backup link by using the after a fault occurs, GSMPv3 establishes a new recovery connection by
existing Add Branch message. Therefore, this draft considers pre- using the existing Add Branch message. Therefore, this draft
planned recovery mechanisms, such as 1+1 dedicated recovery, 1:1 considers pre-planned recovery mechanisms, such as 1+1 dedicated
dedicated recovery with/without extra traffic, and 1:N/M:N shared recovery, 1:1 dedicated recovery with/without extra traffic, and
recovery. 1:N/M:N shared recovery.
The label switch SHOULD provide the protection and restoration The label switch SHOULD provide the protection and restoration
capabilities in order to provide the recovery mechanisms. For example, capabilities in order to provide the recovery mechanisms. For example,
GSMPv3 for Optical Support June 2003
an ingress/egress node reserves backup resources according the each an ingress/egress node reserves backup resources according the each
recovery mechanism, and setup the switch fabric. Then, GSMPv3 is used recovery mechanism, and setup the switch fabric. Then, GSMPv3 is used
to control the switch. to control the switch.
In this section, the recovery mechanisms which can be provided by In this section, the recovery mechanisms which can be provided by
GSMPv3 is specified with including a fault notification, and GSMPv3 are specified with an included fault notification, and
restoration, and related required messages. For example, the port restoration, and related required messages. For example, the port
configuration command MUST be extended to allow autonomous protection configuration command MUST be extended to allow autonomous protection
mechanism. The current GSMP connection management also MUST be mechanism. The current GSMP connection management also MUST be
extended to support this function. In the following subsections, the extended to support this function. In the following subsections, the
supported recovery mechanisms in GSMPv3 are introduced. supported recovery mechanisms in GSMPv3 are introduced.
1.1 1+1 dedicated recovery mechanism 1.1 1+1 dedicated recovery mechanism
In this recovery mechanism, GSMPv3 utilizes the existing Connection - Recovery connection configuration
Management messages. It is not necessary to notify a fault to the All nodes on a working connection use Add Branch message(P) to
controller and restore the failed working link at physical layer. configure a recovery connection. The ingress node transmits traffic
Then, the switch notifies the recovery completion to the controller through the working connection as well as the recovery connection. An
by using Event message. The recovery procedure of the mechanism egress only chooses traffic from the working connection with ignoring
follows. them from the recovery connection. In order to support this type of
recovery mechanism, the optical switch SHOULD support it physically.
- Backup link configuration
Use Add Branch message as for working link.
GSMPv3 for Optical Support March 2003
- Fault notification
Let physical layer process before GSMPv3 recognizes.
- Recovery procedure - Recovery procedure
Let physical layer process before GSMPv3 recognizes. When a failure occurs, a fault-affected working connection is
switched over a 1+1 dedicated recovery connection without notifying
- After recovery completion; the controller. The recovery process is performed at the physical
Firstly, the switch notifies recovery completion to the controller by layer automatically. After the recovery is completed, the switch
using Restoration Completion message, then notifies the recovery completion to the controller by using Event
message.
* Revertible mode; GSMPv3 uses Move Input message to switch the
currently used backup link to the restored working link at an
egress node.
* Non-revertible mode; GSMPv3 deletes the restored working link by
using Delete Branch message, and then configures a new backup
link by using Add Branch message.
1.2 1:1 dedicated recovery mechanism 1.2 1:1 dedicated recovery mechanism
- Backup link configuration 1) 1:1 protection
An ingress/egress node configure a backup link by using Reservation
Request message, and core nodes use Add Branch message to reserve
backup link. In this recovery mechanism, extra traffic can be
delivered through the backup link. If it could be possible, core
nodes use Reservation request message, not Add Branch message.
However this draft only considers the former case as this mechanism.
- Fault notification
* Fault detected from signaling protocol; GSMPv3 have already
known the fault, it directly go into the recovery procedure.
* Fault detected from the switch; Event message (esp. Fault - Recovery connection configuration
Notification message) is used to notify the fault to the All nodes on a working connection configure a recovery connection by
controller. using Add Branch message. However, the ingress node does not transmit
any traffic through the reserved recovery connection since the switch
does not cross connect for the recovery connection.
- Recovery procedure - Recovery procedure
An ingress node uses Move Output message and an egress node used Move When an ingress node detects a fault it switches over the fault-
Input message in order to configure a backup link. Since the backup affected working connection to the reserved recovery connection. This
path is configured through the network, core nodes do not take any type of recovery does not require configuring additional connection
action for recovery. configuration because the recovery connection has been already
established by using Add Branch message(P). Then, an egress node
- After recovery completion switches over the recovery connection to receive traffic.
Firstly, the switch notifies recovery completion to the controller by
using Restoration Completion message, then
* Revertible mode; GSMPv3 uses Move Input message (at an ingress
node) and Move Output message (at an egress node) to switch the
currently used backup link to the restored working link at
GSMPv3 for Optical Support March 2003
destination node. The backup link is still used for backup by
using Reservation Request message.
* Non-revertible mode; Delete Branch message can be used to delete
the restored working link. GSMPv3 uses Reservation Request
message to reserve new backup link for the working link.
1.3 1:N/M:N shared recovery mechanism
- Backup link configuration
Reservation Request message is used to configure a backup link. Since
several working links (= N) share one backup link (1:N) or several
backup links (M:N) GSMPv3 SHUOLD know the sharing working link IDs
for the backup links. Resource management of GSMPv3 is out of scope
of this draft.
- Fault notification GSMPv3 for Optical Support June 2003
* Fault detected from signaling protocol; GSMPv3 have already 2) 1:1 restoration
known the fault, it directly go into the recovery procedure.
* Fault detected from the switch; Event message (esp. Fault - Recovery connection configuration
Notification message) is used to notify the fault to the controller. An ingress node and an egress node both configure a recovery
connection by using the Reservation Request message(P), and core
nodes also use it to reserve recovery connection. Extra traffic can
be delivered through the recovery connection.
- Recovery procedure - Recovery procedure
When GSMPv3 is notified a fault, it uses Add Branch message to The ingress node and the egress node use Add Branch message in order
configure a new working link by using reserved backup link. to configure a recovery connection. Other core nodes also configure
the recovery connection with Add Branch message(P) with the reserved
resource.
- After recovery completion 1.3 1:N/M:N shared recovery mechanism (M, N > 1, M <= N)
Firstly, the switch notifies recovery completion to the controller by
using Restoration Completion message, then
* Revertible mode; GSMPv3 uses Move Input message (at an ingress - Recovery connection configuration
node) and Move Output message (at an egress node) to switch the Reservation Request message(P) is used to configure a recovery
currently used backup link to the restored working link at connection. Since several working connections (= N) share one
destination node. The backup link is still used for shared recovery connection (1:N) or several recovery connections (M:N)
backup by using Reservation Request message. GSMPv3 SHUOLD know the sharing working connection IDs for the
recovery connections.
* Non-revertible mode; Delete Branch message can be used to delete - Recovery procedure
the restored working link. GSMPv3 uses Reservation Request When the GSMPv3 controller is notified a fault, it uses Add Branch
message to reserve new backup link for the working link. message(P) to configure a new working connection by using reserved
recovery connection. The Add Branch message(P) SHOULD contain the
information about the reserved recovery connection.
Appendix II. GSMPv3 support for optical cross-connect system Appendix II. GSMPv3 support for optical cross-connect systems
The GSMPv3 controls and manages the optical cross-connect systems as The GSMPv3 controls and manages the optical cross-connect systems as
label switches. The optical cross-connect (OXC) is a space division label switches. The optical cross-connect (OXC) is a space division
switch that can switch an optical data stream on an input port to an switch that can switch an optical data stream on an input port to an
output port. The OXCs are all optical cross-connects (optical- output port. The OXCs are all optical cross-connects (optical-
optical-optical), transparent optical cross connects (optical- optical-optical), transparent optical cross connects (optical-
electrical-optical, frame independent), and opaque optical cross electrical-optical, frame independent), and opaque optical cross
GSMPv3 for Optical Support March 2003
connects (optical-electrical-optical, SONET/SDH frames).These OXC connects (optical-electrical-optical, SONET/SDH frames).These OXC
(optical cross connect) systems can be IP-based optical routers which (optical cross connect) systems can be IP-based optical routers which
are dynamic wavelength routers, optical label switches, or are dynamic wavelength routers, optical label switches, or
burst/packet-based optical cross connects, and so on[2]. burst/packet-based optical cross connects, and so on[2].
The OXC system consists of switching fabric, multiplexer/ The OXC system consists of switching fabric, multiplexer/
demultiplexer, wavelength converter, and optical-electrical/ demultiplexer, wavelength converter, and optical-electrical/
electrical-optical converter. Multiple wavelengths are multiplexed or electrical-optical converter. Multiple wavelengths are multiplexed or
demultiplexed into a fiber. Multiple fibers belong to a fiber bundle. demultiplexed into a fiber. Multiple fibers belong to a fiber bundle.
A wavelength, a waveband, and a fiber can be used to establish a A wavelength, a waveband, and a fiber can be used to establish a
connection in an optical switch. They SHOULD be recognized at a port connection in an optical switch. They SHOULD be recognized at a port
in the OXC since they are connection entities. When the OXC has in the OXC since they are connection entities. When the OXC has
GSMPv3 for Optical Support June 2003
optical-electrical conversion at the input port and electrical- optical-electrical conversion at the input port and electrical-
optical conversion at the output port it is called as opaque OXC. Or, optical conversion at the output port it is called as opaque OXC. Or,
when it processes optical data stream all optically it is called as when it processes optical data stream all optically it is called as
transparent OXC. Wavelength converter SHOULD be used to resolve transparent OXC. Wavelength converter SHOULD be used to resolve
output port contention when two different connections try to be output port contention when two different connections try to be
established in a same output port. Since the wavelength converter can established in a same output port. Since the wavelength converter can
work only within a limited operating range, the limited numbers of work only within a limited operating range, the limited numbers of
wavelengths are used at the output port. It limits the available wavelengths are used at the output port. It limits the available
wavelengths at the output port. wavelengths at the output port.
If OXCs perform protection and restoration functions they SHOULD have If OXCs perform protection and restoration functions they SHOULD have
suitable switch structure to support them. In case of 1+1 dedicated suitable switch structure to support them. In case of 1+1 dedicated
recovery, input ports and output ports MUST be duplicated in a switch. recovery, input ports and output ports MUST be duplicated in a switch.
The switch transmits optical signal through two ports (one for The switch transmits optical signal through two ports (one for
working connection and another for backup connection) simultaneously. working connection and another for recovery connection)
When a fault happens the switch switches over from failed working simultaneously. When a fault happens the switch switches over from
connection to dedicated backup connection without noticing a failed working connection to dedicated recovery connection without
controller. noticing a controller.
In order to control and manage the OXC systems, GSMP SHOULD be
located as a subset of functions for it and MUST know the current
switch, port and service configuration information. GSMP controller
SHOULD identify the connection entities at the OXC and match them
with the optical labels.
References References
[1] Doria, A, Sundell, K, Hellstrand, F, Worster, T, "General Switch [1] Doria, A, "GSMPv3 Base Specification", draft-ietf-gsmp-base-spec-
Management Protocol V3", RFC 3292, June 2002. 02.txt (work in progress), June 2003.
[2] Georg Kullgren, et. al., "Requirements For Adding Optical Support [2] Georg Kullgren, et. al., "Requirements For Adding Optical Support
To GSMPv3",draft-ietf-gsmp-reqs-04.txt (work in progress), Nov. 2002. To GSMPv3",draft-ietf-gsmp-reqs-06.txt (work in progress), June 2003.
[3] Mannie, E., et. al., "Generalized Multi-Protocol Label Switching [3] Mannie, E., et. al., "Generalized Multi-Protocol Label Switching
(GMPLS) Architecture", draft-ietf-ccamp-gmpls-architecture-03.txt (GMPLS) Architecture", draft-ietf-ccamp-gmpls-architecture-07.txt
(work in progress), August 2002. (work in progress), May 2003.
GSMPv3 for Optical Support March 2003
[4] Ashwood-Smith, D., et. al., "Generalized MPLS - Signaling [4] Ashwood-Smith, D., et. al., "Generalized MPLS - Signaling
Functional Description", RFC3471, Jan. 2003. Functional Description", RFC3471, Jan. 2003.
[5] Rajagopalan, B., et. al., "IP over Optical Networks: A Framework", [5] Rajagopalan, B., et. al., "IP over Optical Networks: A Framework",
draft-ietf-ipo-framework-03.txt (work in progress), Jan. 2003. draft-ietf-ipo-framework-04.txt (work in progress), April 2003.
[6] J. Lang, et. at. "Link Management Protocol (LMP) ", draft-ietf- [6] J. Lang, et. at. "Link Management Protocol (LMP) ", draft-ietf-
ccamp-lmp-07.txt (work in progress), November 2002. ccamp-lmp-09.txt (work in progress), April 2003.
[7] C. Qiao, M. Yoo, "Choice, and Feature and Issues in Optical Burst [7] C. Qiao, M. Yoo, "Choice, and Feature and Issues in Optical Burst
Switching", Optical Net. Mag., vol.1, No.2, Apr.2000, pp.36-44. Switching", Optical Net. Mag., vol.1, No.2, Apr.2000, pp.36-44.
[8] OBS Ilia Baldine, George N. Rouskas, Harry G. Perros, Dan [8] Ilia Baldine, George N. Rouskas, Harry G. Perros, Dan Stevension,
Stevension, "JumpStart: A Just-in-time Signaling Architecture for WDM "JumpStart: A Just-in-time Signaling Architecture for WDM Burst-
Burst-Switching Networks", IEEE Comm. Mag., Feb. 2002. Switching Networks", IEEE Comm. Mag., Feb. 2002.
[9] Angela Chiu, John Strans, et. al., "Impairments And Other [9] Angela Chiu, John Strans, et. al., "Impairments And Other
Constraints On Optical Layer Routing", draft-ietf-ipo-impairments- Constraints On Optical Layer Routing", draft-ietf-ipo-impairments-
04.txt (work in progress), Dec. 2002. 05.txt (work in progress), May 2003.
GSMPv3 for Optical Support June 2003
[10] Daniel Awduche, WYakov Rekhter, "Multiprotocol Lambda Switching: [10] Daniel Awduche, WYakov Rekhter, "Multiprotocol Lambda Switching:
Combining MPLS Traffic Engineering Control with Optical Combining MPLS Traffic Engineering Control with Optical
Crossconnects", IEEE Comm. Mag., March 2001 Crossconnects", IEEE Comm. Mag., March 2001.
[11] Doria, A. and K. Sundell, "General Switch Management Protocol [11] Doria, A. and K. Sundell, "General Switch Management Protocol
Applicability", RFC 3294, June 2002. Applicability", RFC 3294, June 2002.
[12] Mannie, E., et. al., "Recovery (Protection and Restoration) [12] Mannie, E., et. al., "Recovery (Protection and Restoration)
Terminology for GMPLS", draft-ietf-ccamp-gmpls-recovery-terminology- Terminology for GMPLS", draft-ietf-ccamp-gmpls-recovery-terminology-
00.txt (work in progress), June 2002 02.txt (work in progress), May 2003.
[13] Vishal Sharma, et. at., "Framework for MPLS-based Recovery", [13] Vishal Sharma, et. at., "Framework for MPLS-based Recovery", RFC
draft-ietf-mpls-recovery-frmwrk-08.txt (work in progress), October 3469, February 2003
2002
Acknowledgement Acknowledgement
This work was supported in part by the Korean Science and Engineering This work was supported in part by the Korean Science and Engineering
Foundation (KOSEF) through OIRC project Foundation (KOSEF) through OIRC project
Author's Addresses Author's Addresses
Jun Kyun Choi Jun Kyun Choi
Information and Communications University (ICU) Information and Communications University (ICU)
58-4 Hwa Ahm Dong, Yusong, Daejon 58-4 Hwa Ahm Dong, Yusong, Daejon
Korea 305-732 Korea 305-732
Phone: +82-42-866-6122 Phone: +82-42-866-6122
Email: jkchoi@icu.ac.kr Email: jkchoi@icu.ac.kr
GSMPv3 for Optical Support March 2003
Min Ho Kang Min Ho Kang
Information and Communications University (ICU) Information and Communications University (ICU)
58-4 Hwa Ahm Dong, Yusong, Daejon 58-4 Hwa Ahm Dong, Yusong, Daejon
Korea 305-732 Korea 305-732
Phone: +82-42-866-6136 Phone: +82-42-866-6136
Email: mhkang@icu.ac.kr Email: mhkang@icu.ac.kr
Jung Yul Choi Jung Yul Choi
Information and Communications University (ICU) Information and Communications University (ICU)
skipping to change at page 26, line 26 skipping to change at page 24, line 4
Korea 305-732 Korea 305-732
Phone: +82-42-866-6208 Phone: +82-42-866-6208
Email: passjay@icu.ac.kr Email: passjay@icu.ac.kr
Gyu Myung Lee Gyu Myung Lee
Information and Communications University (ICU) Information and Communications University (ICU)
58-4 Hwa Ahm Dong, Yusong, Daejon 58-4 Hwa Ahm Dong, Yusong, Daejon
Korea 305-732 Korea 305-732
Phone: +82-42-866-6231 Phone: +82-42-866-6231
Email: gmlee@icu.ac.kr Email: gmlee@icu.ac.kr
GSMPv3 for Optical Support June 2003
Young Wook Cha
Andong National University (ANU)
388 Song-Chon Dong, Andong, Kyungsangbuk-do
Korea 760-749
Phone: +82-54-820-5714
Email: ywcha@andong.ac.kr
Jook Uk Um Jook Uk Um
KT Network Engineering Center KT Network Engineering Center
206 Jungja-dong, Bungdang-gu, Sungnam City, Kyonggi-do, 463-711, 206 Jungja-dong, Bungdang-gu, Sungnam City, Kyonggi-do, 463-711,
Korea Korea
Phone: +82-31-727-6610 Phone: +82-31-727-6610
Email: jooukum@kt.co.kr Email: jooukum@kt.co.kr
Yong Jae Lee Yong Jae Lee
KT Network Engineering Center KT Network Engineering Center
206 Jungja-dong, Bungdang-gu, Sungnam City, Kyonggi-do, 463-711, Korea 206 Jungja-dong, Bungdang-gu, Sungnam City, Kyonggi-do, 463-711, Korea
Phone: +82-31-727-6651 Phone: +82-31-727-6651
Email: cruiser@kt.co.kr Email: cruiser@kt.co.kr
Young Wook Cha
Andong National University (ANU)
388 Song-Chon Dong, Andong, Kyungsangbuk-do
Korea 760-749
Phone: +82-54-820-5714
Email: ywcha@andong.ac.kr
Jeong Yun Kim Jeong Yun Kim
Electronics and Telecommunications Research Institute (ETRI) Electronics and Telecommunications Research Institute (ETRI)
161 KaJong-Dong, Yusong-Gu, Daejeon 161 KaJong-Dong, Yusong-Gu, Daejeon
Korea 305-309 Korea 305-309
Phone: +82-42-866-5311 Phone: +82-42-866-5311
Email: jykim@etri.re.kr Email: jykim@etri.re.kr
Jonathan Sadler
Tellabs Operations, Inc.
1415 West Diehl Road
Naperville, IL 60563
GSMPv3 for Optical Support March 2003
Phone: +1 630-798-6182
Email: Jonathan.Sadler@tellabs.com
Avri Doria Avri Doria
Div. of Computer Communications Div. of Computer Communications
Lulea University of Technology Lulea University of Technology
S-971 87 Lulea S-971 87 Lulea
Sweden Sweden
Phone: +1 401 663 5024 Phone: +1 401 663 5024
EMail: avri@acm.org EMail: avri@acm.org
Full Copyright Statement Full Copyright Statement
skipping to change at line 1343 skipping to change at line 1227
and derivative works that comment on or otherwise explain it or and derivative works that comment on or otherwise explain it or
assist in its implementation MAY be prepared, copied, published and assist in its implementation MAY be prepared, copied, published and
distributed, in whole or in part, without restriction of any kind, distributed, in whole or in part, without restriction of any kind,
provided that the above copyright notice and this paragraph are provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this included on all such copies and derivative works. However, this
document itself MAY not be modified in any way, such as by removing document itself MAY not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process MUST be copyrights defined in the Internet Standards process MUST be
GSMPv3 for Optical Support June 2003
followed, or as required to translate it into languages other than followed, or as required to translate it into languages other than
English. English.
The limited permissions granted above are perpetual and will not be The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns. revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Choi, et. al. Expires - August 2003 [Page 27] Choi, et. al. Expires - December 2003 [Page 25]
 End of changes. 

This html diff was produced by rfcdiff 1.25, available from http://www.levkowetz.com/ietf/tools/rfcdiff/