idnits 2.17.1 draft-sharma-ccamp-otn-tunnel-model-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (March 11, 2017) is 2601 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'G.709' is defined on line 859, but no explicit reference was found in the text == Unused Reference: 'RFC6020' is defined on line 867, but no explicit reference was found in the text == Unused Reference: 'RFC7139' is defined on line 872, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'G.709' Summary: 0 errors (**), 0 flaws (~~), 5 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 CCAMP Working Group X. Zhang 3 Internet-Draft K. Xiang 4 Intended status: Standards Track Huawei Technologies 5 Expires: September 12, 2017 A. Sharma 6 R. Rao 7 Infinera 8 March 11, 2017 10 OTN Tunnel YANG Model 11 draft-sharma-ccamp-otn-tunnel-model-01 13 Abstract 15 This document describes the YANG data model for OTN Tunnels. 17 Requirements Language 19 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 20 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 21 document are to be interpreted as described in [RFC2119]. 23 Status of This Memo 25 This Internet-Draft is submitted in full conformance with the 26 provisions of BCP 78 and BCP 79. 28 Internet-Drafts are working documents of the Internet Engineering 29 Task Force (IETF). Note that other groups may also distribute 30 working documents as Internet-Drafts. The list of current Internet- 31 Drafts is at http://datatracker.ietf.org/drafts/current/. 33 Internet-Drafts are draft documents valid for a maximum of six months 34 and may be updated, replaced, or obsoleted by other documents at any 35 time. It is inappropriate to use Internet-Drafts as reference 36 material or to cite them other than as "work in progress." 38 This Internet-Draft will expire on September 12, 2017. 40 Copyright Notice 42 Copyright (c) 2017 IETF Trust and the persons identified as the 43 document authors. All rights reserved. 45 This document is subject to BCP 78 and the IETF Trust's Legal 46 Provisions Relating to IETF Documents 47 (http://trustee.ietf.org/license-info) in effect on the date of 48 publication of this document. Please review these documents 49 carefully, as they describe your rights and restrictions with respect 50 to this document. Code Components extracted from this document must 51 include Simplified BSD License text as described in Section 4.e of 52 the Trust Legal Provisions and are provided without warranty as 53 described in the Simplified BSD License. 55 Table of Contents 57 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 58 2. Terminology and Notations . . . . . . . . . . . . . . . . . . 2 59 3. Model Overview . . . . . . . . . . . . . . . . . . . . . . . 3 60 3.1. Mux Service in Multi-Domain OTN Network . . . . . . . . . 3 61 3.2. Bookended and Non-BookEnded OTN Tunnel . . . . . . . . . 4 62 3.3. Network and Client side tunnel services . . . . . . . . . 4 63 3.4. OTN Tunnel YANG Tree . . . . . . . . . . . . . . . . . . 4 64 3.5. OTN Tunnel YANG Code . . . . . . . . . . . . . . . . . . 5 65 3.6. Transport Types YANG Code . . . . . . . . . . . . . . . . 10 66 4. Security Considerations . . . . . . . . . . . . . . . . . . . 19 67 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19 68 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 19 69 7. Normative References . . . . . . . . . . . . . . . . . . . . 19 70 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 19 72 1. Introduction 74 OTN transport networks can carry various types of client services. 75 In many cases, the client signal is carried over an OTN tunnel across 76 connected domains in a multi-domain network. These OTN services can 77 either be transported or switched in the OTN network. If an OTN 78 tunnel is switched, then additional parameters need to be provided to 79 create a Mux OTN service. 81 This document provides YANG model for creating OTN tunnel. The model 82 augments the TE Tunnel model, which is an abstract model to create TE 83 Tunnels. 85 2. Terminology and Notations 87 A simplified graphical representation of the data model is used in 88 this document. The meaning of the symbols in the YANG data tree 89 presented later in this draft is defined in . They are provided below 90 for reference. 92 o Brackets "[" and "]" enclose list keys. 94 o Abbreviations before data node names: "rw" means configuration 95 (read-write) and "ro" state data (read-only). 97 o Symbols after data node names: "?" means an optional node, "!" 98 means a presence container, and "*" denotes a list and leaf-list. 100 o Parentheses enclose choice and case nodes, and case nodes are also 101 marked with a colon (":"). 103 o Ellipsis ("...") stands for contents of subtrees that are not 104 shown. 106 3. Model Overview 108 3.1. Mux Service in Multi-Domain OTN Network 110 OTN Mux Service 111 <---------------------------------> 113 XXXXXXXXXXX XXXXXXXXXXXXXXXXXXXXXXXXX XXXXXXXXX 114 XX XX XX XX XX XX 115 XX +---+ X XX +---+ +---+ X XX +---+ XX 116 X |NE1+--------+-----+NE2+-----------+NE3+--------+-X---+NE4| X 117 X +---+ XX ^ X +---+ +---+ XX ^ XX +---+ X 118 XX XX | XX XX | XX XX 119 XXXXXXXXXXX | XXXXXXXXXXXXXXXXXXXXXXXXX | XXXXXXXXX 120 Domain-1 | Domain-2 | Domain-3 121 + + 122 Same OTN Service attributes: Same OTN Service attributes: 123 1. Client Signal 1. Client Signal 124 2. Tributary Port Number 2. Tributary Port Number 125 3. Tributary Slot Granularity 3. Tributary Slot Granularity 126 4. Tributary Slots 4. Tributary Slots 128 Figure 1: OTN Mux Service in a multi-domain network topology 130 Figure 1 shows a multi-domain OTN network with three domains. In 131 this example, user wants to setup an end-to-end OTN service that 132 passes through Domain-2. In order to create an OTN mux service in 133 Domain-2, user will need to specify the exact details of the client 134 side LO-ODU on NE2 and NE3, so that these service endpoints can be 135 paired with the LO-ODU endpoints on NE1 and NE4, respectively. 137 Let's assume that ODU4 is the client side HO-ODU on NE2 and NE3, and 138 the client signal is ODU2. User will need to specify the OTN client 139 signal (ODU2 in this example), the Tributary Port Number (TPN), 140 Tributary Slot Granularities (TSG) and tributary slots to be used. 142 As shown in the figure above, these service parameters must be the 143 same between NE1 and NE2, and NE3 and NE4. 145 Once the OTN Mux service is setup in Domain-2, the incoming signal 146 from either NE1 and/or NE4 will be switched inside Domain-2, and 147 delivered to NE at the other end. 149 3.2. Bookended and Non-BookEnded OTN Tunnel 151 OTN tunnel model provides support for both bookended and non- 152 bookended OTN tunnels. 154 For bookended tunnels, the same client signal is present on source 155 and destination endpoints. For example, ODU2e bookended tunnel will 156 have the same ODU2e client signal at both source and destination 157 endpoints. 159 For non-bookended tunnels, different client signals are present on 160 source and destination endpoints. For example, the client signal can 161 be ODU2e on the source endpoint and the handoff at the destination 162 can be 10GbE-LAN client signal. 164 3.3. Network and Client side tunnel services 166 The OTN tunnel model provides support for both network to network and 167 client to client tunnels. For network to network tunnel, network 168 termination points on source and destination node represent source 169 and destination endpoints. For client to client tunnel, client 170 termination points on source and destination node represent source 171 and destination endpoints. 173 If a client to client tunnel needs to use one or more HO (or server) 174 network to network tunnels, ERO and routing constraints, defined in 175 the base TE model, can be used to route the client tunnel over one or 176 more server tunnels. 178 3.4. OTN Tunnel YANG Tree 179 module: ietf-otn-tunnel 180 augment /te:te/te:tunnels/te:tunnel/te:config: 181 +--rw payload-treatment? enumeration 182 +--rw src-client-signal? identityref 183 +--rw src-tpn? uint16 184 +--rw src-tsg? identityref 185 +--rw src-tributary-slot-count? uint16 186 +--rw src-tributary-slots 187 | +--rw values* uint8 188 +--rw dst-client-signal? identityref 189 +--rw dst-tpn? uint16 190 +--rw dst-tsg? identityref 191 +--rw dst-tributary-slot-count? uint16 192 +--rw dst-tributary-slots 193 +--rw values* uint8 194 augment /te:te/te:tunnels/te:tunnel/te:state: 195 +--ro payload-treatment? enumeration 196 +--ro src-client-signal? identityref 197 +--ro src-tpn? uint16 198 +--ro src-tsg? identityref 199 +--ro src-tributary-slot-count? uint16 200 +--ro src-tributary-slots 201 | +--ro values* uint8 202 +--ro dst-client-signal? identityref 203 +--ro dst-tpn? uint16 204 +--ro dst-tsg? identityref 205 +--ro dst-tributary-slot-count? uint16 206 +--ro dst-tributary-slots 207 +--ro values* uint8 209 3.5. OTN Tunnel YANG Code 211 file "ietf-otn-tunnel@2017-03-11.yang" 213 module ietf-otn-tunnel { 214 yang-version 1.1; 216 namespace "urn:ietf:params:xml:ns:yang:ietf-otn-tunnel"; 217 prefix "otn-tunnel"; 219 import ietf-te { prefix "te"; } 220 import ietf-transport-types { prefix "tran-types"; } 221 //import yang-ext { prefix ext; revision-date 2013-07-09; } 223 organization 224 "IETF CCAMP Working Group"; 226 contact 227 "WG Web: 228 WG List: 230 Editor: Anurag Sharma 231 233 Editor: Rajan Rao 234 236 Editor: Xian Zhang 237 239 Editor: Kun Xiang 240 "; 242 description 243 "This module defines a model for OTN Tunnel Services."; 245 revision "2017-03-11" { 246 description 247 "Revision 0.3"; 248 reference "TBD"; 249 } 251 grouping otn-tunnel-endpoint { 252 description "Parameters for OTN tunnel."; 254 leaf payload-treatment { 255 type enumeration { 256 enum switching; 257 enum transport; 258 } 259 default switching; 260 description 261 "Treatment of the incoming payload. Payload can 262 either be switched, or transported as is."; 263 } 265 leaf src-client-signal { 266 type identityref { 267 base tran-types:client-signal; 268 } 269 description 270 "Client signal at the source endpoint of 271 the tunnel."; 273 } 275 leaf src-tpn { 276 type uint16 { 277 range "0..4095"; 278 } 279 description 280 "Tributary Port Number. Applicable in case of mux 281 services."; 282 reference 283 "RFC7139: GMPLS Signaling Extensions for Control of 284 Evolving G.709 Optical Transport Networks."; 285 } 287 leaf src-tsg { 288 type identityref { 289 base tran-types:tributary-slot-granularity; 290 } 291 description 292 "Tributary slot granularity. Applicable in case of mux 293 services."; 294 reference 295 "G.709/Y.1331, February 2016: Interfaces for the 296 Optical Transport Network (OTN)"; 297 } 299 leaf src-tributary-slot-count { 300 type uint16; 301 description 302 "Number of tributary slots used at the source."; 303 } 305 container src-tributary-slots { 306 description 307 "A list of tributary slots used by the client 308 service. Applicable in case of mux services."; 309 leaf-list values { 310 type uint8; 311 description 312 "Tributary tributary slot value."; 313 reference 314 "G.709/Y.1331, February 2016: Interfaces for the 315 Optical Transport Network (OTN)"; 316 } 317 } 319 leaf dst-client-signal { 320 type identityref { 321 base tran-types:client-signal; 322 } 323 description 324 "Client signal at the destination endpoint of 325 the tunnel."; 326 } 328 leaf dst-tpn { 329 type uint16 { 330 range "0..4095"; 331 } 332 description 333 "Tributary Port Number. Applicable in case of mux 334 services."; 335 reference 336 "RFC7139: GMPLS Signaling Extensions for Control of 337 Evolving G.709 Optical Transport Networks."; 338 } 340 leaf dst-tsg { 341 type identityref { 342 base tran-types:tributary-slot-granularity; 343 } 344 description 345 "Tributary slot granularity. Applicable in case of mux 346 services."; 347 reference 348 "G.709/Y.1331, February 2016: Interfaces for the 349 Optical Transport Network (OTN)"; 350 } 352 leaf dst-tributary-slot-count { 353 type uint16; 354 description 355 "Number of tributary slots used at the destination."; 356 } 358 container dst-tributary-slots { 359 description 360 "A list of tributary slots used by the client 361 service. Applicable in case of mux services."; 362 leaf-list values { 363 type uint8; 364 description 365 "Tributary slot value."; 366 reference 367 "G.709/Y.1331, February 2016: Interfaces for the 368 Optical Transport Network (OTN)"; 370 } 371 } 372 } 374 /* 375 Note: Comment has been given to authors of TE Tunnel model to add 376 tunnel-types to the model in order to identify the technology 377 type of the service. 379 grouping otn-service-type { 380 description 381 "Identifies the OTN Service type."; 382 container otn-service { 383 presence "Indicates OTN Service."; 384 description 385 "Its presence identifies the OTN Service type."; 386 } 387 } // otn-service-type 389 augment "/te:te/te:tunnels/te:tunnel/te:tunnel-types" { 390 description 391 "Introduce OTN service type for tunnel."; 392 ext:augment-identifier otn-service-type-augment; 393 uses otn-service-type; 394 } 395 */ 397 /* 398 Note: Comment has been given to authors of TE Tunnel model to add 399 list of endpoints under config to support P2MP tunnel. 400 */ 401 augment "/te:te/te:tunnels/te:tunnel/te:config" { 402 description 403 "Augment with additional parameters required for OTN 404 service."; 405 //ext:augment-identifier otn-tunnel-endpoint-config-augment; 406 uses otn-tunnel-endpoint; 407 } 409 augment "/te:te/te:tunnels/te:tunnel/te:state" { 410 description 411 "Augment with additional parameters required for OTN 412 service."; 413 //ext:augment-identifier otn-tunnel-endpoint-state-augment; 414 uses otn-tunnel-endpoint; 415 } 417 /* 418 Note: Comment has been given to authors of TE Tunnel model to add 419 tunnel-lifecycle-event to the model. This notification is reported 420 for all lifecycle changes (create, delete, and update) to the 421 tunnel or lsp. 422 augment "/te:tunnel-lifecycle-event" { 423 description 424 "OTN service event"; 425 uses otn-service-type; 426 uses otn-tunnel-params; 428 list endpoint { 429 key 430 "endpoint-address tp-id"; 431 description 432 "List of Tunnel Endpoints."; 433 uses te:tunnel-endpoint; 434 uses otn-tunnel-params; 435 } 436 } 437 */ 438 } 440 442 3.6. Transport Types YANG Code 444 file "ietf-transport-types@2016-10-25.yang" 446 module ietf-transport-types { 447 namespace "urn:ietf:params:xml:ns:yang:ietf-transport-types"; 448 prefix "tran-types"; 450 organization 451 "IETF CCAMP Working Group"; 452 contact 453 "WG Web: 454 WG List: 456 Editor: Anurag Sharma 457 459 Editor: Rajan Rao 460 462 Editor: Xian Zhang 463 "; 465 description 466 "This module defines transport types."; 468 revision "2016-10-25" { 469 description 470 "Revision 0.2"; 471 reference "TBD"; 472 } 474 identity tributary-slot-granularity { 475 description 476 "Tributary slot granularity."; 477 reference 478 "G.709/Y.1331, February 2016: Interfaces for the 479 Optical Transport Network (OTN)"; 480 } 482 identity tsg-1.25G { 483 base tributary-slot-granularity; 484 description 485 "1.25G tributary slot granularity."; 486 } 488 identity tsg-2.5G { 489 base tributary-slot-granularity; 490 description 491 "2.5G tributary slot granularity."; 492 } 494 identity tributary-protocol-type { 495 description 496 "Base identity for protocol framing used by 497 tributary signals."; 498 } 500 identity prot-OTU1 { 501 base tributary-protocol-type; 502 description 503 "OTU1 protocol (2.66G)"; 504 } 506 /* 507 identity prot-OTU1e { 508 base tributary-protocol-type; 509 description 510 "OTU1e type (11.04G)"; 512 } 514 identity prot-OTU1f { 515 base tributary-protocol-type; 516 description 517 "OTU1f type (11.27G)"; 518 } 519 */ 520 identity prot-OTU2 { 521 base tributary-protocol-type; 522 description 523 "OTU2 type (10.70G)"; 524 } 526 identity prot-OTU2e { 527 base tributary-protocol-type; 528 description 529 "OTU2e type (11.09G)"; 530 } 532 /* 533 identity prot-OTU2f { 534 base tributary-protocol-type; 535 description 536 "OTU2f type (11.31G)"; 537 } 538 */ 540 identity prot-OTU3 { 541 base tributary-protocol-type; 542 description 543 "OTU3 type (43.01G)"; 544 } 546 /* 547 identity prot-OTU3e1 { 548 base tributary-protocol-type; 549 description 550 "OTU3e1 type (44.57G)"; 551 } 553 identity prot-OTU3e2 { 554 base tributary-protocol-type; 555 description 556 "OTU3e2 type (44.58G)"; 557 } 558 */ 559 identity prot-OTU4 { 560 base tributary-protocol-type; 561 description 562 "OTU4 type (111.80G)"; 563 } 565 identity prot-OTUCn { 566 base tributary-protocol-type; 567 description 568 "OTUCn type (beyond 100G)"; 569 } 571 identity prot-ODU0 { 572 base tributary-protocol-type; 573 description 574 "ODU0 protocol (1.24G)."; 575 } 577 identity prot-ODU1 { 578 base tributary-protocol-type; 579 description 580 "ODU1 protocol (2.49G)."; 581 } 583 /* 584 identity prot-ODU1e { 585 base tributary-protocol-type; 586 description 587 "ODU1e protocol (10.35G)."; 588 } 590 identity prot-ODU1f { 591 base tributary-protocol-type; 592 description 593 "ODU1f protocol (10.56G)."; 594 } 595 */ 597 identity prot-ODU2 { 598 base tributary-protocol-type; 599 description 600 "ODU2 protocol (10.03G)."; 601 } 603 identity prot-ODU2e { 604 base tributary-protocol-type; 605 description 606 "ODU2e protocol (10.39G)."; 608 } 610 /* 611 identity prot-ODU2f { 612 base tributary-protocol-type; 613 description 614 "ODU2f protocol (10.60G)."; 615 } 616 */ 618 identity prot-ODU3 { 619 base tributary-protocol-type; 620 description 621 "ODU3 protocol (40.31G)."; 622 } 624 /* 625 identity prot-ODU3e1 { 626 base tributary-protocol-type; 627 description 628 "ODU3e1 protocol (41.77G)."; 629 } 631 identity prot-ODU3e2 { 632 base tributary-protocol-type; 633 description 634 "ODU3e2 protocol (41.78G)."; 635 } 636 */ 638 identity prot-ODU4 { 639 base tributary-protocol-type; 640 description 641 "ODU4 protocol (104.79G)."; 642 } 644 identity prot-ODUFlex-cbr { 645 base tributary-protocol-type; 646 description 647 "ODU Flex CBR protocol for transporting constant bit 648 rate signal."; 649 } 651 identity prot-ODUFlex-gfp { 652 base tributary-protocol-type; 653 description 654 "ODU Flex GFP protocol for transporting stream of packets 655 using Generic Framing Procedure."; 657 } 659 identity prot-ODUCn { 660 base tributary-protocol-type; 661 description 662 "ODUCn protocol (beyond 100G)."; 663 } 665 identity prot-1GbE { 666 base tributary-protocol-type; 667 description 668 "1G Ethernet protocol"; 669 } 671 identity prot-10GbE-LAN { 672 base tributary-protocol-type; 673 description 674 "10G Ethernet LAN protocol"; 675 } 677 identity prot-40GbE { 678 base tributary-protocol-type; 679 description 680 "40G Ethernet protocol"; 681 } 683 identity prot-100GbE { 684 base tributary-protocol-type; 685 description 686 "100G Ethernet protocol"; 687 } 689 identity client-signal { 690 description 691 "Base identity from which specific client signals for the 692 tunnel are derived."; 693 } 695 identity client-signal-1GbE { 696 base client-signal; 697 description 698 "Client signal type of 1GbE"; 699 } 701 identity client-signal-10GbE-LAN { 702 base client-signal; 703 description 704 "Client signal type of 10GbE LAN"; 706 } 708 identity client-signal-10GbE-WAN { 709 base client-signal; 710 description 711 "Client signal type of 10GbE WAN"; 712 } 714 identity client-signal-40GbE { 715 base client-signal; 716 description 717 "Client signal type of 40GbE"; 718 } 720 identity client-signal-100GbE { 721 base client-signal; 722 description 723 "Client signal type of 100GbE"; 724 } 726 identity client-signal-OC3_STM1 { 727 base client-signal; 728 description 729 "Client signal type of OC3 & STM1"; 730 } 732 identity client-signal-OC12_STM4 { 733 base client-signal; 734 description 735 "Client signal type of OC12 & STM4"; 736 } 738 identity client-signal-OC48_STM16 { 739 base client-signal; 740 description 741 "Client signal type of OC48 & STM16"; 742 } 744 identity client-signal-OC192_STM64 { 745 base client-signal; 746 description 747 "Client signal type of OC192 & STM64"; 748 } 750 identity client-signal-OC768_STM256 { 751 base client-signal; 752 description 753 "Client signal type of OC768 & STM256"; 755 } 757 identity client-signal-ODU0 { 758 base client-signal; 759 description 760 "Client signal type of ODU0 (1.24G)"; 761 } 763 identity client-signal-ODU1 { 764 base client-signal; 765 description 766 "ODU1 protocol (2.49G)"; 767 } 769 identity client-signal-ODU2 { 770 base client-signal; 771 description 772 "Client signal type of ODU2 (10.03G)"; 773 } 775 identity client-signal-ODU2e { 776 base client-signal; 777 description 778 "Client signal type of ODU2e (10.39G)"; 779 } 781 identity client-signal-ODU3 { 782 base client-signal; 783 description 784 "Client signal type of ODU3 (40.31G)"; 785 } 787 /* 788 identity client-signal-ODU3e2 { 789 base client-signal; 790 description 791 "Client signal type of ODU3e2 (41.78G)"; 792 } 793 */ 795 identity client-signal-ODU4 { 796 base client-signal; 797 description 798 "Client signal type of ODU4 (104.79G)"; 799 } 801 identity client-signal-ODUFlex-cbr { 802 base client-signal; 803 description 804 "Client signal type of ODU Flex CBR"; 805 } 807 identity client-signal-ODUFlex-gfp { 808 base client-signal; 809 description 810 "Client signal type of ODU Flex GFP"; 811 } 813 identity client-signal-ODUCn { 814 base client-signal; 815 description 816 "Client signal type of ODUCn (beyond 100G)."; 817 } 819 identity client-signal-FC400 { 820 base client-signal; 821 description 822 "Client signal type of Fibre Channel FC400."; 823 } 825 identity client-signal-FC800 { 826 base client-signal; 827 description 828 "Client signal type of Fibre Channel FC800."; 829 } 831 identity client-signal-FICON-4G { 832 base client-signal; 833 description 834 "Client signal type of Fibre Connection 4G."; 835 } 837 identity client-signal-FICON-8G { 838 base client-signal; 839 description 840 "Client signal type of Fibre Connection 8G."; 841 } 842 } 843 845 4. Security Considerations 847 TBD. 849 5. IANA Considerations 851 TBD. 853 6. Acknowledgements 855 TBD. 857 7. Normative References 859 [G.709] "Interfaces for the Optical Transport Network(OTN)", 860 G.709/Y.1331 Recommendation , June 2016. 862 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 863 Requirement Levels", BCP 14, RFC 2119, 864 DOI 10.17487/RFC2119, March 1997, 865 . 867 [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for 868 the Network Configuration Protocol (NETCONF)", RFC 6020, 869 DOI 10.17487/RFC6020, October 2010, 870 . 872 [RFC7139] Zhang, F., Ed., Zhang, G., Belotti, S., Ceccarelli, D., 873 and K. Pithewan, "GMPLS Signaling Extensions for Control 874 of Evolving G.709 Optical Transport Networks", RFC 7139, 875 DOI 10.17487/RFC7139, March 2014, 876 . 878 Authors' Addresses 880 Xian Zhang 881 Huawei Technologies 882 F3-5-B R&D Center, Huawei Industrial Base, Bantian, Longgang District 883 Shenzhen, Guangdong 518129 884 P.R.China 886 Email: zhang.xian@huawei.com 887 Kun Xiang 888 Huawei Technologies 889 F3 R&D Center, Huawei Industrial Base, Bantian, Longgang District 890 Shenzhen, Guangdong 518129 891 P.R.China 893 Email: xiangkun@huawei.com 895 Anurag Sharma 896 Infinera 898 Email: ansharma@infinera.com 900 Rajan Rao 901 Infinera 902 169 Java Drive 903 Sunnyvale, CA 94089 904 USA 906 Email: rrao@infinera.com