idnits 2.17.1 draft-ietf-gsmp-optical-spec-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing document type: Expected "INTERNET-DRAFT" in the upper left hand corner of the first page ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? == There are 2 instances of lines with non-ascii characters in the document. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 292 instances of too long lines in the document, the longest one being 4 characters in excess of 72. ** The abstract seems to contain references ([1]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 942 has weird spacing: '...ncluded fault...' == Line 1005 has weird spacing: '...sharing worki...' -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (June 2003) is 7614 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Looks like a reference, but probably isn't: 'Note' on line 761 == Unused Reference: '5' is defined on line 1068, but no explicit reference was found in the text == Unused Reference: '9' is defined on line 1081, but no explicit reference was found in the text == Unused Reference: '11' is defined on line 1089, but no explicit reference was found in the text == Unused Reference: '12' is defined on line 1092, but no explicit reference was found in the text == Unused Reference: '13' is defined on line 1096, but no explicit reference was found in the text -- No information found for draft-ietf-gsmp-base-spec - is the name correct? -- Possible downref: Normative reference to a draft: ref. '1' ** Downref: Normative reference to an Informational draft: draft-ietf-gsmp-reqs (ref. '2') == Outdated reference: A later version (-05) exists of draft-ietf-ipo-framework-04 ** Downref: Normative reference to an Informational draft: draft-ietf-ipo-framework (ref. '5') == Outdated reference: A later version (-10) exists of draft-ietf-ccamp-lmp-09 -- Possible downref: Non-RFC (?) normative reference: ref. '7' -- Possible downref: Non-RFC (?) normative reference: ref. '8' ** Downref: Normative reference to an Informational draft: draft-ietf-ipo-impairments (ref. '9') -- Possible downref: Non-RFC (?) normative reference: ref. '10' ** Downref: Normative reference to an Informational RFC: RFC 3294 (ref. '11') == Outdated reference: A later version (-06) exists of draft-ietf-ccamp-gmpls-recovery-terminology-02 ** Downref: Normative reference to an Informational draft: draft-ietf-ccamp-gmpls-recovery-terminology (ref. '12') ** Downref: Normative reference to an Informational RFC: RFC 3469 (ref. '13') Summary: 14 errors (**), 0 flaws (~~), 13 warnings (==), 8 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 GSMP Working Group Internet Draft Jun Kyun Choi(ICU) 2 Document: draft-ietf-gsmp-optical-spec-02.txt Min Ho Kang(ICU) 3 Expiration Date: December 2003 Jung Yul Choi(ICU) 4 Gyu Myoung Lee(ICU) 5 Young Wook Cha(ANU) 6 June 2003 8 General Switch Management Protocol (GSMP) v3 for Optical Support 10 Status of this Memo 12 This document is an Internet-Draft and is in full conformance with 13 all provisions of Section 10 of RFC-2026. 15 Internet-Drafts are working documents of the Internet Engineering 16 Task Force (IETF), its areas, and its working groups. Note that other 17 groups MAY also distribute working documents as Internet-Drafts. 19 Internet-Drafts are draft documents valid for a maximum of six months 20 and MAY be updated, replaced, or obsolete by other documents at any 21 time. It is inappropriate to use Internet- Drafts as reference 22 material or to cite them other than as "work in progress." 24 The list of current Internet-Drafts can be accessed at 25 http://www.ietf.org/ietf/1id-abstracts.txt 27 The list of Internet-Draft Shadow Directories can be accessed at 28 http://www.ietf.org/shadow.html. 30 Abstract 32 This document describes the General Switch Management Protocol version 3 33 (GSMPv3) for the support of optical switching. GSMPv3 controller SHOULD 34 control optical label switches and manage optical resources on them. 35 This document describes the extended functions of GSMPv3 for optical 36 switching and explains operational mechanisms to implement them. It 37 SHOULD be referred with [1] for the complete implementation. 39 Conventions 41 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 42 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 43 document are to be interpreted as described in RFC-2119. 45 Table of Contents 47 1. Introduction.....................................................2 48 2. GSMP Packet Encapsulation........................................3 49 3. Common Definitions and Procedures for Optical Support............3 50 3.1 Labels..........................................................3 51 3.1.1 Labels for Fiber..............................................5 52 3.1.2 Labels for Waveband...........................................5 53 3.1.3 Labels for Wavelength.........................................6 54 3.1.4 Labels for optical burst......................................6 55 4. Connection Management Messages...................................7 56 4.1 Add Branch Message: Recovery Specific Block.....................7 57 5. Reservation Management Messages..................................8 58 5.1 Reservation Request Message: Recovery Specific Block............9 59 5.2 Reservation Request Message: Optical Burst Specific Block.......9 60 6. Management Message..............................................10 61 6.1 Label Range Message............................................10 62 6.1.1 Optical Label................................................11 63 7. Statistics Messages: Optical Signal Specific Block..............12 64 8. Configuration Messages..........................................12 65 8.1 Switch Configuration Message: Optical Switch Specific Block....12 66 8.2 Port Configuration Message.....................................13 67 8.2.1 PortType Specific Data for Optical Switching.................13 68 9. Event Messages..................................................15 69 9.1 Recovery Completion Message....................................16 70 9.2 Fault Notification Message.....................................17 71 10. Service Model Definition.......................................18 72 11. Failure Response Codes.........................................18 73 12. Security Considerations........................................19 74 Appendix I. Protection and Restoration Capability in GSMPv3........19 75 1.1 1+1 dedicated recovery mechanism...............................20 76 1.2 1:1 dedicated recovery mechanism...............................20 77 1.3 1:N/M:N shared recovery mechanism (M, N > 1, M <= N)...........21 78 Appendix II. GSMPv3 support for optical cross-connect systems......21 79 References.........................................................22 80 Acknowledgement....................................................23 81 Author's Addresses.................................................23 82 Full Copyright Statement...........................................24 84 1. Introduction 86 This document describes the extended functions and their mechanisms 87 of the General Switch Management Protocol version 3 (GSMPv3) for the 88 support of optical switching. GSMPv3 is an asymmetric protocol to 89 control and manage label switch. The label switches that are used for 90 optical switching are all optical cross-connects (optical-optical- 91 optical), transparent optical cross connects (optical-electrical- 92 optical, frame independent), and opaque optical cross connects 93 (optical-electrical-optical, SONET/SDH frames).These optical cross 94 connect (OXC) systems can be IP-based optical routers which are 95 dynamic wavelength routers, optical label switches, or burst/packet- 96 based optical cross connects [2]. In this draft, we do not limit 97 specific OXC systems, but aim to provide the general functions of 98 optical switching and services for connections in general optical 99 switches. 101 GSMPv3 is a label switch controller and provides a control interface 102 to optical switches. The optical resources used in connection setup 103 are different from those used in legacy networks. In optical 104 switching, basic connection units are a fiber, a wavelength, or a 105 burst and they are assumed to be processed in optical domain without 106 optical/electrical/optical conversion. This specification defines the 107 services, traffic control, and QoS guarantee necessary at to support 108 optical switches. This draft defines several sub-TLVs, parameters, 109 and new messages to support optical services and optical connection 110 management. This draft describes optical resources, connection 111 management, optical services, and switch configuration which can be 112 applied in optical domain generally. 114 One of the important OAM functions is protection and restoration 115 function. In the current situation where a single fiber delivers 116 several Tb/s through several wavelengths, when even a single link 117 gets cut it makes a huge turbulence. Therefore GSMPv3, as an optical 118 switch controller, MUST have survivable capability of switches and 119 connections. By extending the management messages of GSMPv3, this 120 function will be implemented. 122 [Note] For the complete implementation this document MUST be referred 123 with [1]. 125 2. GSMP Packet Encapsulation 127 GSMP Packets may be transported via any suitable medium. GSMP packet 128 encapsulation for optical support will be defined in separate 129 documents. 131 3. Common Definitions and Procedures for Optical Support. 133 3.1 Labels 135 Labels are the basic identifiers for connections. In order to setup 136 connections in optical switch, new labels MUST be defined. Newly 137 defined labels identify entities that are to be switched in optical 138 switches. Generalized Multi-Protocol Label Switching (GMPLS) defines 139 packet switching capable (PSC), Time-Division Multiplex Capable (TDM), 140 lambda switching capable (LSC), fiber switching capable (FSC) 141 interfaces, and it introduces needs of generalized labels to support 142 them [3][4]. The following list is the labels to be supported in 143 GSMPv3 for optical support [2][3][4][7][8][10]. 145 - a single fiber in a bundle 146 - a single waveband within a waveband (or )fiber 147 - a single wavelength within a fiber 148 - an optical burst within a wavelength 150 All labels are encoded in a common structure composed of three fields, 151 a Type, a Length, and a Value [1]. A label TLV is encoded as a 2- 152 octet field that uses 12 bits to specify a Type and four bits to 153 specify certain behavior specified below, followed by 2-octec Length 154 field, and followed by a variable length Value field. 156 A summary of TLV labels supported by the GSMPv3 extensions for 157 optical support defined in this document is listed below: 159 TLV Label Label Type 160 -------------------- ----------- 161 Fiber Label 0x300 162 Waveband Label 0x301 163 Wavelength Label 0x302 164 Optical burst Label 0x303 166 All labels will be designated as follow: 168 0 1 2 3 169 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 170 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 171 |x|S|x|x| Label Type | Label Length | 172 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 173 | | 174 ~ Label Value ~ 175 | | 176 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 178 X: Reserved Flags 179 These are generally used by specific messages and will be defined in 180 those messages. 182 S 183 Stacked Label Indicator 185 Label Type 186 A 12-bit field indicating the type of label. 188 Label Length 189 A 16-bit field indicating the length of the Label Value field in 190 bytes. 192 Label value: Variable 193 A variable length field that is an integer number of 32 bit words 194 long. The interpretation of this field depends on the Label Type as 195 described in the following sections. 197 3.1.1 Labels for Fiber 199 This label indicates a fiber to be used for a connection 200 establishment in optical switching. The label value only has 201 significance between two neighbors, and the receiver MAY need to 202 convert the received value into a value that has local significance. 204 If the label type = labels for fiber, the label MUST be interpreted 205 as labels for fiber and it has the following format: 207 0 1 2 3 208 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 209 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 210 | Label | 211 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 213 Label: 32 bits 214 Indicates a label for fiber to be used. 216 3.1.2 Labels for Waveband 218 A waveband is a set of contiguous wavelengths which can be switched 219 together to a new waveband [3][4]. It MAY be desirable for an optical 220 cross connect to optically switch multiple wavelengths as a unit 221 since it MAY reduce distortion on individual wavelengths and MAY 222 allow tighter separation of individual wavelengths. Waveband 223 switching introduces another level of label hierarchy and as such the 224 waveband is treated the same way all other upper layer labels are 225 treated. The waveband label is defined to support such a waveband 226 switching. The waveband label can be encoded in three parts; waveband 227 ID, start label, and end label. The start label and the end label 228 represent the lowest value of wavelength and the highest value of 229 wavelength. 231 If the label type = labels for waveband, the label MUST be 232 interpreted as labels for waveband and it has the following format: 234 0 1 2 3 235 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 236 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 237 | Waveband Id | 238 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 239 | Start Label | 240 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 241 | End Label | 242 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 244 Waveband Id: 32 bits 245 A waveband identifier. The value is selected by a sender and reused 246 in all subsequent related messages. 248 Start Label: 32 bits 249 Indicates the lowest value of wavelength in the waveband. 251 End Label: 32 bits 252 Indicates the highest value wavelength in the waveband. 254 The start/end label are established either by configuration or by 255 means of a protocol such as LMP [6]. They are normally used in the 256 label parameter of the Generalized Label one PSC and LSC [3][4]. 258 3.1.3 Labels for Wavelength 260 The label indicates a single wavelength to be used for a connection 261 establishment in optical switching. The label value only has 262 significance between two neighbors, and the receiver MAY need to 263 convert the received value into a value that has local significance. 265 If the label type = labels for wavelength, the label MUST be 266 interpreted as labels for wavelength and a format of the label for 267 wavelength is given as the below: 269 0 1 2 3 270 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 271 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 272 | Label | 273 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 275 Label: 32 bits 276 Indicates label for wavelength to be used. 278 3.1.4 Labels for optical burst 280 The label for optical burst represents a label for switching data 281 burst in optical domain. 283 Optical data burst switching, which utilizes finer granularity in 284 time domain in a coarse granularity such as a wavelength, is a new 285 connection entity in optical domain [7][8]. Connection setup for 286 optical burst includes reserving time on the transport medium for the 287 client. 289 This time is characterized by two parameters: start time and duration 290 of data burst. These values define a fast one-way reservation. Upon a 291 request for a connection setup for data burst, the GSMP controller 292 MUST perform appropriate Connection Admission Control for the start 293 time and duration of data burst specified. If the connection is 294 allowed, it MUST signal these parameters to the burst switching 295 device to reserve the exact bandwidth required [7][8]. The burst 296 switch MUST perform switching operation autonomously, using 297 synchronization methods prescribed for the burst network it is 298 operating in. 300 If the label type = labels for optical burst, the label MUST be 301 interpreted as labels for burst switching and a format of the label 302 for optical burst is given as the below: 304 0 1 2 3 305 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 306 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 307 | Label | 308 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 310 Label: 32 bits 311 Indicates label for a burst level connection. 313 4. Connection Management Messages 315 Connection management messages, which are used for establishing, 316 releasing, modifying, and verifying connections across the switch by 317 the controller, SHOULD operate for optical switching. Connection 318 management messages also SHOULD support recovery capabilities of 319 optical switch and these are mainly dealt with in the following sub- 320 sections. 322 The general message definition and semantics in this section follow 323 [1] and the other untouched items are dealt with in it. 325 4.1 Add Branch Message: Recovery Specific Block 327 Recovery capability of optical switch is supported by Add Branch 328 message by establishing recovery connection in order to protect 329 working connection. By using this message a recovery connection is 330 established for various types of recovery mechanism. The recovery 331 block defines a recovery type, connection type, and related 332 connection information for the purpose of recovery. 334 The Add Branch message adds the following block for recovery 335 capability. 337 0 1 2 3 339 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 340 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 341 |Recovery Type |Connection Type| Reserved | 342 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 343 | Recovery Related Port 1 | 344 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 345 | Recovery Related Label 1 | 346 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 347 | . . . | 348 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 349 | . . . | 350 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 351 | Recovery Related Port N | 352 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 353 | Recovery Related Label N | 354 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 356 Recovery Type; 8 bits 357 This field provides the required information for various types of 358 recovery mechanism when a recovery connection is established by using 359 Add Branch message. The Recovery Type has the following value for 360 various types of recovery mechanism. 362 - 0: 0:1 unprotected 363 - 1: 1+1 dedicated protection 364 - 2: 1:1 protection 365 - 3: 1:1 restoration 366 - 4: 1:N shared recovery 367 - 5: M:N shared recovery 369 Connection Type: 8 bits 370 This field indicates which the message is for a working connection or 371 a recovery connection. 373 - 0: working connection 374 - 1: recovery connection 376 Recovery Related Connection 377 This field indicates the corresponding connection for recovery 378 purpose. If the Add Branch message is used to setup a working 379 connection the field implies the related recovery connection, and 380 vice versa. This information consists of the following two fields. 382 - Recovery Related Port 383 - Recovery Related Label 385 5. Reservation Management Messages 387 The GSMPv3 allows a switch to reserve resources for connections 388 before establishing them through Reservation Management messages. 390 Reservable resources are bandwidth, buffers, queues, labels and etc. 391 In this draft the resources imply optical resources, such as data 392 burst, wavelengths, fibers, and so on. In this section, recovery 393 capability and data burst level switching are supported by using the 394 Reservation Management messages. 396 5.1 Reservation Request Message: Recovery Specific Block 398 Reservation Request message is used to reserve a recovery connection 399 for various types of recovery mechanisms. Especially, in 1:N (M:N) 400 shared recovery scheme, a spare connection is reserved for N working 401 connections. In order to support recovery capability, a recovery 402 connection is configured by reserving backup resource for working 403 connections. The GSMPv3 controller SHOULD have mapping information 404 between a shared backup resource and N working connections. Whenever 405 the GSMPv3 uses the reserved resource for a failed working connection, 406 Add Branch message is used to establish a new connection with New 407 Port/Label of one of N working connections. 409 Reservation Request message adds the following block for recovery 410 capability. 412 0 1 2 3 413 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 414 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 415 |Recovery Type |Connection Type| Reserved | 416 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 417 | Recovery Related Port 1 | 418 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 419 | Recovery Related Label 1 | 420 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 421 | . . . | 422 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 423 | . . . | 424 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 425 | Recovery Related Port N | 426 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 427 | Recovery Related Label N | 428 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 430 NOTE: Fields and parameters in the block refer to section 4.1. 432 5.2 Reservation Request Message: Optical Burst Specific Block 434 Reservation Request message also supports a new connection per data 435 burst in optical domain. Data burst is very short in huge bandwidth 436 of a wavelength and needs to process just in time. However, it takes 437 much time to reserve resource and setup a connection per data burst 438 by using the Reservation Request message. Therefore, a short form of 439 Reservation Request message is used to support data burst. The 440 original Reservation Request message tries to reserve resource for 441 data burst and the short form of the message is used to trigger the 442 resource to switch and transmit the data burst. This message only 443 contains information to identify the reservation as well as the 444 original message. In order to configure a connection per burst, two 445 parameters, offset time and burst length, are added on the message. 446 When a controller receives a request for a connection setup for data 447 burst it sends the message. According to the different switching 448 mechanisms for optical burst [7][8], the value of two fields in the 449 message are assigned. That is, by applying them, connection setup and 450 release are performed explicitly or implicitly. This draft does not 451 limit the usage of the block in a specific switching technology. 452 The following message is the short form of Reservation Request 453 message to support data burst. 455 Message type = TBA 457 0 1 2 3 458 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 459 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 460 | Version | Message Type | Result | Code | 461 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 462 | Partition ID | Transaction Identifier | 463 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 464 |I| SubMessage Number | Length | 465 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 466 | Reservation ID | 467 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 468 | Offset Time (T) | 469 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 470 | Burst Length (L) | 471 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 473 NOTE: Fields and parameters that have not been explained follow 474 [1]. 476 Offset Time (T); TBD 477 This field is the time between a connection request reception and the 478 start of the connection for the data burst. 480 Burst Length (L); TBD 481 This field is the time duration of data burst 483 6. Management Message 485 6.1 Label Range Message 487 The label range, which is specified for each port by the Port 488 Configuration or the All Ports Configuration message, can be 489 specified to the range of label supported by a specified port and to 490 be changed by using Label Range message. Since the granularity of 491 each connection is different in optical domain each port SHOULD allow 492 the label range changeable in ports. In addition, a port MAY have 493 wavelength converters with full or limited capability so that each 494 port MAY have different limited labels. In case of waveband switching, 495 a single label for waveband connection is used for a set of 496 wavelengths in the band. To support these cases, the Label Range 497 message is used. 499 The general usage and the format of this message follows [1]. 501 6.1.1 Optical Label 503 If the Label Type is equal to optical label, the label range message 504 MUST be interpreted as shown: 506 0 1 2 3 507 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 508 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 509 |x|x|V|C| Optical Label | Label Length | 510 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 511 | Min Label | 512 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 513 | Max Label | 514 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 515 | Remaining Labels | 516 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 518 V: Label 519 The Label flag is not used. 521 C: Multipoint Capable 522 Indicates label range that can be used for multipoint connections. 523 This field is not used in this document. 525 Optical Label 526 The optical label indicates the type of label for optical support and 527 is referred to the section 3.1 of this document. 529 Min Label: 530 The minimum label value in the range. 532 Max Label: 533 The maximum label value in the range. 535 Remaining Labels: 536 The maximum number of remaining labels that could be requested for 537 allocation on the specified port. 539 7. Statistics Messages: Optical Signal Specific Block 541 The statistics messages are used to query the performance statistics 542 related to ports and connections for optical transmission. The 543 statistics contain optical transmission characteristics which specify 544 transmission quality of connections. Transmission performance is 545 typically defined in terms of signal performance with reference to 546 noise level, or by the signal-to-noise ratio (SNR), and spectral 547 occupancy requirement or signal power level. Optical Signal 548 Statistics message SHOULD contain Optical Signal Block which 549 specifies the transmission property of connections as shown in the 550 below. 552 0 1 2 3 553 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 554 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 555 | | 556 ~ Optical Signal Block ~ 557 | | 558 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 560 Optical Signal Block; variable 561 This field implies quality of transmission signal in a connection so 562 that it informs a controller signal degradation or loss of signal. 563 This field MAY consist of several blocks which specify the optical 564 signal statistics in detail and they will be further added on this 565 message. This information MAY result in an alarm of link failure. 567 8. Configuration Messages 569 The configuration messages allow a controller to discover 570 capabilities of optical switch. Switch configuration, port 571 configuration, and service configuration messages are defined for 572 these functions. 574 8.1 Switch Configuration Message: Optical Switch Specific Block 576 Since an optical switch MAY be able to provide connection services at 577 multiple transport layers, and not all switches are expected to 578 support the same transport layers, the switch will need to notify the 579 controller of the specific layers it can support. Therefore, the 580 switch configuration message MUST be extended to provide a list of 581 the transport layers for which an optical switch can perform 582 switching. For supporting various types of switching capable 583 interfaces, the following optical switch configuration blocks SHOULD 584 be added in the Switch Configuration message. 586 0 1 2 3 587 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 589 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 590 | SW capable | Reserved | 591 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 593 Switching Capable Layer : 8 bits 594 This field indicates the supported switching capable layers in an 595 optical switch. It has three flags which indicate the layers. The 596 flags can be set at the same time when the optical switch contains 597 multiple transport layers. 599 X X X X X X F B L 600 ------------------- 602 X: reserved field 603 F: indicates the switching capable layer per a fiber 604 B: indicates the switching capable layer per a waveband 605 L: indicates the switching capable layer per a wavelength 607 8.2 Port Configuration Message 609 The port configuration message informs a controller configuration 610 information related to a single port. Ports in optical switches 611 differ from those in electrical switches. The ports defined in GSMPv3 612 imply a single physical link and several connections are specified 613 with labels in a port. However, a single port does not identify a 614 single link in optical domain. A port can imply a set of fibers, a 615 single fiber, or a single wavelength. Therefore different types of 616 port SHOULD be identified in GSMPv3. 618 The basic format and usage of Port Configuration message follow [1]. 619 The following new port types are defined to support optical switch. 621 Value PortType 622 ------ --------- 623 10 a fiber (wavelength) 625 When the value of PortType is in the above range, we call "PortType = 626 Optical Switching" in the following section. 628 8.2.1 PortType Specific Data for Optical Switching 630 The format and usage of Port Specific Data in Port Configuration 631 message depends on the PortType value and the basic format of it is 632 given as following [1]. 634 0 1 2 3 635 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 636 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 637 |P|M|L|R|Q| Label Range Count | Label Range Length | 638 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 639 | | 640 ~ Default Label Range Block ~ 641 | | 642 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 643 | Receive Data Rate | 644 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 645 | Transmit Data Rate | 646 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 647 | Port Status | Line Type | Line Status | Priorities | 648 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 649 | Physical Slot Number | Physical Port Number | 650 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 652 Note: Fields and Parameters that have not been explained in the 653 Subsection follow [1]. 655 In this section, we specify some fields for supporting optical 656 switching as following. If PortType is equal to optical switching, 658 Receive Data Rate 659 The maximum rate of data that may arrive at the input port 660 (interface) in; 662 Bits/sec for PortType = Optical Switching 664 Transmit Data Rate 665 The maximum rate of data that may depart from the output port 666 (interface) in; 668 Bits/sec for PortType = Optical Switching 670 Port Status 671 Give the administrative state of the port. The new values of the Port 672 Status are defined to indicate recovery capability in port. 674 Recovery: 675 Port Status = 6. The port is reserved for recovery support. For 676 1+1 dedicated protection, this port is configured to transmit 677 traffic as a backup. On the other hand, for 1:1 protection, this 678 port is just configured to reserve the connection without 679 transmitting traffic. 681 Line Type 682 The type of physical transmission interface for this port. The line 683 type for optical support depends on switching interface for each 684 switching entity, such as for wavelength-related port or fiber- 685 related port. This field MAY define range of wavelength, fiber type, 686 and so on. For example, 688 Line Type for PortType = a fiber 689 ------------------------ 690 Single Mode Fiber 691 Multi Mode Fiber 692 Dispersion Shifted Fiber 693 Nonzero Dispersion Fiber 694 � 696 Line Type for PortType = a wavelength 697 ------------------------ 698 1300nm 699 1550nm 700 � 702 Physical Slot Number 703 The physical location of the slot in optical switching (or OXC). 704 Since the OXC systems can have many bays which contain hundreds of 705 shelf which have tens of thousands of port this field SHLOULD 706 identify the slot. For doing so, the field MAY be partitioned into 707 several sub-fields to define bay, shelf, and slot. 709 The default label range block for optical switching has the following 710 format. 712 0 1 2 3 713 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 714 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 715 |x|x|x|x| Label Type | Label Length | 716 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 717 | | 718 ~ Label Value ~ 719 | | 720 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 722 Label Type: 12 bit 723 Label type for optical support. Each encoding type of the labels is 724 TBD. 726 Label value: Variable 727 Carries label information. The interpretation of this field depends 728 on the type of the link (or the type of connection) over which the 729 label is used. Min Label and Max label value imply the range of 730 available optical labels. Each encoding type of the labels is TBD. 732 9. Event Messages 734 The Event messages allow a switch to inform a controller of certain 735 asynchronous events. This draft deals with recovery-related events. 736 The indication of these asynchronous events related to ports and 737 labels can inform failure of them to the controller and it can 738 initiate a fault recovery mechanism. In the following sub-sections, 739 two messages, Recovery Completion message and Fault Notification 740 message, are used to notify a controller fault-related events of a 741 switch. 743 Event messages for recovery-related events have the following format: 745 0 1 2 3 746 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 747 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 748 |Version| Sub | Message Type | Result| Code | 749 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 750 | Partition ID | Transaction Identifier | 751 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 752 |I| SubMessage Number | Length | 753 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 754 |x x x x x x x x x x x x x x x x| Number of Blocks | 755 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 756 | | 757 ~ Recovery-Related Blocks ~ 758 | | 759 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 761 [Note] Fields and Parameters that have not been explained SHOULD be 762 referred to [1]. 764 Number of Blocks 765 This field implies the total number of the recovery-related blocks. 766 By notifying the contents of the recovery-related blocks in a single 767 event message to the controller the recovery-related events can be 768 processed in very short time. The number of Blocks in a single Event 769 message for recovery-related events MUST NOT cause the packet length 770 to exceed toe maximum transmission unit defined by the encapsulation. 772 Recovery-Related Blocks 773 This field contains several recovery-related blocks for the suitable 774 purpose of the messages. In this draft, these fields are used to 775 notify recovery completion or fault notification. More message 776 specific contents are dealt with in the following sub-sections. 778 9.1 Recovery Completion Message 780 This message is used to notify the recovery completion to the 781 controller by the switch after the failed elements are restored. This 782 message contains restored connection information. Restored Connection 783 information implies restored Port IDs and Label IDs. By using this 784 message, the recovery completion of several failed connections, which 785 consist of port and label, are notified to the controller at one time. 787 Message Type = TBA 789 If a message type is equal to Recovery Completion message the 790 following Recovery Completion Blocks SHOULD be added on the message 791 in order to notify the recovery completion of all failed ports and 792 all fault-affected labels to the controller. 794 0 1 2 3 795 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 796 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 797 | Restored Port ID | 798 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 799 | Restored Label ID | 800 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 802 Restored Port ID list; variable 803 This field describes the restored port IDs which contain different 804 types of port which indicate wavelength-related port, fiber-related 805 port, or fiber bundle-related port. 807 Restored Label ID list; variable 808 This field describes the restored label ID which comes to be used 809 again from a fault. 811 9.2 Fault Notification Message 813 This message is used to inform a controller a fault occurring in a 814 switch. The possible faults are link failure from cutting off 815 (affecting wavelengths, fibers, fiber bundles), port failure, or 816 switch modules. For the notification purpose, the following Fault 817 Notification blocks SHOULD be added in Event message. 819 Message type = TBA 821 If a message type is equal to Fault Notification message the 822 following Fault Notification blocks SHOULD be added on the message in 823 order to notify all fault-affected ports and labels in a switch to a 824 controller. 826 0 1 2 3 827 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 828 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 829 | Failed Port ID | 830 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 831 | Failed Label ID | 832 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 834 Failed Port ID list; variable 835 This field describes the failed port ID which contains different 836 types of port which indicate wavelength-related port, fiber-related 837 port, or fiber bundle-related port. 839 Failed Label ID list; variable 840 This field describes the failed label ID which comes to not be used 841 from a connection failed. 843 10. Service Model Definition 845 In the GSMP Service Model a controller may request the switch to 846 establish a connection with a given Service. The requested Service is 847 identified by including a Service ID in the Add Branch message or the 848 Reservation message. The Service ID refers to a Service Definition 849 (defined in chapter 10 of [1]). This chapter defines the various 850 Service ID for optical capable switches. 852 The following Service Identifiers are defined for optical support. 854 ID Range Service Type 855 -------- ------------ 856 128 - 191 Optical Switch Services 858 Service Identifier 859 The reference number used to identify the Service in GSMP. 861 Service Characteristics 862 A definition of the Service 864 Traffic Parameters 865 A definition of the Traffic Parameters used in connection management 866 messages. 868 QoS parameters 869 A definition of the QoS Parameters that are included in the 870 Capability Set for instances of the Service. 872 Traffic Controls 873 A definition of the Traffic Controls that may be supported by an 874 instance of the Service. 876 11. Failure Response Codes 878 This chapter describes the failure and warning states which can occur 879 in setup optical connections. The following lists are the codes that 880 SHOULD be defined and added in the Failure Response messages. These 881 codes MAY be added more when the services for optical switching are 882 defined. 884 If the switch issues a failure response it MUST choose the most 885 specific failure code according to the following precedence. The code 886 numbers will be assigned in IANA. 888 Optical Connection Failure 889 - recovery failure 890 Due the limitation of available resource for recovery connection, 891 for example, multiple links failure, the switch can not be 892 succeeded the recovery procedure for shared protected connection. 894 - waveband connection setup failure 895 There are not available wavelengths which belong to the range of 896 min and max limits of the waveband 898 - reservation failure for optical burst 899 In case of delayed reservation in time is not exactly matched, 900 the reservation of optical burst can be failed. 902 The following list gives a summary of the failure codes defined for 903 failure response messages: 905 - no available label for shortage of available wavelengths 906 - no available resource for recovery 907 - no available resource for waveband connection setup 908 - no match for the delayed reservation for optical burst connection 910 12. Security Considerations 912 This document does not have any security concerns. The security 913 requirements using this document are described in the referenced 914 documents. 916 Appendix I. Protection and Restoration Capability in GSMPv3 918 The GSMP controller MUST support the protection and restoration 919 capabilities because the optical switch delivers several Gbps data 920 traffic in a single wavelength. To achieve fast protection and 921 restoration, the optical switch MAY be capable of taking an action 922 independent of the GSMP controller, then it informs the controller 923 after completing the restoration [2]. This differs from the master- 924 slave relationship in GSMP. 926 Recovery mechanisms do not distinguish path (end-to-end) and link 927 recovery in GSMPv3. The difference of them is considered in signaling 928 protocol. In case of dynamically calculating the recovery connection 929 after a fault occurs, GSMPv3 establishes a new recovery connection by 930 using the existing Add Branch message. Therefore, this draft 931 considers pre-planned recovery mechanisms, such as 1+1 dedicated 932 recovery, 1:1 dedicated recovery with/without extra traffic, and 933 1:N/M:N shared recovery. 935 The label switch SHOULD provide the protection and restoration 936 capabilities in order to provide the recovery mechanisms. For example, 937 an ingress/egress node reserves backup resources according the each 938 recovery mechanism, and setup the switch fabric. Then, GSMPv3 is used 939 to control the switch. 941 In this section, the recovery mechanisms which can be provided by 942 GSMPv3 are specified with an included fault notification, and 943 restoration, and related required messages. For example, the port 944 configuration command MUST be extended to allow autonomous protection 945 mechanism. The current GSMP connection management also MUST be 946 extended to support this function. In the following subsections, the 947 supported recovery mechanisms in GSMPv3 are introduced. 949 1.1 1+1 dedicated recovery mechanism 951 - Recovery connection configuration 952 All nodes on a working connection use Add Branch message(P) to 953 configure a recovery connection. The ingress node transmits traffic 954 through the working connection as well as the recovery connection. An 955 egress only chooses traffic from the working connection with ignoring 956 them from the recovery connection. In order to support this type of 957 recovery mechanism, the optical switch SHOULD support it physically. 959 - Recovery procedure 960 When a failure occurs, a fault-affected working connection is 961 switched over a 1+1 dedicated recovery connection without notifying 962 the controller. The recovery process is performed at the physical 963 layer automatically. After the recovery is completed, the switch 964 notifies the recovery completion to the controller by using Event 965 message. 967 1.2 1:1 dedicated recovery mechanism 969 1) 1:1 protection 971 - Recovery connection configuration 972 All nodes on a working connection configure a recovery connection by 973 using Add Branch message. However, the ingress node does not transmit 974 any traffic through the reserved recovery connection since the switch 975 does not cross connect for the recovery connection. 977 - Recovery procedure 978 When an ingress node detects a fault it switches over the fault- 979 affected working connection to the reserved recovery connection. This 980 type of recovery does not require configuring additional connection 981 configuration because the recovery connection has been already 982 established by using Add Branch message(P). Then, an egress node 983 switches over the recovery connection to receive traffic. 985 2) 1:1 restoration 987 - Recovery connection configuration 988 An ingress node and an egress node both configure a recovery 989 connection by using the Reservation Request message(P), and core 990 nodes also use it to reserve recovery connection. Extra traffic can 991 be delivered through the recovery connection. 993 - Recovery procedure 994 The ingress node and the egress node use Add Branch message in order 995 to configure a recovery connection. Other core nodes also configure 996 the recovery connection with Add Branch message(P) with the reserved 997 resource. 999 1.3 1:N/M:N shared recovery mechanism (M, N > 1, M <= N) 1001 - Recovery connection configuration 1002 Reservation Request message(P) is used to configure a recovery 1003 connection. Since several working connections (= N) share one 1004 recovery connection (1:N) or several recovery connections (M:N) 1005 GSMPv3 SHUOLD know the sharing working connection IDs for the 1006 recovery connections. 1008 - Recovery procedure 1009 When the GSMPv3 controller is notified a fault, it uses Add Branch 1010 message(P) to configure a new working connection by using reserved 1011 recovery connection. The Add Branch message(P) SHOULD contain the 1012 information about the reserved recovery connection. 1014 Appendix II. GSMPv3 support for optical cross-connect systems 1016 The GSMPv3 controls and manages the optical cross-connect systems as 1017 label switches. The optical cross-connect (OXC) is a space division 1018 switch that can switch an optical data stream on an input port to an 1019 output port. The OXCs are all optical cross-connects (optical- 1020 optical-optical), transparent optical cross connects (optical- 1021 electrical-optical, frame independent), and opaque optical cross 1022 connects (optical-electrical-optical, SONET/SDH frames).These OXC 1023 (optical cross connect) systems can be IP-based optical routers which 1024 are dynamic wavelength routers, optical label switches, or 1025 burst/packet-based optical cross connects, and so on[2]. 1027 The OXC system consists of switching fabric, multiplexer/ 1028 demultiplexer, wavelength converter, and optical-electrical/ 1029 electrical-optical converter. Multiple wavelengths are multiplexed or 1030 demultiplexed into a fiber. Multiple fibers belong to a fiber bundle. 1031 A wavelength, a waveband, and a fiber can be used to establish a 1032 connection in an optical switch. They SHOULD be recognized at a port 1033 in the OXC since they are connection entities. When the OXC has 1034 optical-electrical conversion at the input port and electrical- 1035 optical conversion at the output port it is called as opaque OXC. Or, 1036 when it processes optical data stream all optically it is called as 1037 transparent OXC. Wavelength converter SHOULD be used to resolve 1038 output port contention when two different connections try to be 1039 established in a same output port. Since the wavelength converter can 1040 work only within a limited operating range, the limited numbers of 1041 wavelengths are used at the output port. It limits the available 1042 wavelengths at the output port. 1044 If OXCs perform protection and restoration functions they SHOULD have 1045 suitable switch structure to support them. In case of 1+1 dedicated 1046 recovery, input ports and output ports MUST be duplicated in a switch. 1047 The switch transmits optical signal through two ports (one for 1048 working connection and another for recovery connection) 1049 simultaneously. When a fault happens the switch switches over from 1050 failed working connection to dedicated recovery connection without 1051 noticing a controller. 1053 References 1055 [1] Doria, A, "GSMPv3 Base Specification", draft-ietf-gsmp-base-spec- 1056 02.txt (work in progress), June 2003. 1058 [2] Georg Kullgren, et. al., "Requirements For Adding Optical Support 1059 To GSMPv3",draft-ietf-gsmp-reqs-06.txt (work in progress), June 2003. 1061 [3] Mannie, E., et. al., "Generalized Multi-Protocol Label Switching 1062 (GMPLS) Architecture", draft-ietf-ccamp-gmpls-architecture-07.txt 1063 (work in progress), May 2003. 1065 [4] Ashwood-Smith, D., et. al., "Generalized MPLS - Signaling 1066 Functional Description", RFC3471, Jan. 2003. 1068 [5] Rajagopalan, B., et. al., "IP over Optical Networks: A Framework", 1069 draft-ietf-ipo-framework-04.txt (work in progress), April 2003. 1071 [6] J. Lang, et. at. "Link Management Protocol (LMP) ", draft-ietf- 1072 ccamp-lmp-09.txt (work in progress), April 2003. 1074 [7] C. Qiao, M. Yoo, "Choice, and Feature and Issues in Optical Burst 1075 Switching", Optical Net. Mag., vol.1, No.2, Apr.2000, pp.36-44. 1077 [8] Ilia Baldine, George N. Rouskas, Harry G. Perros, Dan Stevension, 1078 "JumpStart: A Just-in-time Signaling Architecture for WDM Burst- 1079 Switching Networks", IEEE Comm. Mag., Feb. 2002. 1081 [9] Angela Chiu, John Strans, et. al., "Impairments And Other 1082 Constraints On Optical Layer Routing", draft-ietf-ipo-impairments- 1083 05.txt (work in progress), May 2003. 1085 [10] Daniel Awduche, WYakov Rekhter, "Multiprotocol Lambda Switching: 1086 Combining MPLS Traffic Engineering Control with Optical 1087 Crossconnects", IEEE Comm. Mag., March 2001. 1089 [11] Doria, A. and K. Sundell, "General Switch Management Protocol 1090 Applicability", RFC 3294, June 2002. 1092 [12] Mannie, E., et. al., "Recovery (Protection and Restoration) 1093 Terminology for GMPLS", draft-ietf-ccamp-gmpls-recovery-terminology- 1094 02.txt (work in progress), May 2003. 1096 [13] Vishal Sharma, et. at., "Framework for MPLS-based Recovery", RFC 1097 3469, February 2003 1099 Acknowledgement 1101 This work was supported in part by the Korean Science and Engineering 1102 Foundation (KOSEF) through OIRC project 1104 Author's Addresses 1106 Jun Kyun Choi 1107 Information and Communications University (ICU) 1108 58-4 Hwa Ahm Dong, Yusong, Daejon 1109 Korea 305-732 1110 Phone: +82-42-866-6122 1111 Email: jkchoi@icu.ac.kr 1113 Min Ho Kang 1114 Information and Communications University (ICU) 1115 58-4 Hwa Ahm Dong, Yusong, Daejon 1116 Korea 305-732 1117 Phone: +82-42-866-6136 1118 Email: mhkang@icu.ac.kr 1120 Jung Yul Choi 1121 Information and Communications University (ICU) 1122 58-4 Hwa Ahm Dong, Yusong, Daejon 1123 Korea 305-732 1124 Phone: +82-42-866-6208 1125 Email: passjay@icu.ac.kr 1127 Gyu Myung Lee 1128 Information and Communications University (ICU) 1129 58-4 Hwa Ahm Dong, Yusong, Daejon 1130 Korea 305-732 1131 Phone: +82-42-866-6231 1132 Email: gmlee@icu.ac.kr 1133 Young Wook Cha 1134 Andong National University (ANU) 1135 388 Song-Chon Dong, Andong, Kyungsangbuk-do 1136 Korea 760-749 1137 Phone: +82-54-820-5714 1138 Email: ywcha@andong.ac.kr 1140 Jook Uk Um 1141 KT Network Engineering Center 1142 206 Jungja-dong, Bungdang-gu, Sungnam City, Kyonggi-do, 463-711, 1143 Korea 1144 Phone: +82-31-727-6610 1145 Email: jooukum@kt.co.kr 1147 Yong Jae Lee 1148 KT Network Engineering Center 1149 206 Jungja-dong, Bungdang-gu, Sungnam City, Kyonggi-do, 463-711, Korea 1150 Phone: +82-31-727-6651 1151 Email: cruiser@kt.co.kr 1153 Jeong Yun Kim 1154 Electronics and Telecommunications Research Institute (ETRI) 1155 161 KaJong-Dong, Yusong-Gu, Daejeon 1156 Korea 305-309 1157 Phone: +82-42-866-5311 1158 Email: jykim@etri.re.kr 1160 Avri Doria 1161 Div. of Computer Communications 1162 Lulea University of Technology 1163 S-971 87 Lulea 1164 Sweden 1165 Phone: +1 401 663 5024 1166 EMail: avri@acm.org 1168 Full Copyright Statement 1170 Copyright (C) The Internet Society (2002). All Rights Reserved. This 1171 document and translations of it MAY be copied and furnished to others, 1172 and derivative works that comment on or otherwise explain it or 1173 assist in its implementation MAY be prepared, copied, published and 1174 distributed, in whole or in part, without restriction of any kind, 1175 provided that the above copyright notice and this paragraph are 1176 included on all such copies and derivative works. However, this 1177 document itself MAY not be modified in any way, such as by removing 1178 the copyright notice or references to the Internet Society or other 1179 Internet organizations, except as needed for the purpose of 1180 developing Internet standards in which case the procedures for 1181 copyrights defined in the Internet Standards process MUST be 1182 followed, or as required to translate it into languages other than 1183 English. 1185 The limited permissions granted above are perpetual and will not be 1186 revoked by the Internet Society or its successors or assigns. 1188 This document and the information contained herein is provided on an 1189 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 1190 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 1191 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 1192 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 1193 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.