idnits 2.17.1 draft-ietf-ccamp-rwa-wson-encode-16.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 16, 2012) is 4270 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 752, but not defined == Missing Reference: 'ITU-G.698.2' is mentioned on line 754, but not defined == Missing Reference: 'ITU-G.959.1' is mentioned on line 756, but not defined == Unused Reference: 'RFC2578' is defined on line 1103, but no explicit reference was found in the text == Unused Reference: 'G.694.1' is defined on line 1120, but no explicit reference was found in the text == Unused Reference: 'G.694.2' is defined on line 1123, 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 16, 2012 11 Routing and Wavelength Assignment Information Encoding for 12 Wavelength Switched Optical Networks 14 draft-ietf-ccamp-rwa-wson-encode-16.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 16, 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...................................................4 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................................6 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 1.1.16. Changes from 15 draft...............................7 100 2. Terminology....................................................7 101 3. Resources, Blocks, Sets, and the Resource Pool.................8 102 3.1. Resource Block Set Field..................................8 103 4. Resource Pool Accessibility/Availability......................10 104 4.1. Resource Pool Accessibility Sub-TLV......................10 105 4.2. Resource Block Wavelength Constraints Sub-TLV............12 106 4.3. Resource Pool State Sub-TLV..............................14 107 4.4. Block Shared Access Wavelength Availability sub-TLV......15 108 5. Resource Properties Encoding..................................16 109 5.1. Resource Block Information Sub-TLV.......................17 110 5.2. Optical Interface Class List(s) Sub-Sub-TLV..............17 111 5.2.1. Optical Interface Class Format......................18 112 5.3. Input Client Signal List Sub-Sub-TLV.....................19 113 5.4. Processing Capability List Sub-Sub-TLV...................20 114 5.4.1. Processing Capabilities Field.......................20 115 6. Security Considerations.......................................22 116 7. IANA Considerations...........................................22 117 8. Acknowledgments...............................................22 118 APPENDIX A: Encoding Examples....................................23 119 A.1. Wavelength Converter Accessibility Sub-TLV...............23 120 A.2. Wavelength Conversion Range Sub-TLV......................25 121 A.3. An OEO Switch with DWDM Optics...........................25 122 9. References....................................................28 123 9.1. Normative References.....................................28 124 9.2. Informative References...................................28 125 10. Contributors.................................................30 126 Authors' Addresses...............................................31 127 Intellectual Property Statement..................................32 128 Disclaimer of Validity...........................................32 130 1. Introduction 132 A Wavelength Switched Optical Network (WSON) is a Wavelength 133 Division Multiplexing (WDM) optical network in which switching is 134 performed selectively based on the center wavelength of an optical 135 signal. 137 [RFC6163] describes a framework for Generalized Multiprotocol Label 138 Switching (GMPLS) and Path Computation Element (PCE) control of a 139 WSON. Based on this framework, [WSON-Info] describes an information 140 model that specifies what information is needed at various points in 141 a WSON in order to compute paths and establish Label Switched Paths 142 (LSPs). 144 This document provides efficient encodings of information needed by 145 the routing and wavelength assignment (RWA) process in a WSON. Such 146 encodings can be used to extend GMPLS signaling and routing 147 protocols. In addition these encodings could be used by other 148 mechanisms to convey this same information to a path computation 149 element (PCE). Note that since these encodings are relatively 150 efficient they can provide more accurate analysis of the control 151 plane communications/processing load for WSONs looking to utilize a 152 GMPLS control plane. 154 Note that encodings of information needed by the routing and label 155 assignment process applicable to general networks beyond WSON are 156 addressed in a separate document [Gen-Encode]. This document makes 157 use of the Label Set Field encoding of [Gen-Encode] and refers to it 158 as a Wavelength Set Field. 160 1.1. Revision History 162 1.1.1. Changes from 00 draft 164 Edits to make consistent with update to [RFC6205], i.e., removal of 165 sign bit. 167 Clarification of TBD on connection matrix type and possibly 168 numbering. 170 New sections for wavelength converter pool encoding: Wavelength 171 Converter Set Sub-TLV, Wavelength Converter Accessibility Sub-TLV, 172 Wavelength Conversion Range Sub-TLV, WC Usage State Sub-TLV. 174 Added optional wavelength converter pool TLVs to the composite node 175 TLV. 177 1.1.2. Changes from 01 draft 179 The encoding examples have been moved to an appendix. Classified and 180 corrected information elements as either reusable fields or sub- 181 TLVs. Updated Port Wavelength Restriction sub-TLV. Added available 182 wavelength and shared backup wavelength sub-TLVs. Changed the title 183 and scope of section 6 to recommendations since the higher level 184 TLVs that this encoding will be used in is somewhat protocol 185 specific. 187 1.1.3. Changes from 02 draft 189 Removed inconsistent text concerning link local identifiers and the 190 link set field. 192 Added E bit to the Wavelength Converter Set Field. 194 Added bidirectional connectivity matrix example. Added simple link 195 set example. Edited examples for consistency. 197 1.1.4. Changes from 03 draft 199 Removed encodings for general concepts to [Gen-Encode]. 201 Added in WSON signal compatibility and processing capability 202 information encoding. 204 1.1.5. Changes from 04 draft 206 Added encodings to deal with access to resource blocks via shared 207 fiber. 209 1.1.6. Changes from 05 draft 211 Revised the encoding for the "shared access" indicators to only use 212 one bit each for input and output. 214 1.1.7. Changes from 06 draft 216 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 1.1.16. Changes from 15 draft 279 Edits of OIC related text per CCAMP list email. 281 2. Terminology 283 CWDM: Coarse Wavelength Division Multiplexing. 285 DWDM: Dense Wavelength Division Multiplexing. 287 FOADM: Fixed Optical Add/Drop Multiplexer. 289 ROADM: Reconfigurable Optical Add/Drop Multiplexer. A reduced port 290 count wavelength selective switching element featuring input and 291 output line side ports as well as add/drop side ports. 293 RWA: Routing and Wavelength Assignment. 295 Wavelength Conversion. The process of converting an information 296 bearing optical signal centered at a given wavelength to one with 297 "equivalent" content centered at a different wavelength. Wavelength 298 conversion can be implemented via an optical-electronic-optical 299 (OEO) process or via a strictly optical process. 301 WDM: Wavelength Division Multiplexing. 303 Wavelength Switched Optical Network (WSON): A WDM based optical 304 network in which switching is performed selectively based on the 305 center wavelength of an optical signal. 307 3. Resources, Blocks, Sets, and the Resource Pool 309 The optical system to be encoded may contain a pool of resources of 310 different types and properties for processing optical signals. For 311 the purposes here a "resource" is an individual entity such as a 312 wavelength converter or regenerator within the optical node that 313 acts on an individual wavelength signal. 315 Since resources tend to be packaged together in blocks of similar 316 devices, e.g., on line cards or other types of modules, the 317 fundamental unit of identifiable resource in this document is the 318 "resource block". A resource block may contain one or more 319 resources. As resource blocks are the smallest identifiable unit of 320 processing resource, one should group together resources into blocks 321 if they have similar characteristics relevant to the optical system 322 being modeled, e.g., processing properties, accessibility, etc. 324 This document defines the following sub-TLVs pertaining to resources 325 within an optical node: 327 . Resource Pool Accessibility Sub-TLV 329 . Resource Block Wavelength Constraints Sub-TLV 331 . Resource Pool State Sub-TLV 333 . Block Shared Access Wavelength Availability Sub-TLV 335 . Resource Block Information Sub-TLV 337 Each of these sub-TLVs works with one or more sets of resources 338 rather than just a single resource block. This motivates the 339 following field definition. 341 3.1. Resource Block Set Field 343 In a WSON node that includes resource blocks (RB), denoting subsets 344 of these blocks allows one to efficiently describe common properties 345 of the blocks and to describe the structure and characteristics, if 346 non-trivial, of the resource pool. The RB Set field is defined in a 347 similar manner to the label set concept of [RFC3471]. 349 The information carried in a RB set field is defined by: 351 0 1 2 3 352 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 353 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 354 | Action |C| Reserved | Length | 355 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 356 | RB Identifier 1 | 357 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 358 : : : 359 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 360 | RB Identifier n | 361 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 363 Action: 8 bits 365 0 - Inclusive List 367 Indicates that the TLV contains one or more RB elements that are 368 included in the list. 370 2 - Inclusive Range(s) 372 Indicates that the TLV contains one or more ranges of RBs. Each 373 individual range is denoted by two 16 bit RB identifiers in a 32 bit 374 word. The first 16 bits is the RB identifier for the start of the 375 range and the next 16 bits is the RB identifier for the end of the 376 range. Note that the Length field is used to determine the number of 377 ranges. 379 C (Connectivity bit): Set to 0 to denote fixed (possibly multi- 380 cast) connectivity; Set to 1 to denote potential (switched) 381 connectivity. Used in resource pool accessibility sub-TLV. Ignored 382 elsewhere. 384 Reserved: 7 bits 386 This field is reserved. It MUST be set to zero on transmission and 387 MUST be ignored on receipt. 389 Length: 16 bits 391 The total length of this field in bytes. 393 RB Identifier: 395 The RB identifier represents the ID of the resource block which is a 396 16 bit integer. 398 Usage Note: the inclusive range "Action" can result in very compact 399 encoding of resource sets and it can be advantages to number 400 resource blocks in such a way so that status updates (dynamic 401 information) can take advantage of this efficiency. 403 4. Resource Pool Accessibility/Availability 405 This section defines the sub-TLVs for dealing with accessibility and 406 availability of resource blocks within a pool of resources. These 407 include the ResourceBlockAccessibility, ResourceWaveConstraints, and 408 RBPoolState sub-TLVs. 410 4.1. Resource Pool Accessibility Sub-TLV 412 This sub-TLV describes the structure of the resource pool in 413 relation to the switching device. In particular it indicates the 414 ability of an input port to reach sets of resources and of a sets of 415 resources to reach a particular output port. This is the 416 PoolInputMatrix and PoolOutputMatrix of [WSON-Info]. 418 The resource pool accessibility sub-TLV is defined by: 420 0 1 2 3 421 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 422 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 423 | Connectivity | Reserved | 424 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 425 | Input Link Set Field A #1 | 426 : : 427 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 428 | RB Set Field A #1 | 429 : : 430 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 431 | Additional Link set and RB set pairs as needed to | 432 : specify PoolInputMatrix : 433 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 434 | Output Link Set Field B #1 | 435 : : 436 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 437 | RB Set B Field #1 (for output connectivity) | 438 : : 439 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 440 | Additional Link Set and RB set pairs as needed to | 441 : specify PoolOutputMatrix : 442 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 444 Where 446 Connectivity indicates how the input/output ports connect to the 447 resource blocks. 449 0 -- the device is fixed (e.g., a connected port must go 450 through the resource block) 452 1 -- the device is switched (e.g., a port can be configured to 453 go through a resource but isn't required) 455 The For the Input and Output Link Set Fields, the Link Set Field 456 encoding defined in [Gen-Encode] is to be used. 458 Note that the direction parameter within the Link Set Field is used 459 to indicate whether the link set is an input or output link set, and 460 the bidirectional value for this parameter is not permitted in this 461 sub-TLV. 463 See Appendix A.1 for an illustration of this encoding. 465 4.2. Resource Block Wavelength Constraints Sub-TLV 467 Resources, such as wavelength converters, etc., may have a limited 468 input or output wavelength ranges. Additionally, due to the 469 structure of the optical system not all wavelengths can necessarily 470 reach or leave all the resources. These properties are described by 471 using one or more resource wavelength restrictions sub-TLVs as 472 defined below: 474 0 1 2 3 475 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 476 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 477 |I|O|B| Reserved | 478 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 479 | RB Set Field | 480 : : 481 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 482 | Input Wavelength Set Field | 483 : : 484 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 485 | Output Wavelength Set Field | 486 : : 487 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 489 I = 1 or 0 indicates the presence or absence of the Input Wavelength 490 Set Field. 492 O = 1 or 0 indicates the presence or absence of the Output 493 Wavelength Set Field. 495 B = 1 indicates that a single wavelength set field represents both 496 input and output wavelength constraints. 498 Currently the only valid combinations of (I,O,B) are (1,0,0), 499 (0,1,0), (1,1,0), (0,0,1). 501 RB Set Field: 503 A set of resource blocks (RBs) which have the same wavelength 504 restrictions. 506 Input Wavelength Set Field: 508 Indicates the wavelength input restrictions of the RBs in the 509 corresponding RB set. This field is encoded via the Label Set field 510 of [Gen-Encode]. 512 Output Wavelength Set Field: 514 Indicates the wavelength output restrictions of RBs in the 515 corresponding RB set. This field is encoded via the Label Set field 516 of [Gen-Encode]. 518 4.3. Resource Pool State Sub-TLV 520 The state of the pool is given by the number of resources available 521 with particular characteristics. A resource block set is used to 522 encode all or a subset of the resources of interest. The usage state 523 of resources within a resource block set is encoded as either a list 524 of 16 bit integer values or a bit map indicating whether a single 525 resource is available or in use. The bit map encoding is appropriate 526 when resource blocks consist of a single resource. This information 527 can be relatively dynamic, i.e., can change when a connection (LSP 528 is established or torn down. 530 0 1 2 3 531 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 532 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 533 | Action | Reserved | 534 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 535 | RB Set Field | 536 : : 537 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 538 | RB Usage state | 539 : : 540 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 542 Where Action = 0 denotes a list of 16 bit integers and Action = 1 543 denotes a bit map. In both cases the elements of the RB Set field 544 are in a one-to-one correspondence with the values in the usage RB 545 usage state area. 547 0 1 2 3 548 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 549 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 550 | Action = 0 | Reserved | 551 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 552 | RB Set Field | 553 : : 554 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 555 | RB#1 state | RB#2 state | 556 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 557 : : 558 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 559 | RB#n-1 state | RB#n state or Padding | 560 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 562 Whether the last 16 bits is a wavelength converter (RB) state or 563 padding is determined by the number of elements in the RB set field. 565 0 1 2 3 566 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 567 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 568 | Action = 1 | Reserved | 569 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 570 | RB Set Field | 571 : : 572 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 573 | RB Usage state bitmap | 574 : : 575 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 576 | ...... | Padding bits | 577 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 579 RB Usage state: Variable Length but must be a multiple of 4 byes. 581 Each bit indicates the usage status of one RB with 0 indicating the 582 RB is available and 1 indicating the RB is in used. The sequence of 583 the bit map is ordered according to the RB Set field with this sub- 584 TLV. 586 Padding bits: Variable Length 588 4.4. Block Shared Access Wavelength Availability sub-TLV 590 Resources blocks may be accessed via a shared fiber. If this is the 591 case, then wavelength availability on these shared fibers is needed 592 to understand resource availability. 594 0 1 2 3 595 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 596 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 597 |I|E| Reserved | 598 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 599 | RB Set Field | 600 : : 601 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 602 | Input Available Wavelength Set Field | 603 : (Optional) : 604 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 605 | Output Available Wavelength Set Field | 606 : (Optional) : 607 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 608 I bit: 610 Indicates whether the input available wavelength set field is 611 included (1) or not (0). 613 E bit: 615 Indicates whether the output available wavelength set field is 616 included (1) or not (0). 618 RB Set Field: 620 A Resource Block set in which all the members share the same input 621 or output fiber or both. 623 Input Available Wavelength Set Field: 625 Indicates the wavelengths currently available (not being used) on 626 the input fiber to this resource block. This field is encoded via 627 the Label Set field of [Gen-Encode]. 629 Output Available Wavelength Set Field: 631 Indicates the wavelengths currently available (not being used) on 632 the output fiber from this resource block. This field is encoded via 633 the Label Set field of [Gen-Encode]. 635 5. Resource Properties Encoding 637 Within a WSON network element (NE) there may be resources with 638 signal compatibility constraints. These resources be regenerators, 639 wavelength converters, etc... Such resources may also constitute the 640 network element as a whole as in the case of an electro optical 641 switch. This section primarily focuses on the signal compatibility 642 and processing properties of such a resource block. 644 The fundamental properties of a resource block, such as a 645 regenerator or wavelength converter, are: 647 (a) Input constraints (shared input, modulation, FEC, bit rate, 648 GPID) 650 (b) Processing capabilities (number of resources in a block, 651 regeneration, performance monitoring, vendor specific) 653 (c) Output Constraints (shared output, modulation, FEC) 655 5.1. Resource Block Information Sub-TLV 657 Resource Block descriptor sub-TLVs are used to convey relatively 658 static information about individual resource blocks including the 659 resource block compatibility properties, processing properties, and 660 the number of resources in a block. 662 This sub-TLV has the following format: 664 0 1 2 3 665 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 666 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 667 | RB Set Field | 668 : : 669 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 670 |I|E| Reserved | 671 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 672 | Optical Interface Class List(s) Sub-Sub-TLV (opt) | 673 : : 674 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 675 | Input Client Signal Type Sub-Sub-TLV (opt) | 676 : : 677 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 678 | Input Bit Rate Range List Sub-Sub-TLV (opt) | 679 : : 680 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 681 | Processing Capabilities List Sub-Sub-TLV (opt) | 682 : : 683 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 685 Where I and E, the shared input/output indicator, is set to 1 if the 686 resource blocks identified in the RB set field utilized a shared 687 fiber for input/output access and set to 0 otherwise. 689 5.2. Optical Interface Class List(s) Sub-Sub-TLV 691 The list of Optical Interface Class sub-sub-TLV has the following 692 format: 694 0 1 2 3 695 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 696 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 697 | Type | Length | Reserved |I|E| 698 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 699 | Optical Interface Classes | 700 : : 701 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 703 The following I and E combination are defined: 705 I E 707 0 0 Invalid 709 1 0 Optical Interface Class List acceptable in input 711 0 1 Optical Interface Class List available in output 713 1 1 Optical Interface Class List available on both input and 714 output. 716 The Resource Block MAY contain one or more lists according to 717 input/output flags. 719 5.2.1. Optical Interface Class Format 721 0 1 2 3 722 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 723 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 724 |S| Reserved | OI Code Points | 725 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 726 | Optical Interface Class | 727 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 728 | Optical Interface Class (Cont.) | 729 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 731 Where the first 32 bits of the encoding shall be used to identify 732 the semantic of the Optical Interface Class in the following way: 734 S Standard bit. 736 S=0, identify not ITU code points 738 S=1, identify ITU application codes 740 With S=0, the OI Code Points field can take the following 741 values: 743 0: reserved 745 1: Vendor Specific Optical Interface Class. 747 With S=1, the OI Code Points field can take the following 748 values: 750 0: reserved 752 1: [ITU-G.698.1] application code. 754 2: [ITU-G.698.2] application code. 756 3: [ITU-G.959.1] application code. 758 In case of ITU Application Code, there should be a mapping between 759 the string defining the application code and the 64 bits number 760 implementing the optical interface class. 762 5.3. Input Client Signal List Sub-Sub-TLV 764 This sub-sub-TLV contains a list of acceptable input client signal 765 types. 767 Type := Input Client Signal List 769 Value := A list of GPIDs 771 The acceptable client signal list sub-TLV is a list of Generalized 772 Protocol Identifiers (GPIDs). GPIDs are assigned by IANA and many 773 are defined in [RFC3471] and [RFC4328]. 775 0 1 2 3 776 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 777 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 778 | Number of GPIDs | GPID #1 | 779 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 780 : | : 781 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 782 | GPID #N | | 783 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 785 Where the number of GPIDs is an integer greater than or equal to 786 one. 788 5.4. Processing Capability List Sub-Sub-TLV 790 This sub-sub-TLV contains a list of resource processing 791 capabilities. 793 Type := Processing Capabilities List 795 Value := A list of Processing Capabilities Fields 797 The processing capability list sub-sub-TLV is a list of capabilities 798 that can be achieved through the referred resources:: 800 1. Regeneration capability 802 2. Fault and performance monitoring 804 3. Vendor Specific capability 806 Note that the code points for Fault and performance monitoring and 807 vendor specific capability are subject to further study. 809 5.4.1. Processing Capabilities Field 811 The processing capability field is then given by: 813 0 1 2 3 814 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 815 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 816 | Processing Cap ID | Length | 817 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 818 | Possible additional capability parameters depending upon | 819 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 820 : the processing ID : 821 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 823 When the processing Cap ID is "regeneration capability", the 824 following additional capability parameters are provided in the sub- 825 TLV: 827 0 1 2 3 828 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 829 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 830 | T | C | Reserved | 831 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 833 Where T bit indicates the type of regenerator: 835 T=0: Reserved 837 T=1: 1R Regenerator 839 T=2: 2R Regenerator 841 T=3: 3R Regenerator 843 Where C bit indicates the capability of regenerator: 845 C=0: Reserved 847 C=1: Fixed Regeneration Point 849 C=2: Selective Regeneration Point 851 Note that when the capability of regenerator is indicated to be 852 Selective Regeneration Pools, regeneration pool properties such as 853 input and output restrictions and availability need to be specified. 854 This encoding is to be determined in the later revision. 856 6. Security Considerations 858 This document defines protocol-independent encodings for WSON 859 information and does not introduce any security issues. 861 However, other documents that make use of these encodings within 862 protocol extensions need to consider the issues and risks associated 863 with, inspection, interception, modification, or spoofing of any of 864 this information. It is expected that any such documents will 865 describe the necessary security measures to provide adequate 866 protection. 868 7. IANA Considerations 870 This document provides general protocol independent information 871 encodings. There is no IANA allocation request for the TLVs defined 872 in this document. IANA allocation requests will be addressed in 873 protocol specific documents based on the encodings defined here. 875 8. Acknowledgments 877 This document was prepared using 2-Word-v2.0.template.dot. 879 APPENDIX A: Encoding Examples 881 A.1. Wavelength Converter Accessibility Sub-TLV 883 Example: 885 Figure 1 shows a wavelength converter pool architecture know as 886 "shared per fiber". In this case the input and output pool matrices 887 are simply: 889 +-----+ +-----+ 890 | 1 1 | | 1 0 | 891 WI =| |, WE =| | 892 | 1 1 | | 0 1 | 893 +-----+ +-----+ 895 +-----------+ +------+ 896 | |--------------------->| | 897 | |--------------------->| C | 898 /| | |--------------------->| o | 899 /D+--->| |--------------------->| m | 900 + e+--->| | | b 901 |========> 902 ========>| M| | Optical | +-----------+ | i | Port E1 903 Port I1 + u+--->| Switch | | WC Pool | | n | 904 \x+--->| | | +-----+ | | e | 905 \| | +----+->|WC #1|--+---->| r | 906 | | | +-----+ | +------+ 907 | | | | +------+ 908 /| | | | +-----+ | | | 909 /D+--->| +----+->|WC #2|--+---->| C | 910 + e+--->| | | +-----+ | | o | 911 ========>| M| | | +-----------+ | m 912 |========> 913 Port I2 + u+--->| | | b | Port E2 914 \x+--->| |--------------------->| i | 915 \| | |--------------------->| n | 916 | |--------------------->| e | 917 | |--------------------->| r | 918 +-----------+ +------+ 919 Figure 1 An optical switch featuring a shared per fiber wavelength 920 converter pool architecture. 922 This wavelength converter pool can be encoded as follows: 924 0 1 2 3 925 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 926 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 927 | Connectivity=1| Reserved | 928 Note: I1,I2 can connect to either WC1 or WC2 929 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 930 | Action=0 |0| Reserved | Length = 12 | 931 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 932 | Link Local Identifier = #1 | 933 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 934 | Link Local Identifier = #2 | 935 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 936 | Action=0 |1| Reserved | Length = 8 | 937 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 938 | RB ID = #1 | RB ID = #2 | 939 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 940 Note: WC1 can only connect to E1 941 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 942 | Action=0 |1| Reserved | Length = 8 | 943 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 944 | Link Local Identifier = #1 | 945 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 946 | Action=0 |0| Reserved | Length = 8 | 947 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 948 | RB ID = #1 | zero padding | 949 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 950 Note: WC2 can only connect to E2 951 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 952 | Action=0 |1| Reserved | Length = 8 | 953 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 954 | Link Local Identifier = #2 | 955 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 956 | Action=0 |0| | Length = 8 | 957 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 958 | RB ID = #2 | zero padding | 959 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 961 A.2. Wavelength Conversion Range Sub-TLV 963 Example: 965 This example, based on figure 1, shows how to represent the 966 wavelength conversion range of wavelength converters. Suppose the 967 wavelength range of input and output of WC1 and WC2 are {L1, L2, L3, 968 L4}: 970 0 1 2 3 971 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 972 Note: WC Set 973 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 974 | Action=0 |1| Reserved | Length = 8 | 975 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 976 | WC ID = #1 | WC ID = #2 | 977 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 978 Note: wavelength input range 979 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 980 | 2 | Num Wavelengths = 4 | Length = 8 | 981 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 982 |Grid | C.S. | Reserved | n for lowest frequency = 1 | 983 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 984 Note: wavelength output range 985 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 986 | 2 | Num Wavelengths = 4 | Length = 8 | 987 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 988 |Grid | C.S. | Reserved | n for lowest frequency = 1 | 989 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 991 A.3. An OEO Switch with DWDM Optics 993 Figure 2 shows an electronic switch fabric surrounded by DWDM 994 optics. In this example the electronic fabric can handle either 995 G.709 or SDH signals only (2.5 or 10 Gbps). To describe this node, 996 the following information is needed: 998 ::= [Other GMPLS sub- 999 TLVs][...] [][] 1001 In this case there is complete port to port connectivity so the 1002 is not required. In addition since there are 1003 sufficient ports to handle all wavelength signals the 1004 element is not needed. 1006 Hence the attention will be focused on the sub-TLV: 1008 ::= 1009 [...][...] 1012 /| +-----------+ +-------------+ +------+ 1013 /D+--->| +--->|Tunable Laser|-->| | 1014 + e+--->| | +-------------+ | C | 1015 ========>| M| | | ... | o 1016 |========> 1017 Port I1 + u+--->| | +-------------+ | m | Port E1 1018 \x+--->| |--->|Tunable Laser|-->| b | 1019 \| | Electric | +-------------+ +------+ 1020 | Switch | 1021 /| | | +-------------+ +------+ 1022 /D+--->| +--->|Tunable Laser|-->| | 1023 + e+--->| | +-------------+ | C | 1024 ========>| M| | | ... | o 1025 |========> 1026 Port I2 + u+--->| | +-------------+ | m | Port E2 1027 \x+--->| +--->|Tunable Laser|-->| b | 1028 \| | | +-------------+ +------+ 1029 | | 1030 /| | | +-------------+ +------+ 1031 /D+--->| |--->|Tunable Laser|-->| | 1032 + e+--->| | +-------------+ | C | 1033 ========>| M| | | ... | o 1034 |========> 1035 Port I3 + u+--->| | +-------------+ | m | Port E3 1036 \x+--->| |--->|Tunable Laser|-->| b | 1037 \| +-----------+ +-------------+ +------+ 1039 Figure 2 An optical switch built around an electronic switching 1040 fabric. 1042 The resource block information will tell us about the processing 1043 constraints of the receivers, transmitters and the electronic 1044 switch. The resource availability information, although very simple, 1045 tells us that all signals must traverse the electronic fabric (fixed 1046 connectivity). The resource wavelength constraints are not needed 1047 since there are no special wavelength constraints for the resources 1048 that would not appear as port/wavelength constraints. 1050 : 1052 0 1 2 3 1053 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 1054 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1055 | RB Set Field | 1056 : (only one resource block in this example with shared | 1057 | input/output case) | 1058 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1059 |0|1|1| Reserved | 1060 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1061 | Modulation Type List Sub-Sub-TLV | 1062 : NRZ : 1063 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1064 | FEC Type List Sub-Sub-TLV | 1065 : Standard SDH, G.709 FEC : 1066 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1067 | Input Client Signal Type Sub-TLV | 1068 : (GPIDs for SDH and G.709) : 1069 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1070 | Input Bit Rate Range List Sub-Sub-TLV | 1071 : (2.5Gbps, 10Gbps) : 1072 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1073 | Processing Capabilities List Sub-Sub-TLV | 1074 : Fixed (non optional) 3R regeneration : 1075 : : 1076 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1078 Since there is fixed connectivity to resource blocks (the electronic 1079 switch) the is: 1081 0 1 2 3 1082 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 1083 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1084 | Connectivity=0|Reserved | 1085 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1086 | Input Link Set Field A #1 | 1087 : (All input links connect to resource) : 1088 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1089 | RB Set Field A #1 | 1090 : (trivial set only one resource block) : 1091 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1092 | Output Link Set Field B #1 | 1093 : (All output links connect to resource) : 1094 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1096 9. References 1098 9.1. Normative References 1100 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1101 Requirement Levels", BCP 14, RFC 2119, March 1997. 1103 [RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 1104 "Structure of Management Information Version 2 (SMIv2)", 1105 STD 58, RFC 2578, April 1999. 1107 [RFC3471] Berger, L., "Generalized Multi-Protocol Label Switching 1108 (GMPLS) Signaling Functional Description", RFC 3471, 1109 January 2003. 1111 [RFC4328] Papadimitriou, D., Ed., "Generalized Multi-Protocol Label 1112 Switching (GMPLS) Signaling Extensions for G.709 Optical 1113 Transport Networks Control", RFC 4328, January 2006. 1115 [G.694.1] ITU-T Recommendation G.694.1, "Spectral grids for WDM 1116 applications: DWDM frequency grid", June, 2002. 1118 9.2. Informative References 1120 [G.694.1] ITU-T Recommendation G.694.1, Spectral grids for WDM 1121 applications: DWDM frequency grid, June 2002. 1123 [G.694.2] ITU-T Recommendation G.694.2, Spectral grids for WDM 1124 applications: CWDM wavelength grid, December 2003. 1126 [Gen-Encode] G. Bernstein, Y. Lee, D. Li, W. Imajuku, "General 1127 Network Element Constraint Encoding for GMPLS Controlled 1128 Networks", work in progress: draft-ietf-ccamp-general- 1129 constraint-encode. 1131 [RFC6205] T. Otani, H. Guo, K. Miyazaki, D. Caviglia, "Generalized 1132 Labels for G.694 Lambda-Switching Capable Label Switching 1133 Routers", RFC 6205, March 2011. 1135 [RFC6163] Y. Lee, G. Bernstein, W. Imajuku, "Framework for GMPLS 1136 and PCE Control of Wavelength Switched Optical Networks", 1137 RFC 6163, April 2011. 1139 [WSON-Info] G. Bernstein, Y. Lee, D. Li, W. Imajuku, "Routing and 1140 Wavelength Assignment Information Model for Wavelength 1141 Switched Optical Networks", work in progress: draft-ietf- 1142 ccamp-rwa-info, March 2009. 1144 10. Contributors 1146 Diego Caviglia 1147 Ericsson 1148 Via A. Negrone 1/A 16153 1149 Genoa Italy 1151 Phone: +39 010 600 3736 1152 Email: diego.caviglia@(marconi.com, ericsson.com) 1154 Anders Gavler 1155 Acreo AB 1156 Electrum 236 1157 SE - 164 40 Kista Sweden 1159 Email: Anders.Gavler@acreo.se 1161 Jonas Martensson 1162 Acreo AB 1163 Electrum 236 1164 SE - 164 40 Kista, Sweden 1166 Email: Jonas.Martensson@acreo.se 1168 Itaru Nishioka 1169 NEC Corp. 1170 1753 Simonumabe, Nakahara-ku, Kawasaki, Kanagawa 211-8666 1171 Japan 1173 Phone: +81 44 396 3287 1174 Email: i-nishioka@cb.jp.nec.com 1176 Pierre Peloso 1177 ALU 1179 Email: pierre.peloso@alcatel-lucent.com 1181 Cyril Margaria 1182 NSN 1184 Email: cyril.margaria@nsn.com 1186 Authors' Addresses 1188 Greg M. Bernstein (ed.) 1189 Grotto Networking 1190 Fremont California, USA 1192 Phone: (510) 573-2237 1193 Email: gregb@grotto-networking.com 1195 Young Lee (ed.) 1196 Huawei Technologies 1197 1700 Alma Drive, Suite 100 1198 Plano, TX 75075 1199 USA 1201 Phone: (972) 509-5599 (x2240) 1202 Email: ylee@huawei.com 1204 Dan Li 1205 Huawei Technologies Co., Ltd. 1206 F3-5-B R&D Center, Huawei Base, 1207 Bantian, Longgang District 1208 Shenzhen 518129 P.R.China 1210 Phone: +86-755-28973237 1211 Email: danli@huawei.com 1213 Wataru Imajuku 1214 NTT Network Innovation Labs 1215 1-1 Hikari-no-oka, Yokosuka, Kanagawa 1216 Japan 1218 Phone: +81-(46) 859-4315 1219 Email: imajuku.wataru@lab.ntt.co.jp 1220 Jianrui Han 1221 Huawei Technologies Co., Ltd. 1222 F3-5-B R&D Center, Huawei Base, 1223 Bantian, Longgang District 1224 Shenzhen 518129 P.R.China 1226 Phone: +86-755-28972916 1227 Email: hanjianrui@huawei.com 1229 Intellectual Property Statement 1231 The IETF Trust takes no position regarding the validity or scope of 1232 any Intellectual Property Rights or other rights that might be 1233 claimed to pertain to the implementation or use of the technology 1234 described in any IETF Document or the extent to which any license 1235 under such rights might or might not be available; nor does it 1236 represent that it has made any independent effort to identify any 1237 such rights. 1239 Copies of Intellectual Property disclosures made to the IETF 1240 Secretariat and any assurances of licenses to be made available, or 1241 the result of an attempt made to obtain a general license or 1242 permission for the use of such proprietary rights by implementers or 1243 users of this specification can be obtained from the IETF on-line 1244 IPR repository at http://www.ietf.org/ipr 1246 The IETF invites any interested party to bring to its attention any 1247 copyrights, patents or patent applications, or other proprietary 1248 rights that may cover technology that may be required to implement 1249 any standard or specification contained in an IETF Document. Please 1250 address the information to the IETF at ietf-ipr@ietf.org. 1252 Disclaimer of Validity 1254 All IETF Documents and the information contained therein are 1255 provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION 1256 HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, 1257 THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL 1258 WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY 1259 WARRANTY THAT THE USE OF THE INFORMATION THEREIN WILL NOT INFRINGE 1260 ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS 1261 FOR A PARTICULAR PURPOSE. 1263 Acknowledgment 1265 Funding for the RFC Editor function is currently provided by the 1266 Internet Society.