idnits 2.17.1 draft-ietf-ccamp-gmpls-signaling-g709v3-10.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There is 1 instance of too long lines in the document, the longest one being 1 character in excess of 72. ** The abstract seems to contain references ([G709-2012]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. -- The draft header indicates that this document updates RFC4328, but the abstract doesn't seem to directly say this. It does mention RFC4328 though, so this could be OK. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year (Using the creation date from RFC4328, updated by this document, for RFC5378 checks: 2002-04-08) -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (June 18, 2013) is 3958 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) -- Possible downref: Non-RFC (?) normative reference: ref. 'G709-2012' -- Possible downref: Non-RFC (?) normative reference: ref. 'G7044' -- Possible downref: Non-RFC (?) normative reference: ref. 'G7041' -- Possible downref: Non-RFC (?) normative reference: ref. 'IEEE' -- Obsolete informational reference (is this intentional?): RFC 5226 (Obsoleted by RFC 8126) Summary: 2 errors (**), 0 flaws (~~), 1 warning (==), 8 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group Fatai Zhang, Ed. 2 Internet Draft Huawei 3 Updates: 4328 Guoying Zhang 4 Category: Standards Track CATR 5 Sergio Belotti 6 Alcatel-Lucent 7 D. Ceccarelli 8 Ericsson 9 Khuzema Pithewan 10 Infinera 11 Expires: December 18, 2013 June 18, 2013 13 Generalized Multi-Protocol Label Switching (GMPLS) Signaling 14 Extensions for the evolving G.709 Optical Transport Networks Control 16 draft-ietf-ccamp-gmpls-signaling-g709v3-10.txt 18 Status of this Memo 20 This Internet-Draft is submitted to IETF in full conformance with 21 the provisions of BCP 78 and BCP 79. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF), its areas, and its working groups. Note that 25 other groups may also distribute working documents as Internet- 26 Drafts. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 The list of current Internet-Drafts can be accessed at 34 http://www.ietf.org/ietf/1id-abstracts.txt. 36 The list of Internet-Draft Shadow Directories can be accessed at 37 http://www.ietf.org/shadow.html. 39 This Internet-Draft will expire on December 18, 2013. 41 Abstract 43 ITU-T Recommendation G.709 [G709-2012] has introduced new Optical 44 channel Data Unit (ODU) containers (ODU0, ODU4, ODU2e and ODUflex) 45 and enhanced Optical Transport Networking (OTN) flexibility. 47 This document provides an alternative to RFC4328 to provide the 48 extensions to the Generalized Multi-Protocol Label Switching (GMPLS) 49 signaling to control the full set of OTN features including ODU0, 50 ODU4, ODU2e and ODUflex. 52 Conventions used in this document 54 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 55 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 56 document are to be interpreted as described in [RFC2119]. 58 Table of Contents 60 1. Introduction .................................................. 3 61 2. Terminology ................................................... 3 62 3. GMPLS Extensions for the Evolving G.709 - Overview ............ 3 63 4. Generalized Label Request ..................................... 4 64 5. Extensions for Traffic Parameters for the Evolving G.709 ...... 7 65 5.1. Usage of ODUflex(CBR) Traffic Parameters ................. 8 66 5.2. Usage of ODUflex(GFP) Traffic Parameters ................ 10 67 5.3. Notification on Errors of OTN-TDM Traffic Parameters .... 11 68 6. Generalized Label ............................................ 11 69 6.1. OTN-TDM Switching Type Generalized Label ................ 11 70 6.2. Procedures .............................................. 14 71 6.2.1. Notification on Label Error ........................ 15 72 6.3. Supporting Virtual Concatenation and Multiplication ..... 16 73 6.4. Examples ................................................ 17 74 7. Supporting Hitless Adjustment of ODUflex (GFP) ............... 18 75 8. Control Plane Backward Compatibility Considerations........... 19 76 9. Security Considerations ...................................... 20 77 10. IANA Considerations.......................................... 20 78 11. References .................................................. 22 79 11.1. Normative References ................................... 22 80 11.2. Informative References ................................. 23 81 12. Contributors ................................................ 24 82 13. Authors' Addresses .......................................... 24 83 14. Acknowledgment .............................................. 26 85 1. Introduction 87 With the evolution and deployment of OTN technology, it is necessary 88 that appropriate enhanced control technology support be provided for 89 [G709-2012]. 91 [OTN-FWK] provides a framework to allow the development of protocol 92 extensions to support GMPLS and Path Computation Element (PCE) 93 control of OTN as specified in [G709-2012]. Based on this framework, 94 [OTN-INFO] evaluates the information needed by the routing and 95 signaling process in OTNs to support GMPLS control of OTN. 97 [RFC4328] describes the control technology details that are specific 98 to the 2001 revision of the G.709 specification. This document 99 provides an alternative to [RFC4328] to provide Resource ReserVation 100 Protocol-Traffic Engineering (RSVP-TE) extensions to support of 101 control for [G709-2012]. 103 2. Terminology 105 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 106 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 107 document are to be interpreted as described in [RFC2119]. 109 3. GMPLS Extensions for the Evolving G.709 - Overview 111 New features for the evolving OTN, for example, new ODU0, ODU2e, ODU4 112 and ODUflex containers are specified in [G709-2012]. The 113 corresponding new Signal Types are summarized below: 115 - Optical Channel Transport Unit (OTUk): 116 . OTU4 118 - Optical Channel Data Unit (ODUk): 119 . ODU0 120 . ODU2e 121 . ODU4 122 . ODUflex 124 A new Tributary Slot granularity (i.e., 1.25Gbps) is also described 125 in [G709-2012]. Thus, there are now two TS granularities for the 126 foundation OTN ODU1, ODU2 and ODU3 containers. The TS granularity at 127 2.5Gbps is used on legacy interfaces while the new 1.25Gbps is used 128 on the new interfaces. 130 In addition to the support of ODUk mapping into OTUk (k = 1, 2, 3, 131 4), [G709-2012] encompasses the multiplexing of ODUj (j = 0, 1, 2, 132 2e, 3, flex) into an ODUk (k > j), as described in Section 3.1.2 of 133 [OTN-FWK]. 135 Virtual Concatenation (VCAT) of Optical channel Payload Unit-k (OPUk) 136 (OPUk-Xv, k = 1/2/3, X = 1...256) is also supported by [G709-2012]. 137 Note that VCAT of OPU0 / OPU2e / OPU4 / OPUflex is not supported per 138 [G709-2012]. 140 [RFC4328] describes GMPLS signaling extensions to support the control 141 for the 2001 revision of the G.709 specification. However, [RFC4328] 142 does not provide the means to signal all the new Signal Types and 143 related mapping and multiplexing functionalities. Moreover, it 144 supports only the deprecated auto- Multiframe Structure Identifier 145 (MSI) mode which assumes that the Tributary Port Number (TPN) is 146 automatically assigned in the transmit direction and not checked in 147 the receive direction. 149 This document extends the G.709 Traffic Parameters described in 150 [RFC4328] and presents a new flexible and scalable OTN-TDM 151 Generalized Label format. Additionally, procedures about Tributary 152 Port Number assignment through control plane are also provided in 153 this document. 155 4. Generalized Label Request 157 The GENERALIZED_LABEL_REQUEST object, as described in [RFC3471], 158 carries the Label Switched Path (LSP) Encoding Type, the Switching 159 Type and the Generalized Protocol Identifier (G-PID). 161 [RFC4328] extends the GENERALIZED_LABEL_REQUEST object, introducing 162 two new code-points for the LSP Encoding Type (i.e., G.709 ODUk 163 (Digital Path) and G.709 Optical Channel) and adding a list of G-PID 164 values in order to accommodate the 2001 revision of the G.709 165 specification. 167 This document follows these extensions and a new Switching Type is 168 introduced to indicate the ODUk switching capability [G709-2012] in 169 order to support backward compatibility with [RFC4328], as described 170 in [OTN-FWK]. The new Switching Type (OTN-TDM Switching Type) is 171 defined in [OTN-OSPF]. 173 This document also updates the G-PID values defined in [RFC4328]: 175 Value G-PID Type 176 ----- ---------- 177 47 Type field updated from "G.709 ODUj" to "ODU-2.5G" to 178 indicate transport of Digital Paths (e.g., at 2.5, 10 and 179 40Gbps) via 2.5Gbps TS granularity. 181 56 Type field updated from "ESCON" to "SBCON/ESCON" to align 182 with [G709-2012] payload type 0x1A. 184 Note: Value 47 includes mapping of Synchronous Digital Hierarchy 185 (SDH). 187 In the case of ODU multiplexing, the Lower Order ODU (LO ODU) (i.e., 188 the client signal) may be multiplexed into Higher Order ODU (HO ODU) 189 via 1.25G TS granularity, 2.5G TS granularity or any one of them 190 (i.e., TS granularity Auto_Negotiation is enabled). Since the G-PID 191 type "ODUk" defined in [RFC4328] is only used for 2.5Gbps TS 192 granularity, two new G-PID types are defined as follows: 194 - ODU-1.25G: Transport of Digital Paths at 1.25, 2.5, 10, 40 and 100 195 Gbps via 1.25Gbps TS granularity. 197 - ODU-any: Transport of Digital Paths at 1.25, 2.5, 10, 40 and 100 198 Gbps via 1.25 or 2.5Gbps TS granularity (i.e., the 199 fallback procedure is enabled and the default value of 200 1.25Gbps TS granularity can be fallen back to 2.5Gbps 201 if needed). 203 The full list of payload types defined in [G709-2012] and their 204 mapping to existing and new G-PID types are as follows: 206 G.709 207 Payload 208 Type G-PID Type/Comment LSP Encoding 209 ==== ===== ===================== =================== 210 0x01 No standard value 211 0x02 49 CBRa G.709 ODUk 212 0x03 50 CBRb G.709 ODUk 213 0x04 32 ATM G.709 ODUk 214 0x05 59(TBA) Framed GFP G.709 ODUk 215 54 Ethernet MAC (framed GFP) G.709 ODUk 216 70(TBA) 64B/66B GFP-F Ethernet G.709 ODUk (k=2) 217 0x06 Not signaled 218 0x07 55 Ethernet PHY G.709 ODUk (k=0,3,4) 219 (transparent GFP) 221 0x08 58 Fiber Channel G.709 ODUk (k=2e) 222 0x09 59(TBA) Framed GFP G.709 ODUk (k=2) 223 70(TBA) 64B/66B GFP-F Ethernet G.709 ODUk (k=2) 224 0x0A 60(TBA) STM-1 G.709 ODUk (k=0) 225 0x0B 61(TBA) STM-4 G.709 ODUk (k=0) 226 0x0C 58 Fiber Channel G.709 ODUk (k=0) 227 0x0D 58 Fiber Channel G.709 ODUk (k=1) 228 0x0E 58 Fiber Channel G.709 ODUflex 229 0x0F 58 Fiber Channel G.709 ODUflex 230 0x10 51 BSOT G.709 ODUk 231 0x11 52 BSNT G.709 ODUk 232 0x12 62(TBA) InfiniBand G.709 ODUflex 233 0x13 62(TBA) InfiniBand G.709 ODUflex 234 0x14 62(TBA) InfiniBand G.709 ODUflex 235 0x15 63(TBA) Serial Digital Interface G.709 ODUk (k=0) 236 0x16 64(TBA) Serial Digital G.709 ODUk (k=1) 237 Interface/1.001 238 0x17 63(TBA) Serial Digital Interface G.709 ODUk (k=1) 239 0x18 64(TBA) Serial Digital G.709 ODUflex 240 Interface/1.001 241 0x19 63(TBA) Serial Digital Interface G.709 ODUflex 242 0x1A 56 SBCON/ESCON G.709 ODUk (k=0) 243 (IANA to update Type field) 244 0x1B 65(TBA) DVB_ASI G.709 ODUk (k=0) 245 0x1C 58 Fiber Channel G.709 ODUk 246 0x20 47 G.709 ODU-2.5G G.709 ODUk (k=2,3) 247 (IANA to update Type field) 248 66(TBA) G.709 ODU-1.25G G.709 ODUk (k=1) 249 0x21 66(TBA) G.709 ODU-1.25G G.709 ODUk (k=2,3,4) 250 67(TBA) G.709 ODU-Any G.709 ODUk (k=2,3) 251 0x55 No standard value 252 0x66 No standard value 253 0x80-0x8F No standard value 254 0xFD 68(TBA) Null Test G.709 ODUk 255 0xFE 69(TBA) Random Test G.709 ODUk 256 0xFF No standard value 258 Note: Values 59 and 70 include mapping of SDH. 260 Note that the mapping types for ODUj into OPUk are unambiguously per 261 Table 7-10 of [G709-2012], so it does not need to carry mapping type 262 information in the signaling. 264 Note also that additional information on G.709 client mapping can be 265 found in [G7041]. 267 5. Extensions for Traffic Parameters for the Evolving G.709 269 The Traffic Parameters for OTN-TDM capable Switching Type are carried 270 in the OTN-TDM SENDER_TSPEC and OTN-TDM FLOWSPEC objects. The objects 271 have the following class and type: 273 - OTN-TDM SENDER_TSPEC object: Class = 12, C-Type = 7 (TBA) 274 - OTN-TDM FLOWSPEC object: Class = 9, C-Type = 7 (TBA) 276 The format of Traffic Parameters in these two objects is defined as 277 follows: 279 0 1 2 3 280 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 281 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 282 | Signal Type | Reserved | 283 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 284 | NVC | Multiplier (MT) | 285 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 286 | Bit_Rate | 287 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 289 Signal Type: 8 bits 291 As defined in [RFC4328] Section 3.2.1, with the following 292 additional values: 294 Value Type 295 ----- ---- 296 4 ODU4 (i.e., 100Gbps) 297 9 OCh at 100Gbps 298 10 ODU0 (i.e., 1.25Gbps) 299 11 ODU2e (i.e., 10Gbps for FC1200 and GE LAN) 300 12~19 Reserved (for future use) 301 20 ODUflex(CBR) (i.e., 1.25*N Gbps) 302 21 ODUflex(Generic Framing Procedure-Framed (GFP-F)), 303 resizable (i.e., 1.25*N Gbps) 304 22 ODUflex(GFP-F), non resizable (i.e., 1.25*N Gbps) 305 23~255 Reserved (for future use) 307 NVC: 16 bits 309 As defined in [RFC4328] Section 3.2.3. This field MUST be set to 310 0 for ODUflex Signal Types. 312 Multiplier (MT): 16 bits 314 As defined in [RFC4328] Section 3.2.4. This field MUST be set to 315 1 for ODUflex Signal Types. 317 Bit_Rate: 32 bits 319 In case of ODUflex including ODUflex(CBR) and ODUflex(GFP) Signal 320 Types, this field indicates the nominal bit rate of ODUflex 321 expressed in bytes per second, encoded as a 32-bit IEEE single- 322 precision floating-point number (referring to [RFC4506] and 323 [IEEE]). For other Signal Types, this field MUST be set to zero 324 on transmission and MUST be ignored on receipt and SHOULD be 325 passed unmodified by transit nodes. 327 5.1. Usage of ODUflex(CBR) Traffic Parameters 329 In case of ODUflex(CBR), the information of Bit_Rate carried in the 330 ODUflex Traffic Parameters MUST be used to determine the actual 331 bandwidth of ODUflex(CBR) (i.e., Bit_Rate * (1 +/- Tolerance)). 332 Therefore the total number of tributary slots N in the HO ODUk link 333 can be reserved correctly. Where: 335 N = Ceiling of 337 ODUflex(CBR) nominal bit rate * (1 + ODUflex(CBR) bit rate tolerance) 338 --------------------------------------------------------------------- 339 ODTUk.ts nominal bit rate * (1 - HO OPUk bit rate tolerance) 341 In this formula, the ODUflex(CBR) nominal bit rate is the bit rate of 342 the ODUflex(CBR) on the line side, i.e., the client signal bit rate 343 after applying the 239/238 factor (according to Clause 7.3, Table 7-2 344 of [G709-2012]) and the transcoding factor T (if needed) on the CBR 345 client. According to clauses 17.7.3, 17.7.4 and 17.7.5 of [G709- 346 2012]: 348 ODUflex(CBR) nominal bit rate = CBR client bit rate * (239/238) / T 350 The ODTUk.ts (Optical channel Data Tributary Unit k with ts tributary 351 slots) nominal bit rate is the nominal bit rate of the tributary slot 352 of ODUk, as shown in Table 1 (referring to Table 7-7 of [G709-2012]). 354 Table 1 - Actual TS bit rate of ODUk (in Kbps) 356 ODUk.ts Minimum Nominal Maximum 357 ----------------------------------------------------------- 358 ODU2.ts 1,249,384.632 1,249,409.620 1,249,434.608 359 ODU3.ts 1,254,678.635 1,254,703.729 1,254,728.823 360 ODU4.ts 1,301,683.217 1,301,709.251 1,301,735.285 362 Note that: 364 Minimum bit rate of ODUTk.ts = 365 ODTUk.ts nominal bit rate * (1 - HO OPUk bit rate tolerance) 367 Maximum bit rate of ODTUk.ts = 368 ODTUk.ts nominal bit rate * (1 + HO OPUk bit rate tolerance) 370 Where: HO OPUk bit rate tolerance = 20ppm (parts per million) 372 Note that the bit rate tolerance is implicit in Signal Type and the 373 ODUflex(CBR) bit rate tolerance is fixed and it is equal to 100ppm as 374 described in Table 7-2 of [G709-2012]. 376 Therefore, a node receiving a Path message containing ODUflex(CBR) 377 nominal bit rate can allocate precise number of tributary slots and 378 set up the cross-connection for the ODUflex service. 380 Note that for different ODUk, the bit rates of the tributary slots 381 are different, and so the total number of tributary slots to be 382 reserved for the ODUflex(CBR) may not be the same on different HO 383 ODUk links. 385 An example is given below to illustrate the usage of ODUflex(CBR) 386 Traffic Parameters. 388 +-----+ +---------+ +-----+ 389 | +-------------+ +-----+ +-------------+ | 390 | +=============+\| ODU |/+=============+ | 391 | +=============+/| flex+-+=============+ | 392 | +-------------+ | |\+=============+ | 393 | +-------------+ +-----+ +-------------+ | 394 | | | | | | 395 | | ....... | | ....... | | 396 | A +-------------+ B +-------------+ C | 397 +-----+ HO ODU4 +---------+ HO ODU2 +-----+ 399 =========: TSs occupied by ODUflex 400 ---------: available TSs 402 Figure 1 - Example of ODUflex(CBR) Traffic Parameters 404 As shown in Figure 1, assume there is an ODUflex(CBR) service 405 requesting a bandwidth of (2.5Gbps, +/-100ppm) from node A to node C. 407 In other words, the ODUflex Traffic Parameters indicate that Signal 408 Type is 20 (ODUflex(CBR)), Bit_Rate is 2.5Gbps (Note that the 409 tolerance is no longer signaled as explained above). 411 - On the HO ODU4 link between node A and B: 413 The maximum bit rate of the ODUflex(CBR) equals 2.5Gbps * (1 + 414 100ppm), and the minimum bit rate of the tributary slot of ODU4 415 equals 1,301,683.217 Kbps, so the total number of tributary slots 416 N1 to be reserved on this link is: 418 N1 = ceiling (2.5Gbps * (1 + 100ppm) / 1,301,683.217 Kbps) = 2 420 - On the HO ODU2 link between node B and C: 422 The maximum bit rate of the ODUflex equals 2.5Gbps * (1 + 423 100ppm), and the minimum bit rate of the tributary slot of ODU2 424 equals 1,249,384.632 Kbps, so the total number of tributary slots 425 N2 to be reserved on this link is: 427 N2 = ceiling (2.5Gbps * (1 + 100ppm) / 1,249,384.632 Kbps) = 3 429 5.2. Usage of ODUflex(GFP) Traffic Parameters 431 [G709-2012] recommends that the ODUflex(GFP) will fill an integral 432 number of tributary slots of the smallest HO ODUk path over which the 433 ODUflex(GFP) may be carried, as shown in Table 2. 435 Table 2 - Recommended ODUflex(GFP) bit rates and tolerance 437 ODU type | Nominal bit-rate | Tolerance 438 --------------------------------+------------------+----------- 439 ODUflex(GFP) of n TSs, 1<=n<=8 | n * ODU2.ts | +/-100 ppm 440 ODUflex(GFP) of n TSs, 9<=n<=32 | n * ODU3.ts | +/-100 ppm 441 ODUflex(GFP) of n TSs, 33<=n<=80 | n * ODU4.ts | +/-100 ppm 443 According to this table, the Bit_Rate field for ODUflex(GFP) MUST 444 equal to one of the 80 values listed below: 446 1 * ODU2.ts; 2 * ODU2.ts; ...; 8 * ODU2.ts; 447 9 * ODU3.ts; 10 * ODU3.ts, ...; 32 * ODU3.ts; 448 33 * ODU4.ts; 34 * ODU4.ts; ...; 80 * ODU4.ts. 450 In this way, the number of required tributary slots for the 451 ODUflex(GFP) (i.e., the value of "n" in Table 2) can be deduced from 452 the Bit_Rate field. 454 5.3. Notification on Errors of OTN-TDM Traffic Parameters 456 There is no Adspec associated with the OTN-TDM SENDER_TSPEC object. 457 Either the Adspec is omitted or an Int-serv Adspec with the Default 458 General Characterization Parameters and Guaranteed Service fragment 459 is used, see [RFC2210]. 461 For a particular sender in a session, the contents of the OTN-TDM 462 FLOWSPEC object received in a Resv message SHOULD be identical to the 463 contents of the OTN-TDM SENDER_TSPEC object received in the 464 corresponding Path message. If the objects do not match, a ResvErr 465 message with a "Traffic Control Error/Bad Flowspec value" error MUST 466 be generated. 468 Intermediate and egress nodes MUST verify that the node itself, and 469 the interfaces on which the LSP will be established, can support the 470 requested Signal Type, NVC and Bit_Rate values. If the requested 471 value(s) cannot be supported, the receiver node MUST generate a 472 PathErr message with a "Traffic Control Error/Service unsupported" 473 indication (see [RFC2205]). 475 In addition, if the MT field is received with a zero value, the node 476 MUST generate a PathErr message with a "Traffic Control Error/Bad 477 Tspec value" indication (see [RFC2205]). 479 Further, if the Signal Type is not ODU1, ODU2 or ODU3, and the NVC 480 field is not 0, the node MUST generate a PathErr message with a 481 "Traffic Control Error/Bad Tspec value" indication (see [RFC2205]). 483 6. Generalized Label 485 This section defines the format of the OTN-TDM Generalized Label. 487 6.1. OTN-TDM Switching Type Generalized Label 489 The following is the GENERALIZED_LABEL object format for that MUST be 490 used with the OTN-TDM Switching Type: 492 0 1 2 3 493 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 494 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 495 | TPN | Reserved | Length | 496 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 497 ~ Bit Map ...... ~ 498 ~ ...... | Padding Bits ~ 499 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 500 The OTN-TDM GENERALIZED_LABEL object is used to indicate how the LO 501 ODUj signal is multiplexed into the HO ODUk link. Note that the LO 502 OUDj signal type is indicated by Traffic Parameters, while the type 503 of HO ODUk link is identified by the selected interface carried in 504 the IF_ID RSVP_HOP object. 506 TPN (12 bits): indicates the TPN for the assigned Tributary Slot(s). 508 - In case of LO ODUj multiplexed into HO ODU1/ODU2/ODU3, only the 509 lower 6 bits of TPN field are significant and the other bits of 510 TPN MUST be set to 0. 512 - In case of LO ODUj multiplexed into HO ODU4, only the lower 7 513 bits of TPN field are significant and the other bits of TPN 514 MUST be set to 0. 516 - In case of ODUj mapped into OTUk (j=k), the TPN is not needed 517 and this field MUST be set to 0. 519 Per [G709-2012], The TPN is used to allow for correct demultiplexing 520 in the data plane. When an LO ODUj is multiplexed into HO ODUk 521 occupying one or more TSs, a new TPN value is configured at the two 522 ends of the HO ODUk link and is put into the related MSI byte(s) in 523 the OPUk overhead at the (traffic) ingress end of the link, so that 524 the other end of the link can learn which TS(s) is/are used by the LO 525 ODUj in the data plane. 527 According to [G709-2012], the TPN field MUST be set as according to 528 the following tables: 530 Table 3 - TPN Assignment Rules (2.5Gbps TS granularity) 531 +-------+-------+----+----------------------------------------------+ 532 |HO ODUk|LO ODUj|TPN | TPN Assignment Rules | 533 +-------+-------+----+----------------------------------------------+ 534 | ODU2 | ODU1 |1~4 |Fixed, = TS# occupied by ODU1 | 535 +-------+-------+----+----------------------------------------------+ 536 | | ODU1 |1~16|Fixed, = TS# occupied by ODU1 | 537 | ODU3 +-------+----+----------------------------------------------+ 538 | | ODU2 |1~4 |Flexible, != other existing LO ODU2s' TPNs | 539 +-------+-------+----+----------------------------------------------+ 540 Table 4 - TPN Assignment Rules (1.25Gbps TS granularity) 541 +-------+-------+----+----------------------------------------------+ 542 |HO ODUk|LO ODUj|TPN | TPN Assignment Rules | 543 +-------+-------+----+----------------------------------------------+ 544 | ODU1 | ODU0 |1~2 |Fixed, = TS# occupied by ODU0 | 545 +-------+-------+----+----------------------------------------------+ 546 | | ODU1 |1~4 |Flexible, != other existing LO ODU1s' TPNs | 547 | ODU2 +-------+----+----------------------------------------------+ 548 | |ODU0 & |1~8 |Flexible, != other existing LO ODU0s and | 549 | |ODUflex| |ODUflexes' TPNs | 550 +-------+-------+----+----------------------------------------------+ 551 | | ODU1 |1~16|Flexible, != other existing LO ODU1s' TPNs | 552 | +-------+----+----------------------------------------------+ 553 | | ODU2 |1~4 |Flexible, != other existing LO ODU2s' TPNs | 554 | ODU3 +-------+----+----------------------------------------------+ 555 | |ODU0 & | |Flexible, != other existing LO ODU0s and | 556 | |ODU2e &|1~32|ODU2es and ODUflexes' TPNs | 557 | |ODUflex| | | 558 +-------+-------+----+----------------------------------------------+ 559 | ODU4 |Any ODU|1~80|Flexible, != ANY other existing LO ODUs' TPNs | 560 +-------+-------+----+----------------------------------------------+ 562 Note that in the case of "Flexible", the value of TPN MAY not be 563 corresponding to the TS number as per [G709-2012]. 565 Length (12 bits): indicates the number of bits of the Bit Map field, 566 i.e., the total number of TS in the HO ODUk link. The TS granularity, 567 1.25Gbps or 2.5Gbps, may be derived by dividing the HO ODUk link's 568 rate by the value of the Length field. In the context of [G709-2012], 569 the values of 4 and 16 indicate a TS granularity of 2.5Gbps, and the 570 values 2, 8, 32 and 80 indicate a TS granularity of 1.25Gbps. 572 In case of an ODUk mapped into OTUk, there is no need to indicate 573 which tributary slots will be used, so the length field MUST be set 574 to 0. 576 Bit Map (variable): indicates which tributary slots in HO ODUk that 577 the LO ODUj will be multiplexed into. The sequence of the Bit Map is 578 consistent with the sequence of the tributary slots in HO ODUk. Each 579 bit in the bit map represents the corresponding tributary slot in HO 580 ODUk with a value of 1 or 0 indicating whether the tributary slot 581 will be used by LO ODUj or not. 583 Padding bits are added after the Bit Map to make the whole label a 584 multiple of four bytes if necessary. Padding bits MUST be set to 0 585 and MUST be ignored on receipt. 587 6.2. Procedures 589 The ingress node MUST generate a Path message and specify the OTN-TDM 590 Switching Type and corresponding G-PID in the 591 GENERALIZED_LABEL_REQUEST object, which MUST be processed as defined 592 in [RFC3473]. 594 The ingress node of an LSP MAY include Label ERO (Explicit Route 595 Object) to indicate the label in each hops along the path. Note that 596 the TPN in the Label ERO subobject need not be assigned by the 597 ingress node. In this case, the node MUST assign a valid TPN value 598 and then put this value into TPN field of the GENERALIZED_LABEL 599 object when receiving a Path message. 601 In order to create bidirectional LSP, the ingress node and upstream 602 node MUST generate an UPSTREAM_LABEL object on the out outgoing 603 interface to indicate the reserved TSs of ODUk and the assigned TPN 604 value in the upstream direction. This UPSTREAM_LABEL object is sent 605 to the downstream node via Path massage for upstream resource 606 reservation. 608 The ingress node or upstream node MAY generate LABEL_SET object to 609 indicate which labels on the outgoing interface in the downstream 610 direction are acceptable. The downstream node will restrict its 611 choice of labels, i.e., TS resource and TPN value, to one which is in 612 the LABEL_SET object. 614 The ingress node or upstream node MAY also generate SUGGESTED_LABEL 615 object to indicate the preference of TS resource and TPN value on the 616 outgoing interface in the downstream direction. The downstream node 617 is not required to use the suggested labels and may use another label 618 based on local decision and send it to the upstream node, as 619 described in [RFC3473]. 621 When an upstream node receives a Resv message containing a 622 GENERALIZED_LABEL object with an OTN-TDM label, it MUST firstly 623 identify which ODU Signal Type is multiplexed or mapped into which 624 ODU Signal Type accordingly to the Traffic Parameters and the IF_ID 625 RSVP_HOP object in the received message. 627 - In case of ODUj to ODUk multiplexing, the node MUST retrieve the 628 reserved tributary slots in the ODUk by its downstream neighbor 629 node according to the position of the bits that are set to 1 in 630 the Bit Map field. The node determines the TS granularity 631 (according to the total TS number of the ODUk, or pre-configured 632 TS granularity), so that the node can multiplex the ODUj into the 633 ODUk based on the TS granularity. The node MUST also retrieve the 634 TPN value assigned by its downstream neighbor node from the label, 635 and fill the TPN into the related MSI byte(s) in the OPUk overhead 636 in the data plane, so that the downstream neighbor node can check 637 whether the TPN received from the data plane is consistent with 638 the ExMSI and determine whether there is any mismatch defect. 640 - In case of ODUk to OTUk mapping, the size of Bit Map field MUST be 641 0 and no additional procedure is needed. 643 When a downstream node or egress node receives a Path message 644 containing GENERALIZED_LABEL_REQUEST object for setting up an ODUj 645 LSP from its upstream neighbor node, the node MUST generate an OTN- 646 TDM label according to the Signal Type of the requested LSP and the 647 available resources (i.e., available tributary slots of ODUk) that 648 will be reserved for the LSP, and send the label to its upstream 649 neighbor node. 651 - In case of ODUj to ODUk multiplexing, the node MUST firstly 652 determine the size of the Bit Map field according to the Signal 653 Type and the tributary slot type of ODUk, and then set the bits to 654 1 in the Bit Map field corresponding to the reserved tributary 655 slots. The node MUST also assign a valid TPN, which MUST NOT 656 collide with other TPN value used by existing LO ODU connections 657 in the selected HO ODU link, and configure the Expected MSI 658 (ExMSI) using this TPN. Then, the assigned TPN MUST be filled into 659 the label. 661 - In case of ODUk to OTUk mapping, TPN field MUST be set to 0. Bit 662 Map information is not REQUIRED and MUST NOT be included, so 663 Length field MUST be set to 0 as well. 665 6.2.1. Notification on Label Error 667 When an upstream node receives a Resv message containing an 668 GENERALIZED_LABEL object with an OTN-TDM label, the node MUST verify 669 if the label is acceptable. If the label is not acceptable, the node 670 MUST generate a ResvErr message with a "Routing problem/Unacceptable 671 label value" indication. Per [RFC3473], the generated ResvErr 672 message MAY include an ACCEPTABLE_LABEL_SET object. With the 673 exception of label semantics, downstream node processing a received 674 ResvErr message and of ACCEPTABLE_LABEL_SET object is not modified 675 by this document. 677 Similarly, when a downstream node receives a Path message containing 678 an UPSTREAM_LABEL object with an OTN-TDM label, the node MUST verify 679 if the label is acceptable. If the label is not acceptable, the node 680 MUST generate a PathErr message with a "Routing problem/Unacceptable 681 label value" indication. Per [RFC3473], the generated ResvErr message 682 MAY include an ACCEPTABLE_LABEL_SET object. With the exception of 683 label semantics, downstream node processing received a PathErr message 684 and of ACCEPTABLE_LABEL_SET object is not modified by this document. 686 A received label SHALL be considered unacceptable when one of the 687 following cases occurs: 689 - The received label doesn't conform to local policy; 691 - Invalid value in the length field; 693 - The selected link only supports 2.5Gbps TS granularity while the 694 Length field in the label along with ODUk Signal Type indicates 695 the 1.25Gbps TS granularity; 697 - The label includes an invalid TPN value that breaks the TPN 698 assignment rules; 700 - The indicated resources (i.e., the number of "1" in the Bit Map 701 field) are inconsistent with the Traffic Parameters. 703 6.3. Supporting Virtual Concatenation and Multiplication 705 Per [RFC6344], the Virtual Concatenation Groups (VCGs) can be created 706 using Co-Signaled style or Multiple LSPs style. 708 In case of Co-Signaled style, the explicit ordered list of all labels 709 MUST reflect the order of VCG members, which is similar to [RFC4328]. 710 In case of multiplexed virtually concatenated signals (NVC > 1), the 711 first label MUST indicate the components of the first virtually 712 concatenated signal; the second label MUST indicate the components of 713 the second virtually concatenated signal; and so on. In case of 714 multiplication of multiplexed virtually concatenated signals (MT > 715 1), the first label MUST indicate the components of the first 716 multiplexed virtually concatenated signal; the second label MUST 717 indicate components of the second multiplexed virtually concatenated 718 signal; and so on. 720 Support for Virtual Concatenation of ODU1, ODU2 and ODU3 Signal 721 Types, as defined by [RFC6344], is not modified by this document. 722 Virtual Concatenation of other Signal Types is not supported by 723 [G709-2012]. 725 Multiplier (MT) usage is as defined in [RFC6344] and [RFC4328]. 727 6.4. Examples 729 The following examples are given in order to illustrate the label 730 format described in Section 6.1 of this document. 732 (1) ODUk into OTUk mapping: 734 In such conditions, the downstream node along an LSP returns a label 735 indicating that the ODUk (k=1, 2, 3, 4) is directly mapped into the 736 corresponding OTUk. The following example label indicates an ODU1 737 mapped into OTU1. 739 0 1 2 3 740 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 741 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 742 | TPN = 0 | Reserved | Length = 0 | 743 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 745 (2) ODUj into ODUk multiplexing: 747 In such conditions, this label indicates that an ODUj is multiplexed 748 into several tributary slots of OPUk and then mapped into OTUk. Some 749 instances are shown as follow: 751 - ODU0 into ODU2 Multiplexing: 753 0 1 2 3 754 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 755 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 756 | TPN = 2 | Reserved | Length = 8 | 757 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 758 |0 1 0 0 0 0 0 0| Padding Bits (0) | 759 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 761 This above label indicates an ODU0 multiplexed into the second 762 tributary slot of ODU2, wherein there are 8 TSs in ODU2 (i.e., the 763 type of the tributary slot is 1.25Gbps), and the TPN value is 2. 765 - ODU1 into ODU2 Multiplexing with 1.25Gbps TS granularity: 767 0 1 2 3 768 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 769 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 770 | TPN = 1 | Reserved | Length = 8 | 771 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 772 |0 1 0 1 0 0 0 0| Padding Bits (0) | 773 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 774 This above label indicates an ODU1 multiplexed into the 2nd and the 775 4th tributary slot of ODU2, wherein there are 8 TSs in ODU2 (i.e., 776 the type of the tributary slot is 1.25Gbps), and the TPN value is 1. 778 - ODU2 into ODU3 Multiplexing with 2.5Gbps TS granularity: 780 0 1 2 3 781 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 782 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 783 | TPN = 1 | Reserved | Length = 16 | 784 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 785 |0 1 1 0 1 0 1 0 0 0 0 0 0 0 0 0| Padding Bits (0) | 786 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 788 This above label indicates an ODU2 multiplexed into the 2nd, 3rd, 5th 789 and 7th tributary slot of ODU3, wherein there are 16 TSs in ODU3 790 (i.e., the type of the tributary slot is 2.5Gbps), and the TPN value 791 is 1. 793 7. Supporting Hitless Adjustment of ODUflex (GFP) 795 [G7044] describes the procedure of ODUflex (GFP) hitless resizing 796 using Link Connection Resize (LCR) and Bandwidth Resize (BWR) 797 protocols in OTN data plane. 799 For the control plane, signaling messages are REQUIRED to initiate 800 the adjustment procedure. Section 2.5 and Section 4.6.4 of [RFC3209] 801 describe how the Shared Explicit (SE) style is used in Traffic 802 Engineering (TE) network for bandwidth increasing and decreasing, 803 which is still applicable for triggering the ODUflex (GFP) adjustment 804 procedure in data plane. 806 Note that the SE style MUST be used at the beginning when creating a 807 resizable ODUflex connection (Signal Type = 21). Otherwise an error 808 with Error Code "Conflicting reservation style" MUST be generated 809 when performing bandwidth adjustment. 811 - Bandwidth increasing 813 For the ingress node, in order to increase the bandwidth of an 814 ODUflex (GFP) connection, a Path message with SE style (keeping 815 Tunnel ID unchanged and assigning a new LSP ID) MUST be sent 816 along the path. 818 The ingress node will trigger the BWR protocol when successful 819 completion of LCR protocols on every hop after Resv message is 820 processed. On success of BWR, the ingress node SHOULD send a 821 PathTear message to delete the old control state (i.e., the 822 control state of the ODUflex (GFP) before resizing) on the 823 control plane. 825 A downstream node receiving Path message with SE style compares 826 the old Traffic Parameters (stored locally) with the new one 827 carried in the Path message, to determine the number of TS to be 828 added. After choosing and reserving new available TS(s), the 829 downstream node MUST send back a Resv message carrying both the 830 old and new GENERALIZED_LABEL objects in the SE flow descriptor. 832 An upstream neighbor receiving Resv message with SE flow 833 descriptor MUST determine which TS(s) is/are added and trigger 834 the LCR protocol between itself and its downstream neighbor node. 836 - Bandwidth decreasing 838 For the ingress node, a Path message with SE style SHOULD also be 839 sent for ODUflex bandwidth decreasing. 841 The ingress node will trigger the BWR protocol when successful 842 completion of LCR handshake on every hop after Resv message is 843 processed. On success of BWR, the second step of LCR, i.e., link 844 connection decrease procedure will be started on every hop of the 845 connection. After completion of bandwidth decreasing, the ingress 846 node SHOULD send a ResvErr message to tear down the old control 847 state. 849 A downstream node receiving Path message with SE style compares 850 the old Traffic Parameters with the new one carried in the Path 851 message to determine the number of TS to be decreased. After 852 choosing TSs to be decreased, the downstream node MUST send back 853 a Resv message carrying both the old and new GENERALIZED_LABEL 854 objects in the SE flow descriptor. 856 An upstream neighbor receiving Resv message with SE flow 857 descriptor MUST determine which TS(s) is/are decreased and 858 trigger the first step of LCR protocol (i.e., LCR handshake) 859 between itself and its downstream neighbor node. 861 8. Control Plane Backward Compatibility Considerations 863 As described in [OTN-FWK], since the [RFC4328] has been deployed in 864 the network for the nodes that support the 2001 revision of the G.709 865 specification, control plane backward compatibility SHOULD be taken 866 into consideration. More specifically: 868 o Nodes supporting this document SHOULD support [OTN-OSPF]. 870 o Nodes supporting this document MAY support [RFC4328] signaling. 872 o A node supporting both sets of procedures (i.e., [RFC4328] and 873 this document) is not REQUIRED to signal an LSP using both 874 procedures, i.e., to act as a signaling version translator. 876 o Ingress nodes that support both sets of procedures MAY select 877 which set of procedures to follow based on routing information or 878 local policy. 880 o Per [RFC3473], nodes that do not support this document will 881 generate a PathErr message, with a "Routing problem/Switching 882 Type" indication. 884 9. Security Considerations 886 This document is a modification to [RFC3473] and [RFC4328], and only 887 differs in specific information communicated. As such, this document 888 introduces no new security considerations to the existing GMPLS 889 signaling protocols. Referring to [RFC3473] and [RFC4328], further 890 details of the specific security measures are provided. Additionally, 891 [RFC5920] provides an overview of security vulnerabilities and 892 protection mechanisms for the GMPLS control plane. 894 10. IANA Considerations 896 Upon approval of this document, IANA will make the following 897 assignments in the "Class Types or C-Types 9 FLOWSPEC" and "Class 898 Types or C-Types 12 SENDER_TSPEC" section of the "RSVP Parameters" 899 registry located at http://www.iana.org/assignments/rsvp- 900 parameters/rsvp-parameters.xml. 902 Value Description Reference 903 7(*) OTN-TDM [This.I-D] 905 (*) Suggested value 907 IANA maintains the "Generalized Multi-Protocol Label Switching 908 (GMPLS) Signaling Parameters" registry (see 909 http://www.iana.org/assignments/gmpls-sig-parameters). "Generalized 910 PIDs (G-PID)" subregistry is included in this registry, which will be 911 extended and updated by this document as below: 913 Value Type Technology Reference 914 ===== ====================== ========== 915 47 G.709 ODU-2.5G G.709 ODUk [RFC4328] 916 (IANA to update Type field) [This.I-D] 917 56 SBCON/ESCON G.709 ODUk, [RFC4328] 918 (IANA to update Type field) Lambda, Fiber [This.I-D] 919 59* Framed GFP G.709 ODUk [This.I-D] 920 60* STM-1 G.709 ODUk [This.I-D] 921 61* STM-4 G.709 ODUk [This.I-D] 922 62* InfiniBand G.709 ODUflex [This.I-D] 923 63* SDI (Serial Digital Interface) G.709 ODUk [This.I-D] 924 64* SDI/1.001 G.709 ODUk [This.I-D] 925 65* DVB_ASI G.709 ODUk [This.I-D] 926 66* G.709 ODU-1.25G G.709 ODUk [This.I-D] 927 67* G.709 ODU-Any G.709 ODUk [This.I-D] 928 68* Null Test G.709 ODUk [This.I-D] 929 69* Random Test G.709 ODUk [This.I-D] 930 70* 64B/66B GFP-F Ethernet G.709 ODUk [This.I-D] 932 (*) Suggested value 934 Upon approval of this document, IANA will define an "OTN Signal Type" 935 subregistry to the "Generalized Multi-Protocol Label Switching 936 (GMPLS) Signaling Parameters": 938 Value Signal Type Reference 939 ----- ----------- --------- 940 0 Not significant [RFC4328] 941 1 ODU1 (i.e., 2.5Gbps) [RFC4328] 942 2 ODU2 (i.e., 10Gbps) [RFC4328] 943 3 ODU3 (i.e., 40Gbps) [RFC4328] 944 4 ODU4 (i.e., 100Gbps) [this document] 945 5 Reserved (for future use) [RFC4328] 946 6 Och at 2.5Gbps [RFC4328] 947 7 OCh at 10Gbps [RFC4328] 948 8 OCh at 40Gbps [RFC4328] 949 9 OCh at 100Gbps [this document] 950 10 ODU0 (i.e., 1.25Gbps) [this document] 951 11 ODU2e (i.e., 10Gbps for FC1200 [this document] 952 and GE LAN) 953 12~19 Reserved (for future use) [this document] 954 20 ODUflex(CBR) (i.e., 1.25*N Gbps) [this document] 955 21 ODUflex(GFP-F), resizable [this document] 956 (i.e., 1.25*N Gbps) 957 22 ODUflex(GFP-F), non resizable [this document] 958 (i.e., 1.25*N Gbps) 959 23~255 Reserved (for future use) [this document] 961 New values are to be assigned via Standards Action as defined in 962 [RFC5226]. 964 11. References 966 11.1. Normative References 968 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 969 Requirement Levels", BCP 14, RFC 2119, March 1997. 971 [RFC2205] Braden, R., Zhang, L., Berson, S., Herzog, S., and S. 972 Jamin, "Resource ReSerVation Protocol (RSVP) -- Version 1 973 Functional Specification", RFC 2205, September 1997. 975 [RFC2210] Wroclawski, J., "The Use of RSVP with IETF Integrated 976 Services", RFC 2210, September 1997. 978 [RFC3209] D. Awduche et al, "RSVP-TE: Extensions to RSVP for LSP 979 Tunnels", RFC3209, December 2001. 981 [RFC3471] Berger, L., Editor, "Generalized Multi-Protocol Label 982 Switching (GMPLS) Signaling Functional Description", RFC 983 3471, January 2003. 985 [RFC3473] L. Berger, Ed., "Generalized Multi-Protocol Label Switching 986 (GMPLS) Signaling Resource ReserVation Protocol-Traffic 987 Engineering (RSVP-TE) Extensions", RFC 3473, January 2003. 989 [RFC4328] D. Papadimitriou, Ed. "Generalized Multi-Protocol Label 990 Switching (GMPLS) Signaling Extensions for G.709 Optical 991 Transport Networks Control", RFC 4328, Jan 2006. 993 [RFC6344] G. Bernstein et al, "Operating Virtual Concatenation (VCAT) 994 and the Link Capacity Adjustment Scheme (LCAS) with 995 Generalized Multi-Protocol Label Switching (GMPLS)", 996 RFC6344, August 2011. 998 [G709-2012] ITU-T, "Interfaces for the Optical Transport Network 999 (OTN)", G.709/Y.1331 Recommendation, February 2012. 1001 [G7044] ITU-T, "Hitless adjustment of ODUflex", G.7044/Y.1347, 1002 October 2011. 1004 [G7041] ITU-T, "Generic framing procedure", G.7041/Y.1303, April 1005 2011. 1007 [RFC4506] M. Eisler, Ed., "XDR: External Data Representation 1008 Standard", RFC 4506, May 2006. 1010 [IEEE] "IEEE Standard for Binary Floating-Point Arithmetic", 1011 ANSI/IEEE Standard 754-1985, Institute of Electrical and 1012 Electronics Engineers, August 1985. 1014 11.2. Informative References 1016 [OTN-FWK] Fatai Zhang et al, "Framework for GMPLS and PCE Control of 1017 G.709 Optical Transport Networks", Work in Progress: draft- 1018 ietf-ccamp-gmpls-g709-framework, June 2013. 1020 [OTN-INFO] S. Belotti et al, "Information model for G.709 Optical 1021 Transport Networks (OTN)", Work in Progress: draft-ietf- 1022 ccamp-otn-g709-info-model, June 2013. 1024 [OTN-OSPF] D. Ceccarelli et al, "Traffic Engineering Extensions to 1025 OSPF for Generalized MPLS (GMPLS) Control of Evolving G.709 1026 OTN Networks", Work in Progress: draft-ietf-ccamp-gmpls- 1027 ospf-g709v3, June 2013. 1029 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 1030 IANA Considerations Section in RFCs", BCP 26, RFC 5226, May 1031 2008. 1033 [RFC5920] Fang, L., Ed., "Security Framework for MPLS and GMPLS 1034 Networks", RFC 5920, July 2010. 1036 12. Contributors 1038 Jonathan Sadler, Tellabs 1039 Email: jonathan.sadler@tellabs.com 1041 Kam LAM, Alcatel-Lucent 1042 Email: kam.lam@alcatel-lucent.com 1044 Xiaobing Zi, Huawei Technologies 1045 Email: zixiaobing@huawei.com 1047 Francesco Fondelli, Ericsson 1048 Email: francesco.fondelli@ericsson.com 1050 Lyndon Ong, Ciena 1051 Email: lyong@ciena.com 1053 Biao Lu, infinera 1054 Email: blu@infinera.com 1056 13. Authors' Addresses 1058 Fatai Zhang (editor) 1059 Huawei Technologies 1060 F3-5-B R&D Center, Huawei Base 1061 Bantian, Longgang District 1062 Shenzhen 518129 P.R.China 1063 Phone: +86-755-28972912 1064 Email: zhangfatai@huawei.com 1066 Guoying Zhang 1067 China Academy of Telecommunication Research of MII 1068 11 Yue Tan Nan Jie Beijing, P.R.China 1069 Phone: +86-10-68094272 1070 Email: zhangguoying@mail.ritt.com.cn 1072 Sergio Belotti 1073 Alcatel-Lucent 1074 Optics CTO 1075 Via Trento 30 20059 Vimercate (Milano) Italy 1076 +39 039 6863033 1077 Email: sergio.belotti@alcatel-lucent.it 1079 Daniele Ceccarelli 1080 Ericsson 1081 Via A. Negrone 1/A 1082 Genova - Sestri Ponente 1083 Italy 1084 Email: daniele.ceccarelli@ericsson.com 1086 Khuzema Pithewan 1087 Infinera Corporation 1088 169, Java Drive 1089 Sunnyvale, CA-94089, USA 1090 Email: kpithewan@infinera.com 1092 Yi Lin 1093 Huawei Technologies 1094 F3-5-B R&D Center, Huawei Base 1095 Bantian, Longgang District 1096 Shenzhen 518129 P.R.China 1097 Phone: +86-755-28972914 1098 Email: yi.lin@huawei.com 1100 Yunbin Xu 1101 China Academy of Telecommunication Research of MII 1102 11 Yue Tan Nan Jie Beijing, P.R.China 1103 Phone: +86-10-68094134 1104 Email: xuyunbin@mail.ritt.com.cn 1105 Pietro Grandi 1106 Alcatel-Lucent 1107 Optics CTO 1108 Via Trento 30 20059 Vimercate (Milano) Italy 1109 +39 039 6864930 1110 Email: pietro_vittorio.grandi@alcatel-lucent.it 1112 Diego Caviglia 1113 Ericsson 1114 Via A. Negrone 1/A 1115 Genova - Sestri Ponente 1116 Italy 1117 Email: diego.caviglia@ericsson.com 1119 Rajan Rao 1120 Infinera Corporation 1121 169, Java Drive 1122 Sunnyvale, CA-94089 1123 USA 1124 Email: rrao@infinera.com 1126 John E Drake 1127 Juniper 1128 Email: jdrake@juniper.net 1130 Igor Bryskin 1131 Adva Optical 1132 EMail: IBryskin@advaoptical.com 1134 14. Acknowledgment 1136 The authors would like to thank Lou Berger and Deborah Brungard for 1137 their useful comments to the document. 1139 Intellectual Property 1141 The IETF Trust takes no position regarding the validity or scope of 1142 any Intellectual Property Rights or other rights that might be 1143 claimed to pertain to the implementation or use of the technology 1144 described in any IETF Document or the extent to which any license 1145 under such rights might or might not be available; nor does it 1146 represent that it has made any independent effort to identify any 1147 such rights. 1149 Copies of Intellectual Property disclosures made to the IETF 1150 Secretariat and any assurances of licenses to be made available, or 1151 the result of an attempt made to obtain a general license or 1152 permission for the use of such proprietary rights by implementers or 1153 users of this specification can be obtained from the IETF on-line IPR 1154 repository at http://www.ietf.org/ipr 1156 The IETF invites any interested party to bring to its attention any 1157 copyrights, patents or patent applications, or other proprietary 1158 rights that may cover technology that may be required to implement 1159 any standard or specification contained in an IETF Document. Please 1160 address the information to the IETF at ietf-ipr@ietf.org. 1162 The definitive version of an IETF Document is that published by, or 1163 under the auspices of, the IETF. Versions of IETF Documents that are 1164 published by third parties, including those that are translated into 1165 other languages, should not be considered to be definitive versions 1166 of IETF Documents. The definitive version of these Legal Provisions 1167 is that published by, or under the auspices of, the IETF. Versions of 1168 these Legal Provisions that are published by third parties, including 1169 those that are translated into other languages, should not be 1170 considered to be definitive versions of these Legal Provisions. 1172 For the avoidance of doubt, each Contributor to the IETF Standards 1173 Process licenses each Contribution that he or she makes as part of 1174 the IETF Standards Process to the IETF Trust pursuant to the 1175 provisions of RFC 5378. No language to the contrary, or terms, 1176 conditions or rights that differ from or are inconsistent with the 1177 rights and licenses granted under RFC 5378, shall have any effect and 1178 shall be null and void, whether published or posted by such 1179 Contributor, or included with or in such Contribution. 1181 Disclaimer of Validity 1183 All IETF Documents and the information contained therein are provided 1184 on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE 1185 REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE 1186 IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL 1187 WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY 1188 WARRANTY THAT THE USE OF THE INFORMATION THEREIN WILL NOT INFRINGE 1189 ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS 1190 FOR A PARTICULAR PURPOSE. 1192 Copyright Notice 1194 Copyright (c) 2013 IETF Trust and the persons identified as the 1195 document authors. All rights reserved. 1197 This document is subject to BCP 78 and the IETF Trust's Legal 1198 Provisions Relating to IETF Documents 1199 (http://trustee.ietf.org/license-info) in effect on the date of 1200 publication of this document. Please review these documents 1201 carefully, as they describe your rights and restrictions with respect 1202 to this document. Code Components extracted from this document must 1203 include Simplified BSD License text as described in Section 4.e of 1204 the Trust Legal Provisions and are provided without warranty as 1205 described in the Simplified BSD License.