idnits 2.17.1 draft-agraz-ccamp-wson-impairment-ospf-00.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 : ---------------------------------------------------------------------------- ** There are 3 instances of too long lines in the document, the longest one being 4 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (July 5, 2010) is 5044 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Missing Reference: 'RFC3473' is mentioned on line 556, but not defined == Missing Reference: 'RFC4203' is mentioned on line 556, but not defined == Missing Reference: 'RFC4205' is mentioned on line 556, but not defined ** Obsolete undefined reference: RFC 4205 (Obsoleted by RFC 5307) == Missing Reference: 'RFC4204' is mentioned on line 557, but not defined == Missing Reference: 'RFC5440' is mentioned on line 557, but not defined == Missing Reference: 'GMPLS-SEC' is mentioned on line 557, but not defined == Unused Reference: 'RFC3630' is defined on line 574, but no explicit reference was found in the text == Outdated reference: A later version (-11) exists of draft-ietf-ccamp-gmpls-g-694-lambda-labels-07 Summary: 2 errors (**), 0 flaws (~~), 9 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group Fernando Agraz 2 Internet Draft UPC 3 Category: Informational Yabin Ye 4 Huawei 5 Expires: January 4, 2011 July 5, 2010 7 OSPF Extensions in Support of Impairment Aware Routing and Wavelength 8 Assignment in Wavelength Switched Optical Networks (WSONs) 10 draft-agraz-ccamp-wson-impairment-ospf-00.txt 12 Status of this Memo 14 This Internet-Draft is submitted to IETF in full conformance with 15 the provisions of BCP 78 and BCP 79. 17 Internet-Drafts are working documents of the Internet Engineering 18 Task Force (IETF), its areas, and its working groups. Note that 19 other groups may also distribute working documents as Internet- 20 Drafts. 22 Internet-Drafts are draft documents valid for a maximum of six months 23 and may be updated, replaced, or obsoleted by other documents at any 24 time. It is inappropriate to use Internet-Drafts as reference 25 material or to cite them other than as "work in progress." 27 The list of current Internet-Drafts can be accessed at 28 http://www.ietf.org/ietf/1id-abstracts.txt. 30 The list of Internet-Draft Shadow Directories can be accessed at 31 http://www.ietf.org/shadow.html. 33 This Internet-Draft will expire on September 30, 2010. 35 Abstract 37 This document provides OSPF extensions to support Generalized Multi- 38 Protocol Label Switching (GMPLS) and Path Computation Element (PCE) 39 control of Impairment Aware Routing and Wavelength Assignment in 40 Wavelength Switched Optical Networks (WSONs). 42 Table of Contents 44 1. Introduction................................................2 45 2. OSPF-TE Extensions..........................................2 46 2.1. The Link PLI TLV........................................2 47 2.2. The Node PLI TLV........................................5 48 2.3. The sub-TLVs...........................................7 49 2.3.1. Link ID sub-TLV....................................7 50 2.3.2. Local Interface IP sub-TLV.........................7 51 2.3.3. Remote Interface IP sub-TLV........................8 52 2.3.4. Component Impairment sub-TLV.......................9 53 2.3.5. The Impairment Parameters.........................11 54 3. Security Considerations.....................................14 55 4. IANA Considerations........................................14 56 5. Acknowledgments............................................14 57 6. References.................................................15 58 6.1. Normative References...................................15 59 6.2. Informative References.................................15 60 7. Authors' Addresses.........................................15 62 1. Introduction 64 [Imp-Frame] provides a framework for applying GMPLS and the Path 65 Computation Element architecture to the control of WSONs to address 66 the Impairment Aware RWA problem. This document defines extensions to 67 the OSPF routing protocol to distribute physical layer impairments 68 (PLI) information which will be used in the path computation process 69 for GMPLS or PCE control case. 71 The protocol extensions is implemented and emulated in the "Dynamic 72 Impairment Constraint Networking for Transparent Mesh Optical 73 Networks" (DICONET) project which is funded by European commission 74 through the 7th Framework programme. The intent of this document is 75 to show the result of DICONET project and provide an input related to 76 OSPF extensions for CCAMP in IETF. 78 2. OSPF-TE Extensions 80 Two top-TLVs are defined to describe PLI, the Link PLI TLV and the 81 Node PLI TLV, each of which is composed of several sub-TLVs. Note 82 that each PLI LSA instance can only contain one top-TLV. 84 2.1. The Link PLI TLV 86 The Link PLI TLV describes the physical layer impairments related to 87 the link. Each link in the network may have its own Link PLI TLV and 88 it will be flooded into the network. It is stored in the database of 89 each node as a composition of the PLI LSA. The Link PLI TLV is 90 composed of Link ID sub-TLV, Local Interface IP sub-TLV, Remote 91 Interface IP sub-TLV and Component Impairment sub-TLV, as shown in 92 Figure 1. 94 Link ID Sub-TLV must appear exactly once in the Top-TLV and must be 95 the first Sub-TLV in the Top-TLV. Local interface IP address Sub-TLV 96 must appear exactly once in the Top-TLV and must be the second Sub- 97 TLV in the Top-TLV. Remote interface IP address Sub-TLV must appear 98 exactly once in the Top-TLV and must be the third Sub-TLV in the Top- 99 TLV. If the link passes through more than one component, there would 100 be more than one Component Sub-TLV, which is ordered. 102 Y---------------------------------------------------------------Y 103 | +-----------------------------------+ | 104 | |PLI LSA Hearder | | 105 | +-----------------------------------+ | 106 | Y----------------------------------------------------------Y | 107 | | TOP TLV (Link PLI TLV, type = 2) | | 108 | | +-----------------------------------+ | | 109 | | |Link ID sub-TL | | | 110 | | +-----------------------------------+ | | 111 | | |Local interface IP sub-TL | | | 112 | | +-----------------------------------+ | | 113 | | |Remote interface IP sub-TL | | | 114 | | +-----------------------------------+ | | 115 | | Y-----------------------------------------------------Y | | 116 | | | Componet Impairment sub-TLV | | | 117 | | | +-----------------------------------+ | | | 118 | | | |Component ID | | | | 119 | | | +-----------------------------------+ | | | 120 | | | Y----------------------------------------------Y | | | 121 | | | | Wavelength unrelated Impairment sub-sub-TLV | | | | 122 | | | | +-----------------------------------+ | | | | 123 | | | | |Parameter sub-sub-sub-TL | | | | | 124 | | | | +-----------------------------------+ | | | | 125 | | | | |Other Parameter sub-sub-sub-TLV | | | | | 126 | | | | +-----------------------------------+ | | | | 127 | | | Y----------------------------------------------Y | | | 128 | | | Y-----------------------------------------------Y | | | 129 | | | | Wavelength related Impairment sub-sub-TLV | | | | 130 | | | | +------------------------------------+ | | | | 131 | | | | |Wavelength # | | | | | 132 | | | | +------------------------------------+ | | | | 133 | | | | |Parameter sub-sub-sub-TL | | | | | 134 | | | | +------------------------------------+ | | | | 135 | | | | |Other Parameter sub-sub-sub-TLV | | | | | 136 | | | | +------------------------------------+ | | | | 137 | | | Y-----------------------------------------------Y | | | 138 | | | Y-----------------------------------------------Y | | | 139 | | | | Wavelength related Impairment sub-sub-TLV | | | | 140 | | | | +------------------------------------+ | | | | 141 | | | | |Wavelength # | | | | | 142 | | | | +------------------------------------+ | | | | 143 | | | | |Parameter sub-sub-sub-TL | | | | | 144 | | | | +------------------------------------+ | | | | 145 | | | | |Other Parameter sub-sub-sub-TLV | | | | | 146 | | | | +------------------------------------+ | | | | 147 | | | Y-----------------------------------------------Y | | | 148 | | | +------------------------------------------------+ | | | 149 | | | |Other Wavelength_related Impairment sub-sub-TLVs| | | | 150 | | | +------------------------------------------------+ | | | 151 | | Y-----------------------------------------------------Y | | 152 | | +--------------------------------------+ | | 153 | | |Other Component sub-TL | | | 154 | | +--------------------------------------+ | | 155 | Y----------------------------------------------------------Y | 156 Y---------------------------------------------------------------Y 157 Figure 1. The composition of Link PLI TLV 159 2.2. The Node PLI TLV 161 The Node PLI TLV describes the physical layer impairments related to 162 the node. Each node in the network may have its own Node PLI TLV and 163 it will be flooded into the network. It is also stored in the 164 database of each node as a composition of the PLI LSA. The Node PLI 165 TLV is composed of Node IP sub-TLV and Component Impairment sub-TLV, 166 as shown in Figure 2. 168 Y---------------------------------------------------------------Y 169 | +-----------------------------------+ | 170 | |PLI LSA Hearder | | 171 | +-----------------------------------+ | 172 | Y----------------------------------------------------------Y | 173 | | TOP TLV (Node PLI TLV, type = 1) | | 174 | | +-----------------------------------+ | | 175 | | |Node IP sub-TLV | | | 176 | | +-----------------------------------+ | | 177 | | Y-----------------------------------------------------Y | | 178 | | | Component Impairment sub-TLV | | | 179 | | | +-----------------------------------+ | | | 180 | | | |Component ID | | | | 181 | | | +-----------------------------------+ | | | 182 | | | Y----------------------------------------------Y | | | 183 | | | | Wavelength unrelated Impairment sub-sub-TLV | | | | 184 | | | | +-----------------------------------+ | | | | 185 | | | | |Parameter sub-sub-sub-TLV | | | | | 186 | | | | +-----------------------------------+ | | | | 187 | | | | |Other Parameter sub-sub-sub-TLV | | | | | 188 | | | | +-----------------------------------+ | | | | 189 | | | Y----------------------------------------------Y | | | 190 | | | Y-----------------------------------------------Y | | | 191 | | | | Wavelength related Impairment sub-sub-TLV | | | | 192 | | | | +------------------------------------+ | | | | 193 | | | | |Wavelength # | | | | | 194 | | | | +------------------------------------+ | | | | 195 | | | | |Parameter sub-sub-sub-TLV | | | | | 196 | | | | +------------------------------------+ | | | | 197 | | | | |Other Parameter sub-sub-sub-TLV | | | | | 198 | | | | +------------------------------------+ | | | | 199 | | | Y-----------------------------------------------Y | | | 200 | | | Y-----------------------------------------------Y | | | 201 | | | | Wavelength related Impairment sub-sub-TLV | | | | 202 | | | | +------------------------------------+ | | | | 203 | | | | |Wavelength # | | | | | 204 | | | | +------------------------------------+ | | | | 205 | | | | |Parameter sub-sub-sub-TLV | | | | | 206 | | | | +------------------------------------+ | | | | 207 | | | | |Other Parameter sub-sub-sub-TLV | | | | | 208 | | | | +------------------------------------+ | | | | 209 | | | Y-----------------------------------------------Y | | | 210 | | | +------------------------------------------------+ | | | 211 | | | |Other Wavelength_related Impairment sub-sub-TLVs| | | | 212 | | | +------------------------------------------------+ | | | 213 | | Y-----------------------------------------------------Y | | 214 | | +--------------------------------------+ | | 215 | | |Other Component sub-TLV | | | 216 | | +--------------------------------------+ | | 217 | Y----------------------------------------------------------Y | 218 Y---------------------------------------------------------------Y 219 Figure 2. The composition of Node PLI TLV 221 Node IP Sub-TLV must appear exactly once in the Top-TLV and must be 222 the first Sub-TLV in the Top-TLV. Currently there is only one 223 Component impairment sub-TLV (describing the impairment information 224 of a Physical node) will be included. 226 2.3. The sub-TLVs 228 There are five kinds of sub-TLVs: 230 2.3.1. Link ID sub-TLV 232 The Link ID sub-TLV is the composition of the Link PLI TLV, as shown 233 in Figure 3. 235 0 1 2 3 236 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 237 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 238 |Sub-TLV Type (link ID sub TLV) | Sub TLV length | 239 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 240 | Link Id | 241 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 242 Figure 3. Link ID sub-TLV Format 244 The link ID is the same format as defined in RFC3630, where: 246 Sub-TLV type = 2 248 Sub-TLV length = 4 250 Link ID = remote router (node) IP address 252 2.3.2. Local Interface IP sub-TLV 254 The Local Interface IP sub-TLV is the composition of the Link PLI TLV, 255 as shown in Figure 4. 257 0 1 2 3 258 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 259 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 260 | Sub-TLV Type | Sub TLV length | 261 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 262 | Local interface IP address | 263 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 264 Figure 4. Local Interface IP sub-TLV Format 266 The Local interface IP sub-TLV is the same format as defined in 267 RFC3630, where: 269 Sub-TLV type = 3 271 Sub-TLV length = 4 273 Local interface IP address = the IP address of local interface of the 274 link 276 2.3.3. Remote Interface IP sub-TLV 278 The Remote Interface IP sub-TLV is the composition of the Link PLI 280 TLV, as shown in Figure 5 282 0 1 2 3 283 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 284 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 285 | Sub-TLV Type | Sub TLV length | 286 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 287 | Remote interface IP address | 288 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 289 Figure 5. Remote Interface IP sub-TLV Format 291 The Remote interface IP sub-TLV is the same format as defined in 292 RFC3630, where: 294 Sub-TLV type = 4 296 Sub-TLV length = 4 298 Remote interface IP address = the IP address of remote interface of 299 the link. If the remote interface IP is unknown, this field will fill 300 with 0 302 2.3.4. Component Impairment sub-TLV 304 The Component impairments sub-TLV is the composition of both the Link 305 PLI TLV and the Node PLI TLV, as shown in Figure 6. 307 0 1 2 3 308 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 309 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 310 |1|1|1|0|Rvd |S| Component Type| Sub-TLV length | 311 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 312 | Component ID | 313 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 314 | Values | 315 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 316 Figure 6. Component impairments sub-TLV Format 318 The Component Sub-TLV is used to describe all the impairment 319 parameters of one component located on the link identified by Link ID 320 and Local/Remote interface IP address in the Link PLI TLV or describe 321 all the impairment parameters of one component located in the node 322 identified by Node IP address in the Node PLI TLV. For the Link PLI 323 TLV, if the link passes through more than one component, there will 324 be more than one Component Sub-TLV. For the Node PLI TLV, there is 325 only one component (Physical node) currently. But for the 326 extensibility of the protocol, more than one component sub-TLV is 327 allowed: 329 Rvd = Reserved 331 S = the status of the component: 333 0 = unavailable 335 1 = available 337 Component Type: 339 For the Link PLI TLV: 341 0 = Transmitter 343 1 = Fiber 345 2 = DCM 347 3 = Attenuator 348 4 = Receiver 350 5 = Amplifier 352 For the Node PLI TLV: 354 8 = Physical node 356 Sub-TLV length = the total length of the Component ID filed and Value 357 field in Byte (variable) 359 The first line (first 4 Bytes) after the header is the Component ID 361 Values: [Wavelength_unrelated Impairment Sub-sub-TLV, 362 Wavelength_related Impairment Sub-sub-TLV, Wavelength_related 363 Impairment Sub-sub-TLV, ...] 365 1. Wavelength_unrelated Impairment Sub-sub-TLV: 366 All the common impairment parameters unrelated to wavelength will 367 be put here. If no common impairment parameters, this Sub-sub-TLV 368 is not needed. 370 The Wavelength_unrelated Impairment Sub-sub-TLV is defined as 371 shown in Figure 7: 373 0 1 2 3 374 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 375 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 376 |Wavelength unrelated Sub-sub-TLV | Sub-TLV length | 377 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 378 | Values | 379 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 380 Figure 7. Wavelength_unrelated Impairment Sub-sub-TLV Format 382 The Wavelength_unrelated Sub-sub-TLV (=1): 384 (1) Sub-sub-TLV type = 1 385 (2) Sub-sub-TLV length = the total length of the Value field in 386 Byte (variable) 387 (3) Value :: Parameter Sub-sub-sub-TLV [, Parameter Sub-sub-sub- 388 TLV, ...] 390 2. Wavelength_related Impairment Sub-sub-TLV: 391 Typically, if there are N wavelengths in the link or node, then N 392 Wavelength_related Impairment Sub-sub-TLVs should be contained. It's 393 recommended to order the N Wavelength_related Impairment Sub-sub-TLVs 394 by the wavelength (from low to high). If no wavelength_related 395 impairment parameters, this Sub-sub-TLV is not needed. The 396 Wavelength_related Impairment Sub-sub-TLV is defined as shown in 397 Figure 8: 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 |Wavelength related Sub-sub-TLV | Sub-TLV length | 403 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 404 | Values | 405 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 406 Figure 8. Wavelength_related Impairment Sub-sub-TLV Format 408 The Wavelength_related Sub-sub-TLV (=2): 410 (1) impairment sub-sub-TLV type = 2 411 (2) Sub-sub-TLV length = the total length of the Value field in 412 Byte (variable) 413 (3) Value :: Wavelength, Parameter Sub-sub-sub-TLV [, Parameter 414 Sub-sub-sub-TLV, ...] 415 The first line (4 Bytes) of the Value field represents a Wavelength 416 with the format that is consistent with [WSON-Label]. One or more 417 Parameter Sub-sub-sub-TLVs are presented below the Wavelength. Each 418 Parameter Sub-sub-sub-TLV describes a special impairment parameter of 419 the component per wavelength 421 2.3.5. The Impairment Parameters 423 As mentioned in both the Wavelength_unrelated Sub-sub-TLV and the 424 Wavelength_related Sub-sub-TLV appears Impairment Parameter Sub-sub- 425 sub-TLV, s shown in Figure 9: 427 0 1 2 3 428 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 429 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 430 |1|1|0|1|Rvd |Parameter Type | Sub-sub-TLV length | 431 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 432 | Parameter Values | 433 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 434 Figure 9. Impairment Parameter Sub-sub-sub-TLV Format 436 For the Link PLI TLV, the Parameter Types are defined as shown in 437 Table I: 439 Table I. Table of Parameter Types for the Link PLI TLV 441 +---------------+-----------------------------+--------------+ 442 |Component Type | Parameter Type | Wavelength | 443 | | | Related? | 444 +---------------+-----------------------------+--------------+ 445 | | 1=BitRate | Related | 446 | +-----------------------------+--------------+ 447 | | 2=Power | Related | 448 | +-----------------------------+--------------+ 449 | | 3=Center wavelength | Related | 450 | | (for each channel) | | 451 | 1=Transmitter +-----------------------------+--------------+ 452 | | 4=RefWavelength | Unrelated | 453 | +-----------------------------+--------------+ 454 | | 5=Extinction ratio | Related | 455 | +-----------------------------+--------------+ 456 | | 6=Modulation format | Related | 457 | +-----------------------------+--------------+ 458 | | 7=Type of FEC | Related | 459 +---------------+-----------------------------+--------------+ 460 | | 21=fiber type | Unrelated | 461 | +-----------------------------+--------------+ 462 | | 22=fiber length | Unrelated | 463 | +-----------------------------+--------------+ 464 | | 23=Dispersion parameter | Unrelated | 465 | 1 = Fiber +-----------------------------+--------------+ 466 | or | 24=Dispersion slope | Unrelated | 467 | 2 = DCM +-----------------------------+--------------+ 468 | | 25=Linear attenuation | Unrelated | 469 | +-----------------------------+--------------+ 470 | | 26=Nonlinear parameter | Unrelated | 471 | +-----------------------------+--------------+ 472 | | 27=Effective core area | Unrelated | 473 | +-----------------------------+--------------+ 474 | | 28=PMD | Unrelated | 475 | +-----------------------------+--------------+ 476 | | 29=Insertion Loss | Unrelated | 477 +---------------+-----------------------------+--------------+ 478 | 3=Attenuator | 61=Attenuation | Related | 479 +---------------+-----------------------------+--------------+ 480 | | 81=Responsively | Related | 481 | +-----------------------------+--------------+ 482 | | 82=Absolute threshold level | Related | 483 | +-----------------------------+--------------+ 484 | | 83=Thermal noise density | Unrelated | 485 | +-----------------------------+--------------+ 486 | | 84=power | Related | 487 | +-----------------------------+--------------+ 488 | | 85=inner filter type | Unrelated | 489 | +-----------------------------+--------------+ 490 | | 86=inner filter order | Unrelated | 491 | +-----------------------------+--------------+ 492 | | 87= inner filter Noise | Unrelated | 493 | |equivalent bandwidth factor | | 494 | +-----------------------------+--------------+ 495 | 4=Receiver | 88= inner filter 3-dB | Related | 496 | | bandwidth | | 497 | +-----------------------------+--------------+ 498 | | 89=inner filter center | Related | 499 | |wavelength for each channel | | 500 | +-----------------------------+--------------+ 501 | | 90=PMD | Unrelated | 502 | +-----------------------------+--------------+ 503 | | 91=residualCD | Unrelated | 504 | +-----------------------------+--------------+ 505 | | 92=Q value for each channel | Related | 506 | +-----------------------------+--------------+ 507 | | 93=ver for each channel | Related | 508 | +-----------------------------+--------------+ 509 | | 94=Insertion Loss | Unrelated | 510 +---------------+-----------------------------+--------------+ 511 | |101=Spontaneous emission | Unrelated | 512 | | factor | | 513 | +-----------------------------+--------------+ 514 | |102=Amplifier Gain | Unrelated | 515 | +-----------------------------+--------------+ 516 | 5=Amplifier |103=Insertion Loss | Unrelated | 517 | +-----------------------------+--------------+ 518 | |104=in_power | Unrelated | 519 | +-----------------------------+--------------+ 520 | |105=out_power | Unrelated | 521 +---------------+-----------------------------+--------------+ 522 For the Node PLI TLV, the Parameter Types are defined as shown in 523 Table II: 525 Table II. Table of Parameter Types for the Node PLI TLV 527 +---------------+-----------------------------+--------------+ 528 |Component Type | Parameter Type | Wavelength | 529 | | | Related? | 530 +---------------+-----------------------------+--------------+ 531 | | 161 = inner filter type | Unrelated | 532 | +-----------------------------+--------------+ 533 | | 162 = inner filter order | Unrelated | 534 | +-----------------------------+--------------+ 535 | | 163 = Noise equivalent | Unrelated | 536 | | bandwidth factor | | 537 |8=Physical node+-----------------------------+--------------+ 538 | | 164 = 3-dB bandwidth | Related | 539 | +-----------------------------+--------------+ 540 | | 165 = center wavelength | Related | 541 | | for each channel | | 542 +---------------+-----------------------------+--------------+ 543 Note that table I and table II can be updated based on ITU-T 544 definition related to physical impairments. The TLV format do not 545 need to be changed when the physical impairments definition updated. 547 3. Security Considerations 549 The use of control plane protocols for signaling, routing, and path 550 computation opens an OTN to security threats through attacks on those 551 protocols. The data plane technology for an OTN does not introduce 552 any specific vulnerabilities, and so the control plane may be secured 553 using the mechanisms defined for the protocols discussed. 555 For further details of the specific security measures refer to the 556 documents that define the protocols ([RFC3473], [RFC4203], [RFC4205], 557 [RFC4204], and [RFC5440]). [GMPLS-SEC] provides an overview of 558 security vulnerabilities and protection mechanisms for the GMPLS 559 control plane. 561 4. IANA Considerations 563 This document makes not requests for IANA action. 565 5. Acknowledgments 567 This work is supported by DICONET project under FP7/2007-2013 - GA 568 nr 216338 570 6. References 572 6.1. Normative References 574 [RFC3630] Katz, D., Kompella, K., and Yeung, D., "Traffic 575 Engineering (TE) Extensions to OSPF Version 2", RFC 3630, 576 September 2003 577 6.2. Informative References 579 [Imp-Frame] G. Bernstein, Y. Lee, D. Li, G. Martinelli, "A 580 Framework for the Control and Measurement of Wavelength 581 Switched Optical Networks (WSON) with Impairments", Work 582 in Progress, draft-bernstein-ccamp-wson-impairments- 583 05.txt 585 [WSON-Label] Tomohiro Otani, Dan Li, "Generalized Labels for Lambda- 586 Switching Capable Label Switching Routers", Work in 587 Progress, draft-ietf-ccamp-gmpls-g-694-lambda-labels- 588 07.txt 590 7. Authors' Addresses 592 Fernando Agraz 593 Universitat Politecnica de Catalunya 594 C/Jordi Girona, 1-3 D4-S107, 595 08034 Barcelona, Spain 596 Phone: +34 9340107179 597 Email: agraz@tsc.upc.edu 599 Yabin Ye 600 Huawei Technologies Dusseldorf GmbH, 601 Riesstr. 25,D-3.0G 80992 602 Munich, Germany 603 Phone: 0049-891588344078 604 Email: yabin.ye@huawei.com 606 8. Contributors 608 Chava Vijaya Saradhi 609 CREATE-NET 610 Via alla Cascata 56/D-38123, 611 Povo-Trento, Italy 612 Phone: 0039-0461 408400 - ext. 401 613 Email: saradhi.chava@create-net.org 615 Antonio Francescon 616 CREATE-NET 617 Via alla Cascata 56/D-38123, 618 Povo-Trento, Italy 619 Phone: 0039-0461 408400 - ext. 605 620 Email: antonio.francescon@create-net.org 622 Intellectual Property 624 The IETF Trust takes no position regarding the validity or scope of 625 any Intellectual Property Rights or other rights that might be 626 claimed to pertain to the implementation or use of the technology 627 described in any IETF Document or the extent to which any license 628 under such rights might or might not be available; nor does it 629 represent that it has made any independent effort to identify any 630 such rights. 632 Copies of Intellectual Property disclosures made to the IETF 633 Secretariat and any assurances of licenses to be made available, or 634 the result of an attempt made to obtain a general license or 635 permission for the use of such proprietary rights by implementers or 636 users of this specification can be obtained from the IETF on-line IPR 637 repository at http://www.ietf.org/ipr 639 The IETF invites any interested party to bring to its attention any 640 copyrights, patents or patent applications, or other proprietary 641 rights that may cover technology that may be required to implement 642 any standard or specification contained in an IETF Document. Please 643 address the information to the IETF at ietf-ipr@ietf.org. 645 The definitive version of an IETF Document is that published by, or 646 under the auspices of, the IETF. Versions of IETF Documents that are 647 published by third parties, including those that are translated into 648 other languages, should not be considered to be definitive versions 649 of IETF Documents. The definitive version of these Legal Provisions 650 is that published by, or under the auspices of, the IETF. Versions of 651 these Legal Provisions that are published by third parties, including 652 those that are translated into other languages, should not be 653 considered to be definitive versions of these Legal Provisions. 655 For the avoidance of doubt, each Contributor to the IETF Standards 656 Process licenses each Contribution that he or she makes as part of 657 the IETF Standards Process to the IETF Trust pursuant to the 658 provisions of RFC 5378. No language to the contrary, or terms, 659 conditions or rights that differ from or are inconsistent with the 660 rights and licenses granted under RFC 5378, shall have any effect and 661 shall be null and void, whether published or posted by such 662 Contributor, or included with or in such Contribution. 664 Disclaimer of Validity 666 All IETF Documents and the information contained therein are provided 667 on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE 668 REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE 669 IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL 670 WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY 671 WARRANTY THAT THE USE OF THE INFORMATION THEREIN WILL NOT INFRINGE 672 ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS 673 FOR A PARTICULAR PURPOSE. 675 Full Copyright Statement 677 Copyright (c) 2010 IETF Trust and the persons identified as the 678 document authors. All rights reserved. 680 This document is subject to BCP 78 and the IETF Trust's Legal 681 Provisions Relating to IETF Documents 682 (http://trustee.ietf.org/license-info) in effect on the date of 683 publication of this document. Please review these documents carefully, 684 as they describe your rights and restrictions with respect to this 685 document. Code Components extracted from this document must include 686 Simplified BSD License text as described in Section 4.e of the Trust 687 Legal Provisions and are provided without warranty as described in 688 the Simplified BSD License.