idnits 2.17.1 draft-ietf-ccamp-rwa-wson-encode-15.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 (August 8, 2012) is 4279 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'ITU-G.698.1' is mentioned on line 749, but not defined == Missing Reference: 'ITU-G.698.2' is mentioned on line 751, but not defined == Missing Reference: 'ITU-G.959.1' is mentioned on line 753, but not defined == Unused Reference: 'RFC2578' is defined on line 1100, but no explicit reference was found in the text == Unused Reference: 'G.694.1' is defined on line 1117, but no explicit reference was found in the text == Unused Reference: 'G.694.2' is defined on line 1120, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'G.694.1' 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 G. Bernstein 2 Internet Draft Grotto Networking 3 Intended status: Standards Track Y. Lee 4 Expires: February 2013 D. Li 5 Huawei 6 W. Imajuku 7 NTT 9 August 8, 2012 11 Routing and Wavelength Assignment Information Encoding for 12 Wavelength Switched Optical Networks 14 draft-ietf-ccamp-rwa-wson-encode-15.txt 16 Status of this Memo 18 This Internet-Draft is submitted to IETF in full conformance with 19 the provisions of BCP 78 and BCP 79. 21 Internet-Drafts are working documents of the Internet Engineering 22 Task Force (IETF), its areas, and its working groups. Note that 23 other groups may also distribute working documents as Internet- 24 Drafts. 26 Internet-Drafts are draft documents valid for a maximum of six 27 months and may be updated, replaced, or obsoleted by other documents 28 at any time. It is inappropriate to use Internet-Drafts as 29 reference material or to cite them other than as "work in progress." 31 The list of current Internet-Drafts can be accessed at 32 http://www.ietf.org/ietf/1id-abstracts.txt 34 The list of Internet-Draft Shadow Directories can be accessed at 35 http://www.ietf.org/shadow.html 37 This Internet-Draft will expire on February 8, 2013. 39 Copyright Notice 41 Copyright (c) 2012 IETF Trust and the persons identified as the 42 document authors. All rights reserved. 44 This document is subject to BCP 78 and the IETF Trust's Legal 45 Provisions Relating to IETF Documents 46 (http://trustee.ietf.org/license-info) in effect on the date of 47 publication of this document. Please review these documents 48 carefully, as they describe your rights and restrictions with 49 respect to this document. Code Components extracted from this 50 document must include Simplified BSD License text as described in 51 Section 4.e of the Trust Legal Provisions and are provided without 52 warranty as described in the Simplified BSD License. 54 Abstract 56 A wavelength switched optical network (WSON) requires that certain 57 key information elements are made available to facilitate path 58 computation and the establishment of label switching paths (LSPs). 59 The information model described in "Routing and Wavelength 60 Assignment Information for Wavelength Switched Optical Networks" 61 shows what information is required at specific points in the WSON. 62 Part of the WSON information model contains aspects that may be of 63 general applicability to other technologies, while other parts are 64 fairly specific to WSONs. 66 This document provides efficient, protocol-agnostic encodings for 67 the WSON specific information elements. It is intended that 68 protocol-specific documents will reference this memo to describe how 69 information is carried for specific uses. Such encodings can be used 70 to extend GMPLS signaling and routing protocols. In addition these 71 encodings could be used by other mechanisms to convey this same 72 information to a path computation element (PCE). 74 Conventions used in this document 76 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 77 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 78 document are to be interpreted as described in RFC-2119 [RFC2119]. 80 Table of Contents 82 1. Introduction...................................................3 83 1.1. Revision History..........................................4 84 1.1.1. Changes from 00 draft................................4 85 1.1.2. Changes from 01 draft................................5 86 1.1.3. Changes from 02 draft................................5 87 1.1.4. Changes from 03 draft................................5 88 1.1.5. Changes from 04 draft................................5 89 1.1.6. Changes from 05 draft................................5 90 1.1.7. Changes from 06 draft................................5 91 1.1.8. Changes from 07 draft................................5 92 1.1.9. Changes from 08 draft................................6 93 1.1.10. Changes from 09 draft...............................6 94 1.1.11. Changes from 10 draft...............................6 95 1.1.12. Changes from 11 draft...............................6 96 1.1.13. Changes from 12 draft...............................6 97 1.1.14. Changes from 13 draft...............................6 98 1.1.15. Changes from 14 draft...............................7 99 2. Terminology....................................................7 100 3. Resources, Blocks, Sets, and the Resource Pool.................7 101 3.1. Resource Block Set Field..................................8 102 4. Resource Pool Accessibility/Availability......................10 103 4.1. Resource Pool Accessibility Sub-TLV......................10 104 4.2. Resource Block Wavelength Constraints Sub-TLV............12 105 4.3. Resource Pool State Sub-TLV..............................14 106 4.4. Block Shared Access Wavelength Availability sub-TLV......15 107 5. Resource Properties Encoding..................................16 108 5.1. Resource Block Information Sub-TLV.......................17 109 5.2. Optical Interface Class List(s) Sub-Sub-TLV..............17 110 5.2.1. Optical Interface Class Format......................18 111 5.3. Input Client Signal List Sub-Sub-TLV.....................19 112 5.4. Processing Capability List Sub-Sub-TLV...................20 113 5.4.1. Processing Capabilities Field.......................20 114 6. Security Considerations.......................................22 115 7. IANA Considerations...........................................22 116 8. Acknowledgments...............................................22 117 APPENDIX A: Encoding Examples....................................23 118 A.1. Wavelength Converter Accessibility Sub-TLV...............23 119 A.2. Wavelength Conversion Range Sub-TLV......................25 120 A.3. An OEO Switch with DWDM Optics...........................25 121 9. References....................................................28 122 9.1. Normative References.....................................28 123 9.2. Informative References...................................28 124 10. Contributors.................................................30 125 Authors' Addresses...............................................31 126 Intellectual Property Statement..................................32 127 Disclaimer of Validity...........................................32 129 1. Introduction 131 A Wavelength Switched Optical Network (WSON) is a Wavelength 132 Division Multiplexing (WDM) optical network in which switching is 133 performed selectively based on the center wavelength of an optical 134 signal. 136 [RFC6163] describes a framework for Generalized Multiprotocol Label 137 Switching (GMPLS) and Path Computation Element (PCE) control of a 138 WSON. Based on this framework, [WSON-Info] describes an information 139 model that specifies what information is needed at various points in 140 a WSON in order to compute paths and establish Label Switched Paths 141 (LSPs). 143 This document provides efficient encodings of information needed by 144 the routing and wavelength assignment (RWA) process in a WSON. Such 145 encodings can be used to extend GMPLS signaling and routing 146 protocols. In addition these encodings could be used by other 147 mechanisms to convey this same information to a path computation 148 element (PCE). Note that since these encodings are relatively 149 efficient they can provide more accurate analysis of the control 150 plane communications/processing load for WSONs looking to utilize a 151 GMPLS control plane. 153 Note that encodings of information needed by the routing and label 154 assignment process applicable to general networks beyond WSON are 155 addressed in a separate document [Gen-Encode]. This document makes 156 use of the Label Set Field encoding of [Gen-Encode] and refers to it 157 as a Wavelength Set Field. 159 1.1. Revision History 161 1.1.1. Changes from 00 draft 163 Edits to make consistent with update to [RFC6205], i.e., removal of 164 sign bit. 166 Clarification of TBD on connection matrix type and possibly 167 numbering. 169 New sections for wavelength converter pool encoding: Wavelength 170 Converter Set Sub-TLV, Wavelength Converter Accessibility Sub-TLV, 171 Wavelength Conversion Range Sub-TLV, WC Usage State Sub-TLV. 173 Added optional wavelength converter pool TLVs to the composite node 174 TLV. 176 1.1.2. Changes from 01 draft 178 The encoding examples have been moved to an appendix. Classified and 179 corrected information elements as either reusable fields or sub- 180 TLVs. Updated Port Wavelength Restriction sub-TLV. Added available 181 wavelength and shared backup wavelength sub-TLVs. Changed the title 182 and scope of section 6 to recommendations since the higher level 183 TLVs that this encoding will be used in is somewhat protocol 184 specific. 186 1.1.3. Changes from 02 draft 188 Removed inconsistent text concerning link local identifiers and the 189 link set field. 191 Added E bit to the Wavelength Converter Set Field. 193 Added bidirectional connectivity matrix example. Added simple link 194 set example. Edited examples for consistency. 196 1.1.4. Changes from 03 draft 198 Removed encodings for general concepts to [Gen-Encode]. 200 Added in WSON signal compatibility and processing capability 201 information encoding. 203 1.1.5. Changes from 04 draft 205 Added encodings to deal with access to resource blocks via shared 206 fiber. 208 1.1.6. Changes from 05 draft 210 Revised the encoding for the "shared access" indicators to only use 211 one bit each for input and output. 213 1.1.7. Changes from 06 draft 215 Removed section on "WSON Encoding Usage Recommendations" 217 1.1.8. Changes from 07 draft 219 Section 3: Enhanced text to clarify relationship between pools, 220 blocks and resources. Section 3.1, 3.2: Change title to clarify 221 Pool-Block relationship. Section 3.3: clarify block-resource state. 223 Section 4: Deleted reference to previously removed RBNF element. 224 Fixed TLV figures and descriptions for consistent sub-sub-TLV 225 nomenclature. 227 1.1.9. Changes from 08 draft 229 Fixed ordering of fields in second half of sub-TLV example in 230 Appendix A.1. 232 Clarifying edits in section 3 on pools, blocks, and resources. 234 1.1.10. Changes from 09 draft 236 Fixed the "Block Shared Access Wavelength Availability sub-TLV" of 237 section 3.4 to use an "RB set field" rather than a single RB ID. 238 Removed all 1st person idioms. 240 1.1.11. Changes from 10 draft 242 Removed remaining 1st person idioms. Updated IANA section. Update 243 references for newly issued RFCs. 245 1.1.12. Changes from 11 draft 247 Fixed length fields in section 4 to be 16 bits, correcting errors in 248 TLV and field figures. Added a separate section on resources, 249 blocks, sets and the resource pool. Moved definition of the resource 250 block set field to this new section. 252 1.1.13. Changes from 12 draft 254 Replaced all instances of "ingress" with "input" and all instances 255 of "egress" with "output". 257 1.1.14. Changes from 13 draft 259 C bit of Resource Block Set Field is redundant and was removed, 260 i.e., has been returned to "Reserved" block and appendix examples 261 were updated to reflect the change. 263 Enhanced section 4.2 encoding to allow for optionality of input or 264 output wavelength set fields. 266 Clarified that wavelength set fields use the Label Set field 267 encoding from [Gen-Encode]. 269 Enhanced section 5.1 encoding to simplify the Modulation and FEC 270 input and output cases. 272 1.1.15. Changes from 14 draft 274 OIC changes per workgroup request. Removed FEC type and modulation 275 type. Fixed versioning error and return RB identifiers to 32 bits. 277 2. Terminology 279 CWDM: Coarse Wavelength Division Multiplexing. 281 DWDM: Dense Wavelength Division Multiplexing. 283 FOADM: Fixed Optical Add/Drop Multiplexer. 285 ROADM: Reconfigurable Optical Add/Drop Multiplexer. A reduced port 286 count wavelength selective switching element featuring input and 287 output line side ports as well as add/drop side ports. 289 RWA: Routing and Wavelength Assignment. 291 Wavelength Conversion. The process of converting an information 292 bearing optical signal centered at a given wavelength to one with 293 "equivalent" content centered at a different wavelength. Wavelength 294 conversion can be implemented via an optical-electronic-optical 295 (OEO) process or via a strictly optical process. 297 WDM: Wavelength Division Multiplexing. 299 Wavelength Switched Optical Network (WSON): A WDM based optical 300 network in which switching is performed selectively based on the 301 center wavelength of an optical signal. 303 3. Resources, Blocks, Sets, and the Resource Pool 305 The optical system to be encoded may contain a pool of resources of 306 different types and properties for processing optical signals. For 307 the purposes here a "resource" is an individual entity such as a 308 wavelength converter or regenerator within the optical node that 309 acts on an individual wavelength signal. 311 Since resources tend to be packaged together in blocks of similar 312 devices, e.g., on line cards or other types of modules, the 313 fundamental unit of identifiable resource in this document is the 314 "resource block". A resource block may contain one or more 315 resources. As resource blocks are the smallest identifiable unit of 316 processing resource, one should group together resources into blocks 317 if they have similar characteristics relevant to the optical system 318 being modeled, e.g., processing properties, accessibility, etc. 320 This document defines the following sub-TLVs pertaining to resources 321 within an optical node: 323 . Resource Pool Accessibility Sub-TLV 325 . Resource Block Wavelength Constraints Sub-TLV 327 . Resource Pool State Sub-TLV 329 . Block Shared Access Wavelength Availability Sub-TLV 331 . Resource Block Information Sub-TLV 333 Each of these sub-TLVs works with one or more sets of resources 334 rather than just a single resource block. This motivates the 335 following field definition. 337 3.1. Resource Block Set Field 339 In a WSON node that includes resource blocks (RB), denoting subsets 340 of these blocks allows one to efficiently describe common properties 341 of the blocks and to describe the structure and characteristics, if 342 non-trivial, of the resource pool. The RB Set field is defined in a 343 similar manner to the label set concept of [RFC3471]. 345 The information carried in a RB set field is defined by: 347 0 1 2 3 348 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 349 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 350 | Action |C| Reserved | Length | 351 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 352 | RB Identifier 1 | 353 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 354 : : : 355 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 356 | RB Identifier n | 357 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 359 Action: 8 bits 361 0 - Inclusive List 363 Indicates that the TLV contains one or more RB elements that are 364 included in the list. 366 2 - Inclusive Range(s) 368 Indicates that the TLV contains one or more ranges of RBs. Each 369 individual range is denoted by two 16 bit RB identifiers in a 32 bit 370 word. The first 16 bits is the RB identifier for the start of the 371 range and the next 16 bits is the RB identifier for the end of the 372 range. Note that the Length field is used to determine the number of 373 ranges. 375 C (Connectivity bit): Set to 0 to denote fixed (possibly multi- 376 cast) connectivity; Set to 1 to denote potential (switched) 377 connectivity. Used in resource pool accessibility sub-TLV. Ignored 378 elsewhere. 380 Reserved: 7 bits 382 This field is reserved. It MUST be set to zero on transmission and 383 MUST be ignored on receipt. 385 Length: 16 bits 387 The total length of this field in bytes. 389 RB Identifier: 391 The RB identifier represents the ID of the resource block which is a 392 16 bit integer. 394 Usage Note: the inclusive range "Action" can result in very compact 395 encoding of resource sets and it can be advantages to number 396 resource blocks in such a way so that status updates (dynamic 397 information) can take advantage of this efficiency. 399 4. Resource Pool Accessibility/Availability 401 This section defines the sub-TLVs for dealing with accessibility and 402 availability of resource blocks within a pool of resources. These 403 include the ResourceBlockAccessibility, ResourceWaveConstraints, and 404 RBPoolState sub-TLVs. 406 4.1. Resource Pool Accessibility Sub-TLV 408 This sub-TLV describes the structure of the resource pool in 409 relation to the switching device. In particular it indicates the 410 ability of an input port to reach sets of resources and of a sets of 411 resources to reach a particular output port. This is the 412 PoolInputMatrix and PoolOutputMatrix of [WSON-Info]. 414 The resource pool accessibility sub-TLV is defined by: 416 0 1 2 3 417 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 418 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 419 | Connectivity | Reserved | 420 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 421 | Input Link Set Field A #1 | 422 : : 423 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 424 | RB Set Field A #1 | 425 : : 426 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 427 | Additional Link set and RB set pairs as needed to | 428 : specify PoolInputMatrix : 429 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 430 | Output Link Set Field B #1 | 431 : : 432 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 433 | RB Set B Field #1 (for output connectivity) | 434 : : 435 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 436 | Additional Link Set and RB set pairs as needed to | 437 : specify PoolOutputMatrix : 438 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 440 Where 442 Connectivity indicates how the input/output ports connect to the 443 resource blocks. 445 0 -- the device is fixed (e.g., a connected port must go 446 through the resource block) 448 1 -- the device is switched (e.g., a port can be configured to 449 go through a resource but isn't required) 451 The For the Input and Output Link Set Fields, the Link Set Field 452 encoding defined in [Gen-Encode] is to be used. 454 Note that the direction parameter within the Link Set Field is used 455 to indicate whether the link set is an input or output link set, and 456 the bidirectional value for this parameter is not permitted in this 457 sub-TLV. 459 See Appendix A.1 for an illustration of this encoding. 461 4.2. Resource Block Wavelength Constraints Sub-TLV 463 Resources, such as wavelength converters, etc., may have a limited 464 input or output wavelength ranges. Additionally, due to the 465 structure of the optical system not all wavelengths can necessarily 466 reach or leave all the resources. These properties are described by 467 using one or more resource wavelength restrictions sub-TLVs as 468 defined below: 470 0 1 2 3 471 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 472 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 473 |I|O|B| Reserved | 474 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 475 | RB Set Field | 476 : : 477 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 478 | Input Wavelength Set Field | 479 : : 480 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 481 | Output Wavelength Set Field | 482 : : 483 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 485 I = 1 or 0 indicates the presence or absence of the Input Wavelength 486 Set Field. 488 O = 1 or 0 indicates the presence or absence of the Output 489 Wavelength Set Field. 491 B = 1 indicates that a single wavelength set field represents both 492 input and output wavelength constraints. 494 Currently the only valid combinations of (I,O,B) are (1,0,0), 495 (0,1,0), (1,1,0), (0,0,1). 497 RB Set Field: 499 A set of resource blocks (RBs) which have the same wavelength 500 restrictions. 502 Input Wavelength Set Field: 504 Indicates the wavelength input restrictions of the RBs in the 505 corresponding RB set. This field is encoded via the Label Set field 506 of [Gen-Encode]. 508 Output Wavelength Set Field: 510 Indicates the wavelength output restrictions of RBs in the 511 corresponding RB set. This field is encoded via the Label Set field 512 of [Gen-Encode]. 514 4.3. Resource Pool State Sub-TLV 516 The state of the pool is given by the number of resources available 517 with particular characteristics. A resource block set is used to 518 encode all or a subset of the resources of interest. The usage state 519 of resources within a resource block set is encoded as either a list 520 of 16 bit integer values or a bit map indicating whether a single 521 resource is available or in use. The bit map encoding is appropriate 522 when resource blocks consist of a single resource. This information 523 can be relatively dynamic, i.e., can change when a connection (LSP 524 is established or torn down. 526 0 1 2 3 527 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 528 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 529 | Action | Reserved | 530 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 531 | RB Set Field | 532 : : 533 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 534 | RB Usage state | 535 : : 536 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 538 Where Action = 0 denotes a list of 16 bit integers and Action = 1 539 denotes a bit map. In both cases the elements of the RB Set field 540 are in a one-to-one correspondence with the values in the usage RB 541 usage state area. 543 0 1 2 3 544 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 545 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 546 | Action = 0 | Reserved | 547 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 548 | RB Set Field | 549 : : 550 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 551 | RB#1 state | RB#2 state | 552 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 553 : : 554 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 555 | RB#n-1 state | RB#n state or Padding | 556 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 558 Whether the last 16 bits is a wavelength converter (RB) state or 559 padding is determined by the number of elements in the RB set field. 561 0 1 2 3 562 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 563 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 564 | Action = 1 | Reserved | 565 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 566 | RB Set Field | 567 : : 568 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 569 | RB Usage state bitmap | 570 : : 571 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 572 | ...... | Padding bits | 573 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 575 RB Usage state: Variable Length but must be a multiple of 4 byes. 577 Each bit indicates the usage status of one RB with 0 indicating the 578 RB is available and 1 indicating the RB is in used. The sequence of 579 the bit map is ordered according to the RB Set field with this sub- 580 TLV. 582 Padding bits: Variable Length 584 4.4. Block Shared Access Wavelength Availability sub-TLV 586 Resources blocks may be accessed via a shared fiber. If this is the 587 case, then wavelength availability on these shared fibers is needed 588 to understand resource availability. 590 0 1 2 3 591 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 592 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 593 |I|E| Reserved | 594 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 595 | RB Set Field | 596 : : 597 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 598 | Input Available Wavelength Set Field | 599 : (Optional) : 600 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 601 | Output Available Wavelength Set Field | 602 : (Optional) : 603 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 604 I bit: 606 Indicates whether the input available wavelength set field is 607 included (1) or not (0). 609 E bit: 611 Indicates whether the output available wavelength set field is 612 included (1) or not (0). 614 RB Set Field: 616 A Resource Block set in which all the members share the same input 617 or output fiber or both. 619 Input Available Wavelength Set Field: 621 Indicates the wavelengths currently available (not being used) on 622 the input fiber to this resource block. This field is encoded via 623 the Label Set field of [Gen-Encode]. 625 Output Available Wavelength Set Field: 627 Indicates the wavelengths currently available (not being used) on 628 the output fiber from this resource block. This field is encoded via 629 the Label Set field of [Gen-Encode]. 631 5. Resource Properties Encoding 633 Within a WSON network element (NE) there may be resources with 634 signal compatibility constraints. These resources be regenerators, 635 wavelength converters, etc... Such resources may also constitute the 636 network element as a whole as in the case of an electro optical 637 switch. This section primarily focuses on the signal compatibility 638 and processing properties of such a resource block. 640 The fundamental properties of a resource block, such as a 641 regenerator or wavelength converter, are: 643 (a) Input constraints (shared input, modulation, FEC, bit rate, 644 GPID) 646 (b) Processing capabilities (number of resources in a block, 647 regeneration, performance monitoring, vendor specific) 649 (c) Output Constraints (shared output, modulation, FEC) 651 5.1. Resource Block Information Sub-TLV 653 Resource Block descriptor sub-TLVs are used to convey relatively 654 static information about individual resource blocks including the 655 resource block compatibility properties, processing properties, and 656 the number of resources in a block. 658 This sub-TLV has the following format: 660 0 1 2 3 661 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 662 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 663 | RB Set Field | 664 : : 665 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 666 |I|E| Reserved | 667 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 668 | Optical Interface Class List(s) Sub-Sub-TLV (opt) | 669 : : 670 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 671 | Input Client Signal Type Sub-Sub-TLV (opt) | 672 : : 673 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 674 | Input Bit Rate Range List Sub-Sub-TLV (opt) | 675 : : 676 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 677 | Processing Capabilities List Sub-Sub-TLV (opt) | 678 : : 679 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 681 Where I and E, the shared input/output indicator, is set to 1 if the 682 resource blocks identified in the RB set field utilized a shared 683 fiber for input/output access and set to 0 otherwise. 685 5.2. Optical Interface Class List(s) Sub-Sub-TLV 687 The list of Optical Interface Class sub-sub-TLV has the following 688 format: 690 0 1 2 3 691 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 692 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 693 | Type | Length | Reserved |I|E| 694 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 695 | Optical Interface Classes | 696 : : 697 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 699 The following I and E combination are defined: 701 I E 703 0 0 Invalid 705 1 0 Optical Interface Class List acceptable in input 707 0 1 Optical Interface Class List available in output 709 1 1 Optical Interface Class List available on both input and 710 output. 712 The Resource Block MAY contain one or more lists according to 713 input/output flags. The Optical Interface Class format is defined 714 within [x-ref-tbd]. 716 5.2.1. Optical Interface Class Format 718 0 1 2 3 719 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 720 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 721 |S| Reserved | OI Code Points | 722 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 723 | Optical Interface Class | 724 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 725 | Optical Interface Class (Cont.) | 726 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 728 Where the first 32 bits of the encoding shall be used to identify 729 the semantic of the Optical Interface Class in the following way: 731 S Standard bit. 733 S=0, identify not ITU code points 735 S=1, identify ITU application codes 737 With S=0, the OI Code Points field can take the following 738 values: 740 0: reserved 742 1: Vendor Specific Optical Interface Class. 744 With S=1, the OI Code Points field can take the following 745 values: 747 0: reserved 749 1: [ITU-G.698.1] application code. 751 2: [ITU-G.698.2] application code. 753 3: [ITU-G.959.1] application code. 755 In case of ITU Application Code, there should be a mapping between 756 the string defining the application code and the 64 bits number 757 implementing the optical interface class. 759 5.3. Input Client Signal List Sub-Sub-TLV 761 This sub-sub-TLV contains a list of acceptable input client signal 762 types. 764 Type := Input Client Signal List 766 Value := A list of GPIDs 768 The acceptable client signal list sub-TLV is a list of Generalized 769 Protocol Identifiers (GPIDs). GPIDs are assigned by IANA and many 770 are defined in [RFC3471] and [RFC4328]. 772 0 1 2 3 773 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 774 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 775 | Number of GPIDs | GPID #1 | 776 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 777 : | : 778 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 779 | GPID #N | | 780 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 782 Where the number of GPIDs is an integer greater than or equal to 783 one. 785 5.4. Processing Capability List Sub-Sub-TLV 787 This sub-sub-TLV contains a list of resource processing 788 capabilities. 790 Type := Processing Capabilities List 792 Value := A list of Processing Capabilities Fields 794 The processing capability list sub-sub-TLV is a list of capabilities 795 that can be achieved through the referred resources:: 797 1. Regeneration capability 799 2. Fault and performance monitoring 801 3. Vendor Specific capability 803 Note that the code points for Fault and performance monitoring and 804 vendor specific capability are subject to further study. 806 5.4.1. Processing Capabilities Field 808 The processing capability field is then given by: 810 0 1 2 3 811 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 812 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 813 | Processing Cap ID | Length | 814 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 815 | Possible additional capability parameters depending upon | 816 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 817 : the processing ID : 818 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 820 When the processing Cap ID is "regeneration capability", the 821 following additional capability parameters are provided in the sub- 822 TLV: 824 0 1 2 3 825 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 826 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 827 | T | C | Reserved | 828 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 830 Where T bit indicates the type of regenerator: 832 T=0: Reserved 834 T=1: 1R Regenerator 836 T=2: 2R Regenerator 838 T=3: 3R Regenerator 840 Where C bit indicates the capability of regenerator: 842 C=0: Reserved 844 C=1: Fixed Regeneration Point 846 C=2: Selective Regeneration Point 848 Note that when the capability of regenerator is indicated to be 849 Selective Regeneration Pools, regeneration pool properties such as 850 input and output restrictions and availability need to be specified. 851 This encoding is to be determined in the later revision. 853 6. Security Considerations 855 This document defines protocol-independent encodings for WSON 856 information and does not introduce any security issues. 858 However, other documents that make use of these encodings within 859 protocol extensions need to consider the issues and risks associated 860 with, inspection, interception, modification, or spoofing of any of 861 this information. It is expected that any such documents will 862 describe the necessary security measures to provide adequate 863 protection. 865 7. IANA Considerations 867 This document provides general protocol independent information 868 encodings. There is no IANA allocation request for the TLVs defined 869 in this document. IANA allocation requests will be addressed in 870 protocol specific documents based on the encodings defined here. 872 8. Acknowledgments 874 This document was prepared using 2-Word-v2.0.template.dot. 876 APPENDIX A: Encoding Examples 878 A.1. Wavelength Converter Accessibility Sub-TLV 880 Example: 882 Figure 1 shows a wavelength converter pool architecture know as 883 "shared per fiber". In this case the input and output pool matrices 884 are simply: 886 +-----+ +-----+ 887 | 1 1 | | 1 0 | 888 WI =| |, WE =| | 889 | 1 1 | | 0 1 | 890 +-----+ +-----+ 892 +-----------+ +------+ 893 | |--------------------->| | 894 | |--------------------->| C | 895 /| | |--------------------->| o | 896 /D+--->| |--------------------->| m | 897 + e+--->| | | b 898 |========> 899 ========>| M| | Optical | +-----------+ | i | Port E1 900 Port I1 + u+--->| Switch | | WC Pool | | n | 901 \x+--->| | | +-----+ | | e | 902 \| | +----+->|WC #1|--+---->| r | 903 | | | +-----+ | +------+ 904 | | | | +------+ 905 /| | | | +-----+ | | | 906 /D+--->| +----+->|WC #2|--+---->| C | 907 + e+--->| | | +-----+ | | o | 908 ========>| M| | | +-----------+ | m 909 |========> 910 Port I2 + u+--->| | | b | Port E2 911 \x+--->| |--------------------->| i | 912 \| | |--------------------->| n | 913 | |--------------------->| e | 914 | |--------------------->| r | 915 +-----------+ +------+ 916 Figure 1 An optical switch featuring a shared per fiber wavelength 917 converter pool architecture. 919 This wavelength converter pool can be encoded as follows: 921 0 1 2 3 922 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 923 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 924 | Connectivity=1| Reserved | 925 Note: I1,I2 can connect to either WC1 or WC2 926 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 927 | Action=0 |0| Reserved | Length = 12 | 928 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 929 | Link Local Identifier = #1 | 930 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 931 | Link Local Identifier = #2 | 932 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 933 | Action=0 |1| Reserved | Length = 8 | 934 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 935 | RB ID = #1 | RB ID = #2 | 936 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 937 Note: WC1 can only connect to E1 938 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 939 | Action=0 |1| Reserved | Length = 8 | 940 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 941 | Link Local Identifier = #1 | 942 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 943 | Action=0 |0| Reserved | Length = 8 | 944 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 945 | RB ID = #1 | zero padding | 946 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 947 Note: WC2 can only connect to E2 948 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 949 | Action=0 |1| Reserved | Length = 8 | 950 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 951 | Link Local Identifier = #2 | 952 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 953 | Action=0 |0| | Length = 8 | 954 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 955 | RB ID = #2 | zero padding | 956 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 958 A.2. Wavelength Conversion Range Sub-TLV 960 Example: 962 This example, based on figure 1, shows how to represent the 963 wavelength conversion range of wavelength converters. Suppose the 964 wavelength range of input and output of WC1 and WC2 are {L1, L2, L3, 965 L4}: 967 0 1 2 3 968 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 969 Note: WC Set 970 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 971 | Action=0 |1| Reserved | Length = 8 | 972 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 973 | WC ID = #1 | WC ID = #2 | 974 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 975 Note: wavelength input range 976 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 977 | 2 | Num Wavelengths = 4 | Length = 8 | 978 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 979 |Grid | C.S. | Reserved | n for lowest frequency = 1 | 980 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 981 Note: wavelength output range 982 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 983 | 2 | Num Wavelengths = 4 | Length = 8 | 984 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 985 |Grid | C.S. | Reserved | n for lowest frequency = 1 | 986 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 988 A.3. An OEO Switch with DWDM Optics 990 Figure 2 shows an electronic switch fabric surrounded by DWDM 991 optics. In this example the electronic fabric can handle either 992 G.709 or SDH signals only (2.5 or 10 Gbps). To describe this node, 993 the following information is needed: 995 ::= [Other GMPLS sub- 996 TLVs][...] [][] 998 In this case there is complete port to port connectivity so the 999 is not required. In addition since there are 1000 sufficient ports to handle all wavelength signals the 1001 element is not needed. 1003 Hence the attention will be focused on the sub-TLV: 1005 ::= 1006 [...][...] 1009 /| +-----------+ +-------------+ +------+ 1010 /D+--->| +--->|Tunable Laser|-->| | 1011 + e+--->| | +-------------+ | C | 1012 ========>| M| | | ... | o 1013 |========> 1014 Port I1 + u+--->| | +-------------+ | m | Port E1 1015 \x+--->| |--->|Tunable Laser|-->| b | 1016 \| | Electric | +-------------+ +------+ 1017 | Switch | 1018 /| | | +-------------+ +------+ 1019 /D+--->| +--->|Tunable Laser|-->| | 1020 + e+--->| | +-------------+ | C | 1021 ========>| M| | | ... | o 1022 |========> 1023 Port I2 + u+--->| | +-------------+ | m | Port E2 1024 \x+--->| +--->|Tunable Laser|-->| b | 1025 \| | | +-------------+ +------+ 1026 | | 1027 /| | | +-------------+ +------+ 1028 /D+--->| |--->|Tunable Laser|-->| | 1029 + e+--->| | +-------------+ | C | 1030 ========>| M| | | ... | o 1031 |========> 1032 Port I3 + u+--->| | +-------------+ | m | Port E3 1033 \x+--->| |--->|Tunable Laser|-->| b | 1034 \| +-----------+ +-------------+ +------+ 1036 Figure 2 An optical switch built around an electronic switching 1037 fabric. 1039 The resource block information will tell us about the processing 1040 constraints of the receivers, transmitters and the electronic 1041 switch. The resource availability information, although very simple, 1042 tells us that all signals must traverse the electronic fabric (fixed 1043 connectivity). The resource wavelength constraints are not needed 1044 since there are no special wavelength constraints for the resources 1045 that would not appear as port/wavelength constraints. 1047 : 1049 0 1 2 3 1050 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 1051 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1052 | RB Set Field | 1053 : (only one resource block in this example with shared | 1054 | input/output case) | 1055 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1056 |0|1|1| Reserved | 1057 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1058 | Modulation Type List Sub-Sub-TLV | 1059 : NRZ : 1060 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1061 | FEC Type List Sub-Sub-TLV | 1062 : Standard SDH, G.709 FEC : 1063 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1064 | Input Client Signal Type Sub-TLV | 1065 : (GPIDs for SDH and G.709) : 1066 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1067 | Input Bit Rate Range List Sub-Sub-TLV | 1068 : (2.5Gbps, 10Gbps) : 1069 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1070 | Processing Capabilities List Sub-Sub-TLV | 1071 : Fixed (non optional) 3R regeneration : 1072 : : 1073 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1075 Since there is fixed connectivity to resource blocks (the electronic 1076 switch) the is: 1078 0 1 2 3 1079 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 1080 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1081 | Connectivity=0|Reserved | 1082 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1083 | Input Link Set Field A #1 | 1084 : (All input links connect to resource) : 1085 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1086 | RB Set Field A #1 | 1087 : (trivial set only one resource block) : 1088 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1089 | Output Link Set Field B #1 | 1090 : (All output links connect to resource) : 1091 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1093 9. References 1095 9.1. Normative References 1097 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1098 Requirement Levels", BCP 14, RFC 2119, March 1997. 1100 [RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 1101 "Structure of Management Information Version 2 (SMIv2)", 1102 STD 58, RFC 2578, April 1999. 1104 [RFC3471] Berger, L., "Generalized Multi-Protocol Label Switching 1105 (GMPLS) Signaling Functional Description", RFC 3471, 1106 January 2003. 1108 [RFC4328] Papadimitriou, D., Ed., "Generalized Multi-Protocol Label 1109 Switching (GMPLS) Signaling Extensions for G.709 Optical 1110 Transport Networks Control", RFC 4328, January 2006. 1112 [G.694.1] ITU-T Recommendation G.694.1, "Spectral grids for WDM 1113 applications: DWDM frequency grid", June, 2002. 1115 9.2. Informative References 1117 [G.694.1] ITU-T Recommendation G.694.1, Spectral grids for WDM 1118 applications: DWDM frequency grid, June 2002. 1120 [G.694.2] ITU-T Recommendation G.694.2, Spectral grids for WDM 1121 applications: CWDM wavelength grid, December 2003. 1123 [Gen-Encode] G. Bernstein, Y. Lee, D. Li, W. Imajuku, "General 1124 Network Element Constraint Encoding for GMPLS Controlled 1125 Networks", work in progress: draft-ietf-ccamp-general- 1126 constraint-encode. 1128 [RFC6205] T. Otani, H. Guo, K. Miyazaki, D. Caviglia, "Generalized 1129 Labels for G.694 Lambda-Switching Capable Label Switching 1130 Routers", RFC 6205, March 2011. 1132 [RFC6163] Y. Lee, G. Bernstein, W. Imajuku, "Framework for GMPLS 1133 and PCE Control of Wavelength Switched Optical Networks", 1134 RFC 6163, April 2011. 1136 [WSON-Info] G. Bernstein, Y. Lee, D. Li, W. Imajuku, "Routing and 1137 Wavelength Assignment Information Model for Wavelength 1138 Switched Optical Networks", work in progress: draft-ietf- 1139 ccamp-rwa-info, March 2009. 1141 10. Contributors 1143 Diego Caviglia 1144 Ericsson 1145 Via A. Negrone 1/A 16153 1146 Genoa Italy 1148 Phone: +39 010 600 3736 1149 Email: diego.caviglia@(marconi.com, ericsson.com) 1151 Anders Gavler 1152 Acreo AB 1153 Electrum 236 1154 SE - 164 40 Kista Sweden 1156 Email: Anders.Gavler@acreo.se 1158 Jonas Martensson 1159 Acreo AB 1160 Electrum 236 1161 SE - 164 40 Kista, Sweden 1163 Email: Jonas.Martensson@acreo.se 1165 Itaru Nishioka 1166 NEC Corp. 1167 1753 Simonumabe, Nakahara-ku, Kawasaki, Kanagawa 211-8666 1168 Japan 1170 Phone: +81 44 396 3287 1171 Email: i-nishioka@cb.jp.nec.com 1173 Pierre Peloso 1174 ALU 1176 Email: pierre.peloso@alcatel-lucent.com 1178 Cyril Margaria 1179 NSN 1181 Email: cyril.margaria@nsn.com 1183 Authors' Addresses 1185 Greg M. Bernstein (ed.) 1186 Grotto Networking 1187 Fremont California, USA 1189 Phone: (510) 573-2237 1190 Email: gregb@grotto-networking.com 1192 Young Lee (ed.) 1193 Huawei Technologies 1194 1700 Alma Drive, Suite 100 1195 Plano, TX 75075 1196 USA 1198 Phone: (972) 509-5599 (x2240) 1199 Email: ylee@huawei.com 1201 Dan Li 1202 Huawei Technologies Co., Ltd. 1203 F3-5-B R&D Center, Huawei Base, 1204 Bantian, Longgang District 1205 Shenzhen 518129 P.R.China 1207 Phone: +86-755-28973237 1208 Email: danli@huawei.com 1210 Wataru Imajuku 1211 NTT Network Innovation Labs 1212 1-1 Hikari-no-oka, Yokosuka, Kanagawa 1213 Japan 1215 Phone: +81-(46) 859-4315 1216 Email: imajuku.wataru@lab.ntt.co.jp 1217 Jianrui Han 1218 Huawei Technologies Co., Ltd. 1219 F3-5-B R&D Center, Huawei Base, 1220 Bantian, Longgang District 1221 Shenzhen 518129 P.R.China 1223 Phone: +86-755-28972916 1224 Email: hanjianrui@huawei.com 1226 Intellectual Property Statement 1228 The IETF Trust takes no position regarding the validity or scope of 1229 any Intellectual Property Rights or other rights that might be 1230 claimed to pertain to the implementation or use of the technology 1231 described in any IETF Document or the extent to which any license 1232 under such rights might or might not be available; nor does it 1233 represent that it has made any independent effort to identify any 1234 such rights. 1236 Copies of Intellectual Property disclosures made to the IETF 1237 Secretariat and any assurances of licenses to be made available, or 1238 the result of an attempt made to obtain a general license or 1239 permission for the use of such proprietary rights by implementers or 1240 users of this specification can be obtained from the IETF on-line 1241 IPR repository at http://www.ietf.org/ipr 1243 The IETF invites any interested party to bring to its attention any 1244 copyrights, patents or patent applications, or other proprietary 1245 rights that may cover technology that may be required to implement 1246 any standard or specification contained in an IETF Document. Please 1247 address the information to the IETF at ietf-ipr@ietf.org. 1249 Disclaimer of Validity 1251 All IETF Documents and the information contained therein are 1252 provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION 1253 HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, 1254 THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL 1255 WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY 1256 WARRANTY THAT THE USE OF THE INFORMATION THEREIN WILL NOT INFRINGE 1257 ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS 1258 FOR A PARTICULAR PURPOSE. 1260 Acknowledgment 1262 Funding for the RFC Editor function is currently provided by the 1263 Internet Society.