idnits 2.17.1 draft-ietf-ccamp-rwa-wson-framework-10.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (January 10, 2011) is 4854 days in the past. Is this intentional? -- Found something which looks like a code comment -- if you have code sections in the document, please surround them with '' and '' lines. Checking references for intended status: Informational ---------------------------------------------------------------------------- == Missing Reference: 'G.698.1' is mentioned on line 457, but not defined == Missing Reference: 'G.698.2' is mentioned on line 458, but not defined == Missing Reference: 'G.707' is mentioned on line 482, but not defined == Missing Reference: 'G.709' is mentioned on line 483, but not defined == Missing Reference: 'GEN-Encode' is mentioned on line 1876, but not defined == Unused Reference: 'G.Sup43' is defined on line 2141, but no explicit reference was found in the text Summary: 0 errors (**), 0 flaws (~~), 7 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group Y. Lee (ed.) 2 Internet Draft Huawei 3 Intended status: Informational G. Bernstein (ed.) 4 Expires: July 2011 Grotto Networking 5 Wataru Imajuku 6 NTT 8 January 10, 2011 10 Framework for GMPLS and PCE Control of Wavelength Switched Optical 11 Networks (WSON) 12 draft-ietf-ccamp-rwa-wson-framework-10.txt 14 Abstract 16 This document provides a framework for applying Generalized Multi- 17 Protocol Label Switching (GMPLS) and the Path Computation Element 18 (PCE) architecture to the control of wavelength switched optical 19 networks (WSON). In particular, it examines Routing and Wavelength 20 Assignment (RWA) of optical paths. 22 This document focuses on topological elements and path selection 23 constraints that are common across different WSON environments as 24 such it does not address optical impairments in any depth. 26 Status of this Memo 28 This Internet-Draft is submitted to IETF in full conformance with the 29 provisions of BCP 78 and BCP 79. 31 Internet-Drafts are working documents of the Internet Engineering 32 Task Force (IETF), its areas, and its working groups. Note that 33 other groups may also distribute working documents as Internet- 34 Drafts. 36 Internet-Drafts are draft documents valid for a maximum of six months 37 and may be updated, replaced, or obsoleted by other documents at any 38 time. It is inappropriate to use Internet-Drafts as reference 39 material or to cite them other than as "work in progress." 41 The list of current Internet-Drafts can be accessed at 42 http://www.ietf.org/ietf/1id-abstracts.txt 43 The list of Internet-Draft Shadow Directories can be accessed at 44 http://www.ietf.org/shadow.html. 46 This Internet-Draft will expire on July 10, 2011. 48 Copyright Notice 50 Copyright (c) 2011 IETF Trust and the persons identified as the 51 document authors. All rights reserved. 53 This document is subject to BCP 78 and the IETF Trust's Legal 54 Provisions Relating to IETF Documents 55 (http://trustee.ietf.org/license-info) in effect on the date of 56 publication of this document. Please review these documents 57 carefully, as they describe your rights and restrictions with 58 respect to this document. Code Components extracted from this 59 document must include Simplified BSD License text as described in 60 Section 4.e of the Trust Legal Provisions and are provided without 61 warranty as described in the Simplified BSD License. 63 Table of Contents 65 1. Introduction...................................................4 66 2. Terminology....................................................4 67 3. Wavelength Switched Optical Networks...........................6 68 3.1. WDM and CWDM Links........................................6 69 3.2. Optical Transmitters and Receivers........................8 70 3.3. Optical Signals in WSONs..................................9 71 3.3.1. Optical Tributary Signals...........................10 72 3.3.2. WSON Signal Characteristics.........................10 73 3.4. ROADMs, OXCs, Splitters, Combiners and FOADMs............11 74 3.4.1. Reconfigurable Add/Drop Multiplexers and OXCs.......11 75 3.4.2. Splitters...........................................14 76 3.4.3. Combiners...........................................15 77 3.4.4. Fixed Optical Add/Drop Multiplexers.................15 78 3.5. Electro-Optical Systems..................................16 79 3.5.1. Regenerators........................................16 80 3.5.2. OEO Switches........................................19 81 3.6. Wavelength Converters....................................19 82 3.6.1. Wavelength Converter Pool Modeling..................21 83 3.7. Characterizing Electro-Optical Network Elements..........25 84 3.7.1. Input Constraints...................................26 85 3.7.2. Output Constraints..................................26 86 3.7.3. Processing Capabilities.............................27 88 4. Routing and Wavelength Assignment and the Control Plane.......28 89 4.1. Architectural Approaches to RWA..........................28 90 4.1.1. Combined RWA (R&WA).................................29 91 4.1.2. Separated R and WA (R+WA)...........................29 92 4.1.3. Routing and Distributed WA (R+DWA)..................30 93 4.2. Conveying information needed by RWA......................30 94 5. Modeling Examples and Control Plane Use Cases.................31 95 5.1. Network Modeling for GMPLS/PCE Control...................31 96 5.1.1. Describing the WSON nodes...........................32 97 5.1.2. Describing the links................................34 98 5.2. RWA Path Computation and Establishment...................35 99 5.3. Resource Optimization....................................36 100 5.4. Support for Rerouting....................................37 101 5.5. Electro-Optical Networking Scenarios.....................37 102 5.5.1. Fixed Regeneration Points...........................37 103 5.5.2. Shared Regeneration Pools...........................38 104 5.5.3. Reconfigurable Regenerators.........................38 105 5.5.4. Relation to Translucent Networks....................38 106 6. GMPLS and PCE Implications....................................39 107 6.1. Implications for GMPLS signaling.........................39 108 6.1.1. Identifying Wavelengths and Signals.................39 109 6.1.2. WSON Signals and Network Element Processing.........40 110 6.1.3. Combined RWA/Separate Routing WA support............40 111 6.1.4. Distributed Wavelength Assignment: Unidirectional, No 112 Converters.................................................41 113 6.1.5. Distributed Wavelength Assignment: Unidirectional, 114 Limited Converters.........................................41 115 6.1.6. Distributed Wavelength Assignment: Bidirectional, No 116 Converters.................................................41 117 6.2. Implications for GMPLS Routing...........................42 118 6.2.1. Electro-Optical Element Signal Compatibility........42 119 6.2.2. Wavelength-Specific Availability Information........43 120 6.2.3. WSON Routing Information Summary....................43 121 6.3. Optical Path Computation and Implications for PCE........45 122 6.3.1. Optical path Constraints and Characteristics........45 123 6.3.2. Electro-Optical Element Signal Compatibility........45 124 6.3.3. Discovery of RWA Capable PCEs.......................46 125 7. Security Considerations.......................................46 126 8. IANA Considerations...........................................47 127 9. Acknowledgments...............................................47 128 10. References...................................................48 129 10.1. Normative References....................................48 130 10.2. Informative References..................................49 131 11. Contributors.................................................51 132 Author's Addresses...............................................52 133 Intellectual Property Statement..................................52 134 Disclaimer of Validity...........................................53 136 1. Introduction 138 Wavelength Switched Optical Networks (WSONs) are constructed from 139 subsystems that include Wavelength Division Multiplexed (WDM) links, 140 tunable transmitters and receivers, Reconfigurable Optical Add/Drop 141 Multiplexers (ROADM), wavelength converters, and electro-optical 142 network elements. A WSON is a WDM-based optical network in which 143 switching is performed selectively based on the center wavelength of 144 an optical signal. 146 In order to provision an optical connection (an optical path) through 147 a WSON certain path continuity and resource availability constraints 148 must be met to determine viable and optimal paths through the 149 network. The determination of paths is known as Routing and 150 Wavelength Assignment (RWA). 152 Generalized Multi-Protocol Label Switching (GMPLS) [RFC3945] includes 153 a set of control plane protocols that can be used to operate data 154 networks ranging from packet switch capable networks, through those 155 networks that use time division multiplexing, to WDM networks. The 156 Path Computation Element (PCE) architecture [RFC4655] defines 157 functional components that can be used to compute and suggest 158 appropriate paths in connection-oriented traffic-engineered networks. 160 This document provides a framework for applying GMPLS protocols and 161 the PCE architecture to the control and operation of WSONs. To aid 162 in this process this document also provides an overview of the 163 subsystems and processes that comprise WSONs, and describes RWA so 164 that the information requirements, both static and dynamic, can be 165 identified to explain how the information can be modeled for use by 166 GMPLS and PCE systems. This work will facilitate the development of 167 protocol solution models and protocol extensions within the GMPLS and 168 PCE protocol families. 170 Note that this document focuses on the generic properties of links, 171 switches and path selection constraints that occur in WSONs. 172 Different WSONs such as access, metro, and long haul may apply 173 different techniques for dealing with optical impairments hence this 174 document does not address optical impairments in any depth. See 175 [WSON-Imp] for more information on optical impairments and GMPLS. 177 2. Terminology 179 Add/Drop Multiplexers (ADM): An optical device used in WDM networks 180 composed of one or more line side ports and typically many tributary 181 ports. 183 CWDM: Coarse Wavelength Division Multiplexing. 185 DWDM: Dense Wavelength Division Multiplexing. 187 Degree: The degree of an optical device (e.g., ROADM) is given by a 188 count of its line side ports. 190 Drop and continue: A simple multi-cast feature of some ADM where a 191 selected wavelength can be switched out of both a tributary (drop) 192 port and a line side port. 194 FOADM: Fixed Optical Add/Drop Multiplexer. 196 GMPLS: Generalized Multi-Protocol Label Switching. 198 Line side: In WDM system line side ports and links typically can 199 carry the full multiplex of wavelength signals, as compared to 200 tributary (add or drop ports) that typically carry a few (typically 201 one) wavelength signals. 203 OXC: Optical cross connect. An optical switching element in which a 204 signal on any input port can reach any output port. 206 PCC: Path Computation Client. Any client application requesting a 207 path computation to be performed by the Path Computation Element. 209 PCE: Path Computation Element. An entity (component, application, or 210 network node) that is capable of computing a network path or route 211 based on a network graph and applying computational constraints. 213 PCEP: PCE Communication Protocol. The communication protocol between 214 a Path Computation Client and Path Computation Element. 216 ROADM: Reconfigurable Optical Add/Drop Multiplexer. A wavelength 217 selective switching element featuring input and output line side 218 ports as well as add/drop tributary ports. 220 RWA: Routing and Wavelength Assignment. 222 Transparent Network: A wavelength switched optical network that does 223 not contain regenerators or wavelength converters. 225 Translucent Network: A wavelength switched optical network that is 226 predominantly transparent but may also contain limited numbers of 227 regenerators and/or wavelength converters. 229 Tributary: A link or port on a WDM system that can carry 230 significantly less than the full multiplex of wavelength signals 231 found on the line side links/ports. Typical tributary ports are the 232 add and drop ports on an ADM and these support only a single 233 wavelength channel. 235 Wavelength Conversion/Converters: The process of converting an 236 information bearing optical signal centered at a given wavelength to 237 one with "equivalent" content centered at a different wavelength. 238 Wavelength conversion can be implemented via an optical-electronic- 239 optical (OEO) process or via a strictly optical process. 241 WDM: Wavelength Division Multiplexing. 243 Wavelength Switched Optical Networks (WSONs): WDM based optical 244 networks in which switching is performed selectively based on the 245 center wavelength of an optical signal. 247 3. Wavelength Switched Optical Networks 249 WSONs range in size from continent spanning long haul networks, to 250 metropolitan networks, to residential access networks. In all these 251 cases, the main concern is those properties that constrain the choice 252 of wavelengths that can be used, i.e., restrict the wavelength label 253 set, impact the path selection process, and limit the topological 254 connectivity. In addition, if electro-optical network elements are 255 used in the WSON, additional compatibility constraints may be imposed 256 by the network elements on various optical signal parameters. The 257 subsequent sections review and model some of the major subsystems of 258 a WSON with an emphasis on those aspects that are of relevance to the 259 control plane. In particular, WDM links, optical transmitters, 260 ROADMs, and wavelength converters are examined. 262 3.1. WDM and CWDM Links 264 WDM and CWDM links run over optical fibers, and optical fibers come 265 in a wide range of types that tend to be optimized for various 266 applications examples include access networks, metro, long haul, and 267 submarine links. International Telecommunication Union - 268 Telecommunication Standardization Sector (ITU-T) standards exist for 269 various types of fibers. Although fiber can be categorized into 270 Single mode fibers (SMF) and Multi-mode fibers (MMF), the latter are 271 typically used for short-reach campus and premise applications. SMF 272 are used for longer-reach applications and therefore are the primary 273 concern of this document. The following SMF fiber types are typically 274 encountered in optical networks: 276 ITU-T Standard | Common Name 277 ------------------------------------------------------------ 278 G.652 [G.652] | Standard SMF | 279 G.653 [G.653] | Dispersion shifted SMF | 280 G.654 [G.654] | Cut-off shifted SMF | 281 G.655 [G.655] | Non-zero dispersion shifted SMF | 282 G.656 [G.656] | Wideband non-zero dispersion shifted SMF | 283 ------------------------------------------------------------ 285 Typically WDM links operate in one or more of the approximately 286 defined optical bands [G.Sup39]: 288 Band Range (nm) Common Name Raw Bandwidth (THz) 289 O-band 1260-1360 Original 17.5 290 E-band 1360-1460 Extended 15.1 291 S-band 1460-1530 Short 9.4 292 C-band 1530-1565 Conventional 4.4 293 L-band 1565-1625 Long 7.1 294 U-band 1625-1675 Ultra-long 5.5 296 Not all of a band may be usable, for example in many fibers that 297 support E-band there is significant attenuation due to a water 298 absorption peak at 1383nm. Hence a discontinuous acceptable 299 wavelength range for a particular link may be needed and is modeled. 300 Also some systems will utilize more than one band. This is 301 particularly true for CWDM systems. 303 Current technology subdivides the bandwidth capacity of fibers into 304 distinct channels based on either wavelength or frequency. There are 305 two standards covering wavelengths and channel spacing. ITU-T 306 Recommendation G.694.1, Spectral grids for WDM applications: DWDM 307 frequency grid [G.694.1] describes a DWDM grid defined in terms of 308 frequency grids of 12.5GHz, 25GHz, 50GHz, 100GHz, and other multiples 309 of 100GHz around a 193.1THz center frequency. At the narrowest 310 channel spacing this provides less than 4800 channels across the O 311 through U bands. ITU-T Recommendation G.694.2, Spectral grids for WDM 312 applications: CWDM wavelength grid [G.694.2] describes a CWDM grid 313 defined in terms of wavelength increments of 20nm running from 1271nm 314 to 1611nm for 18 or so channels. The number of channels is 315 significantly smaller than the 32 bit GMPLS label space defined for 316 GMPLS, see [RFC3471]. A label representation for these ITU-T grids 317 is given in [Otani] and provides a common label format to be used in 318 signaling optical paths. Further, these ITU-T grid based labels can 319 also be used to describe WDM links, ROADM ports, and wavelength 320 converters for the purposes of path selection. 322 Many WDM links are designed to take advantage of particular fiber 323 characteristics or to try to avoid undesirable properties. For 324 example dispersion shifted SMF [G.653] was originally designed for 325 good long distance performance in single channel systems, however 326 putting WDM over this type of fiber requires significant system 327 engineering and a fairly limited range of wavelengths. Hence the 328 following information is needed as parameters to perform basic, 329 impairment unaware, modeling of a WDM link: 331 o Wavelength range(s): Given a mapping between labels and the ITU-T 332 grids each range could be expressed in terms of a tuple (lambda1, 333 lambda2) or (freq1, freq1) where the lambdas or frequencies can be 334 represented by 32 bit integers. 336 o Channel spacing: Currently there are five channel spacings used in 337 DWDM systems and a single channel spacing defined for CWDM 338 systems. 340 For a particular link this information is relatively static, as 341 changes to these properties generally require hardware upgrades. Such 342 information may be used locally during wavelength assignment via 343 signaling, similar to label restrictions in MPLS or used by a PCE in 344 providing combined RWA. 346 3.2. Optical Transmitters and Receivers 348 WDM optical systems make use of optical transmitters and receivers 349 utilizing different wavelengths (frequencies). Some transmitters are 350 manufactured for a specific wavelength of operation, that is, the 351 manufactured frequency cannot be changed. First introduced to reduce 352 inventory costs, tunable optical transmitters and receivers are 353 deployed in some systems, and allow flexibility in the wavelength 354 used for optical transmission/reception. Such tunable optics aid in 355 path selection. 357 Fundamental modeling parameters from the control plane perspective 358 optical transmitters and receivers are: 360 o Tunable: Do the transmitter and receivers operate at variable or 361 fixed wavelength. 363 o Tuning range: This is the frequency or wavelength range over which 364 the optics can be tuned. With the fixed mapping of labels to 365 lambdas as proposed in [Otani] this can be expressed as a tuple 366 (lambda1, lambda2) or (freq1, freq2) where lambda1 and lambda2 or 367 freq1 and freq2 are the labels representing the lower and upper 368 bounds in wavelength. 370 o Tuning time: Tuning times highly depend on the technology used. 371 Thermal drift based tuning may take seconds to stabilize, whilst 372 electronic tuning might provide sub-ms tuning times. Depending on 373 the application this might be critical. For example, thermal drift 374 might not be usable for fast protection applications. 376 o Spectral characteristics and stability: The spectral shape of a 377 laser's emissions and its frequency stability put limits on 378 various properties of the overall WDM system. One relatively easy 379 to characterize constraint is the closest channel spacing with 380 which the transmitter can be used. 382 Note that ITU-T recommendations specify many aspects of an optical 383 transmitter. Many of these parameters, such as spectral 384 characteristics and stability, are used in the design of WDM 385 subsystems consisting of transmitters, WDM links and receivers 386 however they do not furnish additional information that will 387 influence the Label Switched Path (LSP) provisioning in a properly 388 designed system. 390 Also note that optical components can degrade and fail over time. 391 This presents the possibility of the failure of a LSP (optical path) 392 without either a node or link failure. Hence, additional mechanisms 393 may be necessary to detect and differentiate this failure from the 394 others, e.g., one doesn't not want to initiate mesh restoration if 395 the source transmitter has failed, since the optical transmitter will 396 still be failed on the alternate optical path. 398 3.3. Optical Signals in WSONs 400 In WSONs the fundamental unit of switching is intuitively that of a 401 "wavelength". The transmitters and receivers in these networks will 402 deal with one wavelength at a time, while the switching systems 403 themselves can deal with multiple wavelengths at a time. Hence 404 multichannel DWDM networks with single channel interfaces are the 405 prime focus of this document general concern as opposed to multi- 406 channel interfaces. Interfaces of this type are defined in ITU-T 407 recommendations [G.698.1] and [G.698.2]. Key non-impairment related 408 parameters defined in [G.698.1] and [G.698.2] are: 410 (a) Minimum channel spacing (GHz) 412 (b) Minimum and maximum central frequency 414 (c) Bit-rate/Line coding (modulation) of optical tributary signals 415 For the purposes of modeling the WSON in the control plane, (a) and 416 (b) are considered as properties of the link and restrictions on the 417 GMPLS labels while (c) is a property of the "signal". 419 3.3.1. Optical Tributary Signals 421 The optical interface specifications [G.698.1], [G.698.2], and 422 [G.959.1] all use the concept of an optical tributary signal which is 423 defined as "a single channel signal that is placed within an optical 424 channel for transport across the optical network". Note the use of 425 the qualifier "tributary" to indicate that this is a single channel 426 entity and not a multichannel optical signal. 428 There are currently a number of different types of optical tributary 429 signals, which are known as "optical tributary signal classes". These 430 are currently characterized by a modulation format and bit rate range 431 [G.959.1]: 433 (a) Optical tributary signal class NRZ 1.25G 435 (b) Optical tributary signal class NRZ 2.5G 437 (c) Optical tributary signal class NRZ 10G 439 (d) Optical tributary signal class NRZ 40G 441 (e) Optical tributary signal class RZ 40G 443 Note that with advances in technology more optical tributary signal 444 classes may be added and that this is currently an active area for 445 development and standardization. In particular at the 40G rate there 446 are a number of non-standardized advanced modulation formats that 447 have seen significant deployment including Differential Phase Shift 448 Keying (DPSK) and Phase Shaped Binary Transmission (PSBT). 450 According to [G.698.2] it is important to fully specify the bit rate 451 of the optical tributary signal. Hence it is seen that modulation 452 format (optical tributary signal class) and bit rate are key 453 parameters in characterizing the optical tributary signal. 455 3.3.2. WSON Signal Characteristics 457 An optical tributary signal referenced in ITU-T [G.698.1] and 458 [G.698.2] is referred to as the "signal" in this document. This 459 corresponds to the "lambda" LSP in GMPLS. For signal compatibility 460 purposes with electro-optical network elements, the following signal 461 characteristics are considered: 463 1. Optical tributary signal class (modulation format). 464 2. FEC: whether forward error correction is used in the digital stream 465 and what type of error correcting code is used. 466 3. Center frequency (wavelength). 467 4. Bit rate. 468 5. G-PID: general protocol identifier for the information format. 470 The first three items on this list can change as a WSON signal 471 traverses the optical network with elements that include 472 regenerators, Optical-to-Electrical (OEO) switches, or wavelength 473 converters. 475 Bit rate and G-PID would not change since they describe the encoded 476 bit stream. A set of G-PID values is already defined for lambda 477 switching in [RFC3471] and [RFC4328]. 479 Note that a number of non-standard or proprietary modulation formats 480 and FEC codes are commonly used in WSONs. For some digital bit 481 streams the presence of Forwarding Equivalence Class (FEC) can be 482 detected, e.g., in [G.707] this is indicated in the signal itself via 483 the FEC Status Indication (FSI) byte, while in [G.709] this can be 484 inferred from whether the FEC field of the Optical Channel Transport 485 Unit-k (OTUk) is all zeros or not. 487 3.4. ROADMs, OXCs, Splitters, Combiners and FOADMs 489 Definitions of various optical devices such as ROADMs, Optical Cross- 490 connects (OXCs), splitters, combiners and Fixed Optical Add-Drop 491 Multiplexers (FOADMs) and their parameters can be found in [G.671]. 492 Only a subset of these and their non-impairment related properties 493 are considered in the following sections. 495 3.4.1. Reconfigurable Add/Drop Multiplexers and OXCs 497 ROADMs are available in different forms and technologies. This is a 498 key technology that allows wavelength based optical switching. A 499 classic degree-2 ROADM is shown in Figure 1. 501 Line side input +---------------------+ Line side output 502 --->| |---> 503 | | 504 | ROADM | 505 | | 506 | | 507 +---------------------+ 508 | | | | o o o o 509 | | | | | | | | 510 O O O O | | | | 511 Tributary Side: Drop (output) Add (input) 513 Figure 1. Degree-2 ROADM 515 The key feature across all ROADM types is their highly asymmetric 516 switching capability. In the ROADM of Figure 1, signals introduced 517 via the add ports can only be sent on the line side output port and 518 not on any of the drop ports. The term "degree" is used to refer to 519 the number of line side ports (input and output) of a ROADM, and does 520 not include the number of "add" or "drop" ports. The add and drop 521 ports are sometimes also called tributary ports. As the degree of the 522 ROADM increases beyond two it can have properties of both a switch 523 (OXC) and a multiplexer and hence it is necessary to know the 524 switched connectivity offered by such a network element to 525 effectively utilize it. A straightforward way to represent this is 526 via a "switched connectivity" matrix A where Amn = 0 or 1, depending 527 upon whether a wavelength on input port m can be connected to output 528 port n [Imajuku]. For the ROADM shown in Figure 1 the switched 529 connectivity matrix can be expressed as: 531 Input Output Port 532 Port #1 #2 #3 #4 #5 533 -------------- 534 #1: 1 1 1 1 1 535 #2 1 0 0 0 0 536 A = #3 1 0 0 0 0 537 #4 1 0 0 0 0 538 #5 1 0 0 0 0 540 Where input ports 2-5 are add ports, output ports 2-5 are drop ports 541 and input port #1 and output port #1 are the line side (WDM) ports. 543 For ROADMs, this matrix will be very sparse, and for OXCs the matrix 544 will be very dense, compact encodings and examples, including high 545 degree ROADMs/OXCs, are given in [GEN-Encode]. A degree-4 ROADM is 546 shown in Figure 2. 548 +-----------------------+ 549 Line side-1 --->| |---> Line side-2 550 Input (I1) | | Output (E2) 551 Line side-1 <---| |<--- Line side-2 552 Output (E1) | | Input (I2) 553 | ROADM | 554 Line side-3 --->| |---> Line side-4 555 Input (I3) | | Output (E4) 556 Line side-3 <---| |<--- Line side-4 557 Output (E3) | | Input (I4) 558 | | 559 +-----------------------+ 560 | O | O | O | O 561 | | | | | | | | 562 O | O | O | O | 563 Tributary Side: E5 I5 E6 I6 E7 I7 E8 I8 565 Figure 2. Degree-4 ROADM 567 Note that this example is 4-degree example with one (potentially 568 multi-channel) add/drop per line side port. 570 Note also that the connectivity constraints for typical ROADM designs 571 are "bidirectional", i.e. if input port X can be connected to output 572 port Y, typically input port Y can be connected to output port X, 573 assuming the numbering is done in such a way that input X and output 574 X correspond to the same line side direction or the same add/drop 575 port. This makes the connectivity matrix symmetrical as shown below. 577 Input Output Port 578 Port E1 E2 E3 E4 E5 E6 E7 E8 579 ----------------------- 580 I1 0 1 1 1 0 1 0 0 581 I2 1 0 1 1 0 0 1 0 582 A = I3 1 1 0 1 1 0 0 0 583 I4 1 1 1 0 0 0 0 1 584 I5 0 0 1 0 0 0 0 0 585 I6 1 0 0 0 0 0 0 0 586 I7 0 1 0 0 0 0 0 0 587 I8 0 0 0 1 0 0 0 0 589 Where I5/E5 are add/drop ports to/from line side-3, I6/E6 are 590 add/drop ports to/from line side-1, I7/E7 are add/drop ports to/from 591 line side-2 and I8/E8 are add/drop ports to/from line side-4. Note 592 that diagonal elements are zero since loopback is not supported in 593 the example. If ports support loopback, diagonal elements would be 594 set to one. 596 Additional constraints may also apply to the various ports in a 597 ROADM/OXC. The following restrictions and terms may be used: 599 Colored port: an input or more typically an output (drop) port 600 restricted to a single channel of fixed wavelength. 602 Colorless port: an input or more typically an output (drop) port 603 restricted to a single channel of arbitrary wavelength. 605 In general a port on a ROADM could have any of the following 606 wavelength restrictions: 608 o Multiple wavelengths, full range port. 610 o Single wavelength, full range port. 612 o Single wavelength, fixed lambda port. 614 o Multiple wavelengths, reduced range port (for example wave band 615 switching). 617 To model these restrictions it is necessary to have two pieces of 618 information for each port: (a) number of wavelengths, (b) wavelength 619 range and spacing. Note that this information is relatively static. 620 More complicated wavelength constraints are modeled in [WSON-Info]. 622 3.4.2. Splitters 624 An optical splitter consists of a single input port and two or more 625 output ports. The input optical signaled is essentially copied (with 626 power loss) to all output ports. 628 Using the modeling notions of Section 3.4.1. (Reconfigurable Add/Drop 629 Multiplexers and OXCs) the input and output ports of a splitter would 630 have the same wavelength restrictions. In addition a splitter is 631 modeled by a connectivity matrix Amn as follows: 633 Input Output Port 634 Port #1 #2 #3 ... #N 635 ----------------- 636 A = #1 1 1 1 ... 1 638 The difference from a simple ROADM is that this is not a switched 639 connectivity matrix but the fixed connectivity matrix of the device. 641 3.4.3. Combiners 643 An optical combiner is a device that combines the optical wavelengths 644 carried by multiple input ports into a single multi-wavelength output 645 port. The various ports may have different wavelength restrictions. 646 It is generally the responsibility of those using the combiner to 647 assure that wavelength collision does not occur on the output port. 648 The fixed connectivity matrix Amn for a combiner would look like: 650 Input Output Port 651 Port #1 652 --- 653 #1: 1 654 #2 1 655 A = #3 1 656 ... 1 657 #N 1 659 3.4.4. Fixed Optical Add/Drop Multiplexers 661 A fixed optical add/drop multiplexer can alter the course of an input 662 wavelength in a preset way. In particular a given wavelength (or 663 waveband) from a line side input port would be dropped to a fixed 664 "tributary" output port. Depending on the device's construction that 665 same wavelength may or may not also be sent out the line side output 666 port. This is commonly referred to as "drop and continue" operation. 667 There also may exist tributary input ports ("add" ports) whose 668 signals are combined with each other and other line side signals. 670 In general, to represent the routing properties of an FOADM it is 671 necessary to have both a fixed connectivity matrix Amn as previously 672 discussed and the precise wavelength restrictions for all input and 673 output ports. From the wavelength restrictions on the tributary 674 output ports, what wavelengths have been selected can be derived. 675 From the wavelength restrictions on the tributary input ports, it can 676 be seen which wavelengths have been added to the line side output 677 port. Finally from the added wavelength information and the line side 678 output wavelength restrictions it can be inferred which wavelengths 679 have been continued. 681 To summarize, the modeling methodology introduced in Section 3.4.1. 682 (Reconfigurable Add/Drop Multiplexers and OXCs) consisting of a 683 connectivity matrix and port wavelength restrictions can be used to 684 describe a large set of fixed optical devices such as combiners, 685 splitters and FOADMs. Hybrid devices consisting of both switched and 686 fixed parts are modeled in [WSON-Info]. 688 3.5. Electro-Optical Systems 690 This section describes how Electro-Optical Systems (e.g., OEO 691 switches, wavelength converters, and regenerators) interact with the 692 WSON signal characteristics listed in Section 3.3.2. (WSON Signal 693 Characteristics) OEO switches, wavelength converters and regenerators 694 all share a similar property: they can be more or less "transparent" 695 to an "optical signal" depending on their functionality and/or 696 implementation. Regenerators have been fairly well characterized in 697 this regard and hence their properties can be described first. 699 3.5.1. Regenerators 701 The various approaches to regeneration are discussed in ITU-T G.872 702 Annex A [G.872]. They map a number of functions into the so-called 703 1R, 2R and 3R categories of regenerators as summarized in Table 1 704 below: 706 Table 1. Regenerator functionality mapped to general regenerator 707 classes from [G.872]. 709 --------------------------------------------------------------------- 710 1R | Equal amplification of all frequencies within the amplification 711 | bandwidth. There is no restriction upon information formats. 712 +----------------------------------------------------------------- 713 | Amplification with different gain for frequencies within the 714 | amplification bandwidth. This could be applied to both single- 715 | channel and multi-channel systems. 716 +----------------------------------------------------------------- 717 | Dispersion compensation (phase distortion). This analogue 718 | process can be applied in either single-channel or multi- 719 | channel systems. 720 --------------------------------------------------------------------- 721 2R | Any or all 1R functions. Noise suppression. 722 +----------------------------------------------------------------- 723 | Digital reshaping (Schmitt Trigger function) with no clock 724 | recovery. This is applicable to individual channels and can be 725 | used for different bit rates but is not transparent to line 726 | coding (modulation). 727 -------------------------------------------------------------------- 728 3R | Any or all 1R and 2R functions. Complete regeneration of the 729 | pulse shape including clock recovery and retiming within 730 | required jitter limits. 731 -------------------------------------------------------------------- 733 From this table it is seen that 1R regenerators are generally 734 independent of signal modulation format (also known as line coding), 735 but may work over a limited range of wavelength/frequencies. 2R 736 regenerators are generally applicable to a single digital stream and 737 are dependent upon modulation format (line coding) and to a lesser 738 extent are limited to a range of bit rates (but not a specific bit 739 rate). Finally, 3R regenerators apply to a single channel, are 740 dependent upon the modulation format and generally sensitive to the 741 bit rate of digital signal, i.e., either are designed to only handle 742 a specific bit rate or need to be programmed to accept and regenerate 743 a specific bit rate. In all these types of regenerators the digital 744 bit stream contained within the optical or electrical signal is not 745 modified. 747 It is common for regenerators to modify the digital bit stream for 748 performance monitoring and fault management purposes. Synchronous 749 Optical Networking (SONET), Synchronous Digital Hierarchy (SDH) and 750 Interfaces for the Optical Transport Network (G.709) all have digital 751 signal "envelopes" designed to be used between "regenerators" (in 752 this case 3R regenerators). In SONET this is known as the "section" 753 signal, in SDH this is known as the "regenerator section" signal, in 754 G.709 this is known as an OTUk. These signals reserve a portion of 755 their frame structure (known as overhead) for use by regenerators. 756 The nature of this overhead is summarized in Table 2 below. 758 Table 2. SONET, SDH, and G.709 regenerator related overhead. 760 +-----------------------------------------------------------------+ 761 |Function | SONET/SDH | G.709 OTUk | 762 | | Regenerator | | 763 | | Section | | 764 |------------------+----------------------+-----------------------| 765 |Signal | J0 (section | Trail Trace | 766 |Identifier | trace) | Identifier (TTI) | 767 |------------------+----------------------+-----------------------| 768 |Performance | BIP-8 (B1) | BIP-8 (within SM) | 769 |Monitoring | | | 770 |------------------+----------------------+-----------------------| 771 |Management | D1-D3 bytes | GCC0 (general | 772 |Communications | | communications | 773 | | | channel) | 774 |------------------+----------------------+-----------------------| 775 |Fault Management | A1, A2 framing | FAS (frame alignment | 776 | | bytes | signal), BDI(backward| 777 | | | defect indication)BEI| 778 | | | (backward error | 779 | | | indication) | 780 +------------------+----------------------+-----------------------| 781 |Forward Error | P1,Q1 bytes | OTUk FEC | 782 |Correction (FEC) | | | 783 +-----------------------------------------------------------------+ 785 In the previous table it is seen that frame alignment, signal 786 identification, and FEC are supported. What this table also shows by 787 its omission is that no switching or multiplexing occurs at this 788 layer. This is a significant simplification for the control plane 789 since control plane standards require a multi-layer approach when 790 there are multiple switching layers, but not for "layering" to 791 provide the management functions of Table 2. That is, many existing 792 technologies covered by GMPLS contain extra management related layers 793 that are essentially ignored by the control plane (though not by the 794 management plane!). Hence, the approach here is to include 795 regenerators and other devices at the WSON layer unless they provide 796 higher layer switching and then a multi-layer or multi-region 797 approach [RFC5212] is called for. However, this can result in 798 regenerators having a dependence on the client signal type. 800 Hence depending upon the regenerator technology the following 801 constraints may be imposed by a regenerator device: 803 Table 3. Regenerator Compatibility Constraints. 805 +--------------------------------------------------------+ 806 | Constraints | 1R | 2R | 3R | 807 +--------------------------------------------------------+ 808 | Limited Wavelength Range | x | x | x | 809 +--------------------------------------------------------+ 810 | Modulation Type Restriction | | x | x | 811 +--------------------------------------------------------+ 812 | Bit Rate Range Restriction | | x | x | 813 +--------------------------------------------------------+ 814 | Exact Bit Rate Restriction | | | x | 815 +--------------------------------------------------------+ 816 | Client Signal Dependence | | | x | 817 +--------------------------------------------------------+ 819 Note that the limited wavelength range constraint can be modeled for 820 GMPLS signaling with the label set defined in [RFC3471] and that the 821 modulation type restriction constraint includes FEC. 823 3.5.2. OEO Switches 825 A common place where OEO processing may take place is within WSON 826 switches that utilize (or contain) regenerators. Regenerators may be 827 added to a switching system for a number of reasons. One common 828 reason is to restore signal quality either before or after optical 829 processing (switching). Another reason may be to convert the signal 830 to an electronic form for switching then reconverting to an optical 831 signal prior to output from the switch. In this later case the 832 regeneration is applied to adapt the signal to the switch fabric 833 regardless of whether or not it is needed from a signal quality 834 perspective. 836 In either case these optical switches have essentially the same 837 compatibility constraints as those which are described for 838 regenerators in Table 3. 840 3.6. Wavelength Converters 842 Wavelength converters take an input optical signal at one wavelength 843 and emit an equivalent content optical signal at another wavelength 844 on output. There are multiple approaches to building wavelength 845 converters. One approach is based on OEO conversion with fixed or 846 tunable optics on output. This approach can be dependent upon the 847 signal rate and format, i.e., this is basically an electrical 848 regenerator combined with a laser/receiver. Hence, this type of 849 wavelength converter has signal processing restrictions that are 850 essentially the same as those described for regenerators in Table 3 851 of section 3.5.1. 853 Another approach performs the wavelength conversion, optically via 854 non-linear optical effects, similar in spirit to the familiar 855 frequency mixing used in radio frequency systems, but significantly 856 harder to implement. Such processes/effects may place limits on the 857 range of achievable conversion. These may depend on the wavelength of 858 the input signal and the properties of the converter as opposed to 859 only the properties of the converter in the OEO case. Different WSON 860 system designs may choose to utilize this component to varying 861 degrees or not at all. 863 Current or envisioned contexts for wavelength converters are: 865 1. Wavelength conversion associated with OEO switches and fixed or 866 tunable optics. In this case there are typically multiple 867 converters available since each on the use of an OEO switch can be 868 thought of as a potential wavelength converter. 870 2. Wavelength conversion associated with ROADMs/OXCs. In this case 871 there may be a limited pool of wavelength converters available. 872 Conversion could be either all optical or via an OEO method. 874 3. Wavelength conversion associated with fixed devices such as FOADMs. 875 In this case there may be a limited amount of conversion. Also in 876 this case the conversion may be used as part of optical path 877 routing. 879 Based on the above considerations, wavelength converters are modeled 880 as follows: 882 1. Wavelength converters can always be modeled as associated with 883 network elements. This includes fixed wavelength routing elements. 885 2. A network element may have full wavelength conversion capability, 886 i.e., any input port and wavelength, or a limited number of 887 wavelengths and ports. On a box with a limited number of 888 converters there also may exist restrictions on which ports can 889 reach the converters. Hence regardless of where the converters 890 actually are they can be associated with input ports. 892 3. Wavelength converters have range restrictions that are either 893 independent or dependent upon the input wavelength. 895 In WSONs where wavelength converters are sparse an optical path may 896 appear to loop or "backtrack" upon itself in order to reach a 897 wavelength converter prior to continuing on to its destination. The 898 lambda used on input to the wavelength converter would be different 899 the lambda coming back from the wavelength converter. 901 A model for an individual O-E-O wavelength converter would consist 902 of: 904 o Input lambda or frequency range. 906 o Output lambda or frequency range. 908 3.6.1. Wavelength Converter Pool Modeling 910 A WSON node may include multiple wavelength converters. These are 911 usually arranged into some type of pool to promote resource sharing. 912 There are a number of different approaches used in the design of 913 switches with converter pools. However, from the point of view of 914 path computation it is necessary to know the following: 916 1. The nodes that support wavelength conversion. 918 2. The accessibility and availability of a wavelength converter to 919 convert from a given input wavelength on a particular input port 920 to a desired output wavelength on a particular output port. 922 3. Limitations on the types of signals that can be converted and the 923 conversions that can be performed. 925 To model point 2 above, a similar technique can be used to model 926 ROADMs and optical switches, i.e., matrices to indicate possible 927 connectivity along with wavelength constraints for links/ports. Since 928 wavelength converters are considered a scarce resource it will be 929 desirable to include as a minimum the usage state of individual 930 wavelength converters in the pool. 932 A three stage model is used as shown schematically in Figure 3. 933 (Schematic diagram of wavelength converter pool model). This model 934 represents N input ports (fibers), P wavelength converters, and M 935 output ports (fibers). Since not all input ports can necessarily 936 reach the converter pool, the model starts with a wavelength pool 937 input matrix WI(i,p) = {0,1} where input port i can reach potentially 938 reach wavelength converter p. 940 Since not all wavelength can necessarily reach all the converters or 941 the converters may have limited input wavelength range there is a set 942 of input port constraints for each wavelength converter. Currently it 943 is assumed that a wavelength converter can only take a single 944 wavelength on input. Each wavelength converter input port constraint 945 can be modeled via a wavelength set mechanism. 947 Next a state vector WC(j) = {0,1} dependent upon whether wavelength 948 converter j in the pool is in use. This is the only state kept in the 949 converter pool model. This state is not necessary for modeling 950 "fixed" transponder system, i.e., systems where there is no sharing. 951 In addition, this state information may be encoded in a much more 952 compact form depending on the overall connectivity structure [GEN- 953 Encode]. 955 After that, a set of wavelength converter output wavelength 956 constraints is used. These constraints indicate what wavelengths a 957 particular wavelength converter can generate or are restricted to 958 generating due to internal switch structure. 960 Finally, a wavelength pool output matrix WE(p,k) = {0,1} indicating 961 whether the output from wavelength converter p can reach output port 962 k. Examples of this method being used to model wavelength converter 963 pools for several switch architectures are given in reference [GEN- 964 Encode]. 966 I1 +-------------+ +-------------+ E1 967 ----->| | +--------+ | |-----> 968 I2 | +------+ WC #1 +-------+ | E2 969 ----->| | +--------+ | |-----> 970 | Wavelength | | Wavelength | 971 | Converter | +--------+ | Converter | 972 | Pool +------+ WC #2 +-------+ Pool | 973 | | +--------+ | | 974 | Input | | Output | 975 | Connection | . | Connection | 976 | Matrix | . | Matrix | 977 | | . | | 978 | | | | 979 IN | | +--------+ | | EM 980 ----->| +------+ WC #P +-------+ |-----> 981 | | +--------+ | | 982 +-------------+ ^ ^ +-------------+ 983 | | 984 | | 985 | | 986 | | 988 Input wavelength Output wavelength 989 constraints for constraints for 990 each converter each converter 992 Figure 3. Schematic diagram of wavelength converter pool model. 994 Figure 4 below shows a simple optical switch in a four wavelength 995 DWDM system sharing wavelength converters in a general shared "per 996 node" fashion. 998 +-----------+ ___________ +------+ 999 | |--------------------------->| | 1000 | |--------------------------->| C | 1001 /| | |--------------------------->| o | E1 1002 I1 /D+--->| |--------------------------->| m | 1003 + e+--->| | | b |====> 1004 ====>| M| | Optical | +-----------+ +----+ | i | 1005 + u+--->| Switch | | WC Pool | |O S|-->| n | 1006 \x+--->| | | +-----+ | |p w|-->| e | 1007 \| | +----+->|WC #1|--+->|t i| | r | 1008 | | | +-----+ | |i t| +------+ 1009 | | | | |c c| +------+ 1010 /| | | | +-----+ | |a h|-->| | 1011 I2 /D+--->| +----+->|WC #2|--+->|l |-->| C | E2 1012 + e+--->| | | +-----+ | | | | o | 1013 ====>| M| | | +-----------+ +----+ | m |====> 1014 + u+--->| | | b | 1015 \x+--->| |--------------------------->| i | 1016 \| | |--------------------------->| n | 1017 | |--------------------------->| e | 1018 |___________|--------------------------->| r | 1019 +-----------+ +------+ 1021 Figure 4. An optical switch featuring a shared per node wavelength 1022 converter pool architecture. 1024 In this case the input and output pool matrices are simply: 1026 +-----+ +-----+ 1027 | 1 1 | | 1 1 | 1028 WI =| |, WE =| | 1029 | 1 1 | | 1 1 | 1030 +-----+ +-----+ 1032 Figure 5 shows a different wavelength pool architecture known as 1033 "shared per fiber". In this case the input and output pool matrices 1034 are simply: 1036 +-----+ +-----+ 1037 | 1 1 | | 1 0 | 1038 WI =| |, WE =| | 1039 | 1 1 | | 0 1 | 1040 +-----+ +-----+ 1041 +-----------+ +------+ 1042 | |--------------------------->| | 1043 | |--------------------------->| C | 1044 /| | |--------------------------->| o | E1 1045 I1 /D+--->| |--------------------------->| m | 1046 + e+--->| | | b |====> 1047 ====>| M| | Optical | +-----------+ | i | 1048 + u+--->| Switch | | WC Pool | | n | 1049 \x+--->| | | +-----+ | | e | 1050 \| | +----+->|WC #1|--+---------->| r | 1051 | | | +-----+ | +------+ 1052 | | | | +------+ 1053 /| | | | +-----+ | | | 1054 I2 /D+--->| +----+->|WC #2|--+---------->| C | E2 1055 + e+--->| | | +-----+ | | o | 1056 ====>| M| | | +-----------+ | m |====> 1057 + u+--->| | | b | 1058 \x+--->| |--------------------------->| i | 1059 \| | |--------------------------->| n | 1060 | |--------------------------->| e | 1061 |___________|--------------------------->| r | 1062 +-----------+ +------+ 1063 Figure 5. An optical switch featuring a shared per fiber wavelength 1064 converter pool architecture. 1066 3.7. Characterizing Electro-Optical Network Elements 1068 In this section electro-optical WSON network elements are 1069 characterized by the three key functional components: input 1070 constraints, output constraints and processing capabilities. 1072 WSON Network Element 1073 +-----------------------+ 1074 WSON Signal | | | | WSON Signal 1075 | | | | 1076 ---------------> | | | | -----------------> 1077 | | | | 1078 +-----------------------+ 1079 <-----> <-------> <-----> 1081 Input Processing Output 1083 Figure 6. WSON Network Element 1085 3.7.1. Input Constraints 1087 Section 3. (Wavelength Switched Optical Networks) discussed the basic 1088 properties regenerators, OEO switches and wavelength converters. From 1089 these the following possible types of input constraints and 1090 properties are derived: 1092 1. Acceptable Modulation formats. 1094 2. Client Signal (G-PID) restrictions. 1096 3. Bit Rate restrictions. 1098 4. FEC coding restrictions. 1100 5. Configurability: (a) none, (b) self-configuring, (c) required. 1102 These constraints are represented via simple lists. Note that the 1103 device may need to be "provisioned" via signaling or some other means 1104 to accept signals with some attributes versus others. In other cases 1105 the devices maybe relatively transparent to some attributes, e.g., 1106 such as a 2R regenerator to bit rate. Finally, some devices may be 1107 able to auto-detect some attributes and configure themselves, e.g., a 1108 3R regenerator with bit rate detection mechanisms and flexible phase 1109 locking circuitry. To account for these different cases item 5 has 1110 been added, which describes the devices configurability. 1112 Note that such input constraints also apply to the termination of the 1113 WSON signal. 1115 3.7.2. Output Constraints 1117 None of the network elements considered here modifies either the bit 1118 rate or the basic type of the client signal. However, they may modify 1119 the modulation format or the FEC code. Typically the following types 1120 of output constraints are seen: 1122 1. Output modulation is the same as input modulation (default). 1124 2. A limited set of output modulations is available. 1126 3. Output FEC is the same as input FEC code (default). 1128 4. A limited set of output FEC codes is available. 1130 Note that in cases (2) and (4) above, where there is more than one 1131 choice in the output modulation or FEC code then the network element 1132 will need to be configured on a per LSP basis as to which choice to 1133 use. 1135 3.7.3. Processing Capabilities 1137 A general WSON network element (NE) can perform a number of signal 1138 processing functions including: 1140 (A) Regeneration (possibly different types). 1142 (B) Fault and Performance Monitoring. 1144 (C) Wavelength Conversion. 1146 (D) Switching. 1148 An NE may or may not have the ability to perform regeneration (of the 1149 one of the types previously discussed). In addition some nodes may 1150 have limited regeneration capability, i.e., a shared pool, which may 1151 be applied to selected signals traversing the NE. Hence to describe 1152 the regeneration capability of a link or node it is necessary to have 1153 at a minimum: 1155 1. Regeneration capability: (a)fixed, (b) selective, (c) none. 1157 2. Regeneration type: 1R, 2R, 3R. 1159 3. Regeneration pool properties for the case of selective 1160 regeneration (input and output restrictions, availability). 1162 Note that the properties of shared regenerator pools would be 1163 essentially the same at that of wavelength converter pools modeled in 1164 section 3.6.1. (Wavelength Pool Convertor Modeling). 1166 Item (B), fault and performance monitoring, is typically outside the 1167 scope of the control plane. However, when the operations are to be 1168 performed on an LSP basis or on part of an LSP then the control plane 1169 can be of assistance in their configuration. Per LSP, per node, fault 1170 and performance monitoring examples include setting up a "section 1171 trace" (a regenerator overhead identifier) between two nodes, or 1172 intermediate optical performance monitoring at selected nodes along a 1173 path. 1175 4. Routing and Wavelength Assignment and the Control Plane 1177 From a control plane perspective, a wavelength-convertible network 1178 with full wavelength-conversion capability at each node can be 1179 controlled much like a packet MPLS-labeled network or a circuit- 1180 switched Time-division multiplexing (TDM) network with full time slot 1181 interchange capability is controlled. In this case, the path 1182 selection process needs to identify the Traffic Engineered (TE) links 1183 to be used by an optical path, and wavelength assignment can be made 1184 on a hop-by-hop basis. 1186 However, in the case of an optical network without wavelength 1187 converters, an optical path needs to be routed from source to 1188 destination and must use a single wavelength that is available along 1189 that path without "colliding" with a wavelength used by any other 1190 optical path that may share an optical fiber. This is sometimes 1191 referred to as a "wavelength continuity constraint". 1193 In the general case of limited or no wavelength converters the 1194 computation of both the links and wavelengths is known as RWA. 1196 The inputs to basic RWA are the requested optical path's source and 1197 destination, the network topology, the locations and capabilities of 1198 any wavelength converters, and the wavelengths available on each 1199 optical link. The output from an algorithm providing RWA is an 1200 explicit route through ROADMs, a wavelength for optical transmitter, 1201 and a set of locations (generally associated with ROADMs or switches) 1202 where wavelength conversion is to occur and the new wavelength to be 1203 used on each component link after that point in the route. 1205 It is to be noted that the choice of specific RWA algorithm is out of 1206 the scope for this document. However there are a number of different 1207 approaches to dealing with RWA algorithm that can affect the division 1208 of effort between path computation/routing and signaling. 1210 4.1. Architectural Approaches to RWA 1212 Two general computational approaches are taken to performing RWA. 1213 Some algorithms utilize a two-step procedure of path selection 1214 followed by wavelength assignment, and others perform RWA in a 1215 combined fashion. 1217 In the following, three different ways of performing RWA in 1218 conjunction with the control plane are considered. The choice of one 1219 of these architectural approaches over another generally impacts the 1220 demands placed on the various control plane protocols. The approaches 1221 are provided for reference purposes only, and other approaches are 1222 possible. 1224 4.1.1. Combined RWA (R&WA) 1226 In this case, a unique entity is in charge of performing routing and 1227 wavelength assignment. This approach relies on a sufficient knowledge 1228 of network topology, of available network resources and of network 1229 nodes capabilities. This solution is compatible with most known RWA 1230 algorithms, and in particular those concerned with network 1231 optimization. On the other hand, this solution requires up-to-date 1232 and detailed network information. 1234 Such a computational entity could reside in two different places: 1236 o In a PCE which maintains a complete and updated view of network 1237 state and provides path computation services to nodes (PCCs). 1239 o In an ingress node, in which case all nodes have the R&WA 1240 functionality and network state is obtained by a periodic flooding 1241 of information provided by the other nodes. 1243 4.1.2. Separated R and WA (R+WA) 1245 In this case, one entity performs routing, while a second performs 1246 wavelength assignment. The first entity furnishes one or more paths 1247 to the second entity which will perform wavelength assignment and 1248 final path selection. 1250 As the entities computing the path and the wavelength assignment are 1251 separated, this constrains the class of RWA algorithms that may be 1252 implemented. Although it may seem that algorithms optimizing a joint 1253 usage of the physical and wavelength paths are excluded from this 1254 solution, many practical optimization algorithms only consider a 1255 limited set of possible paths, e.g., as computed via a k-shortest 1256 path algorithm. Hence, while there is no guarantee that the selected 1257 final route and wavelength offers the optimal solution, by allowing 1258 multiple routes to pass to the wavelength selection process 1259 reasonable optimization can be performed. 1261 The entity performing the routing assignment needs the topology 1262 information of the network, whereas the entity performing the 1263 wavelength assignment needs information on the network's available 1264 resources and specific network node capabilities. 1266 4.1.3. Routing and Distributed WA (R+DWA) 1268 In this case, one entity performs routing, while wavelength 1269 assignment is performed on a hop-by-hop, distributed, manner along 1270 the previously computed path. This mechanism relies on updating of a 1271 list of potential wavelengths used to ensure conformance with the 1272 wavelength continuity constraint. 1274 As currently specified, the GMPLS protocol suite signaling protocol 1275 can accommodate such an approach. GMPLS, per [RFC3471], includes 1276 support for the communication of the set of labels (wavelengths) that 1277 may be used between nodes via a Label Set. When conversion is not 1278 performed at an intermediate node, a hop generates the Label Set it 1279 sends to the next hop based on the intersection of the Label Set 1280 received from the previous hop and the wavelengths available on the 1281 node's switch and ongoing interface. The generation of the outgoing 1282 Label Set is up to the node local policy (even if one expects a 1283 consistent policy configuration throughout a given transparency 1284 domain). When wavelength conversion is performed at an intermediate 1285 node, a new Label Set is generated. The egress node selects one label 1286 in the Label Set which it received; additionally the node can apply 1287 local policy during label selection. GMPLS also provides support for 1288 the signaling of bidirectional optical paths. 1290 Depending on these policies a wavelength assignment may not be found 1291 or one consuming too many conversion resources relative to what a 1292 dedicated wavelength assignment policy would have achieved. Hence, 1293 this approach may generate higher blocking probabilities in a heavily 1294 loaded network. 1296 This solution may be facilitated via signaling extensions which ease 1297 its functioning and possibly enhance its performance relatively to 1298 blocking. Note that this approach requires less information 1299 dissemination than the other techniques described. 1301 The first entity may be a PCE or the ingress node of the LSP. 1303 4.2. Conveying information needed by RWA 1305 The previous sections have characterized WSONs and optical path 1306 requests. In particular, high level models of the information used by 1307 RWA process were presented. This information can be viewed as either 1308 relatively static, i.e., changing with hardware changes (including 1309 possibly failures), or relatively dynamic, i.e., those that can 1310 change with optical path provisioning. The time requirement in which 1311 an entity involved in RWA process needs to be notified of such 1312 changes is fairly situational. For example, for network restoration 1313 purposes, learning of a hardware failure or of new hardware coming 1314 online to provide restoration capability can be critical. 1316 Currently there are various methods for communicating RWA relevant 1317 information, these include, but are not limited to: 1319 o Existing control plane protocols, i.e., GMPLS routing and 1320 signaling. Note that routing protocols can be used to convey both 1321 static and dynamic information. 1323 o Management protocols such as NetConf, SNMPv3, CLI, and CORBA. 1325 o Directory services and accompanying protocols. These are typically 1326 used for the dissemination of relatively static information. 1327 Directory services are not suited to manage information in dynamic 1328 and fluid environments. 1330 o Other techniques for dynamic information, e.g., sending 1331 information directly from NEs to PCE to avoid flooding. This would 1332 be useful if the number of PCEs is significantly less than number 1333 of WSON NEs. Or other ways to limit flooding to "interested" NEs. 1335 Possible mechanisms to improve scaling of dynamic information 1336 include: 1338 o Tailor message content to WSON. For example the use of wavelength 1339 ranges, or wavelength occupation bit maps. 1341 o Utilize incremental updates if feasible. 1343 5. Modeling Examples and Control Plane Use Cases 1345 This section provides examples of the fixed and switch optical node 1346 and wavelength constraint models of Section 3. and WSON control 1347 plane use cases related to path computation, establishment, 1348 rerouting, and optimization. 1350 5.1. Network Modeling for GMPLS/PCE Control 1352 Consider a network containing three routers (R1 through R3), eight 1353 WSON nodes (N1 through N8) and 18 links (L1 through L18) and one OEO 1354 converter (O1) in a topology shown below. 1356 +--+ +--+ +--+ +--------+ 1357 +-L3-+N2+-L5-+ +--------L12--+N6+--L15--+ N8 + 1358 | +--+ |N4+-L8---+ +--+ ++--+---++ 1359 | | +-L9--+| | | | 1360 +--+ +-+-+ ++-+ || | L17 L18 1361 | ++-L1--+ | | ++++ +----L16---+ | | 1362 |R1| | N1| L7 |R2| | | | 1363 | ++-L2--+ | | ++-+ | ++---++ 1364 +--+ +-+-+ | | | + R3 | 1365 | +--+ ++-+ | | +-----+ 1366 +-L4-+N3+-L6-+N5+-L10-+ ++----+ 1367 +--+ | +--------L11--+ N7 + 1368 +--+ ++---++ 1369 | | 1370 L13 L14 1371 | | 1372 ++-+ | 1373 |O1+-+ 1374 +--+ 1376 Figure 7. Routers and WSON nodes in a GMPLS and PCE Environment. 1378 5.1.1. Describing the WSON nodes 1380 The eight WSON nodes described in Figure 7 have the following 1381 properties: 1383 o Nodes N1, N2, N3 have FOADMs installed and can therefore only 1384 access a static and pre-defined set of wavelengths. 1386 o All other nodes contain ROADMs and can therefore access all 1387 wavelengths. 1389 o Nodes N4, N5, N7 and N8 are multi-degree nodes, allowing any 1390 wavelength to be optically switched between any of the links. Note 1391 however, that this does not automatically apply to wavelengths 1392 that are being added or dropped at the particular node. 1394 o Node N4 is an exception to that: This node can switch any 1395 wavelength from its add/drop ports to any of its output links (L5, 1396 L7 and L12 in this case). 1398 o The links from the routers are only able to carry one wavelength 1399 with the exception of links L8 and L9 which are capable to 1400 add/drop any wavelength. 1402 o Node N7 contains an OEO transponder (O1) connected to the node via 1403 links L13 and L14. That transponder operates in 3R mode and does 1404 not change the wavelength of the signal. Assume that it can 1405 regenerate any of the client signals, however only for a specific 1406 wavelength. 1408 Given the above restrictions, the node information for the eight 1409 nodes can be expressed as follows: (where ID == identifier, SCM == 1410 switched connectivity matrix, and FCM == fixed connectivity matrix). 1412 +ID+SCM +FCM + 1413 | | |L1 |L2 |L3 |L4 | | |L1 |L2 |L3 |L4 | | 1414 | |L1 |0 |0 |0 |0 | |L1 |0 |0 |1 |0 | | 1415 |N1|L2 |0 |0 |0 |0 | |L2 |0 |0 |0 |1 | | 1416 | |L3 |0 |0 |0 |0 | |L3 |1 |0 |0 |1 | | 1417 | |L4 |0 |0 |0 |0 | |L4 |0 |1 |1 |0 | | 1418 +--+---+---+---+---+---+---+---+---+---+---+---+---+ 1419 | | |L3 |L5 | | | | |L3 |L5 | | | | 1420 |N2|L3 |0 |0 | | | |L3 |0 |1 | | | | 1421 | |L5 |0 |0 | | | |L5 |1 |0 | | | | 1422 +--+---+---+---+---+---+---+---+---+---+---+---+---+ 1423 | | |L4 |L6 | | | | |L4 |L6 | | | | 1424 |N3|L4 |0 |0 | | | |L4 |0 |1 | | | | 1425 | |L6 |0 |0 | | | |L6 |1 |0 | | | | 1426 +--+---+---+---+---+---+---+---+---+---+---+---+---+ 1427 | | |L5 |L7 |L8 |L9 |L12| |L5 |L7 |L8 |L9 |L12| 1428 | |L5 |0 |1 |1 |1 |1 |L5 |0 |0 |0 |0 |0 | 1429 |N4|L7 |1 |0 |1 |1 |1 |L7 |0 |0 |0 |0 |0 | 1430 | |L8 |1 |1 |0 |1 |1 |L8 |0 |0 |0 |0 |0 | 1431 | |L9 |1 |1 |1 |0 |1 |L9 |0 |0 |0 |0 |0 | 1432 | |L12|1 |1 |1 |1 |0 |L12|0 |0 |0 |0 |0 | 1433 +--+---+---+---+---+---+---+---+---+---+---+---+---+ 1434 | | |L6 |L7 |L10|L11| | |L6 |L7 |L10|L11| | 1435 | |L6 |0 |1 |0 |1 | |L6 |0 |0 |1 |0 | | 1436 |N5|L7 |1 |0 |0 |1 | |L7 |0 |0 |0 |0 | | 1437 | |L10|0 |0 |0 |0 | |L10|1 |0 |0 |0 | | 1438 | |L11|1 |1 |0 |0 | |L11|0 |0 |0 |0 | | 1439 +--+---+---+---+---+---+---+---+---+---+---+---+---+ 1440 | | |L12|L15| | | | |L12|L15| | | | 1441 |N6|L12|0 |1 | | | |L12|0 |0 | | | | 1442 | |L15|1 |0 | | | |L15|0 |0 | | | | 1443 +--+---+---+---+---+---+---+---+---+---+---+---+---+ 1444 | | |L11|L13|L14|L16| | |L11|L13|L14|L16| | 1445 | |L11|0 |1 |0 |1 | |L11|0 |0 |0 |0 | | 1446 |N7|L13|1 |0 |0 |0 | |L13|0 |0 |1 |0 | | 1447 | |L14|0 |0 |0 |1 | |L14|0 |1 |0 |0 | | 1448 | |L16|1 |0 |1 |0 | |L16|0 |0 |1 |0 | | 1449 +--+---+---+---+---+---+---+---+---+---+---+---+---+ 1450 | | |L15|L16|L17|L18| | |L15|L16|L17|L18| | 1451 | |L15|0 |1 |0 |0 | |L15|0 |0 |0 |1 | | 1452 |N8|L16|1 |0 |0 |0 | |L16|0 |0 |1 |0 | | 1453 | |L17|0 |0 |0 |0 | |L17|0 |1 |0 |0 | | 1454 | |L18|0 |0 |0 |0 | |L18|1 |0 |1 |0 | | 1455 +--+---+---+---+---+---+---+---+---+---+---+---+---+ 1457 5.1.2. Describing the links 1459 For the following discussion some simplifying assumptions are made: 1461 o It is assumed that the WSON node support a total of four 1462 wavelengths designated WL1 through WL4. 1464 o It is assumed that the impairment feasibility of a path or path 1465 segment is independent from the wavelength chosen. 1467 For the discussion of RWA operation to build LSPs between two 1468 routers, the wavelength constraints on the links between the routers 1469 and the WSON nodes as well as the connectivity matrix of these links 1470 needs to be specified: 1472 +Link+WLs supported +Possible output links+ 1473 | L1 | WL1 | L3 | 1474 +----+-----------------+---------------------+ 1475 | L2 | WL2 | L4 | 1476 +----+-----------------+---------------------+ 1477 | L8 | WL1 WL2 WL3 WL4 | L5 L7 L12 | 1478 +----+-----------------+---------------------+ 1479 | L9 | WL1 WL2 WL3 WL4 | L5 L7 L12 | 1480 +----+-----------------+---------------------+ 1481 | L10| WL2 | L6 | 1482 +----+-----------------+---------------------+ 1483 | L13| WL1 WL2 WL3 WL4 | L11 L14 | 1484 +----+-----------------+---------------------+ 1485 | L14| WL1 WL2 WL3 WL4 | L13 L16 | 1486 +----+-----------------+---------------------+ 1487 | L17| WL2 | L16 | 1488 +----+-----------------+---------------------+ 1489 | L18| WL1 | L15 | 1490 +----+-----------------+---------------------+ 1492 Note that the possible output links for the links connecting to the 1493 routers is inferred from the switched connectivity matrix and the 1494 fixed connectivity matrix of the Nodes N1 through N8 and is show here 1495 for convenience, i.e., this information does not need to be repeated. 1497 5.2. RWA Path Computation and Establishment 1499 The calculation of optical impairment feasible routes is outside the 1500 scope of this document. In general impairment feasible routes serve 1501 as an input to RWA algorithm. 1503 For the example use case shown here, assume the following feasible 1504 routes: 1506 +Endpoint 1+Endpoint 2+Feasible Route + 1507 | R1 | R2 | L1 L3 L5 L8 | 1508 | R1 | R2 | L1 L3 L5 L9 | 1509 | R1 | R2 | L2 L4 L6 L7 L8 | 1510 | R1 | R2 | L2 L4 L6 L7 L9 | 1511 | R1 | R2 | L2 L4 L6 L10 | 1512 | R1 | R3 | L1 L3 L5 L12 L15 L18 | 1513 | R1 | N7 | L2 L4 L6 L11 | 1514 | N7 | R3 | L16 L17 | 1515 | N7 | R2 | L16 L15 L12 L9 | 1516 | R2 | R3 | L8 L12 L15 L18 | 1517 | R2 | R3 | L8 L7 L11 L16 L17 | 1518 | R2 | R3 | L9 L12 L15 L18 | 1519 | R2 | R3 | L9 L7 L11 L16 L17 | 1521 Given a request to establish a LSP between R1 and R2 RWA algorithm 1522 finds the following possible solutions: 1524 +WL + Path + 1525 | WL1| L1 L3 L5 L8 | 1526 | WL1| L1 L3 L5 L9 | 1527 | WL2| L2 L4 L6 L7 L8| 1528 | WL2| L2 L4 L6 L7 L9| 1529 | WL2| L2 L4 L6 L10 | 1531 Assume now that RWA algorithm yields WL1 and the Path L1 L3 L5 L8 for 1532 the requested LSP. 1534 Next, another LSP is signaled from R1 to R2. Given the established 1535 LSP using WL1, the following table shows the available paths: 1537 +WL + Path + 1538 | WL2| L2 L4 L6 L7 L9| 1539 | WL2| L2 L4 L6 L10 | 1541 Assume now that RWA algorithm yields WL2 and the path L2 L4 L6 L7 L9 1542 for the establishment of the new LSP. 1544 A LSP request -this time from R2 to R3 - can not be fulfilled since 1545 the only four possible paths (starting at L8 and L9) are already in 1546 use. 1548 5.3. Resource Optimization 1550 The preceding example gives rise to another use case: the 1551 optimization of network resources. Optimization can be achieved on a 1552 number of layers (e.g. through electrical or optical multiplexing of 1553 client signals) or by re-optimizing the solutions found by a RWA 1554 algorithm. 1556 Given the above example again, assume that a RWA algorithm should 1557 identify a path between R2 and R3. The only possible path to reach R3 1558 from R2 needs to use L9. L9 however is blocked by one of the LSPs 1559 from R1. 1561 5.4. Support for Rerouting 1563 It is also envisioned that the extensions to GMPLS and PCE support 1564 rerouting of wavelengths in case of failures. 1566 Assume for this discussion that the only two LSPs in use in the 1567 system are: 1569 LSP1: WL1 L1 L3 L5 L8 1571 LSP2: WL2 L2 L4 L6 L7 L9 1573 Assume furthermore that the link L5 fails. An RWA algorithm can now 1574 compute the following alternate path and establish that path: 1576 R1 -> N7 -> R2 1578 Level 3 regeneration will take place at N7, so that the complete path 1579 looks like this: 1581 R1 -> L2 L4 L6 L11 L13 -> O1 -> L14 L16 L15 L12 L9 -> R2 1583 5.5. Electro-Optical Networking Scenarios 1585 In the following various networking scenarios are considered 1586 involving regenerators, OEO switches and wavelength converters. These 1587 scenarios can be grouped roughly by type and number of extensions to 1588 the GMPLS control plane that would be required. 1590 5.5.1. Fixed Regeneration Points 1592 In the simplest networking scenario involving regenerators, 1593 regeneration is associated with a WDM link or an entire node and is 1594 not optional, i.e., all signals traversing the link or node will be 1595 regenerated. This includes OEO switches since they provide 1596 regeneration on every port. 1598 There may be input constraints and output constraints on the 1599 regenerators. Hence the path selection process will need to know from 1600 routing or other means the regenerator constraints so that it can 1601 choose a compatible path. For impairment aware routing and wavelength 1602 assignment (IA-RWA) the path selection process will also need to know 1603 which links/nodes provide regeneration. Even for "regular" RWA, this 1604 regeneration information is useful since wavelength converters 1605 typically perform regeneration and the wavelength continuity 1606 constraint can be relaxed at such a point. 1608 Signaling does not need to be enhanced to include this scenario since 1609 there are no reconfigurable regenerator options on input, output or 1610 with respect to processing. 1612 5.5.2. Shared Regeneration Pools 1614 In this scenario there are nodes with shared regenerator pools within 1615 the network in addition to fixed regenerators of the previous 1616 scenario. These regenerators are shared within a node and their 1617 application to a signal is optional. There are no reconfigurable 1618 options on either input or output. The only processing option is to 1619 "regenerate" a particular signal or not. 1621 Regenerator information in this case is used in path computation to 1622 select a path that ensures signal compatibility and IA-RWA criteria. 1624 To setup an LSP that utilizes a regenerator from a node with a shared 1625 regenerator pool it is necessary to indicate that regeneration is to 1626 take place at that particular node along the signal path. Such a 1627 capability currently does not exist in GMPLS signaling. 1629 5.5.3. Reconfigurable Regenerators 1631 This scenario is concerned with regenerators that require 1632 configuration prior to use on an optical signal. As discussed 1633 previously, this could be due to a regenerator that must be 1634 configured to accept signals with different characteristics, for 1635 regenerators with a selection of output attributes, or for 1636 regenerators with additional optional processing capabilities. 1638 As in the previous scenarios it is necessary to have information 1639 concerning regenerator properties for selection of compatible paths 1640 and for IA-RWA computations. In addition during LSP setup it is 1641 necessary to be able configure regenerator options at a particular 1642 node along the path. Such a capability currently does not exist in 1643 GMPLS signaling. 1645 5.5.4. Relation to Translucent Networks 1647 Networks that contain both transparent network elements such as 1648 reconfigurable optical add drop multiplexers (ROADMs) and electro- 1649 optical network elements such regenerators or OEO switches are 1650 frequently referred to as translucent optical networks. 1652 Three main types of translucent optical networks have been discussed: 1654 1. Transparent "islands" surrounded by regenerators. This is 1655 frequently seen when transitioning from a metro optical sub- 1656 network to a long haul optical sub-network. 1658 2. Mostly transparent networks with a limited number of OEO 1659 ("opaque") nodes strategically placed. This takes advantage of the 1660 inherent regeneration capabilities of OEO switches. In the 1661 planning of such networks one has to determine the optimal 1662 placement of the OEO switches. 1664 3. Mostly transparent networks with a limited number of optical 1665 switching nodes with "shared regenerator pools" that can be 1666 optionally applied to signals passing through these switches. 1667 These switches are sometimes called translucent nodes. 1669 All three types of translucent networks fit within the networking 1670 scenarios of Section 5.5.1. and Section 5.5.2. above. And hence, 1671 can be accommodated by the GMPLS extensions envisioned in this 1672 document. 1674 6. GMPLS and PCE Implications 1676 The presence and amount of wavelength conversion available at a 1677 wavelength switching interface has an impact on the information that 1678 needs to be transferred by the control plane (GMPLS) and the PCE 1679 architecture. Current GMPLS and PCE standards can address the full 1680 wavelength conversion case so the following will only address the 1681 limited and no wavelength conversion cases. 1683 6.1. Implications for GMPLS signaling 1685 Basic support for WSON signaling already exists in GMPLS with the 1686 lambda (value 9) LSP encoding type [RFC3471], or for G.709 compatible 1687 optical channels, the LSP encoding type (value = 13) "G.709 Optical 1688 Channel" from [RFC4328]. However a number of practical issues arise 1689 in the identification of wavelengths and signals, and distributed 1690 wavelength assignment processes which are discussed below. 1692 6.1.1. Identifying Wavelengths and Signals 1694 As previously stated a global fixed mapping between wavelengths and 1695 labels simplifies the characterization of WDM links and WSON devices. 1697 Furthermore such a mapping as described in [Otani] provides such a 1698 fixed mapping for communication between PCE and WSON PCCs. 1700 6.1.2. WSON Signals and Network Element Processing 1702 As discussed in Section 3.3.2. a WSON signal at any point along its 1703 path can be characterized by the (a) modulation format, (b) FEC, (c) 1704 wavelength, (d)bit rate, and (d)G-PID. 1706 Currently G-PID, wavelength (via labels), and bit rate (via bandwidth 1707 encoding) are supported in [RFC3471] and [RFC3473]. These RFCs can 1708 accommodate the wavelength changing at any node along the LSP and can 1709 thus provide explicit control of wavelength converters. 1711 In the fixed regeneration point scenario described in Section 5.5.1. 1712 (Fixed Regeneration Points) no enhancements are required to signaling 1713 since there are no additional configuration options for the LSP at a 1714 node. 1716 In the case of shared regeneration pools described in Section 5.5.2. 1717 (Shared Regeneration Pools) it is necessary to indicate to a node 1718 that it should perform regeneration on a particular signal. Viewed 1719 another way, for an LSP, it is desirable to specify that certain 1720 nodes along the path perform regeneration. Such a capability 1721 currently does not exist in GMPLS signaling. 1723 The case of configurable regenerators described in Section 5.5.3. 1724 (Reconfigurable Regenerators) is very similar to the previous except 1725 that now there are potentially many more items that can be configured 1726 on a per node basis for an LSP. 1728 Note that the techniques of [RFC5420] which allow for additional LSP 1729 attributes and their recording in a Record Route Object (RRO) object 1730 could be extended to allow for additional LSP attributes in an ERO. 1731 This could allow one to indicate where optional 3R regeneration 1732 should take place along a path, any modification of LSP attributes 1733 such as modulation format, or any enhance processing such as 1734 performance monitoring. 1736 6.1.3. Combined RWA/Separate Routing WA support 1738 In either the combined RWA or separate routing WA cases, the node 1739 initiating the signaling will have a route from the source to 1740 destination along with the wavelengths (generalized labels) to be 1741 used along portions of the path. Current GMPLS signaling supports an 1742 Explicit Route Object (ERO) and within an ERO an ERO Label subobject 1743 can be used to indicate the wavelength to be used at a particular 1744 node. In case the local label map approach is used the label sub- 1745 object entry in the ERO has to be interpreted appropriately. 1747 6.1.4. Distributed Wavelength Assignment: Unidirectional, No 1748 Converters 1750 GMPLS signaling for a unidirectional optical path LSP allows for the 1751 use of a label set object in the Resource Reservation Protocol - 1752 Traffic Engineering (RSVP-TE) path message. The processing of the 1753 label set object to take the intersection of available lambdas along 1754 a path can be performed resulting in the set of available lambda 1755 being known to the destination that can then use a wavelength 1756 selection algorithm to choose a lambda. 1758 6.1.5. Distributed Wavelength Assignment: Unidirectional, Limited 1759 Converters 1761 In the case of wavelength converters, nodes with wavelength 1762 converters would need to make the decision as to whether to perform 1763 conversion. One indicator for this would be that the set of available 1764 wavelengths which is obtained via the intersection of the incoming 1765 label set and the output links available wavelengths is either null 1766 or deemed too small to permit successful completion. 1768 At this point the node would need to remember that it will apply 1769 wavelength conversion and will be responsible for assigning the 1770 wavelength on the previous lambda-contiguous segment when the RSVP-TE 1771 RESV message is processed. The node will pass on an enlarged label 1772 set reflecting only the limitations of the wavelength converter and 1773 the output link. The record route option in RSVP-TE signaling can be 1774 used to show where wavelength conversion has taken place. 1776 6.1.6. Distributed Wavelength Assignment: Bidirectional, No 1777 Converters 1779 There are cases of a bidirectional optical path which requires the 1780 use of the same lambda in both directions. The above procedure can be 1781 used to determine the available bidirectional lambda set if it is 1782 interpreted that the available label set is available in both 1783 directions. In bidirectional LSPs setup, according to [RFC3471] 1784 Section 4.1. (Architectural Approaches to RWA), is indicated by the 1785 presence of an upstream label in the path message. 1787 However, until the intersection of the available label sets is 1788 determined along the path and at the destination node the upstream 1789 label information may not be correct. This case can be supported 1790 using current GMPLS mechanisms, but may not be as efficient as an 1791 optimized bidirectional single-label allocation mechanism. 1793 6.2. Implications for GMPLS Routing 1795 GMPLS routing [RFC4202] currently defines an interface capability 1796 descriptor for "lambda switch capable" (LSC) which can be used to 1797 describe the interfaces on a ROADM or other type of wavelength 1798 selective switch. In addition to the topology information typically 1799 conveyed via an IGP, it would be necessary to convey the following 1800 subsystem properties to minimally characterize a WSON: 1802 1. WDM Link properties (allowed wavelengths). 1804 2. Optical transmitters (wavelength range). 1806 3. ROADM/FOADM Properties (connectivity matrix, port wavelength 1807 restrictions). 1809 4. Wavelength converter properties (per network element, may change if 1810 a common limited shared pool is used). 1812 This information is modeled in detail in [WSON-Info] and a compact 1813 encoding is given in [WSON-Encode]. 1815 6.2.1. Electro-Optical Element Signal Compatibility 1817 In network scenarios where signal compatibility is a concern it is 1818 necessary to add parameters to our existing node and link models to 1819 take into account electro-optical input constraints, output 1820 constraints, and the signal processing capabilities of a NE in path 1821 computations. 1823 Input constraints: 1825 1. Permitted optical tributary signal classes: A list of optical 1826 tributary signal classes that can be processed by this network 1827 element or carried over this link. (configuration type) 1828 2. Acceptable FEC codes. (configuration type) 1829 3. Acceptable Bit Rate Set: a list of specific bit rates or bit rate 1830 ranges that the device can accommodate. Coarse bit rate info is 1831 included with the optical tributary signal class restrictions. 1832 4. Acceptable G-PID list: a list of G-PIDs corresponding to the 1833 "client" digital streams that is compatible with this device. 1835 Note that since the bit rate of the signal does not change over the 1836 LSP. This can be communicated as an LSP parameter and hence this 1837 information would be available for any NE that needs to use it for 1838 configuration. Hence it is not necessary to have "configuration type" 1839 for the NE with respect to bit rate. 1841 Output constraints: 1843 1. Output modulation: (a)same as input, (b) list of available types 1845 2. FEC options: (a) same as input, (b) list of available codes 1847 Processing capabilities: 1849 1. Regeneration: (a) 1R, (b) 2R, (c) 3R, (d)list of selectable 1850 regeneration types 1852 2. Fault and performance monitoring: (a) G-PID particular 1853 capabilities, (b) optical performance monitoring capabilities. 1855 Note that such parameters could be specified on an (a) Network 1856 element wide basis, (b) a per port basis, (c) on a per regenerator 1857 basis. Typically such information has been on a per port basis, see, 1858 the GMPLS interface switching capability descriptor [RFC4202]. 1860 6.2.2. Wavelength-Specific Availability Information 1862 For wavelength assignment it is necessary to know which specific 1863 wavelengths are available and which are occupied if a combined RWA 1864 process or separate WA process is run as discussed in sections 4.1.1. 1865 4.1.2. This is currently not possible with GMPLS routing. 1867 In the routing extensions for GMPLS [RFC4202], requirements for 1868 layer-specific TE attributes are discussed. RWA for optical networks 1869 without wavelength converters imposes an additional requirement for 1870 the lambda (or optical channel) layer: that of knowing which specific 1871 wavelengths are in use. Note that current DWDM systems range from 16 1872 channels to 128 channels with advanced laboratory systems with as 1873 many as 300 channels. Given these channel limitations and if the 1874 approach of a global wavelength to label mapping or furnishing the 1875 local mappings to the PCEs is taken then representing the use of 1876 wavelengths via a simple bit-map is feasible [GEN-Encode]. 1878 6.2.3. WSON Routing Information Summary 1880 The following table summarizes the WSON information that could be 1881 conveyed via GMPLS routing and attempts to classify that information 1882 as to its static or dynamic nature and whether that information would 1883 tend to be associated with either a link or a node. 1885 Information Static/Dynamic Node/Link 1886 ------------------------------------------------------------------ 1887 Connectivity matrix Static Node 1888 Per port wavelength restrictions Static Node(1) 1889 WDM link (fiber) lambda ranges Static Link 1890 WDM link channel spacing Static Link 1891 Optical transmitter range Static Link(2) 1892 Wavelength conversion capabilities Static(3) Node 1893 Maximum bandwidth per wavelength Static Link 1894 Wavelength availability Dynamic(4) Link 1895 Signal compatibility and processing Static/Dynamic Node 1897 Notes: 1899 1. These are the per port wavelength restrictions of an optical 1900 device such as a ROADM and are independent of any optical 1901 constraints imposed by a fiber link. 1903 2. This could also be viewed as a node capability. 1905 3. This could be dynamic in the case of a limited pool of converters 1906 where the number available can change with connection 1907 establishment. Note it may be desirable to include regeneration 1908 capabilities here since OEO converters are also regenerators. 1910 4. Not necessarily needed in the case of distributed wavelength 1911 assignment via signaling. 1913 While the full complement of the information from the previous table 1914 is needed in the Combined RWA and the separate Routing and WA 1915 architectures, in the case of Routing + distributed WA via signaling 1916 only the following information is needed: 1918 Information Static/Dynamic Node/Link 1919 ------------------------------------------------------------------ 1920 Connectivity matrix Static Node 1921 Wavelength conversion capabilities Static(3) Node 1923 Information models and compact encodings for this information is 1924 provided in [WSON-Info], [Gen-Encode] and [WSON-Encode]. 1926 6.3. Optical Path Computation and Implications for PCE 1928 As previously noted RWA can be computationally intensive. Such 1929 computationally intensive path computations and optimizations were 1930 part of the impetus for the PCE architecture [RFC4655]. 1932 The Path Computation Element Protocol (PCEP) defines the procedures 1933 necessary to support both sequential [RFC5440] and global concurrent 1934 path computations (PCE-GCO) [RFC5557], PCE is well positioned to 1935 support WSON-enabled RWA computation with some protocol enhancement. 1937 Implications for PCE generally fall into two main categories: (a) 1938 optical path constraints and characteristics, (b) computation 1939 architectures. 1941 6.3.1. Optical path Constraints and Characteristics 1943 For the varying degrees of optimization that may be encountered in a 1944 network the following models of bulk and sequential optical path 1945 requests are encountered: 1947 o Batch optimization, multiple optical paths requested at one time 1948 (PCE-GCO). 1950 o Optical path(s) and backup optical path(s) requested at one time 1951 (PCEP). 1953 o Single optical path requested at a time (PCEP). 1955 PCEP and PCE-GCO can be readily enhanced to support all of the 1956 potential models of RWA computation. 1958 Optical path constraints include: 1960 o Bidirectional Assignment of wavelengths. 1962 o Possible simultaneous assignment of wavelength to primary and 1963 backup paths. 1965 o Tuning range constraint on optical transmitter. 1967 6.3.2. Electro-Optical Element Signal Compatibility 1969 When requesting a path computation to PCE, the PCC should be able to 1970 indicate the following: 1972 o The G-PID type of an LSP. 1974 o The signal attributes at the transmitter (at the source): (i) 1975 modulation type; (ii) FEC type. 1977 o The signal attributes at the receiver (at the sink): (i) 1978 modulation type; (ii) FEC type. 1980 The PCE should be able to respond to the PCC with the following: 1982 o The conformity of the requested optical characteristics associated 1983 with the resulting LSP with the source, sink and NE along the LSP. 1985 o Additional LSP attributes modified along the path (e.g., 1986 modulation format change, etc.). 1988 6.3.3. Discovery of RWA Capable PCEs 1990 The algorithms and network information needed for RWA are somewhat 1991 specialized and computationally intensive hence not all PCEs within a 1992 domain would necessarily need or want this capability. Hence, it 1993 would be useful via the mechanisms being established for PCE 1994 discovery [RFC5088] to indicate that a PCE has the ability to deal 1995 with RWA. Reference [RFC5088] indicates that a sub-TLV could be 1996 allocated for this purpose. 1998 Recent progress on objective functions in PCE [RFC5541] would allow 1999 the operators to flexibly request differing objective functions per 2000 their need and applications. For instance, this would allow the 2001 operator to choose an objective function that minimizes the total 2002 network cost associated with setting up a set of paths concurrently. 2003 This would also allow operators to choose an objective function that 2004 results in a most evenly distributed link utilization. 2006 This implies that PCEP would easily accommodate wavelength selection 2007 algorithm in its objective function to be able to optimize the path 2008 computation from the perspective of wavelength assignment if chosen 2009 by the operators. 2011 7. Security Considerations 2013 This document has no requirement for a change to the security models 2014 within GMPLS and associated protocols. That is the OSPF-TE, RSVP-TE, 2015 and PCEP security models could be operated unchanged. 2017 However satisfying the requirements for RWA using the existing 2018 protocols may significantly affect the loading of those protocols. 2019 This may make the operation of the network more vulnerable to denial 2020 of service attacks. Therefore additional care maybe required to 2021 ensure that the protocols are secure in the WSON environment. 2023 Furthermore the additional information distributed in order to 2024 address RWA represents a disclosure of network capabilities that an 2025 operator may wish to keep private. Consideration should be given to 2026 securing this information. For a general discussion on MPLS and GMPLS 2027 related security issues, see the MPLS/GMPLS security framework 2028 [RFC5920]. 2030 8. IANA Considerations 2032 This document makes no request for IANA actions. 2034 9. Acknowledgments 2036 The authors would like to thank Adrian Farrel for many helpful 2037 comments that greatly improved the contents of this draft. 2039 This document was prepared using 2-Word-v2.0.template.dot. 2041 10. References 2043 10.1. Normative References 2045 [RFC3471] Berger, L., "Generalized Multi-Protocol Label Switching 2046 (GMPLS) Signaling Functional Description", RFC 3471, 2047 January 2003. 2049 [RFC3473] Berger, L., Ed., "Generalized Multi-Protocol Label 2050 Switching (GMPLS) Signaling Resource ReserVation Protocol- 2051 Traffic Engineering (RSVP-TE) Extensions", RFC 3473, 2052 January 2003. 2054 [RFC3945] Mannie, E. "Generalized Multi-Protocol Label Switching 2055 (GMPLS) Architecture", RFC 3945, October 2004. 2057 [RFC4202] Kompella, K. and Y. Rekhter, "Routing Extensions in Support 2058 of Generalized Multi-Protocol Label Switching (GMPLS)", RFC 2059 4202, October 2005. 2061 [RFC4328] Papadimitriou, D., "Generalized Multi-Protocol Label 2062 Switching (GMPLS) Signaling Extensions for G.709 Optical 2063 Transport Networks Control", RFC 4328, January 2006. 2065 [RFC4655] Farrel, A., Vasseur, JP., and Ash, J., "A Path Computation 2066 Element (PCE)-Based Architecture ", RFC 4655, August 2006. 2068 [RFC5088] J.L. Le Roux, J.P. Vasseur, Yuichi Ikejiri, and Raymond 2069 Zhang, "OSPF protocol extensions for Path Computation 2070 Element (PCE) Discovery", January 2008. 2072 [RFC5212] Shiomoto, K., Papadimitriou, D., Le Roux, JL., Vigoureux, 2073 M., and D. Brungard, "Requirements for GMPLS-Based Multi- 2074 Region and Multi-Layer Networks (MRN/MLN)", RFC 5212, July 2075 2008. 2077 [RFC5557] Y. Lee, J.L. Le Roux, D. King, and E. Oki, "Path 2078 Computation Element Communication Protocol (PCECP) 2079 Requirements and Protocol Extensions In Support of Global 2080 Concurrent Optimization", RFC 5557, July 2009. 2082 [RFC5420] Farrel, A., Ed., Papadimitriou, D., Vasseur, JP., and A. 2083 Ayyangarps, "Encoding of Attributes for MPLS LSP 2084 Establishment Using Resource Reservation Protocol Traffic 2085 Engineering (RSVP-TE)", RFC 5420, February 2009. 2087 [RFC5440] J.P. Vasseur and J.L. Le Roux (Editors), "Path Computation 2088 Element (PCE) Communication Protocol (PCEP)", RFC 5440, May 2089 2009. 2091 [RFC5541] J.L. Le Roux, J.P. Vasseur, and Y. Lee, "Encoding of 2092 Objective Functions in Path Computation Element (PCE) 2093 communication and discovery protocols", RFC 5541, July 2094 2009. 2096 10.2. Informative References 2098 [Gen-Encode] G. Bernstein, Y. Lee, D. Li, and W. Imajuku, "General 2099 Network Element Constraint Encoding for GMPLS Controlled 2100 Networks", draft-ietf-ccamp-general-constraint-encode, work 2101 in progress. 2103 [G.652] ITU-T Recommendation G.652, Characteristics of a single-mode 2104 optical fibre and cable, June 2005. 2106 [G.653] ITU-T Recommendation G.653, Characteristics of a dispersion- 2107 shifted single-mode optical fibre and cable, December 2006. 2109 [G.654] ITU-T Recommendation G.654, Characteristics of a cut-off 2110 shifted single-mode optical fibre and cable, December 2006. 2112 [G.655] ITU-T Recommendation G.655, Characteristics of a non-zero 2113 dispersion-shifted single-mode optical fibre and cable, 2114 March 2006. 2116 [G.656] ITU-T Recommendation G.656, Characteristics of a fibre and 2117 cable with non-zero dispersion for wideband optical 2118 transport, December 2006. 2120 [G.671] ITU-T Recommendation G.671, Transmission characteristics of 2121 optical components and subsystems, January 2005. 2123 [G.694.1] ITU-T Recommendation G.694.1, "Spectral grids for WDM 2124 applications: DWDM frequency grid", June, 2002. 2126 [G.872] ITU-T Recommendation G.872, Architecture of optical 2127 transport networks, November 2001. 2129 [G.959.1] ITU-T Recommendation G.959.1, Optical Transport Network 2130 Physical Layer Interfaces, March 2006. 2132 [G.694.1] ITU-T Recommendation G.694.1, Spectral grids for WDM 2133 applications: DWDM frequency grid, June 2002. 2135 [G.694.2] ITU-T Recommendation G.694.2, Spectral grids for WDM 2136 applications: CWDM wavelength grid, December 2003. 2138 [G.Sup39] ITU-T Series G Supplement 39, Optical system design and 2139 engineering considerations, February 2006. 2141 [G.Sup43] ITU-T Series G Supplement 43, Transport of IEEE 10G base-R 2142 in optical transport networks (OTN), November 2006. 2144 [Imajuku] W. Imajuku, Y. Sone, I. Nishioka, S. Seno, "Routing 2145 Extensions to Support Network Elements with Switching 2146 Constraint", work in progress: draft-imajuku-ccamp-rtg- 2147 switching-constraint. 2149 [Otani] T. Otani, H. Guo, K. Miyazaki, D. Caviglia, "Generalized 2150 Labels of Lambda-Switching Capable Label Switching Routers 2151 (LSR)", work in progress: draft-ietf-ccamp-gmpls-g-694- 2152 lambda-labels, work in progress. 2154 [RFC5920] Fang, L., "Security Framework for MPLS and GMPLS 2155 Networks", RFC 5920, July 2010.[Otani]T. Otani, H. Guo, K. 2156 Miyazaki, D. Caviglia, "Generalized Labels of Lambda- 2157 Switching Capable Label Switching Routers (LSR)", work in 2158 progress: draft-otani-ccamp-gmpls-g-694-lambda-labels, work 2159 in progress. 2161 [WSON-Encode] G. Bernstein, Y. Lee, D. Li, and W. Imajuku, "Routing 2162 and Wavelength Assignment Information Encoding for 2163 Wavelength Switched Optical Networks", draft-ietf-ccamp- 2164 rwa-wson-encode, work in progress. 2166 [WSON-Imp] Y. Lee, G. Bernstein, D. Li, G. Martinelli, "A Framework 2167 for the Control of Wavelength Switched Optical Networks 2168 (WSON) with Impairments", draft-ietf-ccamp-wson- 2169 impairments, work in progress. 2171 [WSON-Info] Y. Lee, G. Bernstein, D. Li, W. Imajuku, "Routing and 2172 Wavelength Assignment Information for Wavelength Switched 2173 Optical Networks", draft-bernstein-ccamp-wson-info, work in 2174 progress 2176 11. Contributors 2178 Snigdho Bardalai 2179 Fujitsu 2181 Email: Snigdho.Bardalai@us.fujitsu.com 2183 Diego Caviglia 2184 Ericsson 2185 Via A. Negrone 1/A 16153 2186 Genoa Italy 2188 Phone: +39 010 600 3736 2189 Email: diego.caviglia@(marconi.com, ericsson.com) 2191 Daniel King 2192 Old Dog Consulting 2193 UK 2195 Email: daniel@olddog.co.uk 2197 Itaru Nishioka 2198 NEC Corp. 2199 1753 Simonumabe, Nakahara-ku 2200 Kawasaki, Kanagawa 211-8666 2201 Japan 2203 Phone: +81 44 396 3287 2204 Email: i-nishioka@cb.jp.nec.com 2206 Lyndon Ong 2207 Ciena 2209 Email: Lyong@Ciena.com 2211 Pierre Peloso 2212 Alcatel-Lucent 2213 Route de Villejust, 91620 Nozay 2214 France 2216 Email: pierre.peloso@alcatel-lucent.fr 2218 Jonathan Sadler 2219 Tellabs 2220 Email: Jonathan.Sadler@tellabs.com 2222 Dirk Schroetter 2223 Cisco 2224 Email: dschroet@cisco.com 2226 Jonas Martensson 2227 Acreo 2228 Electrum 236 2229 16440 Kista, Sweden 2231 Email:Jonas.Martensson@acreo.se 2233 Author's Addresses 2235 Greg M. Bernstein (ed.) 2236 Grotto Networking 2237 Fremont California, USA 2239 Phone: (510) 573-2237 2240 Email: gregb@grotto-networking.com 2242 Young Lee (ed.) 2243 Huawei Technologies 2244 1700 Alma Drive, Suite 100 2245 Plano, TX 75075 2246 USA 2248 Phone: (972) 509-5599 (x2240) 2249 Email: ylee@huawei.com 2251 Wataru Imajuku 2252 NTT Network Innovation Labs 2253 1-1 Hikari-no-oka, Yokosuka, Kanagawa 2254 Japan 2256 Phone: +81-(46) 859-4315 2257 Email: imajuku.wataru@lab.ntt.co.jp 2259 Intellectual Property Statement 2261 The IETF Trust takes no position regarding the validity or scope of 2262 any Intellectual Property Rights or other rights that might be 2263 claimed to pertain to the implementation or use of the technology 2264 described in any IETF Document or the extent to which any license 2265 under such rights might or might not be available; nor does it 2266 represent that it has made any independent effort to identify any 2267 such rights. 2269 Copies of Intellectual Property disclosures made to the IETF 2270 Secretariat and any assurances of licenses to be made available, or 2271 the result of an attempt made to obtain a general license or 2272 permission for the use of such proprietary rights by implementers or 2273 users of this specification can be obtained from the IETF on-line IPR 2274 repository at http://www.ietf.org/ipr 2276 The IETF invites any interested party to bring to its attention any 2277 copyrights, patents or patent applications, or other proprietary 2278 rights that may cover technology that may be required to implement 2279 any standard or specification contained in an IETF Document. Please 2280 address the information to the IETF at ietf-ipr@ietf.org. 2282 Disclaimer of Validity 2284 All IETF Documents and the information contained therein are provided 2285 on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE 2286 REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE 2287 IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL 2288 WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY 2289 WARRANTY THAT THE USE OF THE INFORMATION THEREIN WILL NOT INFRINGE 2290 ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS 2291 FOR A PARTICULAR PURPOSE. 2293 Acknowledgment 2295 Funding for the RFC Editor function is currently provided by the 2296 Internet Society.