idnits 2.17.1 draft-ietf-ccamp-rwa-wson-encode-06.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 (October 13, 2010) is 4943 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) == Unused Reference: 'G.694.1' is defined on line 1223, but no explicit reference was found in the text == Unused Reference: 'G.694.2' is defined on line 1226, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'G.694.1' -- No information found for draft-ietf-ccamp-general-ext-encode - is the name correct? Summary: 0 errors (**), 0 flaws (~~), 3 warnings (==), 3 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: April 2011 D. Li 5 Huawei 6 W. Imajuku 7 NTT 9 October 13, 2010 11 Routing and Wavelength Assignment Information Encoding for 12 Wavelength Switched Optical Networks 14 draft-ietf-ccamp-rwa-wson-encode-06.txt 16 Status of this Memo 18 This Internet-Draft is submitted to IETF in full conformance with the 19 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 months 27 and may be updated, replaced, or obsoleted by other documents at any 28 time. It is inappropriate to use Internet-Drafts as reference 29 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 April 13, 2011. 39 Copyright Notice 41 Copyright (c) 2010 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 respect 49 to this document. Code Components extracted from this document must 50 include Simplified BSD License text as described in Section 4.e of 51 the Trust Legal Provisions and are provided without warranty as 52 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 Assignment 60 Information for Wavelength Switched Optical Networks" shows what 61 information is required at specific points in the WSON. Part of the 62 WSON information model contains aspects that may be of general 63 applicability to other technologies, while other parts are fairly 64 specific to WSONs. 66 This document provides efficient, protocol-agnostic encodings for the 67 WSON specific information elements. It is intended that protocol- 68 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................................4 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 2. Terminology....................................................5 91 3. WSON Encoding Usage Recommendations............................6 92 3.1. WSON Node TLV.............................................6 93 3.2. WSON Dynamic Node TLV.....................................6 94 4. Resource Accessibility/Availability............................7 95 4.1. Block Accessibility Sub-TLV...............................8 96 4.2. Wavelength Constraints Sub-TLV...........................10 97 4.3. Block Pool State Sub-TLV.................................10 98 4.4. Block Shared Access Wavelength Availability sub-TLV......12 99 5. Resource Properties Encoding..................................13 100 5.1. Resource Block Information Sub-TLV.......................13 101 5.2. Input Modulation Format List Sub-Sub-TLV.................14 102 5.2.1. Modulation Format Field.............................15 103 5.3. Input FEC Type List Sub-Sub-TLV..........................16 104 5.3.1. FEC Type Field......................................17 105 5.4. Input Bit Range List Sub-Sub-TLV.........................19 106 5.4.1. Bit Range Field.....................................19 107 5.5. Input Client Signal List Sub-Sub-TLV.....................20 108 5.6. Processing Capability List Sub-Sub-TLV...................21 109 5.6.1. Processing Capabilities Field.......................21 110 5.7. Output Modulation Format List Sub-Sub-TLV................23 111 5.8. Output FEC Type List Sub-Sub-TLV.........................23 112 6. Security Considerations.......................................23 113 7. IANA Considerations...........................................24 114 8. Acknowledgments...............................................24 115 APPENDIX A: Encoding Examples....................................25 116 A.1. Wavelength Converter Accessibility Sub-TLV...............25 117 A.2. Wavelength Conversion Range Sub-TLV......................26 118 A.3. An OEO Switch with DWDM Optics...........................27 119 9. References....................................................31 120 9.1. Normative References.....................................31 121 9.2. Informative References...................................31 122 10. Contributors.................................................32 123 Authors' Addresses...............................................33 124 Intellectual Property Statement..................................34 125 Disclaimer of Validity...........................................34 127 1. Introduction 129 A Wavelength Switched Optical Network (WSON) is a Wavelength Division 130 Multiplexing (WDM) optical network in which switching is performed 131 selectively based on the center wavelength of an optical signal. 133 [WSON-Frame] describes a framework for Generalized Multiprotocol 134 Label Switching (GMPLS) and Path Computation Element (PCE) control of 135 a WSON. Based on this framework, [WSON-Info] describes an information 136 model that specifies what information is needed at various points in 137 a WSON in order to compute paths and establish Label Switched Paths 138 (LSPs). 140 This document provides efficient encodings of information needed by 141 the routing and wavelength assignment (RWA) process in a WSON. Such 142 encodings can be used to extend GMPLS signaling and routing 143 protocols. In addition these encodings could be used by other 144 mechanisms to convey this same information to a path computation 145 element (PCE). Note that since these encodings are relatively 146 efficient they can provide more accurate analysis of the control 147 plane communications/processing load for WSONs looking to utilize a 148 GMPLS control plane. 150 Note that encodings of information needed by the routing and label 151 assignment process applicable to general networks beyond WSON are 152 addressed in a separate document [Gen-Encode]. 154 1.1. Revision History 156 1.1.1. Changes from 00 draft 158 Edits to make consistent with update to [Otani], i.e., removal of 159 sign bit. 161 Clarification of TBD on connection matrix type and possibly 162 numbering. 164 New sections for wavelength converter pool encoding: Wavelength 165 Converter Set Sub-TLV, Wavelength Converter Accessibility Sub-TLV, 166 Wavelength Conversion Range Sub-TLV, WC Usage State Sub-TLV. 168 Added optional wavelength converter pool TLVs to the composite node 169 TLV. 171 1.1.2. Changes from 01 draft 173 The encoding examples have been moved to an appendix. Classified and 174 corrected information elements as either reusable fields or sub-TLVs. 175 Updated Port Wavelength Restriction sub-TLV. Added available 176 wavelength and shared backup wavelength sub-TLVs. Changed the title 177 and scope of section 6 to recommendations since the higher level TLVs 178 that this encoding will be used in is somewhat protocol specific. 180 1.1.3. Changes from 02 draft 182 Removed inconsistent text concerning link local identifiers and the 183 link set field. 185 Added E bit to the Wavelength Converter Set Field. 187 Added bidirectional connectivity matrix example. Added simple link 188 set example. Edited examples for consistency. 190 1.1.4. Changes from 03 draft 192 Removed encodings for general concepts to [Gen-Encode]. 194 Added in WSON signal compatibility and processing capability 195 information encoding. 197 1.1.5. Changes from 04 draft 199 Added encodings to deal with access to resource blocks via shared 200 fiber. 202 1.1.5. 1.1.6. Changes from 05 draft 204 Revised the encoding for the "shared access" indicators to only use 205 one bit each for ingress and egress. 207 2. Terminology 209 CWDM: Coarse Wavelength Division Multiplexing. 211 DWDM: Dense Wavelength Division Multiplexing. 213 FOADM: Fixed Optical Add/Drop Multiplexer. 215 ROADM: Reconfigurable Optical Add/Drop Multiplexer. A reduced port 216 count wavelength selective switching element featuring ingress and 217 egress line side ports as well as add/drop side ports. 219 RWA: Routing and Wavelength Assignment. 221 Wavelength Conversion. The process of converting an information 222 bearing optical signal centered at a given wavelength to one with 223 "equivalent" content centered at a different wavelength. Wavelength 224 conversion can be implemented via an optical-electronic-optical (OEO) 225 process or via a strictly optical process. 227 WDM: Wavelength Division Multiplexing. 229 Wavelength Switched Optical Network (WSON): A WDM based optical 230 network in which switching is performed selectively based on the 231 center wavelength of an optical signal. 233 3. WSON Encoding Usage Recommendations 235 In this section we give recommendations of typical usage of the sub- 236 TLVs and composite TLVs which are based on the high level information 237 bundles of [WSON-Info]. 239 3.1. WSON Node TLV 241 The WSON Node TLV would consist of the following list of sub-TLVs: 243 ::= [Other GMPLS sub-TLVs] 244 [][] 246 Where 248 ::= ... 249 [...] [...] 251 The encoding of structure and properties of a general resource pool 252 utilizes a resource block info sub-TLV ( in 253 section 5. ), an accessibility sub-TLV ( 254 in section 4.1. ), and a resource pool wavelength constraint sub-TLV 255 ( in section 4.2. ). 257 3.2. WSON Dynamic Node TLV 259 If the protocol supports the separation of dynamic information from 260 relatively static information then the wavelength converter pool 261 state can be separated from the general Node TLV into a dynamic Node 262 TLV as follows. 264 ::= 265 [][...] 267 Where the resource pool state sub-TLV is defined in 268 section 4.3. Note that currently the only dynamic information modeled 269 with a node is associated with the status of the wavelength converter 270 pool. 272 4. Resource Accessibility/Availability 274 In this section we define the sub-TLVs for dealing with accessibility 275 and availability of resource blocks. These include the 276 ResourceBlockAccessibility, ResourceWaveConstraints, and RBPoolState 277 sub-TLVs. All these sub-TLVs are concerned with sets of resources. 279 In a WSON node that includes resource blocks (RB) we will want to 280 denote subsets these blocks to efficiently describe common properties 281 the blocks and to describe the structure, if non-trivial, of the 282 resource pool. The RB Set field is defined in a similar manner to the 283 label set concept of [RFC3471]. 285 The information carried in a RB set field is defined by: 287 0 1 2 3 288 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 289 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 290 | Action |E|C| Reserved | Length | 291 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 292 | RB Identifier 1 | RB Identifier 2 | 293 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 294 : : : 295 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 296 | RB Identifier n-1 | RB Identifier n | 297 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 299 Action: 8 bits 301 0 - Inclusive List 303 Indicates that the TLV contains one or more RB elements that are 304 included in the list. 306 2 - Inclusive Range 308 Indicates that the TLV contains a range of RBs. The object/TLV 309 contains two WC elements. The first element indicates the start of 310 the range. The second element indicates the end of the range. A value 311 of zero indicates that there is no bound on the corresponding portion 312 of the range. 314 E (Even bit): Set to 0 denotes an odd number of RB identifiers in 315 the list (last entry zero pad); Set to 1 denotes an even number of RB 316 identifiers in the list (no zero padding). 318 C (Connectivity bit): Set to 0 to denote fixed (possibly multi- 319 cast) connectivity; Set to 1 to denote potential (switched) 320 connectivity. Used in resource pool accessibility sub-TLV. Ignored 321 elsewhere. 323 Reserved: 6 bits 325 This field is reserved. It MUST be set to zero on transmission and 326 MUST be ignored on receipt. 328 Length: 16 bits 330 The total length of this field in bytes. 332 RB Identifier: 334 The RB identifier represents the ID of the resource block which is a 335 16 bit integer. 337 4.1. Block Accessibility Sub-TLV 339 This sub-TLV describes the structure of the resource pool in relation 340 to the switching device. In particular it indicates the ability of an 341 ingress port to reach a resource block and of a resource block to 342 reach a particular egress port. This is the PoolIngressMatrix and 343 PoolEgressMatrix of [WSON-Info]. 345 The resource block accessibility sub-TLV 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 | Connectivity | Reserved | 351 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 352 | Ingress Link Set Field A #1 | 353 : : 354 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 355 | RB Set Field A #1 | 356 : : 357 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 358 | Additional Link set and RB set pairs as needed to | 359 : specify PoolIngressMatrix : 360 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 361 | Egress Link Set Field B #1 | 362 : : 363 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 364 | RB Set B Field #1 (for egress connectivity) | 365 : : 366 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 367 | Additional Link Set and RB set pairs as needed to | 368 : specify PoolEgressMatrix : 369 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 371 Where 373 Connectivity indicates how the ingress/egress ports connect to the 374 resource blocks. 376 0 -- the device is fixed (e.g. a connected port must go through 377 the resource block) 379 1 -- the device is switched(e.g., a port can be configured to 380 go through a resource but isn't required ) 382 The Link Set Field is defined in [Gen-Encode]. 384 Note that the direction parameter within the Link Set Field is used 385 to indicate whether the link set is an ingress or egress link set, 386 and the bidirectional value for this parameter is not permitted in 387 this sub-TLV. 389 See Appendix A.1 for an illustration of this encoding. 391 4.2. Wavelength Constraints Sub-TLV 393 Resources, such as wavelength converters, etc., may have a limited 394 input or output wavelength ranges. Additionally, due to the structure 395 of the optical system not all wavelengths can necessarily reach or 396 leave all the resources. These properties are described by using one 397 or more resource wavelength restrictions sub-TLVs as defined below: 399 0 1 2 3 400 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 401 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 402 | RB Set Field | 403 : : 404 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 405 | Input Wavelength Set Field | 406 : : 407 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 408 | Output Wavelength Set Field | 409 : : 410 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 412 RB Set Field: 414 A set of resource blocks (RBs) which have the same wavelength 415 restrictions. 417 Input Wavelength Set Field: 419 Indicates the wavelength input restrictions of the RBs in the 420 corresponding RB set. 422 Output Wavelength Set Field: 424 Indicates the wavelength output restrictions of RBs in the 425 corresponding RB set. 427 4.3. Block Pool State Sub-TLV 429 The usage state of a resource is encoded as either a list of 16 bit 430 integer values or a bit map indicating whether a single resource is 431 available or in use. This information can be relatively dynamic, 432 i.e., can change when a connection is established or torn down. 434 0 1 2 3 435 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 436 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 437 | Action | Reserved | 438 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 439 | RB Set Field | 440 : : 441 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 442 | RB Usage state | 443 : : 444 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 446 Where Action = 0 denotes a list of 16 bit integers and Action = 1 447 denotes a bit map. In both cases the elements of the RB Set field are 448 in a one-to-one correspondence with the values in the usage RB usage 449 state area. 451 0 1 2 3 452 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 453 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 454 | Action = 0 | Reserved | 455 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 456 | RB Set Field | 457 : : 458 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 459 | RB#1 state | RB#2 state | 460 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 461 : : 462 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 463 | RB#n-1 state | RB#n state or Padding | 464 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 466 Whether the last 16 bits is a wavelength converter (RB) state or 467 padding is determined by the number of elements in the RB set field. 469 0 1 2 3 470 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 471 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 472 | Action = 1 | Reserved | 473 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 474 | RB Set Field | 475 : : 476 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 477 | RB Usage state bitmap | 478 : : 480 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 481 | ...... | Padding bits | 482 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 484 RB Usage state: Variable Length but must be a multiple of 4 byes. 486 Each bit indicates the usage status of one RB with 0 indicating the 487 RB is available and 1 indicating the RB is in used. The sequence of 488 the bit map is ordered according to the RB Set field with this sub- 489 TLV. 491 Padding bits: Variable Length 493 4.4. Block Shared Access Wavelength Availability sub-TLV 495 Resources blocks may be accessed via a shared fiber. If this is the 496 case then wavelength availability on these shared fiber is needed to 497 understand resource availability. 499 0 1 2 3 500 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 501 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 502 | Resource Block ID |I|E| Reserved | 503 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 504 | Ingress Available Wavelength Set Field | 505 : : 506 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 507 | Egress Available Wavelength Set Field | 508 : : 509 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 511 Resource Block ID: 513 The 16 bit integer used to identify a particular resource block. 515 I bit: 517 Indicates whether the ingress available wavelength set field is 518 included (1) or not (0). 520 E bit: 522 Indicates whether the egress available wavelength set field is 523 included (1) or not (0). 525 Ingress Available Wavelength Set Field: 527 Indicates the wavelengths currently available (not being used) on the 528 ingress fiber to this resource block. 530 Egress Available Wavelength Set Field: 532 Indicates the wavelengths currently available (not being used) on the 533 egress fiber from this resource block. 535 5. Resource Properties Encoding 537 Within a WSON network element (NE) there may be resources with signal 538 compatibility constraints. Such resources typically come in "blocks" 539 which contain a group on identical and indistinguishable individual 540 resources. These resource blocks may consist of regenerators, 541 wavelength converters, etc... Such resource blocks may also 542 constitute the network element as a whole as in the case of an 543 electro optical switch. In this section we primarily focus on the 544 signal compatibility and processing properties of such a resource 545 block, i.e., of section 3.1. the accessibility 546 aspects of a resource in a shared pool, except for the shared access 547 indicators, were encoded in the previous section. 549 The fundamental properties of a resource block, such as a regenerator 550 or wavelength converter, are: 552 (a)Input constraints (shared ingress, modulation, FEC, bit rate, 553 GPID) 555 (b)Processing capabilities (number of resources in a block, 556 regeneration, performance monitoring, vendor specific) 558 (c)Output Constraints (shared egress, modulation, FEC) 560 5.1. Resource Block Information Sub-TLV 562 Resource Block descriptor sub-TLVs are used to convey relatively 563 static information about individual resource blocks including the 564 resource block properties of section 3. and the number of resources 565 in a block. 567 This sub-TLV has the following format: 569 0 1 2 3 570 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 571 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 572 | RB Set Field | 573 : : 574 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 575 |I|E| Reserved | 576 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 577 | Input Modulation Type List Sub-Sub-TLV (opt) | 578 : : 579 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 580 | Input FEC Type List Sub-Sub-TLV (opt) | 581 : : 582 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 583 | Input Client Signal Type Sub-TLV (opt) | 584 : : 585 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 586 | Input Bit Rate Range List Sub-Sub-TLV (opt) | 587 : : 588 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 589 | Processing Capabilities List Sub-Sub-TLV (opt) | 590 : : 591 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 592 | Output Modulation Type List Sub-Sub-TLV (opt) | 593 : : 594 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 595 | Output FEC Type List Sub-Sub-TLV (opt) | 596 : : 597 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 599 Where I and E, the shared ingress/egress indicator, is set to 1 if 600 the resource blocks identified in the RB set field utilized a shared 601 fiber for ingress/egress access and set to 0 otherwise. 603 5.2. Input Modulation Format List Sub-Sub-TLV 605 This sub-TLV contains a list of acceptable input modulation formats. 607 Type := Input Modulation Format List 609 Value:= A list of Modulation Format Fields 610 5.2.1. Modulation Format Field 612 Two different types of modulation format fields are defined: a 613 standard modulation field and a vendor specific modulation field. 614 Both start with the same 32 bit header shown below. 616 0 1 2 3 617 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 618 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 619 |S|I| Modulation ID | Length | 620 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 622 Where S bit set to 1 indicates a standardized modulation format and S 623 bit set to 0 indicates a vendor specific modulation format. The 624 length is the length in bytes of the entire modulation type field. 626 Where I bit set to 1 indicates it is an input modulation constraint 627 and I bit set to 0 indicates it is an output modulation constraint. 629 Note that if an output modulation is not specified then it is implied 630 that it is the same as the input modulation. In such case, no 631 modulation conversion is performed. 633 The format for the standardized type for the input modulation is 634 given by: 636 0 1 2 3 637 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 638 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 639 |1|1| Modulation ID | Length | 640 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 641 | Possible additional modulation parameters depending upon | 642 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 643 : the modulation ID : 644 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 646 Modulation ID (S bit = 1); Input modulation (I bit = 1) 648 Takes on the following currently defined values: 650 0 Reserved 652 1 optical tributary signal class NRZ 1.25G 653 2 optical tributary signal class NRZ 2.5G 655 3 optical tributary signal class NRZ 10G 657 4 optical tributary signal class NRZ 40G 659 5 optical tributary signal class RZ 40G 661 Note that future modulation types may require additional parameters 662 in their characterization. 664 The format for vendor specific modulation field (for input 665 constraint) is given by: 667 0 1 2 3 668 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 669 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 670 |0|1| Vendor Modulation ID | Length | 671 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 672 | Enterprise Number | 673 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 674 : Any vendor specific additional modulation parameters : 675 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 677 Vendor Modulation ID 679 This is a vendor assigned identifier for the modulation type. 681 Enterprise Number 683 A unique identifier of an organization encoded as a 32-bit integer. 684 Enterprise Numbers are assigned by IANA and managed through an IANA 685 registry [RFC2578]. 687 Vendor Specific Additional parameters 689 There can be potentially additional parameters characterizing the 690 vendor specific modulation. 692 5.3. Input FEC Type List Sub-Sub-TLV 694 This sub-TLV contains a list of acceptable FEC types. 696 Type := Input FEC Type field List 698 Value:= A list of FEC type Fields 700 5.3.1. FEC Type Field 702 The FEC type Field may consist of two different formats of fields: a 703 standard FEC field or a vendor specific FEC field. Both start with 704 the same 32 bit header shown below. 706 0 1 2 3 707 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 708 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 709 |S|I| FEC ID | Length | 710 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 711 | Possible additional FEC parameters depending upon | 712 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 713 : the FEC ID : 714 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 716 Where S bit set to 1 indicates a standardized FEC format and S bit 717 set to 0 indicates a vendor specific FEC format. The length is the 718 length in bytes of the entire FEC type field. 720 Where I bit set to 1 indicates it is an input FEC constraint and I 721 bit set to 0 indicates it is an output FEC constraint. 723 Note that if an output FEC is not specified then it is implied that 724 it is the same as the input FEC. In such case, no FEC conversion is 725 performed. 727 The length is the length in bytes of the entire FEC type field. 729 The format for input standard FEC field is given by: 731 0 1 2 3 732 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 733 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 734 |1|1| FEC ID | Length | 735 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 736 | Possible additional FEC parameters depending upon | 737 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 738 : the FEC ID : 739 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 741 Takes on the following currently defined values for the standard 742 FEC ID: 744 0 Reserved 746 1 G.709 RS FEC 748 2 G.709V compliant Ultra FEC 750 3 G.975.1 Concatenated FEC 751 (RS(255,239)/CSOC(n0/k0=7/6,J=8)) 753 4 G.975.1 Concatenated FEC (BCH(3860,3824)/BCH(2040,1930)) 755 5 G.975.1 Concatenated FEC (RS(1023,1007)/BCH(2407,1952)) 757 6 G.975.1 Concatenated FEC (RS(1901,1855)/Extended Hamming 758 Product Code (512,502)X(510,500)) 760 7 G.975.1 LDPC Code 762 8 G.975.1 Concatenated FEC (Two orthogonally concatenated 763 BCH codes) 765 9 G.975.1 RS(2720,2550) 767 10 G.975.1 Concatenated FEC (Two interleaved extended BCH 768 (1020,988) codes) 770 Where RS stands for Reed-Solomon and BCH for Bose-Chaudhuri- 771 Hocquengham. 773 The format for input vendor-specific FEC field is given by: 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 |0|1| Vendor FEC ID | Length | 779 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 780 | Enterprise Number | 781 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 782 : Any vendor specific additional FEC parameters : 783 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 785 Vendor FEC ID 787 This is a vendor assigned identifier for the FEC type. 789 Enterprise Number 791 A unique identifier of an organization encoded as a 32-bit integer. 792 Enterprise Numbers are assigned by IANA and managed through an IANA 793 registry [RFC2578]. 795 Vendor Specific Additional FEC parameters 797 There can be potentially additional parameters characterizing the 798 vendor specific FEC. 800 5.4. Input Bit Range List Sub-Sub-TLV 802 This sub-TLV contains a list of acceptable input bit rate ranges. 804 Type := Input Bit Range List 806 Value:= A list of Bit Range Fields 808 5.4.1. Bit Range Field 810 The bit rate range list sub-TLV makes use of the following bit rate 811 range field: 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 | Starting Bit Rate | 817 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 818 | Ending Bit Rate | 819 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 821 The starting and ending bit rates are given as 32 bit IEEE floating 822 point numbers in bits per second. Note that the starting bit rate is 823 less than or equal to the ending bit rate. 825 The bit rate range list sub-TLV is then given by: 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 | | 831 +-+-+-+-+-+-+-+-+-+-+-+-+ Bit Range Field #1 +-+-+-+-+-+-+-+-+-+ 832 | | 833 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 834 : : : 835 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 836 | | 837 +-+-+-+-+-+-+-+-+-+-+-+-+ Bit Range Field #M +-+-+-+-+-+-+-+-+-+ 838 | | 839 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 841 5.5. Input Client Signal List Sub-Sub-TLV 843 This sub-TLV contains a list of acceptable input client signal types. 845 Type := Input Client Signal List 847 Value:= A list of GPIDs 849 The acceptable client signal list sub-TLV is a list of Generalized 850 Protocol Identifiers (GPIDs). GPIDs are assigned by IANA and many are 851 defined in [RFC3471] and [RFC4328]. 853 0 1 2 3 854 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 855 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 856 | Number of GPIDs | GPID #1 | 857 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 858 : | : 859 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 860 | GPID #N | | 861 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 863 Where the number of GPIDs is an integer greater than or equal to one. 865 5.6. Processing Capability List Sub-Sub-TLV 867 This sub-TLV contains a list of resource block processing 868 capabilities. 870 Type := Processing Capabilities List 872 Value:= A list of Processing Capabilities Fields 874 The processing capability list sub-TLV is a list of WSON network 875 element (NE) that can perform signal processing functions including: 877 1. Number of Resources within the block 879 2. Regeneration capability 881 3. Fault and performance monitoring 883 4. Vendor Specific capability 885 Note that the code points for Fault and performance monitoring and 886 vendor specific capability are subject to further study. 888 5.6.1. Processing Capabilities Field 890 The processing capability field is then given by: 892 0 1 2 3 893 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 894 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 895 | Processing Cap ID | Length | 896 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 897 | Possible additional capability parameters depending upon | 898 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 899 : the processing ID : 900 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 902 When the processing Cap ID is "number of resources" the format is 903 simply: 905 0 1 2 3 906 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 907 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 908 | Processing Cap ID | Length = 8 | 909 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 910 | Number of resources per block | 911 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 913 When the processing Cap ID is "regeneration capability", the 914 following additional capability parameters are provided in the sub- 915 TLV: 917 0 1 2 3 918 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 919 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 920 | T | C | Reserved | 921 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 923 Where T bit indicates the type of regenerator: 925 T=0: Reserved 927 T=1: 1R Regenerator 929 T=2: 2R Regenerator 931 T=3: 3R Regenerator 933 Where C bit indicates the capability of regenerator: 935 C=0: Reserved 937 C=1: Fixed Regeneration Point 939 C=2: Selective Regeneration Point 941 Note that when the capability of regenerator is indicated to be 942 Selective Regeneration Pools, regeneration pool properties such as 943 ingress and egress restrictions and availability need to be 944 specified. This encoding is to be determined in the later revision. 946 5.7. Output Modulation Format List Sub-Sub-TLV 948 This sub-TLV contains a list of available output modulation formats. 950 Type := Output Modulation Format List 952 Value:= A list of Modulation Format Fields 954 5.8. Output FEC Type List Sub-Sub-TLV 956 This sub-TLV contains a list of output FEC types. 958 Type := Output FEC Type field List 960 Value:= A list of FEC type Fields 962 6. Security Considerations 964 This document defines protocol-independent encodings for WSON 965 information and does not introduce any security issues. 967 However, other documents that make use of these encodings within 968 protocol extensions need to consider the issues and risks associated 969 with, inspection, interception, modification, or spoofing of any of 970 this information. It is expected that any such documents will 971 describe the necessary security measures to provide adequate 972 protection. 974 7. IANA Considerations 976 TBD. Once our approach is finalized we may need identifiers for the 977 various sub-sub-TLVs. 979 8. Acknowledgments 981 This document was prepared using 2-Word-v2.0.template.dot. 983 APPENDIX A: Encoding Examples 985 A.1. Wavelength Converter Accessibility Sub-TLV 987 Example: 989 Figure 1 shows a wavelength converter pool architecture know as 990 "shared per fiber". In this case the ingress and egress pool matrices 991 are simply: 993 +-----+ +-----+ 994 | 1 1 | | 1 0 | 995 WI =| |, WE =| | 996 | 1 1 | | 0 1 | 997 +-----+ +-----+ 999 +-----------+ +------+ 1000 | |--------------------->| | 1001 | |--------------------->| C | 1002 /| | |--------------------->| o | 1003 /D+--->| |--------------------->| m | 1004 + e+--->| | | b |========> 1005 ========>| M| | Optical | +-----------+ | i | Port E1 1006 Port I1 + u+--->| Switch | | WC Pool | | n | 1007 \x+--->| | | +-----+ | | e | 1008 \| | +----+->|WC #1|--+---->| r | 1009 | | | +-----+ | +------+ 1010 | | | | +------+ 1011 /| | | | +-----+ | | | 1012 /D+--->| +----+->|WC #2|--+---->| C | 1013 + e+--->| | | +-----+ | | o | 1014 ========>| M| | | +-----------+ | m |========> 1015 Port I2 + u+--->| | | b | Port E2 1016 \x+--->| |--------------------->| i | 1017 \| | |--------------------->| n | 1018 | |--------------------->| e | 1019 | |--------------------->| r | 1020 +-----------+ +------+ 1021 Figure 1 An optical switch featuring a shared per fiber wavelength 1022 converter pool architecture. 1024 This wavelength converter pool can be encoded as follows: 1026 0 1 2 3 1027 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 1028 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1029 | Connectivity=1| Reserved | 1030 Note: I1,I2 can connect to either WC1 or WC2 1031 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1032 | Action=0 |0 1|0 0 0 0 0 0| Length = 12 | 1033 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1034 | Link Local Identifier = #1 | 1035 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1036 | Link Local Identifier = #2 | 1037 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1038 | Action=0 |1| Reserved | Length = 8 | 1039 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1040 | RB ID = #1 | RB ID = #2 | 1041 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1042 Note: WC1 can only connect to E1 1043 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1044 | Action=0 |0| Reserved | Length = 8 | 1045 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1046 | RB ID = #1 | zero padding | 1047 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1048 | Action=0 |1 0|0 0 0 0 0 0| Length = 8 | 1049 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1050 | Link Local Identifier = #1 | 1051 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1052 Note: WC2 can only connect to E2 1053 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1054 | Action=0 |0| | Length = 8 | 1055 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1056 | RB ID = #2 | zero padding | 1057 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1058 | Action=0 |1 0|0 0 0 0 0 0| Length = 8 | 1059 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1060 | Link Local Identifier = #2 | 1061 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1063 A.2. Wavelength Conversion Range Sub-TLV 1065 Example: 1067 We give an example based on figure 1 about how to represent the 1068 wavelength conversion range of wavelength converters. Suppose the 1069 wavelength range of input and output of WC1 and WC2 are {L1, L2, L3, 1070 L4}: 1072 0 1 2 3 1073 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 1074 Note: WC Set 1075 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1076 | Action=0 |1| Reserved | Length = 8 | 1077 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1078 | WC ID = #1 | WC ID = #2 | 1079 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1080 Note: wavelength input range 1081 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1082 | 2 | Num Wavelengths = 4 | Length = 8 | 1083 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1084 |Grid | C.S. | Reserved | n for lowest frequency = 1 | 1085 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1086 Note: wavelength output range 1087 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1088 | 2 | Num Wavelengths = 4 | Length = 8 | 1089 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1090 |Grid | C.S. | Reserved | n for lowest frequency = 1 | 1091 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1093 A.3. An OEO Switch with DWDM Optics 1095 In Figure 2 we show an electronic switch fabric surrounded by DWDM 1096 optics. In this example the electronic fabric can can handle either 1097 G.709 or SDH signals only (2.5 or 10 Gbps). To describe this node we 1098 have the potential information: 1100 ::= [Other GMPLS sub- 1101 TLVs][...] [][] 1103 In this case there is complete port to port connectivity so the 1104 is not required. In addition since there are 1105 sufficient ports to handle all wavelength signals we will not need 1106 the element. 1108 Hence our attention will be focused on the sub-TLV: 1110 ::= 1111 [...][...] 1113 /| +-----------+ +-------------+ +------+ 1114 /D+--->| +--->|Tunable Laser|-->| | 1115 + e+--->| | +-------------+ | C | 1116 ========>| M| | | ... | o |========> 1117 Port I1 + u+--->| | +-------------+ | m | Port E1 1118 \x+--->| |--->|Tunable Laser|-->| b | 1119 \| | Electric | +-------------+ +------+ 1120 | Switch | 1121 /| | | +-------------+ +------+ 1122 /D+--->| +--->|Tunable Laser|-->| | 1123 + e+--->| | +-------------+ | C | 1124 ========>| M| | | ... | o |========> 1125 Port I2 + u+--->| | +-------------+ | m | Port E2 1126 \x+--->| +--->|Tunable Laser|-->| b | 1127 \| | | +-------------+ +------+ 1128 | | 1129 /| | | +-------------+ +------+ 1130 /D+--->| |--->|Tunable Laser|-->| | 1131 + e+--->| | +-------------+ | C | 1132 ========>| M| | | ... | o |========> 1133 Port I3 + u+--->| | +-------------+ | m | Port E3 1134 \x+--->| |--->|Tunable Laser|-->| b | 1135 \| +-----------+ +-------------+ +------+ 1137 Figure 2 An optical switch built around an electronic switching 1138 fabric. 1140 The resource block information will tell us about the processing 1141 constraints of the receivers, transmitters and the electronic switch. 1142 The resource availability information, although very simple, tells us 1143 that all signals must traverse the electronic fabric (fixed 1144 connectivity). The resource wavelength constraints are not needed 1145 since there are no special wavelength constraints for the resources 1146 that would not appear as port/wavelength constraints. 1148 : 1150 0 1 2 3 1151 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 1152 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1153 | RB Set Field | 1154 : (only one resource block in this example with shared | 1155 | input/output case) | 1156 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1157 |0|0| Reserved | 1158 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1159 | Input Modulation Type List Sub-Sub-TLV | 1160 : (The receivers can only process NRZ) : 1161 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1162 | Input FEC Type List Sub-Sub-TLV | 1163 : (Only Standard SDH and G.709 FECs) : 1164 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1165 | Input Client Signal Type Sub-TLV | 1166 : (GPIDs for SDH and G.709) : 1167 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1168 | Input Bit Rate Range List Sub-Sub-TLV | 1169 : (2.5Gbps, 10Gbps) : 1170 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1171 | Processing Capabilities List Sub-Sub-TLV | 1172 : Fixed (non optional) 3R regeneration : 1173 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1174 | Output Modulation Type List Sub-Sub-TLV | 1175 : NRZ : 1176 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1177 | Output FEC Type List Sub-Sub-TLV | 1178 : Standard SDH, G.709 FECs : 1179 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1181 Since we have fixed connectivity to resource block (the electronic 1182 switch) we get : 1184 0 1 2 3 1185 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 1186 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1187 | Connectivity=1|Reserved | 1188 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1189 | Ingress Link Set Field A #1 | 1190 : (All ingress links connect to resource) : 1191 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1192 | RB Set Field A #1 | 1193 : (trivial set only one resource block) : 1194 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1195 | Egress Link Set Field B #1 | 1196 : (All egress links connect to resource) : 1197 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1199 9. References 1201 9.1. Normative References 1203 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1204 Requirement Levels", BCP 14, RFC 2119, March 1997. 1206 [RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 1207 "Structure of Management Information Version 2 (SMIv2)", 1208 STD 58, RFC 2578, April 1999. 1210 [RFC3471] Berger, L., "Generalized Multi-Protocol Label Switching 1211 (GMPLS) Signaling Functional Description", RFC 3471, 1212 January 2003. 1214 [RFC4328] Papadimitriou, D., Ed., "Generalized Multi-Protocol Label 1215 Switching (GMPLS) Signaling Extensions for G.709 Optical 1216 Transport Networks Control", RFC 4328, January 2006. 1218 [G.694.1] ITU-T Recommendation G.694.1, "Spectral grids for WDM 1219 applications: DWDM frequency grid", June, 2002. 1221 9.2. Informative References 1223 [G.694.1] ITU-T Recommendation G.694.1, Spectral grids for WDM 1224 applications: DWDM frequency grid, June 2002. 1226 [G.694.2] ITU-T Recommendation G.694.2, Spectral grids for WDM 1227 applications: CWDM wavelength grid, December 2003. 1229 [Gen-Encode] G. Bernstein, Y. Lee, D. Li, W. Imajuku, "General 1230 Network Element Constraint Encoding for GMPLS Controlled 1231 Networks", work in progress: draft-ietf-ccamp-general-ext- 1232 encode-00.txt. 1234 [Otani] T. Otani, H. Guo, K. Miyazaki, D. Caviglia, "Generalized 1235 Labels for G.694 Lambda-Switching Capable Label Switching 1236 Routers", work in progress: draft-ietf-ccamp-gmpls-g-694- 1237 lambda-labels. 1239 [WSON-Frame] Y. Lee, G. Bernstein, W. Imajuku, "Framework for GMPLS 1240 and PCE Control of Wavelength Switched Optical Networks", 1241 work in progress: draft-ietf-ccamp-wavelength-switched- 1242 framework, Marh 2009. 1244 [WSON-Info] G. Bernstein, Y. Lee, D. Li, W. Imajuku, "Routing and 1245 Wavelength Assignment Information Model for Wavelength 1246 Switched Optical Networks", work in progress: draft-ietf- 1247 ccamp-rwa-info, March 2009. 1249 10. Contributors 1251 Diego Caviglia 1252 Ericsson 1253 Via A. Negrone 1/A 16153 1254 Genoa Italy 1256 Phone: +39 010 600 3736 1257 Email: diego.caviglia@(marconi.com, ericsson.com) 1259 Anders Gavler 1260 Acreo AB 1261 Electrum 236 1262 SE - 164 40 Kista Sweden 1264 Email: Anders.Gavler@acreo.se 1266 Jonas Martensson 1267 Acreo AB 1268 Electrum 236 1269 SE - 164 40 Kista, Sweden 1271 Email: Jonas.Martensson@acreo.se 1273 Itaru Nishioka 1274 NEC Corp. 1275 1753 Simonumabe, Nakahara-ku, Kawasaki, Kanagawa 211-8666 1276 Japan 1278 Phone: +81 44 396 3287 1279 Email: i-nishioka@cb.jp.nec.com 1281 Authors' Addresses 1283 Greg M. Bernstein (ed.) 1284 Grotto Networking 1285 Fremont California, USA 1287 Phone: (510) 573-2237 1288 Email: gregb@grotto-networking.com 1290 Young Lee (ed.) 1291 Huawei Technologies 1292 1700 Alma Drive, Suite 100 1293 Plano, TX 75075 1294 USA 1296 Phone: (972) 509-5599 (x2240) 1297 Email: ylee@huawei.com 1299 Dan Li 1300 Huawei Technologies Co., Ltd. 1301 F3-5-B R&D Center, Huawei Base, 1302 Bantian, Longgang District 1303 Shenzhen 518129 P.R.China 1305 Phone: +86-755-28973237 1306 Email: danli@huawei.com 1308 Wataru Imajuku 1309 NTT Network Innovation Labs 1310 1-1 Hikari-no-oka, Yokosuka, Kanagawa 1311 Japan 1313 Phone: +81-(46) 859-4315 1314 Email: imajuku.wataru@lab.ntt.co.jp 1315 Jianrui Han 1316 Huawei Technologies Co., Ltd. 1317 F3-5-B R&D Center, Huawei Base, 1318 Bantian, Longgang District 1319 Shenzhen 518129 P.R.China 1321 Phone: +86-755-28972916 1322 Email: hanjianrui@huawei.com 1324 Intellectual Property Statement 1326 The IETF Trust takes no position regarding the validity or scope of 1327 any Intellectual Property Rights or other rights that might be 1328 claimed to pertain to the implementation or use of the technology 1329 described in any IETF Document or the extent to which any license 1330 under such rights might or might not be available; nor does it 1331 represent that it has made any independent effort to identify any 1332 such rights. 1334 Copies of Intellectual Property disclosures made to the IETF 1335 Secretariat and any assurances of licenses to be made available, or 1336 the result of an attempt made to obtain a general license or 1337 permission for the use of such proprietary rights by implementers or 1338 users of this specification can be obtained from the IETF on-line IPR 1339 repository at http://www.ietf.org/ipr 1341 The IETF invites any interested party to bring to its attention any 1342 copyrights, patents or patent applications, or other proprietary 1343 rights that may cover technology that may be required to implement 1344 any standard or specification contained in an IETF Document. Please 1345 address the information to the IETF at ietf-ipr@ietf.org. 1347 Disclaimer of Validity 1349 All IETF Documents and the information contained therein are provided 1350 on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE 1351 REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE 1352 IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL 1353 WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY 1354 WARRANTY THAT THE USE OF THE INFORMATION THEREIN WILL NOT INFRINGE 1355 ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS 1356 FOR A PARTICULAR PURPOSE. 1358 Acknowledgment 1360 Funding for the RFC Editor function is currently provided by the 1361 Internet Society.