idnits 2.17.1 draft-sharma-ccamp-otn-tunnel-model-02.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 (May 25, 2017) is 2525 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) == Outdated reference: A later version (-20) exists of draft-ietf-netmod-rfc6087bis-12 Summary: 0 errors (**), 0 flaws (~~), 3 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 CCAMP Working Group H. Zheng 3 Internet-Draft Z. Fan 4 Intended status: Standards Track Huawei Technologies 5 Expires: November 26, 2017 A. Sharma 6 Google 7 R. Rao 8 Infinera 9 S. Belotti 10 Nokia 11 V. Lopez 12 Telefonica 13 Y. Li 14 China Mobile 15 May 25, 2017 17 OTN Tunnel YANG Model 18 draft-sharma-ccamp-otn-tunnel-model-02 20 Abstract 22 This document describes the YANG data model for OTN Tunnels. 24 Requirements Language 26 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 27 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 28 document are to be interpreted as described in [RFC2119]. 30 Status of This Memo 32 This Internet-Draft is submitted in full conformance with the 33 provisions of BCP 78 and BCP 79. 35 Internet-Drafts are working documents of the Internet Engineering 36 Task Force (IETF). Note that other groups may also distribute 37 working documents as Internet-Drafts. The list of current Internet- 38 Drafts is at http://datatracker.ietf.org/drafts/current/. 40 Internet-Drafts are draft documents valid for a maximum of six months 41 and may be updated, replaced, or obsoleted by other documents at any 42 time. It is inappropriate to use Internet-Drafts as reference 43 material or to cite them other than as "work in progress." 45 This Internet-Draft will expire on November 26, 2017. 47 Copyright Notice 49 Copyright (c) 2017 IETF Trust and the persons identified as the 50 document authors. All rights reserved. 52 This document is subject to BCP 78 and the IETF Trust's Legal 53 Provisions Relating to IETF Documents 54 (http://trustee.ietf.org/license-info) in effect on the date of 55 publication of this document. Please review these documents 56 carefully, as they describe your rights and restrictions with respect 57 to this document. Code Components extracted from this document must 58 include Simplified BSD License text as described in Section 4.e of 59 the Trust Legal Provisions and are provided without warranty as 60 described in the Simplified BSD License. 62 Table of Contents 64 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 65 2. Terminology and Notations . . . . . . . . . . . . . . . . . . 3 66 3. Model Overview . . . . . . . . . . . . . . . . . . . . . . . 3 67 3.1. Mux Service in Multi-Domain OTN Network . . . . . . . . . 3 68 3.2. Bookended and Non-BookEnded OTN Tunnel . . . . . . . . . 4 69 3.3. Network and Client side tunnel services . . . . . . . . . 4 70 3.4. OTN Tunnel YANG Tree . . . . . . . . . . . . . . . . . . 5 71 3.5. OTN Tunnel YANG Code . . . . . . . . . . . . . . . . . . 5 72 3.6. Transport Types YANG Code . . . . . . . . . . . . . . . . 10 73 4. Security Considerations . . . . . . . . . . . . . . . . . . . 19 74 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19 75 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 19 76 7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 19 77 8. Normative References . . . . . . . . . . . . . . . . . . . . 20 78 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20 80 1. Introduction 82 OTN transport networks can carry various types of client services. 83 In many cases, the client signal is carried over an OTN tunnel across 84 connected domains in a multi-domain network. These OTN services can 85 either be transported or switched in the OTN network. If an OTN 86 tunnel is switched, then additional parameters need to be provided to 87 create a Mux OTN service. 89 This document provides YANG model for creating OTN tunnel. The model 90 augments the TE Tunnel model, which is an abstract model to create TE 91 Tunnels. 93 2. Terminology and Notations 95 A simplified graphical representation of the data model is used in 96 this document. The meaning of the symbols in the YANG data tree 97 presented later in this draft is defined in 98 [I-D.ietf-netmod-rfc6087bis]. They are provided below for reference. 100 o Brackets "[" and "]" enclose list keys. 102 o Abbreviations before data node names: "rw" means configuration 103 (read-write) and "ro" state data (read-only). 105 o Symbols after data node names: "?" means an optional node, "!" 106 means a presence container, and "*" denotes a list and leaf-list. 108 o Parentheses enclose choice and case nodes, and case nodes are also 109 marked with a colon (":"). 111 o Ellipsis ("...") stands for contents of subtrees that are not 112 shown. 114 3. Model Overview 116 3.1. Mux Service in Multi-Domain OTN Network 118 OTN Mux Service 119 <---------------------------------> 121 XXXXXXXXXXX XXXXXXXXXXXXXXXXXXXXXXXXX XXXXXXXXX 122 XX XX XX XX XX XX 123 XX +---+ X XX +---+ +---+ X XX +---+ XX 124 X |NE1+--------+-----+NE2+-----------+NE3+--------+-X---+NE4| X 125 X +---+ XX ^ X +---+ +---+ XX ^ XX +---+ X 126 XX XX | XX XX | XX XX 127 XXXXXXXXXXX | XXXXXXXXXXXXXXXXXXXXXXXXX | XXXXXXXXX 128 Domain-1 | Domain-2 | Domain-3 129 + + 130 Same OTN Service attributes: Same OTN Service attributes: 131 1. Client Signal 1. Client Signal 132 2. Tributary Port Number 2. Tributary Port Number 133 3. Tributary Slot Granularity 3. Tributary Slot Granularity 134 4. Tributary Slots 4. Tributary Slots 136 Figure 1: OTN Mux Service in a multi-domain network topology 138 Figure 1 shows a multi-domain OTN network with three domains. In 139 this example, user wants to setup an end-to-end OTN service that 140 passes through Domain-2. In order to create an OTN mux service in 141 Domain-2, user will need to specify the exact details of the client 142 side LO-ODU on NE2 and NE3, so that these service endpoints can be 143 paired with the LO-ODU endpoints on NE1 and NE4, respectively. 145 Let's assume that ODU4 is the client side HO-ODU on NE2 and NE3, and 146 the client signal is ODU2. User will need to specify the OTN client 147 signal (ODU2 in this example), the Tributary Port Number (TPN), 148 Tributary Slot Granularities (TSG) and tributary slots to be used. 149 As shown in the figure above, these service parameters must be the 150 same between NE1 and NE2, and NE3 and NE4. 152 Once the OTN Mux service is setup in Domain-2, the incoming signal 153 from either NE1 and/or NE4 will be switched inside Domain-2, and 154 delivered to NE at the other end. 156 3.2. Bookended and Non-BookEnded OTN Tunnel 158 OTN tunnel model provides support for both bookended and non- 159 bookended OTN tunnels. 161 For bookended tunnels, the same client signal is present on source 162 and destination endpoints. For example, ODU2e bookended tunnel will 163 have the same ODU2e client signal at both source and destination 164 endpoints. 166 For non-bookended tunnels, different client signals are present on 167 source and destination endpoints. For example, the client signal can 168 be ODU2e on the source endpoint and the handoff at the destination 169 can be 10GbE-LAN client signal. 171 3.3. Network and Client side tunnel services 173 The OTN tunnel model provides support for both network to network and 174 client to client tunnels. For network to network tunnel, network 175 termination points on source and destination node represent source 176 and destination endpoints. For client to client tunnel, client 177 termination points on source and destination node represent source 178 and destination endpoints. 180 If a client to client tunnel needs to use one or more HO (or server) 181 network to network tunnels, ERO and routing constraints, defined in 182 the base TE model, can be used to route the client tunnel over one or 183 more server tunnels. 185 3.4. OTN Tunnel YANG Tree 187 module: ietf-otn-tunnel 188 augment /te:te/te:tunnels/te:tunnel/te:config: 189 +--rw payload-treatment? enumeration 190 +--rw src-client-signal? identityref 191 +--rw src-tpn? uint16 192 +--rw src-tsg? identityref 193 +--rw src-tributary-slot-count? uint16 194 +--rw src-tributary-slots 195 | +--rw values* uint8 196 +--rw dst-client-signal? identityref 197 +--rw dst-tpn? uint16 198 +--rw dst-tsg? identityref 199 +--rw dst-tributary-slot-count? uint16 200 +--rw dst-tributary-slots 201 +--rw values* uint8 202 augment /te:te/te:tunnels/te:tunnel/te:state: 203 +--ro payload-treatment? enumeration 204 +--ro src-client-signal? identityref 205 +--ro src-tpn? uint16 206 +--ro src-tsg? identityref 207 +--ro src-tributary-slot-count? uint16 208 +--ro src-tributary-slots 209 | +--ro values* uint8 210 +--ro dst-client-signal? identityref 211 +--ro dst-tpn? uint16 212 +--ro dst-tsg? identityref 213 +--ro dst-tributary-slot-count? uint16 214 +--ro dst-tributary-slots 215 +--ro values* uint8 217 3.5. OTN Tunnel YANG Code 219 file "ietf-otn-tunnel@2017-05-25.yang" 221 module ietf-otn-tunnel { 222 yang-version 1.1; 224 namespace "urn:ietf:params:xml:ns:yang:ietf-otn-tunnel"; 225 prefix "otn-tunnel"; 227 import ietf-te { prefix "te"; } 228 import ietf-transport-types { prefix "tran-types"; } 229 //import yang-ext { prefix ext; revision-date 2013-07-09; } 230 organization 231 "IETF CCAMP Working Group"; 233 contact 234 "WG Web: 235 WG List: 237 Editor: Haomian Zheng 238 240 Editor: Zheyu Fan 241 243 Editor: Anurag Sharma 244 246 Editor: Rajan Rao 247 249 Editor: Sergio Belotti 250 252 Editor: Victor Lopez 253 255 Editor: Yunbo Li 256 "; 258 description 259 "This module defines a model for OTN Tunnel Services."; 261 revision "2017-05-25" { 262 description 263 "Revision 0.3"; 264 reference 265 "draft-sharma-ccamp-otn-tunnel-model-02.txt"; 266 } 268 grouping otn-tunnel-endpoint { 269 description "Parameters for OTN tunnel."; 271 leaf payload-treatment { 272 type enumeration { 273 enum switching; 274 enum transport; 275 } 276 default switching; 277 description 278 "Treatment of the incoming payload. Payload can 279 either be switched, or transported as is."; 280 } 282 leaf src-client-signal { 283 type identityref { 284 base tran-types:client-signal; 285 } 286 description 287 "Client signal at the source endpoint of 288 the tunnel."; 289 } 291 leaf src-tpn { 292 type uint16 { 293 range "0..4095"; 294 } 295 description 296 "Tributary Port Number. Applicable in case of mux 297 services."; 298 reference 299 "RFC7139: GMPLS Signaling Extensions for Control of 300 Evolving G.709 Optical Transport Networks."; 301 } 303 leaf src-tsg { 304 type identityref { 305 base tran-types:tributary-slot-granularity; 306 } 307 description 308 "Tributary slot granularity. Applicable in case of 309 mux services."; 310 reference 311 "G.709/Y.1331, February 2016: Interfaces for the 312 Optical Transport Network (OTN)"; 313 } 315 leaf src-tributary-slot-count { 316 type uint16; 317 description 318 "Number of tributary slots used at the source."; 319 } 321 container src-tributary-slots { 322 description 323 "A list of tributary slots used by the client 324 service. Applicable in case of mux services."; 325 leaf-list values { 326 type uint8; 327 description 328 "Tributary tributary slot value."; 329 reference 330 "G.709/Y.1331, February 2016: Interfaces for the 331 Optical Transport Network (OTN)"; 332 } 333 } 335 leaf dst-client-signal { 336 type identityref { 337 base tran-types:client-signal; 338 } 339 description 340 "Client signal at the destination endpoint of 341 the tunnel."; 342 } 344 leaf dst-tpn { 345 type uint16 { 346 range "0..4095"; 347 } 348 description 349 "Tributary Port Number. Applicable in case of mux 350 services."; 351 reference 352 "RFC7139: GMPLS Signaling Extensions for Control of 353 Evolving G.709 Optical Transport Networks."; 354 } 356 leaf dst-tsg { 357 type identityref { 358 base tran-types:tributary-slot-granularity; 359 } 360 description 361 "Tributary slot granularity. Applicable in case of 362 mux services."; 363 reference 364 "G.709/Y.1331, February 2016: Interfaces for the 365 Optical Transport Network (OTN)"; 366 } 368 leaf dst-tributary-slot-count { 369 type uint16; 370 description 371 "Number of tributary slots used at the destination."; 372 } 373 container dst-tributary-slots { 374 description 375 "A list of tributary slots used by the client 376 service. Applicable in case of mux services."; 377 leaf-list values { 378 type uint8; 379 description 380 "Tributary slot value."; 381 reference 382 "G.709/Y.1331, February 2016: Interfaces for the 383 Optical Transport Network (OTN)"; 384 } 385 } 386 } 388 /* 389 Note: Comment has been given to authors of TE Tunnel model to add 390 tunnel-types to the model in order to identify the technology 391 type of the service. 393 grouping otn-service-type { 394 description 395 "Identifies the OTN Service type."; 396 container otn-service { 397 presence "Indicates OTN Service."; 398 description 399 "Its presence identifies the OTN Service type."; 400 } 401 } // otn-service-type 403 augment "/te:te/te:tunnels/te:tunnel/te:tunnel-types" { 404 description 405 "Introduce OTN service type for tunnel."; 406 ext:augment-identifier otn-service-type-augment; 407 uses otn-service-type; 408 } 409 */ 411 /* 412 Note: Comment has been given to authors of TE Tunnel model to add 413 list of endpoints under config to support P2MP tunnel. 414 */ 415 augment "/te:te/te:tunnels/te:tunnel/te:config" { 416 description 417 "Augment with additional parameters required for OTN 418 service."; 419 //ext:augment-identifier otn-tunnel-endpoint-config-augment; 420 uses otn-tunnel-endpoint; 422 } 424 augment "/te:te/te:tunnels/te:tunnel/te:state" { 425 description 426 "Augment with additional parameters required for OTN 427 service."; 428 //ext:augment-identifier otn-tunnel-endpoint-state-augment; 429 uses otn-tunnel-endpoint; 430 } 432 /* 433 Note: Comment has been given to authors of TE Tunnel model to 434 add tunnel-lifecycle-event to the model. This notification is 435 reported for all lifecycle changes (create, delete, and update) 436 to the tunnel or lsp. 437 augment "/te:tunnel-lifecycle-event" { 438 description 439 "OTN service event"; 440 uses otn-service-type; 441 uses otn-tunnel-params; 443 list endpoint { 444 key 445 "endpoint-address tp-id"; 446 description 447 "List of Tunnel Endpoints."; 448 uses te:tunnel-endpoint; 449 uses otn-tunnel-params; 450 } 451 } 452 */ 453 } 454 456 3.6. Transport Types YANG Code 458 file "ietf-transport-types@2017-05-25.yang" 460 module ietf-transport-types { 461 namespace "urn:ietf:params:xml:ns:yang:ietf-transport-types"; 462 prefix "tran-types"; 464 organization 465 "IETF CCAMP Working Group"; 466 contact 467 "WG Web: 468 WG List: 470 Editor: Haomian Zheng 471 473 Editor: Zheyu Fan 474 476 Editor: Anurag Sharma 477 479 Editor: Rajan Rao 480 482 Editor: Sergio Belotti 483 485 Editor: Victor Lopez 486 488 Editor: Yunbo Li 489 "; 491 description 492 "This module defines transport types."; 494 revision "2017-05-25" { 495 description 496 "Revision 0.3"; 497 reference 498 "draft-sharma-ccamp-otn-tunnel-model-02.txt"; 499 } 501 identity tributary-slot-granularity { 502 description 503 "Tributary slot granularity."; 504 reference 505 "G.709/Y.1331, February 2016: Interfaces for the 506 Optical Transport Network (OTN)"; 507 } 509 identity tsg-1.25G { 510 base tributary-slot-granularity; 511 description 512 "1.25G tributary slot granularity."; 513 } 515 identity tsg-2.5G { 516 base tributary-slot-granularity; 517 description 518 "2.5G tributary slot granularity."; 519 } 521 identity tributary-protocol-type { 522 description 523 "Base identity for protocol framing used by 524 tributary signals."; 525 } 527 identity prot-OTU1 { 528 base tributary-protocol-type; 529 description 530 "OTU1 protocol (2.66G)"; 531 } 533 /* 534 identity prot-OTU1e { 535 base tributary-protocol-type; 536 description 537 "OTU1e type (11.04G)"; 538 } 540 identity prot-OTU1f { 541 base tributary-protocol-type; 542 description 543 "OTU1f type (11.27G)"; 544 } 545 */ 546 identity prot-OTU2 { 547 base tributary-protocol-type; 548 description 549 "OTU2 type (10.70G)"; 550 } 552 identity prot-OTU2e { 553 base tributary-protocol-type; 554 description 555 "OTU2e type (11.09G)"; 556 } 558 /* 559 identity prot-OTU2f { 560 base tributary-protocol-type; 561 description 562 "OTU2f type (11.31G)"; 563 } 564 */ 566 identity prot-OTU3 { 567 base tributary-protocol-type; 568 description 569 "OTU3 type (43.01G)"; 570 } 572 /* 573 identity prot-OTU3e1 { 574 base tributary-protocol-type; 575 description 576 "OTU3e1 type (44.57G)"; 577 } 579 identity prot-OTU3e2 { 580 base tributary-protocol-type; 581 description 582 "OTU3e2 type (44.58G)"; 583 } 584 */ 586 identity prot-OTU4 { 587 base tributary-protocol-type; 588 description 589 "OTU4 type (111.80G)"; 590 } 592 identity prot-OTUCn { 593 base tributary-protocol-type; 594 description 595 "OTUCn type (beyond 100G)"; 596 } 598 identity prot-ODU0 { 599 base tributary-protocol-type; 600 description 601 "ODU0 protocol (1.24G)."; 602 } 604 identity prot-ODU1 { 605 base tributary-protocol-type; 606 description 607 "ODU1 protocol (2.49G)."; 608 } 610 /* 611 identity prot-ODU1e { 612 base tributary-protocol-type; 613 description 614 "ODU1e protocol (10.35G)."; 615 } 617 identity prot-ODU1f { 618 base tributary-protocol-type; 619 description 620 "ODU1f protocol (10.56G)."; 621 } 622 */ 624 identity prot-ODU2 { 625 base tributary-protocol-type; 626 description 627 "ODU2 protocol (10.03G)."; 628 } 630 identity prot-ODU2e { 631 base tributary-protocol-type; 632 description 633 "ODU2e protocol (10.39G)."; 634 } 636 /* 637 identity prot-ODU2f { 638 base tributary-protocol-type; 639 description 640 "ODU2f protocol (10.60G)."; 641 } 642 */ 644 identity prot-ODU3 { 645 base tributary-protocol-type; 646 description 647 "ODU3 protocol (40.31G)."; 648 } 650 /* 651 identity prot-ODU3e1 { 652 base tributary-protocol-type; 653 description 654 "ODU3e1 protocol (41.77G)."; 655 } 657 identity prot-ODU3e2 { 658 base tributary-protocol-type; 659 description 660 "ODU3e2 protocol (41.78G)."; 661 } 662 */ 664 identity prot-ODU4 { 665 base tributary-protocol-type; 666 description 667 "ODU4 protocol (104.79G)."; 668 } 670 identity prot-ODUFlex-cbr { 671 base tributary-protocol-type; 672 description 673 "ODU Flex CBR protocol for transporting constant bit 674 rate signal."; 675 } 677 identity prot-ODUFlex-gfp { 678 base tributary-protocol-type; 679 description 680 "ODU Flex GFP protocol for transporting stream of packets 681 using Generic Framing Procedure."; 682 } 684 identity prot-ODUCn { 685 base tributary-protocol-type; 686 description 687 "ODUCn protocol (beyond 100G)."; 688 } 690 identity prot-1GbE { 691 base tributary-protocol-type; 692 description 693 "1G Ethernet protocol"; 694 } 696 identity prot-10GbE-LAN { 697 base tributary-protocol-type; 698 description 699 "10G Ethernet LAN protocol"; 700 } 702 identity prot-40GbE { 703 base tributary-protocol-type; 704 description 705 "40G Ethernet protocol"; 706 } 707 identity prot-100GbE { 708 base tributary-protocol-type; 709 description 710 "100G Ethernet protocol"; 711 } 713 identity client-signal { 714 description 715 "Base identity from which specific client signals for the 716 tunnel are derived."; 717 } 719 identity client-signal-1GbE { 720 base client-signal; 721 description 722 "Client signal type of 1GbE"; 723 } 725 identity client-signal-10GbE-LAN { 726 base client-signal; 727 description 728 "Client signal type of 10GbE LAN"; 729 } 731 identity client-signal-10GbE-WAN { 732 base client-signal; 733 description 734 "Client signal type of 10GbE WAN"; 735 } 737 identity client-signal-40GbE { 738 base client-signal; 739 description 740 "Client signal type of 40GbE"; 741 } 743 identity client-signal-100GbE { 744 base client-signal; 745 description 746 "Client signal type of 100GbE"; 747 } 749 identity client-signal-OC3_STM1 { 750 base client-signal; 751 description 752 "Client signal type of OC3 & STM1"; 753 } 755 identity client-signal-OC12_STM4 { 756 base client-signal; 757 description 758 "Client signal type of OC12 & STM4"; 759 } 761 identity client-signal-OC48_STM16 { 762 base client-signal; 763 description 764 "Client signal type of OC48 & STM16"; 765 } 767 identity client-signal-OC192_STM64 { 768 base client-signal; 769 description 770 "Client signal type of OC192 & STM64"; 771 } 773 identity client-signal-OC768_STM256 { 774 base client-signal; 775 description 776 "Client signal type of OC768 & STM256"; 777 } 779 identity client-signal-ODU0 { 780 base client-signal; 781 description 782 "Client signal type of ODU0 (1.24G)"; 783 } 785 identity client-signal-ODU1 { 786 base client-signal; 787 description 788 "ODU1 protocol (2.49G)"; 789 } 791 identity client-signal-ODU2 { 792 base client-signal; 793 description 794 "Client signal type of ODU2 (10.03G)"; 795 } 797 identity client-signal-ODU2e { 798 base client-signal; 799 description 800 "Client signal type of ODU2e (10.39G)"; 801 } 802 identity client-signal-ODU3 { 803 base client-signal; 804 description 805 "Client signal type of ODU3 (40.31G)"; 806 } 808 /* 809 identity client-signal-ODU3e2 { 810 base client-signal; 811 description 812 "Client signal type of ODU3e2 (41.78G)"; 813 } 814 */ 816 identity client-signal-ODU4 { 817 base client-signal; 818 description 819 "Client signal type of ODU4 (104.79G)"; 820 } 822 identity client-signal-ODUFlex-cbr { 823 base client-signal; 824 description 825 "Client signal type of ODU Flex CBR"; 826 } 828 identity client-signal-ODUFlex-gfp { 829 base client-signal; 830 description 831 "Client signal type of ODU Flex GFP"; 832 } 834 identity client-signal-ODUCn { 835 base client-signal; 836 description 837 "Client signal type of ODUCn (beyond 100G)."; 838 } 840 identity client-signal-FC400 { 841 base client-signal; 842 description 843 "Client signal type of Fibre Channel FC400."; 844 } 846 identity client-signal-FC800 { 847 base client-signal; 848 description 849 "Client signal type of Fibre Channel FC800."; 851 } 853 identity client-signal-FICON-4G { 854 base client-signal; 855 description 856 "Client signal type of Fibre Connection 4G."; 857 } 859 identity client-signal-FICON-8G { 860 base client-signal; 861 description 862 "Client signal type of Fibre Connection 8G."; 863 } 864 } 865 867 4. Security Considerations 869 TBD. 871 5. IANA Considerations 873 TBD. 875 6. Acknowledgements 877 TBD. 879 7. Contributors 881 Dieter Beller 882 Nokia 883 Email: dieter.beller@nokia.com 885 Yanlei Zheng 886 China Unicom 887 Email: zhengyl@dimpt.com 889 Xian Zhang 890 Huawei Technologies 891 Email: zhang.xian@huawei.com 893 Lei Wang 894 China Mobile 895 Email: wangleiyj@chinamobile.com 897 Oscar Gonzalez de Dios 898 Telefonica 899 Email: oscar.gonzalezdedios@telefonica.com 901 8. Normative References 903 [I-D.ietf-netmod-rfc6087bis] 904 Bierman, A., "Guidelines for Authors and Reviewers of YANG 905 Data Model Documents", draft-ietf-netmod-rfc6087bis-12 906 (work in progress), March 2017. 908 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 909 Requirement Levels", BCP 14, RFC 2119, 910 DOI 10.17487/RFC2119, March 1997, 911 . 913 Authors' Addresses 915 Haomian Zheng 916 Huawei Technologies 917 F3 R&D Center, Huawei Industrial Base, Bantian, Longgang District 918 Shenzhen, Guangdong 518129 919 P.R.China 921 Email: zhenghaomian@huawei.com 923 Zheyu Fan 924 Huawei Technologies 925 F3 R&D Center, Huawei Industrial Base, Bantian, Longgang District 926 Shenzhen, Guangdong 518129 927 P.R.China 929 Email: fanzheyu2@huawei.com 931 Anurag Sharma 932 Google 933 1600 Amphitheatre Parkway 934 Mountain View, CA 94043 935 USA 937 Email: ansha@google.com 938 Rajan Rao 939 Infinera 940 169 Java Drive 941 Sunnyvale, CA 94089 942 USA 944 Email: rrao@infinera.com 946 Sergio Belotti 947 Nokia 949 Email: sergio.belotti@nokia.com 951 Victor Lopez 952 Telefonica 954 Email: victor.lopezalvarez@telefonica.com 956 Yunbo Li 957 China Mobile 959 Email: liyunbo@chinamobile.com