idnits 2.17.1 draft-zheng-ccamp-gmpls-g709v5-signal-ext-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. (A line matching the expected section header was found, but with an unexpected indentation: ' 1. Introduction' ) ** The document seems to lack a Security Considerations section. (A line matching the expected section header was found, but with an unexpected indentation: ' 4. Security Considerations' ) ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) (A line matching the expected section header was found, but with an unexpected indentation: ' 5. IANA considerations' ) ** There are 29 instances of too long lines in the document, the longest one being 13 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (March 6, 2017) is 2607 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 section? 'ITU-T G.709v5' on line 515 looks like a reference -- Missing reference section? 'B100G-fwk' on line 87 looks like a reference -- Missing reference section? 'RFC4328' on line 456 looks like a reference -- Missing reference section? 'RFC7139' on line 527 looks like a reference -- Missing reference section? 'RFC7963' on line 535 looks like a reference -- Missing reference section? 'RFC2119' on line 512 looks like a reference -- Missing reference section? 'G.Sup43' on line 155 looks like a reference -- Missing reference section? 'G.709-2016' on line 191 looks like a reference -- Missing reference section? 'G709-2016' on line 272 looks like a reference -- Missing reference section? 'RFC5226' on line 434 looks like a reference -- Missing reference section? 'RFC7062' on line 518 looks like a reference -- Missing reference section? 'RFC7138' on line 522 looks like a reference -- Missing reference section? 'RFC7892' on line 531 looks like a reference Summary: 4 errors (**), 0 flaws (~~), 1 warning (==), 14 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 CCAMP Working Group Haomian Zheng 2 Internet-Draft Italo Busi 3 Intended status: Standards Track Huawei 4 Zafar Ali 5 Cisco 6 Daniele Ceccarelli 7 Ericsson 8 Daniel King 9 Lancaster University 10 Expires: September 6, 2017 March 6, 2017 12 GMPLS Signaling Extension for Optical Transport Networks with Beyond 13 100G in G.709 Edition 5 15 draft-zheng-ccamp-gmpls-g709v5-signal-ext-00.txt 17 Abstract 19 The International Telecommunication Union Telecommunication 20 Standardization Sector (ITU-T) has extended its Recommendations 21 G.709 to edition 5 to support beyond 100G (B100G) features. 22 Corresponding signaling extensions have been described in this 23 document. 25 Status of this Memo 27 This Internet-Draft is submitted to IETF in full conformance with 28 the provisions of BCP 78 and BCP 79. 30 Internet-Drafts are working documents of the Internet Engineering 31 Task Force (IETF), its areas, and its working groups. Note that 32 other groups may also distribute working documents as Internet- 33 Drafts. 35 Internet-Drafts are draft documents valid for a maximum of six 36 months and may be updated, replaced, or obsoleted by other documents 37 at any time. It is inappropriate to use Internet-Drafts as 38 reference material or to cite them other than as "work in progress." 40 The list of current Internet-Drafts can be accessed at 41 http://www.ietf.org/ietf/1id-abstracts.txt. 43 The list of Internet-Draft Shadow Directories can be accessed at 44 http://www.ietf.org/shadow.html. 46 This Internet-Draft will expire on September 6, 2017. 48 Copyright Notice 50 Copyright (c) 2017 IETF Trust and the persons identified as the 51 document authors. All rights reserved. 53 This document is subject to BCP 78 and the IETF Trust's Legal 54 Provisions Relating to IETF Documents 55 (http://trustee.ietf.org/license-info) in effect on the date of 56 publication of this document. Please review these documents 57 carefully, as they describe your rights and restrictions with 58 respect to this document. Code Components extracted from this 59 document must include Simplified BSD License text as described in 60 Section 4.e of the Trust Legal Provisions and are provided without 61 warranty as described in the Simplified BSD License. 63 Table of Contents 65 1. Introduction ................................................. 2 66 2. Terminology .................................................. 3 67 2.1. Conventions Used in this Document ....................... 3 68 3. RSVP-TE Extensions to Support Optical Transport Network B100G. 3 69 3.1. New Signal types in B100G OTN ........................... 3 70 3.2. New Tributary Slot Definition in B100G OTN .............. 4 71 3.3. Generalized Label for B100G ............................. 5 72 3.4. TPN allocation and MSI .................................. 6 73 3.5. Supporting of OTUCn sub rates (OTUCn-M) ................. 8 74 3.6. Examples: ............................................... 8 75 4. Security Considerations ...................................... 9 76 5. IANA considerations .......................................... 9 77 6. Contributors' Addresses ..................................... 12 78 7. References .................................................. 12 79 7.1. Normative References ................................... 12 80 7.2. Informative References ................................. 13 81 Authors' Addresses ............................................. 13 83 1. Introduction 85 [ITU-T G.709v5] defines the interfaces to Optical Transport Network. 86 B100G features was included in the latest version v5. Corresponding 87 OTN control plane techniques have been considered in [B100G-fwk]. 89 [RFC4328] describes the control technology details that are specific 90 to the 2001 revision of the G.709 specification. The previous 91 signaling extension drafts include the [RFC7139] too support ODU4, 92 ODU2e and ODUflex, and [RFC7963] to support additional ODU1e, ODU3e1 93 and ODU3e2. The signaling extension for B100G OTN network is 94 described in this document. 96 2. Terminology 98 2.1. Conventions Used in this Document 100 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 101 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 102 document are to be interpreted as described in RFC-2119 [RFC2119]. 104 3. RSVP-TE Extensions to Support Optical Transport Network B100G 106 3.1. New Signal types in B100G OTN 108 New features has been defined for B100G OTN. The corresponding new 109 signal types can be summarized as follow: 111 - Optical Data Unit - Cn (ODUCn) 113 n can vary from 1 to 255; 115 - Optical Transport Unit - Cn (OTUCn) 117 n can vary from 1 to 255; 119 [RFC7139] defines the format of Traffic Parameters in OTN-TDM 120 SENDER_TSPEC and OTN-TDM FLOWSPEC objects. These traffic parameters 121 have a Signal Type field. This document defines a new Signal Type 122 for ODUCn, where n can vary from 1 to 255. 124 Value Type 125 ----- ---- 126 TBD(31) ODUCn (i.e., n * 100 Gbps) 128 0 1 2 3 129 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 130 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 131 | Signal Type | n | Reserved | 132 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 133 | NVC | Multiplier (MT) | 134 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 135 | Bit_Rate | 136 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 138 Signal Type: 8 bits 140 As defined in Section 3.2.1 of [RFC4328], with the following 141 additional values: 143 Value Type 144 ----- ---- 145 4 ODU4 (i.e., 100 Gbps) 146 9 OCh at 100 Gbps 147 10 ODU0 (i.e., 1.25 Gbps) 148 11 ODU2e (i.e., 10 Gbps for FC1200 and GE LAN) 149 12-19 Reserved (for future use) 150 20 ODUflex(CBR) (i.e., 1.25*N Gbps) 151 21 ODUflex(GFP-F), resizable (i.e., 1.25*N Gbps) 152 22 ODUflex(GFP-F), non-resizable (i.e., 1.25*N Gbps) 153 23 ODU1e (10Gbps Ethernet [G.Sup43]) 154 26 ODU3e1 (40Gbps Ethernet [G.Sup43]) 155 27 ODU3e2 (40Gbps Ethernet [G.Sup43]) 156 31 ODUCn (B100G OTN [G.709-2016]) 157 32-255 Reserved (for future use) 159 n : 8 bits 161 When the signal type is ODUCn, the n is used to specify the ODUCn 162 granularity, the value of n varies from 1 to 255. When the signal 163 type is not ODUCn, the n MUST be set to 0 and ignored. 165 3.2. New Tributary Slot Definition in B100G OTN 167 A new tributary slot granularity (i.e., 5Gbps) is defined in [G.709- 168 2016]. This granularity is specially used to support ODUCn in B100G 169 OTN networks. Legacy OTN interfaces will continue to use 170 2.5Gbps/1.25Gbps tributary slot granularity. 172 The OPUCn consists of n OPUC. Each OPUC is divided into 20 tributary 173 slots (TS) and these tributary slots are 16-byte interleaved within 174 the OPUC payload area. A tributary slot includes a part of the OPUC 175 OH area and a part of the OPUC payload area. The bytes of the ODUk 176 frame are mapped into the ODTUCn payload area and the ODTUCn bytes 177 are mapped into the OPUCn tributary slot or slots. The bytes of the 178 ODTUCn justification overhead are mapped into the OPUCn OH area. 180 There is only one type of tributary slot: Tributary slot with a 181 bandwidth of approximately 5 Gbit/s; an OPUCn is divided into 20n 182 tributary slots, numbered 1.1 to n.20. 184 To satisfy the new TS granularity, this document also updates the G- 185 PID values defined in [RFC4328]. 187 Value G-PID Type 189 ----- ---------- 191 TBA(71) OTN B100G control defined in [G.709-2016] 193 The update of payload types updated in [G709-2016] and their mapping 194 to existing and new G-PID types are as follows: 196 G.709 198 Payload 200 Type G-PID Type/Comment LSP Encoding 202 ==== ===== ===================== =================== 204 0x22 TBA(71) G.709 ODU-5G G.709 ODUCn(n=1..255) 206 3.3. Generalized Label for B100G 208 [RFC7139] defined the GENERALIZED_LABEL object format that MUST be 209 used with the OTN-TDM Switching Type, the format is re-drawn as 210 follow: 212 0 1 2 3 214 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 216 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 218 | TPN | Reserved | Length | 219 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 221 ~ Bit Map ...... ~ 223 ~ ...... | Padding Bits ~ 225 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 227 This object was used to indicate how LO ODUj is multiplexed into HO 228 ODUk. It can also be used to indicate how ODUk can be multiplexed 229 into ODUCn. 231 In the extreme case for B100G, ODU0 need to be multiplexed to 232 ODUC255. The maximum for TPN number is 20,400, which is beyond the 233 2^12. In this document this object need to be updated as follow: 235 0 1 2 3 237 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 239 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 241 | TPN | Length | 243 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 245 ~ Bit Map ...... ~ 247 ~ ...... | Padding Bits ~ 249 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 251 After the extension, the maximum values for TPN and Length are 252 updated to 65,536, which can cover the extreme case in B100G 253 multiplexing. 255 3.4. TPN allocation and MSI 257 TPN section has been used to indicates the tributary port number for 258 the assigned tributary slot(s). 260 - In the case of an ODUk mapped into ODUCn, only the lower 15 261 bits of the TPN field are significant; the other bits of TPN field 262 MUST be set to 0; 264 Per [G709-2016], the TPN is used to allow for correct demultiplexing 265 in the data plane. When an LO ODUj is multiplexed into an HO ODUk 266 occupying one or more TSs, a new TPN value is configured at the two 267 ends of the HO ODUk link and is put into the related MSI byte(s) in 268 the OPUk overhead at the (traffic) ingress end of the link, so that 269 the other end of the link can learn which TS(s) is/are used by the 270 LO ODUj in the data plane. 272 According to [G709-2016], the TPN field MUST be set according to the 273 following tables: 275 +-------+-------+----+----------------------------------------------+ 276 | ODUk | ODUC1 |TPN | TPN Assignment Rules | 277 +-------+-------+----+----------------------------------------------+ 278 | ODU0 | ODUC1 |1-20|Flexible, != any other existing LO ODUs'TPNs | 279 +-------+-------+----+----------------------------------------------+ 280 | ODU1 | ODUC1 |1-20|Flexible, != any other existing LO ODUs' TPNs | 281 |-------+-------+----+----------------------------------------------+ 282 | ODU2 | ODUC1 |1-10|Flexible, != any other existing LO ODUs' TPNs | 283 +-------+-------+----+----------------------------------------------+ 284 | ODU3 | ODUC1 |1-2 |Flexible, != any other existing LO ODUs' TPNs | 285 |-------+-------+----+----------------------------------------------+ 286 | ODU4 | ODUC1 |1-1 |Flexible, != any other existing LO ODUs' TPNs | 287 +-------+-------+----+----------------------------------------------+ 289 Table X: TPN Assignment Rules from ODUk to ODUC1 (5 Gbps TS Granularity) 291 Editor's Note: The I-D stills need to consider how to multiplex ODU2e, 292 ODU1e, and ODUFlex to ODUCn. This is a topic for further discussion. 294 For ODUCn where n>1, the only changes are the upper bound of TPN. As 295 ODUCn is composed by n ODUC, the upper bound of TPN is multiplied by 296 n. 298 +-------+-------+-----+----------------------------------------------+ 299 | ODUk | ODUCn | TPN | TPN Assignment Rules | 300 +-------+-------+-----+----------------------------------------------+ 301 | ODU0 | ODUCn |1-20n|Flexible, != any other existing LO ODUs'TPNs | 302 +-------+-------+----+----------------------------------------------+ 303 | ODU1 | ODUCn |1-20n|Flexible, != any other existing LO ODUs' TPNs | 304 |-------+-------+-----+----------------------------------------------+ 305 | ODU2 | ODUCn |1-10n|Flexible, != any other existing LO ODUs' TPNs | 306 +-------+-------+-----+----------------------------------------------+ 307 | ODU3 | ODUCn |1-2n |Flexible, != any other existing LO ODUs' TPNs | 308 |-------+-------+-----+----------------------------------------------+ 309 | ODU4 | ODUCn | 1-n |Flexible, != any other existing LO ODUs' TPNs | 310 +-------+-------+-----+----------------------------------------------+ 312 Table X: TPN Assignment Rules from ODUk to ODUCn (5 Gbps TS Granularity) 314 3.5. Supporting of OTUCn sub rates (OTUCn-M) 316 The OTUCn-M frame is a type of OTUCn frame which contains n 317 instances of OTUC, ODUC and OPUC overhead and M 5 Gbit/s OPUCn 318 tributary slots. If a particular value of M is not indicated, the 319 frame contains 20*n tributary slots. 321 For OTUCn-M, there is totally 20*n+M tributary slots. Accordingly, M 322 need to be considered as in TPN numbers defined in section 3.4. 324 3.6. Examples: 326 Following examples are given to illustrate how to multiplexing ODUk 327 into ODUCn format. 329 (1) ODU2 to ODUC1 Multiplexing 331 In this example, the n value in ODUCn is set to 1, with a signal 332 type assigned as 31 which means ODUCn. 334 0 1 2 3 335 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 336 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 337 | Signal Type=31| n=1 | Reserved | 338 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 340 The label format, defined in section 3.3 of this document, is 341 illustrated as follow. 343 0 1 2 3 345 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 347 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 349 | TPN = 1 | Length = 20 | 350 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 352 |0 1 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 | Padding Bits (0) | 354 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 356 The label above indicate that ODU2 (10G) is using the 2nd and 5th 357 tributary slots of ODUC1. The tributary slot granularity in B100G 358 MUST be set to 5Gbps. 360 (2) ODU4 to ODUC1 Multiplexing 362 This example is special, as both ODU4 and ODUC1 are assumed to be 363 with a rate of 100Gbps. The signal type of ODUC1 is the same as 364 previous example. 366 0 1 2 3 368 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 370 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 372 | TPN = 1 | Length = 20 | 374 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 376 |1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 | Padding Bits (0) | 378 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 380 In this example, all the 20 tributary slots are occupied in the 381 multiplexing. 383 4. Security Considerations 385 TBD. 387 5. IANA considerations 389 IANA maintains the "Generalized Multi-Protocol Label Switching 390 (GMPLS) Signaling Parameters" registry (see 391 ). The 392 "Generalized PIDs (G-PID)" subregistry is included in this registry, 393 which is extended and updated by this document as detailed below. 395 Value Type Technology Reference 397 ===== ====================== ========== ========= 399 47 G.709 ODU-2.5G G.709 ODUk [RFC4328] 401 (IANA updated the Type field) [RFC7139] 403 56 SBCON/ESCON G.709 ODUk, [RFC4328] 405 (IANA updated the Type field) Lambda, Fiber [RFC7139] 407 59 Framed GFP G.709 ODUk [RFC7139] 409 60 STM-1 G.709 ODUk [RFC7139] 411 61 STM-4 G.709 ODUk [RFC7139] 413 62 InfiniBand G.709 ODUflex [RFC7139] 415 63 SDI (Serial Digital Interface) G.709 ODUk [RFC7139] 417 64 SDI/1.001 G.709 ODUk [RFC7139] 419 65 DVB_ASI G.709 ODUk [RFC7139] 421 66 G.709 ODU-1.25G G.709 ODUk [RFC7139] 423 67 G.709 ODU-any G.709 ODUk [RFC7139] 425 68 Null Test G.709 ODUk [RFC7139] 427 69 Random Test G.709 ODUk [RFC7139] 429 70 64B/66B GFP-F Ethernet G.709 ODUk [RFC7139] 431 TBD(71)G.709 ODU-5G G.709 ODUCn [This draft] 433 This document also request IANA to add the following signal types in 434 the subregistry via the Specification Required policy [RFC5226]: 436 Value Signal Type Reference 438 ----- ----------- --------- 440 0 Not significant [RFC4328] 442 1 ODU1 (i.e., 2.5 Gbps) [RFC4328] 444 2 ODU2 (i.e., 10 Gbps) [RFC4328] 446 3 ODU3 (i.e., 40 Gbps) [RFC4328] 448 4 ODU4 (i.e., 100 Gbps) [RFC7139] 450 5 Unassigned [RFC4328] 452 6 Och at 2.5 Gbps [RFC4328] 454 7 OCh at 10 Gbps [RFC4328] 456 8 OCh at 40 Gbps [RFC4328] 458 9 OCh at 100 Gbps [RFC7139] 460 10 ODU0 (i.e., 1.25 Gbps) [RFC7139] 462 11 ODU2e (i.e., 10 Gbps for FC1200 [RFC7139] 464 and GE LAN) 466 12-19 Unassigned 468 20 ODUflex(CBR) (i.e., 1.25*N Gbps) [RFC7139] 470 21 ODUflex(GFP-F), resizable [RFC7139] 472 (i.e., 1.25*N Gbps) 474 22 ODUflex(GFP-F), non-resizable [RFC7139] 476 (i.e., 1.25*N Gbps) 478 23 ODU1e (10Gbps Ethernet) [RFC7963] 480 26 ODU3e1 (40Gbps Ethernet) [RFC7963] 482 27 ODU3e2 (40Gbps Ethernet) [RFC7963] 483 31 ODUCn [This Draft] 485 23-255 Unassigned 487 These Signal Types are carried in the Traffic Parameters in OTN- 488 TDM SENDER_TSPEC and OTN-TDM FLOWSPEC objects. 490 6. Contributors' Addresses 492 Xian Zhang 493 Huawei Technologies 494 Email: zhang.xian@huawei.com 496 Antonello Bonfanti 497 Cisco 498 Email: abonfant@cisco.com 500 Sergio Belotti 501 Nokia 502 Email: sergio.belotti@nokia.com 504 Dieter Beller 505 Nokia 506 Email: Dieter.Beller@nokia.com 508 7. References 510 7.1. Normative References 512 [RFC2119] S. Bradner, "Key words for use in RFCs to indicate 513 requirements levels", RFC 2119, March 1997. 515 [ITU-T G.709v5] ITU-T, "Interface for the Optical Transport Network 516 (OTN)", G.709/Y.1331 Recommendation, June 2016. 518 [RFC7062] F. Zhang, D. Li, H. Li, S. Belotti, D. Ceccarelli, 519 'Framework for GMPLS and PCE Control of G.709 Optical 520 Transport Networks', RFC 7062, November 2013. 522 [RFC7138] D. Ceccarelli, F. Zhang, S. Belotti, R. Rao, J. Drake, 523 'Traffic Engineering Extensions to OSPF for GMPLS Control 524 of Evolving G.709 Optical Transport Networks', RFC7138, 525 March 2014. 527 [RFC7139] F. Zhang, G. Zhang, S. Belotti, D. Ceccarelli, K. Pithewan, 528 'GMPLS Signaling Extensions for Control of Evolving G.709 529 Optical Transport Networks', RFC7139, March 2014. 531 [RFC7892] Z. Ali, A. Bonfanti, M. Hartley, F. Zhang, 'IANA 532 Allocation Procedures for the GMPLS OTN Signal Type 533 Registry', RFC7892, May 2016. 535 [RFC7963] Z. Ali, A. Bonfanti, M. Hartley, F. Zhang, 'RSVP-TE 536 Extension for Additional Signal Types in G.709 Optical 537 Transport Networks (OTNs)', RFC7963, August 2016. 539 7.2. Informative References 541 Authors' Addresses 543 Haomian Zheng 544 Huawei Technologies 545 Email: zhenghaomian@huawei.com 547 Italo Busi 548 Huawei Technologies 549 Email: Italo.Busi@huawei.com 551 Zafar Ali 552 Cisco 553 Email: zali@cisco.com 555 Daniele Ceccarelli 556 Ericsson 557 Email: daniele.ceccarelli@ericsson.com 559 Daniel King 560 Lancaster University 561 Email: d.king@lancaster.ac.uk