idnits 2.17.1 draft-ietf-ccamp-gmpls-signaling-g709v3-03.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 13 instances of too long lines in the document, the longest one being 1 character 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 13, 2012) is 4304 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'G.709-V3' is mentioned on line 164, but not defined == Missing Reference: 'OTN-V3' is mentioned on line 170, but not defined == Missing Reference: 'G709-v1' is mentioned on line 196, but not defined == Missing Reference: 'RFC4606' is mentioned on line 484, but not defined == Unused Reference: 'OTN-INFO' is defined on line 1071, but no explicit reference was found in the text == Unused Reference: 'OTN-LMP' is defined on line 1080, but no explicit reference was found in the text == Unused Reference: 'G709-V2' is defined on line 1097, but no explicit reference was found in the text == Unused Reference: 'G798-V2' is defined on line 1100, but no explicit reference was found in the text == Unused Reference: 'G798-V3' is defined on line 1104, but no explicit reference was found in the text ** Downref: Normative reference to an Informational draft: draft-ietf-ccamp-gmpls-g709-framework (ref. 'OTN-FWK') ** Downref: Normative reference to an Informational draft: draft-ietf-ccamp-otn-g709-info-model (ref. 'OTN-INFO') -- No information found for draft-zhang-ccamp-gmpls-g - is the name correct? -- Possible downref: Normative reference to a draft: ref. 'OTN-LMP' -- Possible downref: Non-RFC (?) normative reference: ref. 'G709-V3' -- Possible downref: Non-RFC (?) normative reference: ref. 'G709-V3-A2' Summary: 3 errors (**), 0 flaws (~~), 10 warnings (==), 5 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 Category: Standards Track Guoying Zhang 4 CATR 5 Sergio Belotti 6 Alcatel-Lucent 7 D. Ceccarelli 8 Ericsson 9 Khuzema Pithewan 10 Infinera 11 Expires: January 13, 2013 July 13, 2012 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-03.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 January 13, 2013. 41 Abstract 43 Recent progress in ITU-T Recommendation G.709 standardization has 44 introduced new ODU containers (ODU0, ODU4, ODU2e and ODUflex) and 45 enhanced Optical Transport Networking (OTN) flexibility. Several 46 recent documents have proposed ways to modify GMPLS signaling 47 protocols to support these new OTN features. 49 It is important that a single solution is developed for use in GMPLS 50 signaling and routing protocols. This solution must support ODUk 51 multiplexing capabilities, address all of the new features, be 52 acceptable to all equipment vendors, and be extensible considering 53 continued OTN evolution. 55 This document describes the extensions to the Generalized Multi- 56 Protocol Label Switching (GMPLS) signaling to control the evolving 57 Optical Transport Networks (OTN) addressing ODUk multiplexing and new 58 features including ODU0, ODU4, ODU2e and ODUflex. 60 Conventions used in this document 62 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 63 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 64 document are to be interpreted as described in [RFC2119]. 66 Table of Contents 68 1. Introduction ................................................ 3 69 2. Terminology ................................................. 4 70 3. GMPLS Extensions for the Evolving G.709 - Overview ........... 4 71 4. Generalized Label Request .................................... 5 72 5. Extensions for Traffic Parameters for the Evolving G.709 ..... 6 73 5.1. Usage of ODUflex(CBR) Traffic Parameters ................ 8 74 5.2. Usage of ODUflex(GFP) Traffic Parameters ............... 10 75 6. Generalized Label ........................................... 11 76 6.1. New definition of ODU Generalized Label ................ 11 77 6.2. Examples ............................................... 14 78 6.3. Label Distribution Procedure ........................... 15 79 6.3.1. Notification on Label Error ....................... 16 80 6.4. Supporting Virtual Concatenation and Multiplication .... 17 81 7. Supporting Multiplexing Hierarchy ........................... 17 82 7.1. Extension to LSP_ATTRIBUTES Object ..................... 18 83 7.2. ODU FA-LSP Creation .................................... 19 84 8. Supporting Hitless Adjustment of ODUflex (GFP) .............. 20 85 9. Control Plane Backward Compatibility Considerations.......... 21 86 10. Security Considerations................................. ... 22 87 11. IANA Considerations.................................. ...... 22 88 12. References ................................................. 23 89 12.1. Normative References................................... 23 90 12.2. Informative References................................. 25 91 13. Contributors ............................................... 25 92 14. Authors' Addresses ......................................... 26 93 15. Acknowledgment ............................................. 28 95 1. Introduction 97 Generalized Multi-Protocol Label Switching (GMPLS) [RFC3945] extends 98 MPLS to include Layer-2 Switching (L2SC), Time-Division Multiplex 99 (e.g., SONET/SDH, PDH, and ODU), Wavelength (OCh, Lambdas) Switching, 100 and Spatial Switching (e.g., incoming port or fiber to outgoing port 101 or fiber). [RFC3471] presents a functional description of the 102 extensions to Multi-Protocol Label Switching (MPLS) signaling 103 required to support Generalized MPLS. RSVP-TE-specific formats and 104 mechanisms and technology specific details are defined in [RFC3473]. 106 With the evolution and deployment of G.709 technology, it is 107 necessary that appropriate enhanced control technology support be 108 provided for G.709. [RFC4328] describes the control technology 109 details that are specific to foundation G.709 Optical Transport 110 Networks (OTN), as specified in the ITU-T Recommendation G.709 [G709- 111 V1], for ODUk deployments without multiplexing. 113 In addition to increasing need to support ODUk multiplexing, the 114 evolution of OTN has introduced additional containers and new 115 flexibility. For example, ODU0, ODU2e, ODU4 containers and ODUflex 116 are developed in [G709-V3]. 118 In addition, the following issues require consideration: 120 - Support for Hitless Adjustment of ODUflex (GFP) (HAO), which is 121 defined in [G.7044]. 123 - Support for Tributary Port Number. The Tributary Port Number 124 has to be negotiated on each link for flexible assignment of 125 tributary ports to tributary slots in case of LO-ODU over HO- 126 ODU (e.g., ODU2 into ODU3). 128 Therefore, it is clear that [RFC4328] has to be updated or superceded 129 in order to support ODUk multiplexing, as well as other ODU 130 enhancements introduced by evolution of OTN standards. 132 This document updates [RFC4328] extending the G.709 ODUk traffic 133 parameters and also presents a new OTN label format which is very 134 flexible and scalable. 136 2. Terminology 138 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 139 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 140 document are to be interpreted as described in [RFC2119]. 142 3. GMPLS Extensions for the Evolving G.709 - Overview 144 New features for the evolving OTN, for example, new ODU0, ODU2e, ODU4 145 and ODUflex containers are specified in [G709-V3]. The corresponding 146 new signal types are summarized below: 148 - Optical Channel Transport Unit (OTUk): 149 . OTU4 151 - Optical Channel Data Unit (ODUk): 152 . ODU0 153 . ODU2e 154 . ODU4 155 . ODUflex 157 A new Tributary Slot Granularity (TSG) (i.e., 1.25 Gbps) is also 158 described in [G709-V3]. Thus, there are now two TS granularities for 159 the foundation OTN ODU1, ODU2 and ODU3 containers. The TS granularity 160 at 2.5 Gbps is used on legacy interfaces while the new 1.25 Gbps is 161 used on the new interfaces. 163 In addition to the support of ODUk mapping into OTUk (k = 1, 2, 3, 4), 164 the evolving OTN [G.709-V3] encompasses the multiplexing of ODUj (j = 165 0, 1, 2, 2e, 3, flex) into an ODUk (k > j), as described in Section 166 3.1.2 of [OTN-FWK]. 168 Virtual Concatenation (VCAT) of OPUk (OPUk-Xv, k = 1/2/3, X = 1...256) 169 is also supported by [OTN-V3]. Note that VCAT of OPU0 / OPU2e / OPU4 170 / OPUflex is not supported per [OTN-V3]. 172 [RFC4328] describes GMPLS signaling extensions to support the control 173 for G.709 Optical Transport Networks (OTN) [G709-V1]. However, 174 [RFC4328] needs to be updated because it does not provide the means 175 to signal all the new signal types and related mapping and 176 multiplexing functionalities. Moreover, it supports only the 177 deprecated auto-MSI mode which assumes that the Tributary Port Number 178 is automatically assigned in the transmit direction and not checked 179 in the receive direction. 181 This document extends the G.709 traffic parameters described in 182 [RFC4328] and presents a new flexible and scalable OTN label format. 184 Additionally, procedures about Tributary Port Number assignment 185 through control plane are also provided in this document. 187 4. Generalized Label Request 189 The Generalized Label Request, as described in [RFC3471], carries the 190 LSP Encoding Type, the Switching Type and the Generalized Protocol 191 Identifier (G-PID). 193 [RFC4328] extends the Generalized Label Request, introducing two new 194 code-points for the LSP Encoding Type (i.e., G.709 ODUk (Digital Path) 195 and G.709 Optical Channel) and adding a list of G-PID values in order 196 to accommodate [G709-v1]. 198 This document follows these extensions and a new Switching Type is 199 introduced to indicate the ODUk switching capability [G709-V3] in 200 order to support backward compatibility with [RFC4328], as described 201 in [OTN-FWK]. The new Switching Type (101, TBA by IANA) is defined in 202 [OTN-OSPF]. 204 This document also updates the G-PID values defined in [RFC4328]: 206 Value G-PID Type 208 ----- ---------- 210 47 ODU-2.5G: transport of Digital Paths at 2.5, 10 and 40 211 Gbps via 2.5Gbps TSG 213 49 CBRa: asynchronous Constant Bit Rate (i.e., mapping of 214 CBR2G5, CBR10G and CBR40G) 216 50 CBRb: bit synchronous Constant Bit Rate (i.e., mapping of 217 CBR2G5, CBR10G, CBR40G, CBR10G3 and supra-2.488 CBR 218 Gbit/s signal (carried by OPUflex)) 220 32 ATM: mapping at 1.25, 2.5, 10 and 40 Gbps 222 51 BSOT: non-specific client Bit Stream with Octet Timing (i.e., 223 Mapping of 1.25, 2.5, 10, 40 and 100 Gbps Bit Stream) 225 52 BSNT: non-specific client Bit Stream without Octet Timing 226 (i.e., Mapping of 1.25, 2.5, 10, 40 and 100 Gbps Bit 227 Stream) 229 Note: Values 32, 47, 49 and 50 include mapping of SDH. 231 In the case of ODU multiplexing, the LO ODU (i.e., the client signal) 232 may be multiplexed into HO ODU via 1.25G TSG, 2.5G TSG or any one of 233 them (i.e., TSG Auto_Negotiation is enabled). Since the G-PID type 234 "ODUk" defined in [RFC4328] is only used for 2.5Gbps TSG, two new G- 235 PID types are needed: 237 - ODU-1.25G: transport of Digital Paths at 1.25, 2.5, 10, 40 and 238 100 Gbps via 1.25Gbps TSG 240 - ODU-any: transport of Digital Paths at 1.25, 2.5, 10, 40 and 100 241 Gbps via 1.25 or 2.5Gbps TSG (i.e., the fallback 242 procedure is enabled and the default value of 1.25Gbps 243 TSG can be fallen back to 2.5Gbps if needed) 245 In addition, some other new G-PID types are defined to support other 246 new client signals described in [G709-V3]: 248 - CBRc: Mapping of constant bit-rate signals with justification 249 into OPUk (k = 0, 1, 2, 3, 4) via GMP (i.e., mapping of 250 sub-1.238, supra-1.238 to sub-2.488, close-to 9.995, 251 close-to 40.149 and close-to 104.134 Gbit/s CBR client 252 signal) 254 - 1000BASE-X: Mapping of a 1000BASE-X signal via timing 255 transparent transcoding into OPU0 257 - FC-1200: Mapping of a FC-1200 signal via timing transparent 258 transcoding into OPU2e 260 The following table summarizes the new G-PID values with respect to 261 the LSP Encoding Type: 263 Value G-PID Type LSP Encoding Type 264 ----- ---------- ----------------- 265 59(TBA) G.709 ODU-1.25G G.709 ODUk 266 60(TBA) G.709 ODU-any G.709 ODUk 267 61(TBA) CBRc G.709 ODUk 268 62(TBA) 1000BASE-X G.709 ODUk (k=0) 269 63(TBA) FC-1200 G.709 ODUk (k=2e) 271 Note: Values 59 and 60 include mapping of SDH. 273 5. Extensions for Traffic Parameters for the Evolving G.709 275 The traffic parameters for G.709 are defined as follows: 277 0 1 2 3 278 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 279 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 280 | Signal Type | Reserved | NMC/ Tolerance | 281 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 282 | NVC | Multiplier (MT) | 283 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 284 | Bit_Rate | 285 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 287 The Signal Type needs to be extended in order to cover the new Signal 288 Type introduced by the evolving OTN. The new Signal Type values are 289 extended as follows: 291 Value Type 292 ----- ---- 293 0 Not significant 294 1 ODU1 (i.e., 2.5 Gbps) 295 2 ODU2 (i.e., 10 Gbps) 296 3 ODU3 (i.e., 40 Gbps) 297 4 ODU4 (i.e., 100 Gbps) 298 5 Reserved (for future use) 299 6 OCh at 2.5 Gbps 300 7 OCh at 10 Gbps 301 8 OCh at 40 Gbps 302 9 OCh at 100 Gbps 303 10 ODU0 (i.e., 1.25 Gbps) 304 11 ODU2e (i.e., 10Gbps for FC1200 and GE LAN) 305 12~19 Reserved (for future use) 306 20 ODUflex(CBR) (i.e., 1.25*N Gbps) 307 21 ODUflex(GFP-F), resizable (i.e., 1.25*N Gbps) 308 22 ODUflex(GFP-F), non resizable (i.e., 1.25*N Gbps) 309 23~255 Reserved (for future use) 311 NMC/Tolerance: 313 This field is redefined from the original definition in [RFC4328]. 314 NMC field defined in [RFC4328] cannot be fixed value for an end-to- 315 end circuit involving dissimilar OTN link types. For example, ODU2e 316 requires 9 TS on ODU3 and 8 TS on ODU4. Usage of NMC field is 317 deprecated and should be used only with [RFC4328] generalized label 318 format for backwards compatibility reasons. For the new generalized 319 label format as defined in this document this field is interpreted as 320 Tolerance. 322 In case of ODUflex(CBR), the Bit_Rate and Tolerance fields MUST be 323 used together to represent the actual bandwidth of ODUflex, where: 325 - The Bit_Rate field indicates the nominal bit rate of ODUflex(CBR) 326 expressed in bytes per second, encoded as a 32-bit IEEE single- 327 precision floating-point number (referring to [RFC4506] and 328 [IEEE]). The value contained in the Bit Rate field has to keep 329 into account both 239/238 factor and the Transcoding factor. 331 - The Tolerance field indicates the bit rate tolerance (part per 332 million, ppm) of the ODUflex(CBR) encoded as an unsigned integer, 333 which is bounded in 0~100ppm. 335 For example, for an ODUflex(CBR) service with Bit_Rate = 2.5Gbps and 336 Tolerance = 100ppm, the actual bandwidth of the ODUflex is: 338 2.5Gbps * (1 +/- 100ppm) 340 In case of ODUflex(GFP), the Bit_Rate field is used to indicate the 341 nominal bit rate of the ODUflex(GFP), which implies the number of 342 tributary slots requested for the ODUflex(GFP). Since the tolerance 343 of ODUflex(GFP) makes no sense on tributary slot resource reservation, 344 the Tolerance field for ODUflex(GFP) is not necessary and MUST be 345 filled with 0. 347 In case of other ODUk signal types, the Bit_Rate and Tolerance fields 348 are not necessary and MUST be set to 0. 350 The usage of the NVC and Multiplier (MT) fields are the same as 351 [RFC4328]. 353 5.1. Usage of ODUflex(CBR) Traffic Parameters 355 In case of ODUflex(CBR), the information of Bit_Rate and Tolerance in 356 the ODUflex traffic parameters MUST be used to determine the total 357 number of tributary slots N in the HO ODUk link to be reserved. Here: 359 N = Ceiling of 361 ODUflex(CBR) nominal bit rate * (1 + ODUflex(CBR) bit rate tolerance) 362 --------------------------------------------------------------------- 363 ODTUk.ts nominal bit rate * (1 - HO OPUk bit rate tolerance) 365 In this formula, the ODUflex(CBR) nominal bit rate is the bit rate of 366 the ODUflex(CBR) on the line side, i.e., the client signal bit rate 367 after applying the 239/238 factor (according to clause 7.3 table 7.2 368 of [G709-V3]) and the transcoding factor T (if needed) on the CBR 369 client. According to clauses 17.7.3, 17.7.4 and 17.7.5 of [G709-V3]: 371 ODUflex(CBR) nominal bit rate = CBR client bit rate * (239/238) / T 373 The ODTUk.ts nominal bit rate is the nominal bit rate of the 374 tributary slot of ODUk, as shown in Table 1 (referring to [G709-V3]). 376 Table 1 - Actual TS bit rate of ODUk (in Gbps) 378 ODUk.ts Minimum Nominal Maximum 379 ---------------------------------------------------------- 380 ODU2.ts 1.249 384 632 1.249 409 620 1.249 434 608 381 ODU3.ts 1.254 678 635 1.254 703 729 1.254 728 823 382 ODU4.ts 1.301 683 217 1.301 709 251 1.301 735 285 384 Note that: 386 Minimum bit rate of ODUTk.ts = 387 ODTUk.ts nominal bit rate * (1 - HO OPUk bit rate tolerance) 389 Maximum bit rate of ODTUk.ts = 390 ODTUk.ts nominal bit rate * (1 + HO OPUk bit rate tolerance) 392 Where: HO OPUk bit rate tolerance = 20ppm 394 Therefore, a node receiving a PATH message containing ODUflex(CBR) 395 nominal bit rate and tolerance can allocate precise number of 396 tributary slots and set up the cross-connection for the ODUflex 397 service. 399 Note that for different ODUk, the bit rates of the tributary slots 400 are different, and so the total number of tributary slots to be 401 reserved for the ODUflex(CBR) may not be the same on different HO 402 ODUk links. 404 An example is given below to illustrate the usage of ODUflex(CBR) 405 traffic parameters. 407 As shown in Figure 1, assume there is an ODUflex(CBR) service 408 requesting a bandwidth of (2.5Gbps, +/-100ppm) from node A to node C. 409 In other words, the ODUflex traffic parameters indicate that Signal 410 Type is 20 (ODUflex(CBR)), Bit_Rate is 2.5Gbps and Tolerance is 411 100ppm. 413 +-----+ +---------+ +-----+ 414 | +-------------+ +-----+ +-------------+ | 415 | +=============+\| ODU |/+=============+ | 416 | +=============+/| flex+-+=============+ | 417 | +-------------+ | |\+=============+ | 418 | +-------------+ +-----+ +-------------+ | 419 | | | | | | 420 | | ....... | | ....... | | 421 | A +-------------+ B +-------------+ C | 422 +-----+ HO ODU4 +---------+ HO ODU2 +-----+ 424 =========: TS occupied by ODUflex 425 ---------: free TS 427 Figure 1 - Example of ODUflex(CBR) Traffic Parameters 429 - On the HO ODU4 link between node A and B: 431 The maximum bit rate of the ODUflex(CBR) equals 2.5Gbps * (1 + 432 100ppm), and the minimum bit rate of the tributary slot of ODU4 433 equals 1.301 683 217Gbps, so the total number of tributary slots 434 N1 to be reserved on this link is: 436 N1 = ceiling (2.5Gbps * (1 + 100ppm) / 1.301 683 217Gbps) = 2 438 - On the HO ODU2 link between node B and C: 440 The maximum bit rate of the ODUflex equals 2.5Gbps * (1 + 100ppm), 441 and the minimum bit rate of the tributary slot of ODU2 equals 442 1.249 384 632Gbps, so the total number of tributary slots N2 to 443 be reserved on this link is: 445 N2 = ceiling (2.5Gbps * (1 + 100ppm) / 1.249 384 632Gbps) = 3 447 5.2. Usage of ODUflex(GFP) Traffic Parameters 449 [G709-V3-A2] recommends that the ODUflex(GFP) will fill an integral 450 number of tributary slots of the smallest HO ODUk path over which the 451 ODUflex(GFP) may be carried, as shown in Table 2. 453 Table 2 - Recommended ODUflex(GFP) bit rates and tolerance 455 ODU type | Nominal bit-rate | Tolerance 457 --------------------------------+------------------+----------- 458 ODUflex(GFP) of n TS, 1<=n<=8 | n * ODU2.ts | +/-100 ppm 459 ODUflex(GFP) of n TS, 9<=n<=32 | n * ODU3.ts | +/-100 ppm 460 ODUflex(GFP) of n TS, 33<=n<=80 | n * ODU4.ts | +/-100 ppm 462 According to this table, the Bit_Rate field for ODUflex(GFP) MUST 463 equal to one of the 80 values listed below: 465 1 * ODU2.ts; 2 * ODU2.ts; ...; 8 * ODU2.ts; 466 9 * ODU3.ts; 10 * ODU3.ts, ...; 32 * ODU3.ts; 467 33 * ODU4.ts; 34 * ODU4.ts; ...; 80 * ODU4.ts. 469 In this way, the number of required tributary slots for the 470 ODUflex(GFP) (i.e., the value of "n" in Table 2) can be deduced from 471 the Bit_Rate field. 473 6. Generalized Label 475 [RFC3471] has defined the Generalized Label which extends the 476 traditional label by allowing the representation of not only labels 477 which are sent in-band with associated data packets, but also labels 478 which identify time-slots, wavelengths, or space division multiplexed 479 positions. The format of the corresponding RSVP-TE Generalized Label 480 object is defined in the Section 2.3 of [RFC3473]. 482 However, for different technologies, we usually need use specific 483 label rather than the Generalized Label. For example, the label 484 format described in [RFC4606] could be used for SDH/SONET, the label 485 format in [RFC4328] for G.709. 487 6.1. New definition of ODU Generalized Label 489 In order to be compatible with new types of ODU signal and new types 490 of tributary slot, the following new ODU label format MUST be used: 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 499 The ODU Generalized Label is used to indicate how the LO ODUj signal 500 is multiplexed into the HO ODUk link. Note that the LO OUDj signal 501 type is indicated by traffic parameters, while the type of HO ODUk 502 link can be figured out locally according to the identifier of the 503 selected interface carried in the IF_ID RSVP_HOP Object. 505 TPN (12 bits): indicates the Tributary Port Number (TPN) for the 506 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 As per [G709-V3], 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-V3], the TPN field MUST be set as according to the 528 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 is not 563 corresponding to the TS number as per [G709-V3]. 565 Length (12 bits): indicates the number of bit of the Bit Map field, 566 i.e., the total number of TS in the HO ODUk link. 568 In case of an ODUk mapped into OTUk, there is no need to indicate 569 which tributary slots will be used, so the length field MUST be set 570 to 0. 572 Bit Map (variable): indicates which tributary slots in HO ODUk that 573 the LO ODUj will be multiplexed into. The sequence of the Bit Map is 574 consistent with the sequence of the tributary slots in HO ODUk. Each 575 bit in the bit map represents the corresponding tributary slot in HO 576 ODUk with a value of 1 or 0 indicating whether the tributary slot 577 will be used by LO ODUj or not. 579 Padded bits are added behind the Bit Map to make the whole label a 580 multiple of four bytes if necessary. Padded bit MUST be set to 0 and 581 MUST be ignored. 583 Note that the Length field in the label format can also be used to 584 indicate the TS type of the HO ODUk (i.e., TS granularity at 1.25Gbps 585 or 2.5Gbps) since the HO ODUk type can be known from IF_ID RSVP_HOP 586 Object. In some cases when there is no LMP (Link Management Protocol) 587 or routing to make the two end points of the link to know the TSG, 588 the TSG information used by another end can be deduced from the label 589 format. For example, for HO ODU2 link, the value of the length filed 590 will be 4 or 8, which indicates the TS granularity is 2.5Gbps or 591 1.25Gbps, respectively. 593 6.2. Examples 595 The following examples are given in order to illustrate the label 596 format described in the previous sections of this document. 598 (1) ODUk into OTUk mapping: 600 In such conditions, the downstream node along an LSP returns a label 601 indicating that the ODUk (k=1, 2, 3, 4) is directly mapped into the 602 corresponding OTUk. The following example label indicates an ODU1 603 mapped into OTU1. 605 0 1 2 3 606 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 607 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 608 | TPN = 0 | Reserved | Length = 0 | 609 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 611 (2) ODUj into ODUk multiplexing: 613 In such conditions, this label indicates that an ODUj is multiplexed 614 into several tributary slots of OPUk and then mapped into OTUk. Some 615 instances are shown as follow: 617 - ODU0 into ODU2 Multiplexing: 619 0 1 2 3 620 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 621 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 622 | TPN = 2 | Reserved | Length = 8 | 623 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 624 |0 1 0 0 0 0 0 0| Padded Bits (0) | 625 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 627 This above label indicates an ODU0 multiplexed into the second 628 tributary slot of ODU2, wherein there are 8 TS in ODU2 (i.e., the 629 type of the tributary slot is 1.25Gbps), and the TPN value is 2. 631 - ODU1 into ODU2 Multiplexing with 1.25Gbps TS granularity: 633 0 1 2 3 634 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 635 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 636 | TPN = 1 | Reserved | Length = 8 | 637 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 638 |0 1 0 1 0 0 0 0| Padded Bits (0) | 639 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 641 This above label indicates an ODU1 multiplexed into the 2nd and the 642 4th tributary slot of ODU2, wherein there are 8 TS in ODU2 (i.e., the 643 type of the tributary slot is 1.25Gbps), and the TPN value is 1. 645 - ODU2 into ODU3 Multiplexing with 2.5Gbps TS granularity: 647 0 1 2 3 648 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 649 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 650 | TPN = 1 | Reserved | Length = 16 | 651 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 652 |0 1 1 0 1 0 1 0 0 0 0 0 0 0 0 0| Padded Bits (0) | 653 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 655 This above label indicates an ODU2 multiplexed into the 2nd, 3rd, 5th 656 and 7th tributary slot of ODU3, wherein there are 16 TS in ODU3 (i.e., 657 the type of the tributary slot is 2.5Gbps), and the TPN value is 1. 659 6.3. Label Distribution Procedure 661 This document does not change the existing label distribution 662 procedures [RFC4328] for GMPLS except that the new ODUk label MUST be 663 processed as follows. 665 When a node receives a generalized label request for setting up an 666 ODUj LSP from its upstream neighbor node, the node MUST generate an 667 ODU label according to the signal type of the requested LSP and the 668 free resources (i.e., free tributary slots of ODUk) that will be 669 reserved for the LSP, and send the label to its upstream neighbor 670 node. 672 In case of ODUj to ODUk multiplexing, the node MUST firstly determine 673 the size of the Bit Map field according to the signal type and the 674 tributary slot type of ODUk, and then set the bits to 1 in the Bit 675 Map field corresponding to the reserved tributary slots. The node 676 MUST also assign a valid TPN, which does not collide with other TPN 677 value used by existing LO ODU connections in the selected HO ODU link, 678 and configure the expected multiplex structure identifier (ExMSI) 679 using this TPN. Then, the assigned TPN is filled into the label. 681 In case of ODUk to OTUk mapping, the node only needs to fill the ODUj 682 and the ODUk fields with corresponding values in the label. Other 683 bits are reserved and MUST be set to 0. 685 In order to process a received ODU label, the node MUST firstly learn 686 which ODU signal type is multiplexed or mapped into which ODU signal 687 type accordingly to the traffic parameters and the IF_ID RSVP_HOP 688 Object in the received message. 690 In case of ODUj to ODUk multiplexing, the node MUST retrieve the 691 reserved tributary slots in the ODUk by its downstream neighbor node 692 according to the position of the bits that are set to 1 in the Bit 693 Map field. The node determines the TS type (according to the total TS 694 number of the ODUk, or pre-configured TS type), so that the node, 695 based on the TS type, can multiplex the ODUj into the ODUk. The node 696 MUST also retrieve the TPN value assigned by its downstream neighbor 697 node from the label, and fill the TPN into the related MSI byte(s) in 698 the OPUk overhead in the data plane, so that the downstream neighbor 699 node can check whether the TPN received from the data plane is 700 consistent with the ExMSI and determine whether there is any mismatch 701 defect. 703 In case of ODUk to OTUk mapping, the size of Bit Map field MUST be 0 704 and no additional procedure is needed. 706 Note that the procedures of other label related objects (e.g., 707 Upstream Label, Label Set) are similar to the one described above. 709 Note also that the TPN in the label_ERO MAY not be assigned (i.e., 710 TPN field = 0) if the TPN is requested to be assigned locally. 712 6.3.1. Notification on Label Error 714 When receiving an ODUk label from the neighbor node, the node SHOULD 715 check the integrity of the label. An error message containing an 716 "Unacceptable label value" indication ([RFC3209]) SHOULD be sent if 717 one of the following cases occurs: 719 - Invalid value in the length field. 721 - The selected link only supports 2.5Gbps TS granularity while the 722 Length field in the label along with ODUk signal type indicates 723 the 1.25Gbps TS granularity; 725 - The label includes an invalid TPN value that breaks the TPN 726 assignment rules; 728 - The reserved resources (i.e., the number of "1" in the Bit Map 729 field) do not match with the Traffic Parameters. 731 6.4. Supporting Virtual Concatenation and Multiplication 733 As per [RFC6344], the VCGs can be created using Co-Signaled style or 734 Multiple LSPs style. 736 In case of Co-Signaled style, the explicit ordered list of all labels 737 reflects the order of VCG members, which is similar to [RFC4328]. In 738 case of multiplexed virtually concatenated signals (NVC > 1), the 739 first label indicates the components of the first virtually 740 concatenated signal; the second label indicates the components of the 741 second virtually concatenated signal; and so on. In case of 742 multiplication of multiplexed virtually concatenated signals (MT > 1), 743 the first label indicates the components of the first multiplexed 744 virtually concatenated signal; the second label indicates components 745 of the second multiplexed virtually concatenated signal; and so on. 747 In case of Multiple LSPs style, multiple control plane LSPs are 748 created with a single VCG and the VCAT Call can be used to associate 749 the control plane LSPs. The procedures are similar to section 6 of 750 [RFC6344]. 752 7. Supporting Multiplexing Hierarchy 754 As described in [OTN-FWK], one ODUj connection can be nested into 755 another ODUk (j| 770 | | | | 771 | |<---- ODU2 Connection ----->| | 772 | | | | 773 +----+ +----+ +----+ +----+ +----+ 774 | N1 +---------+ N2 +=========+ N3 +=========+ N4 +---------+ N5 | 775 +----+ +----+ +----+ +----+ +----+ 776 ODU3 link ODU3 link ODU3 link ODU3 link 778 Figure 2 - Example of multiplexing hierarchy 780 The control plane signaling should support the provisioning of 781 hierarchical multiplexing. Two methods are provided below (taking 782 Figure 2 as example): 784 - Using the multi-layer network signaling described in [RFC4206], 785 [RFC6107] and [RFC6001] (including related modifications, if 786 needed). That is, when the signaling message for ODUO connection 787 arrives at N2, a new RSVP session between N2 and N4 is triggered 788 to create the ODU2 connection. This ODU2 connection is treated as 789 a Forwarding Adjacency (FA) after it is created. And then the 790 signaling procedure for the ODU0 connection can be continued using 791 the resource of the ODU2 FA. 793 - The ODU2 FA-LSP is created in advance based on network planning, 794 which is treated as an FA. Then the ODU0 connection can be created 795 using the resource of the ODU2 FA. In this case, the ODU2 FA-LSP 796 and inner ODU0 connections are created separately. 798 For both methods, when creating an FA-LSP(e.g., ODU2 FA-LSP), the 799 penultimate hop needs to choose a correct outgoing interface for the 800 ODU2 connection, so that the destination node can support 801 multiplexing and de-multiplexing LO ODU signal(e.g., ODU0). In order 802 to choose a correct outgoing interface for the penultimate hop of the 803 FA-LSP, multiplexing capability (i.e., what client signal type that 804 can be adapted directly to this FA-LSP) should be carried in the 805 signaling to setup this FA-LSP. In addition, when Auto_Negotiation in 806 the data plane is not enabled, TS granularity may also be needed. 808 7.1. Extension to LSP_ATTRIBUTES Object 810 In order to indicate the adaptation information for a requested FA- 811 LSP (i.e., the server layer LSP) to carry the client LSP, a new type 812 of Attributes TLV of the LSP_ATTRIBUTES Object (Class-Num = 197, C- 813 Type = 1, defined in [RFC5420]) is defined: 815 0 1 2 3 816 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 817 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 818 | Type = 2 (ODU adaptation) | Length | 819 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 820 | Reserved | Signal Type | Reserved | 821 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 822 | | 823 | ... | 824 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 825 | Reserved | Signal Type | Reserved | 826 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 828 One or more ODU adaptation TLVs can be carried to indicate the 829 desired adaptation capabilities. Each of an ODU adaptation TLV for 830 each branch of the client signal multiplexing supported by the server 831 LSP MUST be used. Inside each TLV a row for each stage of the 832 hierarchy MUST be included. 834 A row for the server stage MUST NOT be included as it is already 835 signaled via the Traffic Parameters. 837 The number of stages is implicitly inferred from the length value. 839 Signal Type: as defined in [RFC4328] and this document. 841 For example, in order to create ODU3 FA-LSP passing through a set of 842 ODU4 links to perform ODU1->ODU2->ODU3 hierarchy, the ODU adaptation 843 TLV can be used to indicate the ODU2 into ODU3 multiplexing and ODU1 844 into ODU2 multiplexing stages. 846 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 847 | Type = 2 (ODU adaptation) | Length = 8 | 848 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 849 | Reserved | Sig. = ODU2 | Reserved | 850 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 851 | Reserved | Sig. = ODU1 | Reserved | 852 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 854 7.2. ODU FA-LSP Creation 856 When creating an ODU FA-LSP to carry lower ODU, the source node (e.g., 857 node N2 in Figure 2) can include the LSP_ATTRIBUTES object to specify 858 the desired ODU adaptation capabilities. 860 On receiving the Path message, the penultimate node on the FA-LSP 861 (e.g., node N3 in Figure 2) MUST select an outgoing link which can 862 support the TS granularity (indicated in the G-PID filed in Section 4) 863 and the multiplexing hierarchy (listed in the LSP_ATTRIBUTES object). 864 If no link supporting the specified hierarchy capabilities or TSG, a 865 ParhErr message with Error Code = 38 (LSP Hierarchy Issue) and Error 866 Value = y1(TBA) MUST be sent back to upstream. 868 Intermediate nodes (except end points and penultimate node) along the 869 FA-LSP don't need to process the ODU adaptation TLV, which SHOULD be 870 forwarded to the next node in the Path message without any 871 modification. 873 8. Supporting Hitless Adjustment of ODUflex (GFP) 875 [G.7044] describes the procedure of ODUflex (GFP) hitless resizing 876 using LCR (Link Connection Resize) and BWR (Bandwidth Resize) 877 protocols in OTN data plane. 879 For the control plane, signaling messages are required to initiate 880 the adjustment procedure. Section 2.5 and Section 4.6.4 of [RFC3209] 881 describe how the Share Explicit (SE) style is used in TE network for 882 bandwidth increasing and decreasing, which is still applicable for 883 triggering the ODUflex (GFP) adjustment procedure in data plane. 885 Note that the SE style SHOULD be used at the beginning when creating 886 a resizable ODUflex connection (Signal Type = 21). Otherwise an error 887 with Error Code "Conflicting reservation style" will be generated 888 when performing bandwidth adjustment. 890 If any node along the ODUflex connection doesn't support hitless 891 resizing, a Notify message with Error Code = x2 and Error Value = y1 892 will be sent to the source node. The source node MAY keep the 893 connection and treat it as a non resizable ODUflex connection, or MAY 894 tear it down, depending on the local policy. 896 - Bandwidth increasing 898 In order to increase the bandwidth of an ODUflex (GFP) connection, 899 a Path message with SE style (keeping Tunnel ID unchanged and 900 assigning a new LSP ID) is sent along the path. 902 A downstream node compares the old Traffic Parameters (stored 903 locally) with the new one carried in the Path message, to 904 determine the number of TS to be added. After choosing and 905 reserving new free TS, the downstream node sends back a Resv 906 message carrying both the old and new LABEL Objects in the SE 907 flow descriptor, so that its upstream neighbor can determine 908 which TS are added. And the LCR protocol between each pair of 909 neighbor nodes is triggered. 911 On the source node, the BWR protocol will be triggered by the 912 successful completion of LCR protocols on every hop after Resv 913 message is processed. On success of BWR, the source node SHOULD 914 send a PathTear message to delete the old control state (i.e., 915 the control state of the ODUflex (GFP) before resizing) on the 916 control plane. 918 - Bandwidth decreasing 920 The SE style can also be used for ODUflex bandwidth decreasing. 921 For each pair of neighbor nodes, the sending and receiving Resv 922 message with old and new LABEL Objects will trigger the first 923 step of LCR between them to perform LCR handshake. On the source 924 node, the BWR protocol will be triggered by the successful 925 completion of LCR handshake on every hop after Resv message is 926 processed. On success of BWR, the second step of LCR, i.e., link 927 connection decrease procedure will be started on every hop of the 928 connection. 930 Similarly, after completion of bandwidth decreasing, a ResvErr 931 message SHOULD be sent to tear down the old control state. 933 9. Control Plane Backward Compatibility Considerations 935 Since the [RFC4328] has been deployed in the network for the nodes 936 that support [G709-V1], control plane backward compatibility SHOULD 937 be taken into consideration when the new nodes (supporting [G709-V3] 938 and RSVP-TE extensions defined in this document) and the legacy nodes 939 (supporting [G709-V1] and [RFC4328]) are interworking. 941 The backward compatibility needs to be considered only when 942 controlling ODU1 or ODU2 or ODU3 connection, because legacy nodes can 943 only support these three ODU signal types. In such case, new nodes 944 can fall back to use signaling message defined in [RFC4328] when 945 detecting legacy node on the path. More detailedly: 947 o When receiving Path message using [RFC4328] (i.e., Switching Type 948 = 100), a new node SHOULD follow [RFC4328] to process and reply it. 950 o A source node of an ODU LSP can send Path message using new OTN 951 control message (with new Switching Type = 101, TBA by IANA). If 952 there is legacy node on the LSP, it will fail to process the 953 Generalized Label Request Object because of unknown of the new 954 Switching Type, and reply a PathErr message indicating unknown of 955 this object. The source node MAY re-signal the Path message using 956 [RFC4328], depending on local policies. 958 o Alternatively, if a new node has known that its neighbor only 959 supports [RFC4328] in advance (e.g., through manual configuration 960 or auto discovery mechanism), the new node MAY act as an RSVP 961 agent to translate new RSVP-TE message into old one before sending 962 to its neighbor. 964 No special compatibility consideration needs to be taken if the 965 legacy device has updated its control plane to support this document. 967 10. Security Considerations 969 This document introduces no new security considerations to the 970 existing GMPLS signaling protocols. Referring to [RFC3473], further 971 details of the specific security measures are provided. Additionally, 972 [GMPLS-SEC] provides an overview of security vulnerabilities and 973 protection mechanisms for the GMPLS control plane. 975 11. IANA Considerations 977 - G.709 SENDER_TSPEC and FLOWSPEC objects: 979 The traffic parameters, which are carried in the G.709 980 SENDER_TSPEC and FLOWSPEC objects, do not require any new object 981 class and type based on [RFC4328]: 983 o G.709 SENDER_TSPEC Object: Class = 12, C-Type = 5 [RFC4328] 985 o G.709 FLOWSPEC Object: Class = 9, C-Type = 5 [RFC4328] 987 - Generalized Label Object: 989 The new defined ODU label (Section 6) is a kind of generalized 990 label. Therefore, the Class-Num and C-Type of the ODU label is 991 the same as that of generalized label described in [RFC3473], 992 i.e., Class-Num = 16, C-Type = 2. 994 - LSP_ATTIBUTES Object: 996 New TLV with Type = 2 (TBA). This TLV is carried in the 997 LSP_ATTIBUTES Object (Class-Num = 197, C-Type = 1). See Section 7 998 for the detail definition. 1000 - Error Code = 38 (LSP Hierarchy Issue, referring to [RFC6107]): 1002 A new Error Value is added to the Error Code "LSP Hierarchy 1003 Issue": 1005 Error Value Error case 1006 -------------------------------------------------------------- 1007 y1 Last hop of an ODU FA-LSP doesn't support 1008 specified adaptation capabilities (Section 7.2). 1010 - Error Code = x2: 1012 New Error Code, indicating errors occurring when controlling a 1013 resizable ODUflex connection. 1015 Error Value Error case 1016 -------------------------------------------------------------- 1017 y1 Do not support hitless assignment of ODUflex (GFP) 1018 (Section 8). 1020 12. References 1022 12.1. Normative References 1024 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1025 Requirement Levels", BCP 14, RFC 2119, March 1997. 1027 [RFC4328] D. Papadimitriou, Ed. "Generalized Multi-Protocol Label 1028 Switching (GMPLS) Signaling Extensions for G.709 Optical 1029 Transport Networks Control", RFC 4328, Jan 2006. 1031 [RFC3209] D. Awduche et al, "RSVP-TE: Extensions to RSVP for LSP 1032 Tunnels", RFC3209, December 2001. 1034 [RFC3471] Berger, L., Editor, "Generalized Multi-Protocol Label 1035 Switching (GMPLS) Signaling Functional Description", RFC 1036 3471, January 2003. 1038 [RFC3473] L. Berger, Ed., "Generalized Multi-Protocol Label Switching 1039 (GMPLS) Signaling Resource ReserVation Protocol-Traffic 1040 Engineering (RSVP-TE) Extensions", RFC 3473, January 2003. 1042 [RFC3945] Mannie, E., "Generalized Multi-Protocol Label Switching 1043 (GMPLS) Architecture", RFC 3945, October 2004. 1045 [RFC6344] G. Bernstein et al, "Operating Virtual Concatenation (VCAT) 1046 and the Link Capacity Adjustment Scheme (LCAS) with 1047 Generalized Multi-Protocol Label Switching (GMPLS)", 1048 RFC6344, August 2011. 1050 [RFC4206] K. Kompella, Y. Rekhter, Ed., " Label Switched Paths (LSP) 1051 Hierarchy with Generalized Multi-Protocol Label Switching 1052 (GMPLS) Traffic Engineering (TE)", RFC 4206, October 2005. 1054 [RFC6107] K. Shiomoto, A. Farrel, "Procedures for Dynamically 1055 Signaled Hierarchical Label Switched Paths", RFC6107, 1056 February 2011. 1058 [RFC6001] Dimitri Papadimitriou et al, "Generalized Multi-Protocol 1059 Label Switching (GMPLS) Protocol Extensions for Multi-Layer 1060 and Multi-Region Networks (MLN/MRN)", RFC6001, February 21, 1061 2010. 1063 [RFC5420] A. Farrel, Ed., "Encoding of Attributes for MPLS LSP 1064 Establishment Using Resource Reservation Protocol Traffic 1065 Engineering (RSVP-TE)", RFC5420, February 2009. 1067 [OTN-FWK] Fatai Zhang et al, "Framework for GMPLS and PCE Control of 1068 G.709 Optical Transport Networks", draft-ietf-ccamp-gmpls- 1069 g709-framework, Work in Progress, June 2012. 1071 [OTN-INFO] S. Belotti et al, "Information model for G.709 Optical 1072 Transport Networks (OTN)", draft-ietf-ccamp-otn-g709-info- 1073 model, Work in Progress, January 2012. 1075 [OTN-OSPF] D. Ceccarelli et al, "Traffic Engineering Extensions to 1076 OSPF for Generalized MPLS (GMPLS) Control of Evolving G.709 1077 OTN Networks", draft-ietf-ccamp-gmpls-ospf-g709v3, Work in 1078 Progress, April 2012. 1080 [OTN-LMP] Fatai Zhang, Ed., "Link Management Protocol (LMP) 1081 extensions for G.709 Optical Transport Networks", draft- 1082 zhang-ccamp-gmpls-g.709-lmp-discovery, Work in Progress, 1083 July 2012. 1085 [G709-V3] ITU-T, "Interfaces for the Optical Transport Network (OTN) 1086 ", G.709/Y.1331, December 2009. 1088 [G709-V3-A2] ITU-T, "Interfaces for the Optical Transport Network 1089 (OTN) Amendment 2", G.709/y.1331 Amendment 2, April 2011. 1091 12.2. Informative References 1093 [G709-V1] ITU-T, "Interface for the Optical Transport Network (OTN)," 1094 G.709 Recommendation (and Amendment 1), February 2001 1095 (November 2001). 1097 [G709-V2] ITU-T, "Interface for the Optical Transport Network (OTN)," 1098 G.709 Recommendation, March 2003. 1100 [G798-V2] ITU-T, "Characteristics of optical transport network 1101 hierarchy equipment functional blocks", G.798, December 1102 2006. 1104 [G798-V3] ITU-T, "Characteristics of optical transport network 1105 hierarchy equipment functional blocks", G.798v3, consented 1106 June 2010. 1108 [G.7044] ITU-T, "Hitless adjustment of ODUflex", G.7044 (and 1109 Amendment 1), February 2012. 1111 [RFC4506] M. Eisler, Ed., "XDR: External Data Representation 1112 Standard", RFC 4506, May 2006. 1114 [IEEE] "IEEE Standard for Binary Floating-Point Arithmetic", 1115 ANSI/IEEE Standard 754-1985, Institute of Electrical and 1116 Electronics Engineers, August 1985. 1118 [GMPLS-SEC] Fang, L., Ed., "Security Framework for MPLS and GMPLS 1119 Networks", Work in Progress, October 2009. 1121 13. Contributors 1123 Jonathan Sadler, Tellabs 1124 Email: jonathan.sadler@tellabs.com 1126 Kam LAM, Alcatel-Lucent 1127 Email: kam.lam@alcatel-lucent.com 1128 Xiaobing Zi, Huawei Technologies 1129 Email: zixiaobing@huawei.com 1131 Francesco Fondelli, Ericsson 1132 Email: francesco.fondelli@ericsson.com 1134 Lyndon Ong, Ciena 1135 Email: lyong@ciena.com 1137 Biao Lu, infinera 1138 Email: blu@infinera.com 1140 14. Authors' Addresses 1142 Fatai Zhang (editor) 1143 Huawei Technologies 1144 F3-5-B R&D Center, Huawei Base 1145 Bantian, Longgang District 1146 Shenzhen 518129 P.R.China 1147 Phone: +86-755-28972912 1148 Email: zhangfatai@huawei.com 1150 Guoying Zhang 1151 China Academy of Telecommunication Research of MII 1152 11 Yue Tan Nan Jie Beijing, P.R.China 1153 Phone: +86-10-68094272 1154 Email: zhangguoying@mail.ritt.com.cn 1156 Sergio Belotti 1157 Alcatel-Lucent 1158 Optics CTO 1159 Via Trento 30 20059 Vimercate (Milano) Italy 1160 +39 039 6863033 1161 Email: sergio.belotti@alcatel-lucent.it 1163 Daniele Ceccarelli 1164 Ericsson 1165 Via A. Negrone 1/A 1166 Genova - Sestri Ponente 1167 Italy 1168 Email: daniele.ceccarelli@ericsson.com 1170 Khuzema Pithewan 1171 Infinera Corporation 1172 169, Java Drive 1173 Sunnyvale, CA-94089, USA 1174 Email: kpithewan@infinera.com 1176 Yi Lin 1177 Huawei Technologies 1178 F3-5-B R&D Center, Huawei Base 1179 Bantian, Longgang District 1180 Shenzhen 518129 P.R.China 1181 Phone: +86-755-28972914 1182 Email: yi.lin@huawei.com 1184 Yunbin Xu 1185 China Academy of Telecommunication Research of MII 1186 11 Yue Tan Nan Jie Beijing, P.R.China 1187 Phone: +86-10-68094134 1188 Email: xuyunbin@mail.ritt.com.cn 1190 Pietro Grandi 1191 Alcatel-Lucent 1192 Optics CTO 1193 Via Trento 30 20059 Vimercate (Milano) Italy 1194 +39 039 6864930 1195 Email: pietro_vittorio.grandi@alcatel-lucent.it 1197 Diego Caviglia 1198 Ericsson 1199 Via A. Negrone 1/A 1200 Genova - Sestri Ponente 1201 Italy 1202 Email: diego.caviglia@ericsson.com 1204 Rajan Rao 1205 Infinera Corporation 1206 169, Java Drive 1207 Sunnyvale, CA-94089 1208 USA 1209 Email: rrao@infinera.com 1211 John E Drake 1212 Juniper 1213 Email: jdrake@juniper.net 1215 Igor Bryskin 1216 Adva Optical 1217 EMail: IBryskin@advaoptical.com 1219 15. Acknowledgment 1221 The authors would like to thank Lou Berger and Deborah Brungard for 1222 their useful comments to the document. 1224 Intellectual Property 1226 The IETF Trust takes no position regarding the validity or scope of 1227 any Intellectual Property Rights or other rights that might be 1228 claimed to pertain to the implementation or use of the technology 1229 described in any IETF Document or the extent to which any license 1230 under such rights might or might not be available; nor does it 1231 represent that it has made any independent effort to identify any 1232 such rights. 1234 Copies of Intellectual Property disclosures made to the IETF 1235 Secretariat and any assurances of licenses to be made available, or 1236 the result of an attempt made to obtain a general license or 1237 permission for the use of such proprietary rights by implementers or 1238 users of this specification can be obtained from the IETF on-line IPR 1239 repository at http://www.ietf.org/ipr 1241 The IETF invites any interested party to bring to its attention any 1242 copyrights, patents or patent applications, or other proprietary 1243 rights that may cover technology that may be required to implement 1244 any standard or specification contained in an IETF Document. Please 1245 address the information to the IETF at ietf-ipr@ietf.org. 1247 The definitive version of an IETF Document is that published by, or 1248 under the auspices of, the IETF. Versions of IETF Documents that are 1249 published by third parties, including those that are translated into 1250 other languages, should not be considered to be definitive versions 1251 of IETF Documents. The definitive version of these Legal Provisions 1252 is that published by, or under the auspices of, the IETF. Versions of 1253 these Legal Provisions that are published by third parties, including 1254 those that are translated into other languages, should not be 1255 considered to be definitive versions of these Legal Provisions. 1257 For the avoidance of doubt, each Contributor to the IETF Standards 1258 Process licenses each Contribution that he or she makes as part of 1259 the IETF Standards Process to the IETF Trust pursuant to the 1260 provisions of RFC 5378. No language to the contrary, or terms, 1261 conditions or rights that differ from or are inconsistent with the 1262 rights and licenses granted under RFC 5378, shall have any effect and 1263 shall be null and void, whether published or posted by such 1264 Contributor, or included with or in such Contribution. 1266 Disclaimer of Validity 1268 All IETF Documents and the information contained therein are provided 1269 on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE 1270 REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE 1271 IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL 1272 WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY 1273 WARRANTY THAT THE USE OF THE INFORMATION THEREIN WILL NOT INFRINGE 1274 ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS 1275 FOR A PARTICULAR PURPOSE. 1277 Copyright Notice 1278 Copyright (c) 2010 IETF Trust and the persons identified as the 1279 document authors. All rights reserved. 1281 This document is subject to BCP 78 and the IETF Trust's Legal 1282 Provisions Relating to IETF Documents 1283 (http://trustee.ietf.org/license-info) in effect on the date of 1284 publication of this document. Please review these documents 1285 carefully, as they describe your rights and restrictions with respect 1286 to this document. Code Components extracted from this document must 1287 include Simplified BSD License text as described in Section 4.e of 1288 the Trust Legal Provisions and are provided without warranty as 1289 described in the Simplified BSD License.