idnits 2.17.1 draft-chen-nvo3-vxlan-yang-06.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 10 instances of too long lines in the document, the longest one being 24 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 144 has weird spacing: '...vlan-id vla...' == Line 155 has weird spacing: '...ce-name if:...' == Line 164 has weird spacing: '...xlan-id vxl...' == Line 173 has weird spacing: '...xlan-id vxl...' == Line 177 has weird spacing: '...y-group uin...' == (4 more instances...) == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (January 3, 2018) is 2303 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: 'RFC6020' is defined on line 811, but no explicit reference was found in the text == Unused Reference: 'RFC6991' is defined on line 821, but no explicit reference was found in the text == Unused Reference: 'RFC7223' is defined on line 825, but no explicit reference was found in the text ** Obsolete normative reference: RFC 7223 (Obsoleted by RFC 8343) ** Downref: Normative reference to an Informational RFC: RFC 7348 Summary: 3 errors (**), 0 flaws (~~), 11 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 NVO3 WG Fangwei. Hu 3 Internet-Draft Ran. Chen 4 Intended status: Standards Track ZTE Corporation 5 Expires: July 7, 2018 Mallik. Mahalingam 6 Springpath 7 Qiang. Zu 8 Ericsson 9 S. Davari 10 yahoo 11 X. Liu 12 Jabil 13 January 3, 2018 15 YANG Data Model for VxLAN Protocol 16 draft-chen-nvo3-vxlan-yang-06.txt 18 Abstract 20 This document defines a YANG data model for VxLAN protocol. 22 Status of This Memo 24 This Internet-Draft is submitted in full conformance with the 25 provisions of BCP 78 and BCP 79. 27 Internet-Drafts are working documents of the Internet Engineering 28 Task Force (IETF). Note that other groups may also distribute 29 working documents as Internet-Drafts. The list of current Internet- 30 Drafts is at https://datatracker.ietf.org/drafts/current/. 32 Internet-Drafts are draft documents valid for a maximum of six months 33 and may be updated, replaced, or obsoleted by other documents at any 34 time. It is inappropriate to use Internet-Drafts as reference 35 material or to cite them other than as "work in progress." 37 This Internet-Draft will expire on July 7, 2018. 39 Copyright Notice 41 Copyright (c) 2018 IETF Trust and the persons identified as the 42 document authors. All rights reserved. 44 This document is subject to BCP 78 and the IETF Trust's Legal 45 Provisions Relating to IETF Documents 46 (https://trustee.ietf.org/license-info) in effect on the date of 47 publication of this document. Please review these documents 48 carefully, as they describe your rights and restrictions with respect 49 to this document. Code Components extracted from this document must 50 include Simplified BSD License text as described in Section 4.e of 51 the Trust Legal Provisions and are provided without warranty as 52 described in the Simplified BSD License. 54 Table of Contents 56 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 57 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 2 58 3. Requirements Language . . . . . . . . . . . . . . . . . . . . 2 59 4. YANG Data Model for VxLAN Configuration . . . . . . . . . . . 2 60 4.1. VxLAN Multicast IP Address . . . . . . . . . . . . . . . 2 61 4.2. VxLAN Access Type . . . . . . . . . . . . . . . . . . . . 3 62 4.3. Inner VLAN Tag Handling Mode . . . . . . . . . . . . . . 3 63 5. Design Tree of VxLAN YANG Data Model . . . . . . . . . . . . 3 64 6. VxLAN YANG Model . . . . . . . . . . . . . . . . . . . . . . 5 65 7. Security Considerations . . . . . . . . . . . . . . . . . . . 17 66 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 17 67 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17 68 10. Normative References . . . . . . . . . . . . . . . . . . . . 17 69 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 18 71 1. Introduction 73 YANG[RFC6020]is a data definition language that was introduced to 74 define the contents of a conceptual data store that allows networked 75 devices to be managed using NETCONF [RFC6241]. This document defines 76 a YANG data model for the configuration of VxLAN protocol [RFC7348]. 78 2. Terminology 80 3. Requirements Language 82 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 83 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 84 "OPTIONAL" in this document are to be interpreted as described in BCP 85 14 [RFC2119] [RFC8174] when, and only when, they appear in all 86 capitals, as shown here. 88 4. YANG Data Model for VxLAN Configuration 90 4.1. VxLAN Multicast IP Address 92 The vxlan-multicast-ip is used to configure the IP multicast group, 93 which the VxLAN VNI of the VTEP is mapping to. Both the IPv4 and 94 IPv6 address family are supported in this document. 96 4.2. VxLAN Access Type 98 There are several access types supported for VxLAN: 100 o vlan-1:1: the vxlan access type is VLAN, and each VxLAN is only 101 mapping to one VLAN. 103 o vlan- n:1: the vxlan access type is VLAN, and each VxLAN is mapped 104 to several VLANs. 106 o L3-interface: the VxLAN access type is layer 3 interface. 108 o mac: the VxLAN access type is MAC address. 110 o vlan-l2-interface: the VxLAN access type is VLAN plus Layer 2 111 interface. 113 4.3. Inner VLAN Tag Handling Mode 115 There are two handling modes for the inner VLAN tag: discard-inner- 116 vlan mode and no-discard-inner-vlan mode. If the VTEP interface 117 works in the discard-inner-vlan mode, the VxLAN is only mapped to one 118 VLAN. The inner VLAN tag will be stripped when encapsulating the 119 VxLAN frame. On the decapsulation side, if VTEP receives the VxLAN 120 frame with inner VLAN tag, it will discard the frame in this work 121 mode. If the VTEP receives the VxLAN frame without VLAN tag, it will 122 fill in the VLAN tag based on the VxLAN and VLAN mapping entry. 124 If the VTEP interface works in the no-discard-inner-vlan mode, the 125 VxLAN could be mapped to several VLANs. The inner VLAN tag will not 126 stripped when encapsulating the VxLAN frame in the VxLAN 127 encapsulation side. On the decapsulation side, if VTEP receives the 128 VxLAN frame, it will strip the VxLAN header, and keep the VLAN frame. 130 5. Design Tree of VxLAN YANG Data Model 132 module: ietf-vxlan 133 +--rw vxlan 134 | +--rw global-enable? empty 135 | +--rw vxlan-instance* [vxlan-id] 136 | +--rw vxlan-id vxlan-id 137 | +--rw description? string 138 | +--rw unknow-unicast-drop? enumeration 139 | +--rw filter-vrrp? enumeration 140 | +--rw (vxlan-access-types)? {vxlan-access-types}? 141 | | +--:(access-type-vlan) 142 | | | +--rw access-type-vlan? access-type-vlan 143 | | | +--rw access-vlan-list* [vlan-id] 144 | | | +--rw vlan-id vlan 145 | | +--:(access-type-mac) 146 | | | +--rw access-type-mac? empty 147 | | | +--rw mac yang:mac-address 148 | | +--:(access-type-l2interface) 149 | | | +--rw access-type-l2interface? empty 150 | | | +--rw vlan-id vlan 151 | | | +--rw interface-name if:interface-ref 152 | | +--:(access-type-l3interface) 153 | | +--rw access-type-l3interface? empty 154 | | +--rw map-l3interface* [interface-name] 155 | | +--rw interface-name if:interface-ref 156 | +--rw vtep-instances* [vtep-id] 157 | | +--rw vtep-id uint32 158 | | +--rw vtep-name? string 159 | | +--rw source-interface? if:interface-ref 160 | | +--rw multicast-ip inet:ip-address 161 | | +--rw mtu? uint32 {mtu}? 162 | | +--rw inner-vlan-handling-mode? inner-vlan-handling-mode 163 | | +--rw bind-vxlan-id* [vxlan-id] 164 | | +--rw vxlan-id vxlan-id 165 | +--rw static-vxlan-tunnel* [vxlan-tunnel-id] 166 | | +--rw vxlan-tunnel-id uint32 167 | | +--rw vxlan-tunnel-name? string 168 | | +--rw address-family* [af] 169 | | +--rw af address-family-type 170 | | +--rw tunnel-source-ip? address-family-type 171 | | +--rw tunnel-destination-ip? address-family-type 172 | | +--rw bind-vxlan-id* [vxlan-id] 173 | | +--rw vxlan-id vxlan-id 174 | +--rw redundancy-group-binds 175 | +--rw redundancy-group-bind* [vxlan-id redundancy-group] 176 | +--rw vxlan-id uint32 177 | +--rw redundancy-group uint32 178 +--ro vxlan-state 179 +--ro vxlan 180 +--ro vxlan-tunnels 181 +--ro vxlan-tunnel* [local-ip remote-ip] 182 +--ro local-ip address-family-type 183 +--ro remote-ip address-family-type 184 +--ro static-tunnel-id? uint32 185 +--ro evpn-tunnel-id? uint32 186 +--ro statistics 187 +--ro tunnel-statistics 188 | +--ro in-bytes? string 189 | +--ro out-bytes? string 190 | +--ro in-packets? string 191 | +--ro out-packets? string 192 +--ro tunnel-vni-statistics 193 +--ro tunnel-vni-statistic* [vxlan-id] 194 +--ro vxlan-id uint32 195 +--ro in-bytes? string 196 +--ro out-bytes? string 197 +--ro in-packets? string 198 +--ro out-packets? string 200 augment /evpn:evpn/evpn:evpn-instances/evpn:evpn-instance/evpn:bgp-parameters/evpn:common: 201 +--rw bgp-parameters 202 +--rw common 203 +--rw rd-rt* [route-distinguisher] 204 +--rw route-distinguisher string 205 +--rw vpn-target* [rt-value] 206 +--rw rt-value string 207 +--rw rt-type bgp-rt-type 209 6. VxLAN YANG Model 211 file "ietf-vxlan@2018-01-03.yang" 212 module ietf-vxlan { 213 namespace "urn:ietf:params:xml:ns:yang:ietf-vxlan"; 214 prefix "vxlan"; 216 import ietf-evpn { 217 prefix "evpn"; 218 } 220 import ietf-interfaces { 221 prefix "if"; 222 } 224 import ietf-inet-types { 225 prefix "inet"; 226 } 228 import ietf-yang-types { 229 prefix yang; 230 } 232 organization 233 "IETF NVO3(Network Virtualization Overlays) Working Group"; 235 contact 236 " 237 WG List: 239 WG Chair: Matthew Bocci 240 242 WG Chair: Benson Schliesser 243 245 Editor: Fangwei Hu 246 248 Editor: Ran Chen 249 251 Editor: Mallik Mahalingam 252 254 Editor: Zu Qiang 255 256 "; 258 description 259 "The YANG module defines a generic configuration 260 model for VxLAN protocol"; 262 revision 2018-01-03 { 263 description "Changes the yang data model according to the NMDA style."; 264 reference 265 "draft-chen-nvo3-vxlan-yang-06"; 266 } 268 revision 2017-06-29 { 269 description "no changes."; 270 reference 271 "draft-chen-nvo3-vxlan-yang-05"; 272 } 274 revision 2016-12-08 { 275 description "updated the vxlan yang model based on the comments from IETF 97th meeting," 276 +"augmenting EVPN data model, adding access type configuration and MTU configuration."; 277 reference 278 "draft-chen-nvo3-vxlan-yang-04"; 279 } 281 revision 2016-06-02 { 282 description 283 "03 revision. Update the YANG data model based on thec comments of IETF 95th meeting."; 284 reference 285 "draft-chen-nvo3-vxlan-yang-03"; 286 } 288 revision 2015-12-01 { 289 description 290 "02 revision."; 291 reference 292 "draft-chen-nvo3-vxlan-yang-02"; 293 } 295 revision 2015-10-12 { 296 description 297 "01 revision."; 298 reference 299 "draft-chen-nvo3-vxlan-yang-01"; 300 } 302 revision 2015-05-05 { 303 description "Initial revision"; 304 reference 305 "draft-chen-nvo3-vxlan-yang-00"; 306 } 308 /* Feature */ 310 feature vxlan-access-types { 311 description 312 "Support configuration vxlan access types."; 313 } 315 feature mtu { 316 description 317 "Support configuration vxlan MTU value."; 318 } 320 feature evpn-bgp-params { 321 description "Support EVPN BGP parameter."; 322 } 324 /* Typedefs */ 326 typedef vlan { 327 type uint16 { 328 range 1..4094; 329 } 330 description 331 "Typedef for VLAN"; 332 } 333 typedef vxlan-id { 334 type uint32; 335 description 336 "Typedef for VxLAN ID."; 337 } 338 typedef access-type-vlan { 339 type enumeration { 340 enum access-type-vlan1to1 { 341 description 342 "Access type is VLAN 1:1."; 343 } 344 enum access-type-vlan1ton { 345 description 346 "Access type is VLAN 1:n."; 347 } 349 } 350 default access-type-vlan1to1 ; 351 description 352 "VxLAN access type is VLAN."; 353 } 355 typedef access-type-mac { 356 type empty ; 357 description 358 "VxLAN access type is MAC."; 359 } 361 typedef inner-vlan-handling-mode { 362 type enumeration { 363 enum discard-inner-vlan { 364 description 365 "Discard inner-VLAN."; 366 } 367 enum no-discard-inner-vlan { 368 description 369 "No discard inner-VLAN."; 370 } 371 } 372 default discard-inner-vlan ; 373 description 374 "Typedef for inner-vlan-handling-mode"; 375 } 377 typedef address-family-type { 378 type enumeration { 379 enum ipv4 { 380 description 381 "IPv4"; 382 } 383 enum ipv6 { 384 description 385 "IPv6"; 386 } 387 } 388 description 389 "Typedef for address family type."; 390 } 392 /* Configuration Data */ 394 container vxlan{ 395 leaf global-enable { 396 type empty ; 397 description 'VXLAN global enble.'; 398 } 400 list vxlan-instance { 401 key vxlan-id ; 402 leaf vxlan-id { 403 type vxlan-id; 404 description "VxLAN ID."; 405 } 407 leaf description { 408 type string { 409 length 0..64 { 410 description 'VXLAN instance description information.'; 411 } 412 } 413 description 'The description information of VXLAN instance.'; 414 } 416 leaf unknow-unicast-drop { 417 type enumeration { 418 enum enable { 419 value 1 ; 420 description 'Unknown unicast drop enable.'; 421 } 422 enum disable { 423 value 2 ; 424 description 'Unknown unicast drop disable.'; 425 } 426 } 427 default enable ; 428 description 'Unknow unicast drop configuration of VXLAN instance.'; 429 } 431 leaf filter-vrrp { 432 type enumeration { 433 enum enable { 434 value 1 ; 435 description 'VRRP packets filter.'; 436 } 437 enum disable { 438 value 2 ; 439 description 'VRRP packets not filter.'; 440 } 441 } 442 default enable ; 443 description 'VRRP packets filter configuration of VXLAN instance.'; 444 } 446 choice vxlan-access-types { 447 if-feature vxlan-access-types; 448 case access-type-vlan { 450 leaf access-type-vlan { 451 type access-type-vlan; 453 description 454 "Access type is VLAN."; 455 } 457 list access-vlan-list { 458 key vlan-id ; 459 leaf vlan-id { 460 type vlan; 461 description 462 "VLAN ID."; 463 } 464 description 465 "VLAN ID list." ; 466 } 467 description 468 "VxLAN access type choice is VLAN."; 469 } 471 case access-type-mac { 472 leaf access-type-mac { 473 type empty ; 474 description 475 "Access type is MAC."; 477 } 479 leaf mac { 480 type yang:mac-address ; 481 mandatory true ; 482 description 483 "MAC Address."; 484 } 485 description 486 "VxLAN access type choice is MAC Address."; 487 } 489 case access-type-l2interface { 490 leaf access-type-l2interface { 491 type empty ; 492 description 493 "VXLAN map layer two interface."; 494 } 496 leaf vlan-id { 497 type vlan; 498 mandatory true ; 499 description 500 "VLAN ID."; 501 } 503 leaf interface-name { 504 type if:interface-ref; 505 mandatory true ; 506 description 507 "Layer two interface name."; 508 } 509 description 510 "VxLAN access type choice is layer two interface."; 511 } 513 case access-type-l3interface { 514 leaf access-type-l3interface { 515 type empty ; 516 description 517 "Access type of VxLAN is layer three interface."; 518 } 520 list map-l3interface { 521 key interface-name ; 522 leaf interface-name { 523 type if:interface-ref; 524 description 525 "Layer three interface name."; 526 } 527 description 528 "Layer three interface list."; 529 } 530 description 531 "VxLAN access type choice is layer three interface."; 532 } 533 description 534 "VxLAN access type choice."; 535 } 537 list vtep-instances { 538 key vtep-id ; 539 leaf vtep-id { 540 type uint32; 541 description 542 "VTEP ID."; 543 } 545 leaf vtep-name{ 546 type string; 547 description 548 "VTEP instance name."; 549 } 551 leaf source-interface { 552 type if:interface-ref; 553 description 554 "Source interface name."; 555 } 557 leaf multicast-ip { 558 type inet:ip-address; 559 mandatory true ; 560 description 561 "VxLAN multicast IP address."; 562 } 564 leaf mtu { 565 if-feature mtu; 566 type uint32; 567 description "vxlan mtu"; 568 } 570 leaf inner-vlan-handling-mode { 571 type inner-vlan-handling-mode; 572 description 573 "The inner vlan tag handling mode."; 574 } 576 list bind-vxlan-id { 577 key vxlan-id; 578 leaf vxlan-id { 579 type vxlan-id; 580 description 581 "VxLAN ID."; 582 } 583 description 584 "VxLAN ID list for the VTEP."; 585 } 586 description 587 "VTEP instance."; 588 } 590 list static-vxlan-tunnel{ 591 key vxlan-tunnel-id; 592 leaf vxlan-tunnel-id { 593 type uint32; 594 description 595 "Static VxLAN tunnel ID."; 596 } 598 leaf vxlan-tunnel-name { 599 type string; 600 description 601 "Name of the static VxLAN tunnel."; 602 } 604 list address-family { 605 key "af"; 606 leaf af { 607 type address-family-type; 608 description 609 "Address family type value."; 610 } 612 leaf tunnel-source-ip { 613 type address-family-type; 614 description 615 "Source IP address for the static VxLAN tunnel"; 616 } 618 leaf tunnel-destination-ip { 619 type address-family-type; 620 description 621 "Destination IP address for the static VxLAN tunnel"; 622 } 624 list bind-vxlan-id { 625 key vxlan-id; 626 leaf vxlan-id { 627 type vxlan-id; 628 description 629 "VxLAN ID."; 630 } 631 description 632 "VxLAN ID list for the VTEP."; 633 } 635 description 636 "Per-af params."; 637 } 638 description 639 "Configure the static VxLAN tunnel"; 640 } 642 container redundancy-group-binds { 643 list redundancy-group-bind { 644 key 'vxlan-id redundancy-group'; 645 leaf vxlan-id { 646 type uint32 { 647 range 1..16777215 { 648 description 'The value of VXLAN,it must between 1 to 16777215.'; 649 } 650 } 651 description 'VXLAN ID binding by redundancy group.'; 652 } 654 leaf redundancy-group { 655 type uint32 { 656 range 1..4294967293 { 657 description 'The value of redundancy group,it must between 1 to' 658 + ' 4294967293.'; 659 } 660 } 661 description 'Redundancy group ID.'; 662 } 663 description 'Redundancy group bind table.'; 664 } 665 description 'Redundancy group bind table.'; 666 } 667 description "vxlan instance list"; 668 } 669 description 670 "VxLAN configure model."; 671 } 673 augment "/evpn:evpn/evpn:evpn-instances/evpn:evpn-instance" 674 +"/evpn:bgp-parameters/evpn:common" { 676 uses evpn:bgp-parameters-grp { 677 if-feature evpn-bgp-params; 678 } 679 description "EVPN configuration"; 680 } 682 /* Operational data */ 683 container vxlan-state{ 684 config false; 685 container vxlan { 686 container vxlan-tunnels { 687 list vxlan-tunnel { 688 key 'local-ip remote-ip'; 689 leaf local-ip { 690 type address-family-type ; 691 description 'Local IP of tunnel.'; 692 } 694 leaf remote-ip { 695 type address-family-type ; 696 description 'Remote IP of tunnel.'; 697 } 699 leaf static-tunnel-id { 700 type uint32 ; 701 description 'Static tunnel ID.'; 702 } 704 leaf evpn-tunnel-id { 705 type uint32 ; 706 description 'EVPN tunnel ID.'; 707 } 709 container statistics { 710 container tunnel-statistics { 711 leaf in-bytes { 712 type string { 713 length 0..24 ; 714 } 715 description 'Total bytes received.'; 717 } 719 leaf out-bytes { 720 type string { 721 length 0..24 ; 722 } 723 description 'Total bytes sent.'; 724 } 726 leaf in-packets { 727 type string { 728 length 0..24; 729 } 730 description 'Total packets received.'; 731 } 733 leaf out-packets { 734 type string { 735 length 0..24 ; 736 } 737 description 'Total packets sent.'; 738 } 739 description 'Total tunnel statistics.'; 740 } 742 container tunnel-vni-statistics { 743 list tunnel-vni-statistic { 744 key vxlan-id ; 745 leaf vxlan-id { 746 type uint32 ; 747 description 'The VXLAN in tunnel.'; 748 } 750 leaf in-bytes { 751 type string { 752 length 1..24 ; 753 } 754 description 'Total bytes received.'; 755 } 757 leaf out-bytes { 758 type string { 759 length 1..24 ; 760 } 761 description 'Total bytes sent.'; 762 } 764 leaf in-packets { 765 type string { 766 length 1..24 ; 767 } 768 description 'Total packets received.'; 769 } 771 leaf out-packets { 773 type string { 774 length 1..24 ; 775 } 776 description 'Total packets sent.'; 777 } 778 description 'Statistics in VXLAN tunnel.'; 779 } 780 description 'Statistics in VXLAN tunnel.'; 781 } 782 description 'Tunnel statistics.' ; 783 } 784 description 'VXLAN tunnel info.'; 785 } 786 description 'VXLAN tunnel Info.'; 787 } 788 description 'Information of VXLAN state.'; 789 } 790 description 'Information of VXLAN state.'; 791 } 792 } 793 795 7. Security Considerations 797 8. Acknowledgements 799 9. IANA Considerations 801 This document requires no IANA Actions. Please remove this section 802 before RFC publication. 804 10. Normative References 806 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 807 Requirement Levels", BCP 14, RFC 2119, 808 DOI 10.17487/RFC2119, March 1997, 809 . 811 [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for 812 the Network Configuration Protocol (NETCONF)", RFC 6020, 813 DOI 10.17487/RFC6020, October 2010, 814 . 816 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 817 and A. Bierman, Ed., "Network Configuration Protocol 818 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 819 . 821 [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", 822 RFC 6991, DOI 10.17487/RFC6991, July 2013, 823 . 825 [RFC7223] Bjorklund, M., "A YANG Data Model for Interface 826 Management", RFC 7223, DOI 10.17487/RFC7223, May 2014, 827 . 829 [RFC7348] Mahalingam, M., Dutt, D., Duda, K., Agarwal, P., Kreeger, 830 L., Sridhar, T., Bursell, M., and C. Wright, "Virtual 831 eXtensible Local Area Network (VXLAN): A Framework for 832 Overlaying Virtualized Layer 2 Networks over Layer 3 833 Networks", RFC 7348, DOI 10.17487/RFC7348, August 2014, 834 . 836 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 837 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 838 May 2017, . 840 Authors' Addresses 842 Fangwei Hu 843 ZTE Corporation 844 No.889 Bibo Rd 845 Shanghai 201203 846 China 848 Phone: +86 21 68896273 849 Email: hu.fangwei@zte.com.cn 850 Ran Chen 851 ZTE Corporation 852 No.50 Software Avenue,Yuhuatai District 853 Nanjing, Jiangsu Province 210012 854 China 856 Phone: +86 025 88014636 857 Email: chen.ran@zte.com.cn 859 Mallik Mahalingam 860 Springpath 861 640 W. California Ave, Suite #110 862 Sunnyvale, CA 94086 863 USA 865 Email: mallik_mahalingam@yahoo.com 867 Zu Qiang 868 Ericsson 869 8400, boul. Decarie 870 Ville Mont-Royal, QC 871 Canada 873 Email: Zu.Qiang@Ericsson.com 875 Davari Shahram 876 yahoo 878 Email: davarish@yahoo.com 880 Xufeng Liu 881 Jabil 882 8281 Greensboro Drive,Suite 200 883 McLean, VA 22102 884 USA 886 Email: Xufeng_Liu@jabil.com