idnits 2.17.1 draft-chen-nvo3-vxlan-yang-04.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 9 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 136 has weird spacing: '...vlan-id vla...' == Line 147 has weird spacing: '...ce-name if:...' == Line 156 has weird spacing: '...xlan-id vxl...' == Line 165 has weird spacing: '...xlan-id vxl...' == Line 169 has weird spacing: '...y-group uin...' == (4 more instances...) -- The document date (December 26, 2016) is 2678 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 812, but no explicit reference was found in the text == Unused Reference: 'RFC6991' is defined on line 822, but no explicit reference was found in the text == Unused Reference: 'RFC7223' is defined on line 826, 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 (~~), 10 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: June 29, 2017 Mallik. Mahalingam 6 Springpath 7 Qiang. Zu 8 Ericsson 9 S. Davari 10 yahoo 11 X. Liu 12 Jabil 13 December 26, 2016 15 YANG Data Model for VxLAN Protocol 16 draft-chen-nvo3-vxlan-yang-04.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 http://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 June 29, 2017. 39 Copyright Notice 41 Copyright (c) 2016 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 (http://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. YANG Data Model for VxLAN Configuration . . . . . . . . . . . 2 59 3.1. VxLAN Multicast IP Address . . . . . . . . . . . . . . . 2 60 3.2. VxLAN Access Type . . . . . . . . . . . . . . . . . . . . 2 61 3.3. Inner VLAN Tag Handling Mode . . . . . . . . . . . . . . 3 62 4. Design Tree of Configuration Data Model . . . . . . . . . . . 3 63 5. Design Tree of Operational State Model . . . . . . . . . . . 5 64 6. VxLAN YANG Model . . . . . . . . . . . . . . . . . . . . . . 5 65 7. Security Considerations . . . . . . . . . . . . . . . . . . . 17 66 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 17 67 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17 68 10. Normative References . . . . . . . . . . . . . . . . . . . . 18 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. YANG Data Model for VxLAN Configuration 82 3.1. VxLAN Multicast IP Address 84 The vxlan-multicast-ip is used to configure the IP multicast group, 85 which the VxLAN VNI of the VTEP is mapping to. Both the IPv4 and 86 IPv6 address family are supported. 88 3.2. VxLAN Access Type 90 There are several access types supported for VxLAN: 92 o vlan-1:1: the vxlan access type is VLAN, and each VxLAN is only 93 mapping to one VLAN. 95 o vlan- n:1: the vxlan access type is VLAN, and each VxLAN could be 96 mapped to several VLANs. 98 o L3-interface: the VxLAN access type is layer 3 interface. 100 o mac: the VxLAN access type is MAC address. 102 o vlan-l2-interface: the VxLAN access type is VLAN plus Layer 2 103 interface. 105 3.3. Inner VLAN Tag Handling Mode 107 There are two handling modes for the inner VLAN tag: discard-inner- 108 vlan mode and no-discard-inner-vlan mode. If the VTEP interface 109 works in the discard-inner-vlan mode, the VxLAN is only mapped to one 110 VLAN. The inner VLAN tag will be stripped when encapsulating the 111 VxLAN frame. On the decapsulation side, if VTEP receives the VxLAN 112 frame with inner VLAN tag, it will discard the frame in this work 113 mode. If the VTEP receives the VxLAN frame without VLAN tag, it will 114 fill in the VLAN tag based on the VxLAN and VLAN mapping. 116 If the VTEP interface works in the no-discard-inner-vlan mode, the 117 VxLAN could be mapped to several VLANs. The inner VLAN tag will not 118 stripped when encapsulating the VxLAN frame in the VxLAN 119 encapsulation side. On the decapsulation side, if VTEP receives the 120 VxLAN frame, it will strip the VxLAN header, and keep the VLAN frame. 122 4. Design Tree of Configuration Data Model 124 module: ietf-vxlan 125 +--rw vxlan 126 | +--rw global-enable? empty 127 | +--rw vxlan-instance* [vxlan-id] 128 | +--rw vxlan-id vxlan-id 129 | +--rw description? string 130 | +--rw unknow-unicast-drop? enumeration 131 | +--rw filter-vrrp? enumeration 132 | +--rw (vxlan-access-types)? {vxlan-access-types}? 133 | | +--:(access-type-vlan) 134 | | | +--rw access-type-vlan? access-type-vlan 135 | | | +--rw access-vlan-list* [vlan-id] 136 | | | +--rw vlan-id vlan 137 | | +--:(access-type-mac) 138 | | | +--rw access-type-mac? empty 139 | | | +--rw mac yang:mac-address 140 | | +--:(access-type-l2interface) 141 | | | +--rw access-type-l2interface? empty 142 | | | +--rw vlan-id vlan 143 | | | +--rw interface-name if:interface-ref 144 | | +--:(access-type-l3interface) 145 | | +--rw access-type-l3interface? empty 146 | | +--rw map-l3interface* [interface-name] 147 | | +--rw interface-name if:interface-ref 148 | +--rw vtep-instances* [vtep-id] 149 | | +--rw vtep-id uint32 150 | | +--rw vtep-name? string 151 | | +--rw source-interface? if:interface-ref 152 | | +--rw multicast-ip inet:ip-address 153 | | +--rw mtu? uint32 {mtu}? 154 | | +--rw inner-vlan-handling-mode? inner-vlan-handling-mode 155 | | +--rw bind-vxlan-id* [vxlan-id] 156 | | +--rw vxlan-id vxlan-id 157 | +--rw static-vxlan-tunnel* [vxlan-tunnel-id] 158 | | +--rw vxlan-tunnel-id uint32 159 | | +--rw vxlan-tunnel-name? string 160 | | +--rw address-family* [af] 161 | | +--rw af address-family-type 162 | | +--rw tunnel-source-ip? address-family-type 163 | | +--rw tunnel-destination-ip? address-family-type 164 | | +--rw bind-vxlan-id* [vxlan-id] 165 | | +--rw vxlan-id vxlan-id 166 | +--rw redundancy-group-binds 167 | +--rw redundancy-group-bind* [vxlan-id redundancy-group] 168 | +--rw vxlan-id uint32 169 | +--rw redundancy-group uint32 170 +--ro vxlan-state 171 +--ro vxlan 172 +--ro vxlan-tunnels 173 +--ro vxlan-tunnel* [local-ip remote-ip] 174 +--ro local-ip address-family-type 175 +--ro remote-ip address-family-type 176 +--ro static-tunnel-id? uint32 177 +--ro evpn-tunnel-id? uint32 178 +--ro statistics 179 +--ro tunnel-statistics 180 | +--ro in-bytes? string 181 | +--ro out-bytes? string 182 | +--ro in-packets? string 183 | +--ro out-packets? string 184 +--ro tunnel-vni-statistics 185 +--ro tunnel-vni-statistic* [vxlan-id] 186 +--ro vxlan-id uint32 187 +--ro in-bytes? string 188 +--ro out-bytes? string 189 +--ro in-packets? string 190 +--ro out-packets? string 192 augment /evpn:evpn/evpn:evpn-instances/evpn:evpn-instance/evpn:bgp-parameters/evpn:common: 193 +--rw bgp-parameters 194 +--rw common 195 +--rw rd-rt* [route-distinguisher] 196 +--rw route-distinguisher string 197 +--rw vpn-target* [rt-value] 198 +--rw rt-value string 199 +--rw rt-type bgp-rt-type 201 5. Design Tree of Operational State Model 203 +--ro vxlan-state 204 +--ro vxlan 205 +--ro vxlan-tunnels 206 +--ro vxlan-tunnel* [local-ip remote-ip] 207 +--ro local-ip address-family-type 208 +--ro remote-ip address-family-type 209 +--ro static-tunnel-id? uint32 210 +--ro evpn-tunnel-id? uint32 211 +--ro statistics 212 +--ro tunnel-statistics 213 | +--ro in-bytes? string 214 | +--ro out-bytes? string 215 | +--ro in-packets? string 216 | +--ro out-packets? string 217 +--ro tunnel-vni-statistics 218 +--ro tunnel-vni-statistic* [vxlan-id] 219 +--ro vxlan-id uint32 220 +--ro in-bytes? string 221 +--ro out-bytes? string 222 +--ro in-packets? string 223 +--ro out-packets? string 225 6. VxLAN YANG Model 227 file "ietf-vxlan@2016-12-08.yang" 228 module ietf-vxlan { 229 namespace "urn:ietf:params:xml:ns:yang:ietf-vxlan"; 230 prefix "vxlan"; 232 import ietf-evpn { 233 prefix "evpn"; 234 } 236 import ietf-interfaces { 237 prefix "if"; 238 } 240 import ietf-inet-types { 241 prefix "inet"; 242 } 244 import ietf-yang-types { 245 prefix yang; 246 } 248 organization 249 "IETF NVO3(Network Virtualization Overlays) Working Group"; 251 contact 252 " 253 WG List: 255 WG Chair: Matthew Bocci 256 258 WG Chair: Benson Schliesser 259 261 Editor: Fangwei Hu 262 264 Editor: Ran Chen 265 267 Editor: Mallik Mahalingam 268 270 Editor: Zu Qiang 271 272 "; 274 description 275 "The YANG module defines a generic configuration 276 model for VxLAN protocol"; 278 revision 2016-12-08 { 279 description "updated the vxlan yang model based on the comments from IETF 97th meeting," 280 +"augmenting EVPN data model, adding access type configuration and MTU configuration."; 281 reference 282 "draft-chen-nvo3-vxlan-yang-04"; 283 } 284 revision 2016-06-02 { 285 description 286 "03 revision. Update the YANG data model based on thec comments of IETF 95th meeting."; 287 reference 288 "draft-chen-nvo3-vxlan-yang-03"; 289 } 291 revision 2015-12-01 { 292 description 293 "02 revision."; 294 reference 295 "draft-chen-nvo3-vxlan-yang-02"; 296 } 298 revision 2015-10-12 { 299 description 300 "01 revision."; 301 reference 302 "draft-chen-nvo3-vxlan-yang-01"; 303 } 305 revision 2015-05-05 { 306 description "Initial revision"; 307 reference 308 "draft-chen-nvo3-vxlan-yang-00"; 309 } 311 /* Feature */ 313 feature vxlan-access-types { 314 description 315 "Support configuration vxlan access types."; 316 } 318 feature mtu { 319 description 320 "Support configuration vxlan MTU value."; 321 } 323 feature evpn-bgp-params { 324 description "Support EVPN BGP parameter."; 325 } 327 /* Typedefs */ 329 typedef vlan { 330 type uint16 { 331 range 1..4094; 333 } 334 description 335 "Typedef for VLAN"; 336 } 338 typedef vxlan-id { 339 type uint32; 340 description 341 "Typedef for VxLAN ID."; 342 } 343 typedef access-type-vlan { 344 type enumeration { 345 enum access-type-vlan1to1 { 346 description 347 "Access type is VLAN 1:1."; 348 } 349 enum access-type-vlan1ton { 350 description 351 "Access type is VLAN 1:n."; 352 } 354 } 355 default access-type-vlan1to1 ; 356 description 357 "VxLAN access type is VLAN."; 358 } 360 typedef access-type-mac { 361 type empty ; 362 description 363 "VxLAN access type is MAC."; 364 } 366 typedef inner-vlan-handling-mode { 367 type enumeration { 368 enum discard-inner-vlan { 369 description 370 "Discard inner-VLAN."; 371 } 372 enum no-discard-inner-vlan { 373 description 374 "No discard inner-VLAN."; 375 } 376 } 377 default discard-inner-vlan ; 378 description 379 "Typedef for inner-vlan-handling-mode"; 381 } 383 typedef address-family-type { 384 type enumeration { 385 enum ipv4 { 386 description 387 "IPv4"; 388 } 389 enum ipv6 { 390 description 391 "IPv6"; 392 } 393 } 394 description 395 "Typedef for address family type."; 396 } 398 /* Configuration Data */ 400 container vxlan{ 401 leaf global-enable { 402 type empty ; 403 description 'VXLAN global enble.'; 404 } 406 list vxlan-instance { 407 key vxlan-id ; 408 leaf vxlan-id { 409 type vxlan-id; 410 description "VxLAN ID."; 411 } 413 leaf description { 414 type string { 415 length 0..64 { 416 description 'VXLAN instance description information.'; 417 } 418 } 419 description 'The description information of VXLAN instance.'; 420 } 422 leaf unknow-unicast-drop { 423 type enumeration { 424 enum enable { 425 value 1 ; 426 description 'Unknown unicast drop enable.'; 427 } 428 enum disable { 429 value 2 ; 430 description 'Unknown unicast drop disable.'; 431 } 432 } 433 default enable ; 434 description 'Unknow unicast drop configuration of VXLAN instance.'; 435 } 437 leaf filter-vrrp { 438 type enumeration { 439 enum enable { 440 value 1 ; 441 description 'VRRP packets filter.'; 442 } 443 enum disable { 444 value 2 ; 445 description 'VRRP packets not filter.'; 446 } 447 } 448 default enable ; 449 description 'VRRP packets filter configuration of VXLAN instance.'; 450 } 452 choice vxlan-access-types { 453 if-feature vxlan-access-types; 454 case access-type-vlan { 456 leaf access-type-vlan { 457 type access-type-vlan; 459 description 460 "Access type is VLAN."; 461 } 463 list access-vlan-list { 464 key vlan-id ; 465 leaf vlan-id { 466 type vlan; 467 description 468 "VLAN ID."; 469 } 470 description 471 "VLAN ID list." ; 472 } 473 description 474 "VxLAN access type choice is VLAN."; 475 } 476 case access-type-mac { 477 leaf access-type-mac { 478 type empty ; 479 description 480 "Access type is MAC."; 481 } 483 leaf mac { 484 type yang:mac-address ; 485 mandatory true ; 486 description 487 "MAC Address."; 488 } 489 description 490 "VxLAN access type choice is MAC Address."; 491 } 493 case access-type-l2interface { 494 leaf access-type-l2interface { 495 type empty ; 496 description 497 "VXLAN map layer two interface."; 498 } 500 leaf vlan-id { 501 type vlan; 502 mandatory true ; 503 description 504 "VLAN ID."; 505 } 507 leaf interface-name { 508 type if:interface-ref; 509 mandatory true ; 510 description 511 "Layer two interface name."; 512 } 513 description 514 "VxLAN access type choice is layer two interface."; 515 } 517 case access-type-l3interface { 518 leaf access-type-l3interface { 519 type empty ; 520 description 521 "Access type of VxLAN is layer three interface."; 522 } 523 list map-l3interface { 524 key interface-name ; 525 leaf interface-name { 526 type if:interface-ref; 527 description 528 "Layer three interface name."; 529 } 530 description 531 "Layer three interface list."; 532 } 533 description 534 "VxLAN access type choice is layer three interface."; 535 } 536 description 537 "VxLAN access type choice."; 538 } 540 list vtep-instances { 541 key vtep-id ; 542 leaf vtep-id { 543 type uint32; 544 description 545 "VTEP ID."; 546 } 548 leaf vtep-name{ 549 type string; 550 description 551 "VTEP instance name."; 552 } 554 leaf source-interface { 555 type if:interface-ref; 556 description 557 "Source interface name."; 558 } 560 leaf multicast-ip { 561 type inet:ip-address; 562 mandatory true ; 563 description 564 "VxLAN multicast IP address."; 565 } 567 leaf mtu { 568 if-feature mtu; 569 type uint32; 570 description "vxlan mtu"; 572 } 574 leaf inner-vlan-handling-mode { 575 type inner-vlan-handling-mode; 576 description 577 "The inner vlan tag handling mode."; 578 } 580 list bind-vxlan-id { 581 key vxlan-id; 582 leaf vxlan-id { 583 type vxlan-id; 584 description 585 "VxLAN ID."; 586 } 587 description 588 "VxLAN ID list for the VTEP."; 589 } 590 description 591 "VTEP instance."; 592 } 594 list static-vxlan-tunnel{ 595 key vxlan-tunnel-id; 596 leaf vxlan-tunnel-id { 597 type uint32; 598 description 599 "Static VxLAN tunnel ID."; 600 } 602 leaf vxlan-tunnel-name { 603 type string; 604 description 605 "Name of the static VxLAN tunnel."; 606 } 608 list address-family { 609 key "af"; 610 leaf af { 611 type address-family-type; 612 description 613 "Address family type value."; 614 } 616 leaf tunnel-source-ip { 617 type address-family-type; 618 description 619 "Source IP address for the static VxLAN tunnel"; 621 } 623 leaf tunnel-destination-ip { 624 type address-family-type; 625 description 626 "Destination IP address for the static VxLAN tunnel"; 627 } 629 list bind-vxlan-id { 630 key vxlan-id; 631 leaf vxlan-id { 632 type vxlan-id; 633 description 634 "VxLAN ID."; 635 } 636 description 637 "VxLAN ID list for the VTEP."; 638 } 640 description 641 "Per-af params."; 642 } 643 description 644 "Configure the static VxLAN tunnel"; 645 } 647 container redundancy-group-binds { 648 list redundancy-group-bind { 649 key 'vxlan-id redundancy-group'; 650 leaf vxlan-id { 651 type uint32 { 652 range 1..16777215 { 653 description 'The value of VXLAN,it must between 1 to 16777215.'; 654 } 655 } 656 description 'VXLAN ID binding by redundancy group.'; 657 } 659 leaf redundancy-group { 660 type uint32 { 661 range 1..4294967293 { 662 description 'The value of redundancy group,it must between 1 to' 663 + ' 4294967293.'; 664 } 665 } 666 description 'Redundancy group ID.'; 667 } 668 description 'Redundancy group bind table.'; 670 } 671 description 'Redundancy group bind table.'; 672 } 673 description "vxlan instance list"; 674 } 675 description 676 "VxLAN configure model."; 677 } 679 augment "/evpn:evpn/evpn:evpn-instances/evpn:evpn-instance" 680 +"/evpn:bgp-parameters/evpn:common" { 682 uses evpn:bgp-parameters-grp { 683 if-feature evpn-bgp-params; 684 } 685 description "EVPN configuration"; 686 } 688 /* Operational data */ 689 container vxlan-state{ 690 config false; 691 container vxlan { 692 container vxlan-tunnels { 693 list vxlan-tunnel { 694 key 'local-ip remote-ip'; 695 leaf local-ip { 696 type address-family-type ; 697 description 'Local IP of tunnel.'; 698 } 700 leaf remote-ip { 701 type address-family-type ; 702 description 'Remote IP of tunnel.'; 703 } 705 leaf static-tunnel-id { 706 type uint32 ; 707 description 'Static tunnel ID.'; 708 } 710 leaf evpn-tunnel-id { 711 type uint32 ; 712 description 'EVPN tunnel ID.'; 713 } 715 container statistics { 716 container tunnel-statistics { 717 leaf in-bytes { 718 type string { 719 length 0..24 ; 720 } 721 description 'Total bytes received.'; 722 } 724 leaf out-bytes { 725 type string { 726 length 0..24 ; 727 } 728 description 'Total bytes sent.'; 729 } 731 leaf in-packets { 732 type string { 733 length 0..24; 734 } 735 description 'Total packets received.'; 736 } 738 leaf out-packets { 739 type string { 740 length 0..24 ; 741 } 742 description 'Total packets sent.'; 743 } 744 description 'Total tunnel statistics.'; 745 } 747 container tunnel-vni-statistics { 748 list tunnel-vni-statistic { 749 key vxlan-id ; 750 leaf vxlan-id { 751 type uint32 ; 752 description 'The VXLAN in tunnel.'; 753 } 755 leaf in-bytes { 756 type string { 757 length 1..24 ; 758 } 759 description 'Total bytes received.'; 760 } 762 leaf out-bytes { 763 type string { 764 length 1..24 ; 766 } 767 description 'Total bytes sent.'; 768 } 770 leaf in-packets { 771 type string { 772 length 1..24 ; 773 } 774 description 'Total packets received.'; 775 } 777 leaf out-packets { 779 type string { 780 length 1..24 ; 781 } 782 description 'Total packets sent.'; 783 } 784 description 'Statistics in VXLAN tunnel.'; 785 } 786 description 'Statistics in VXLAN tunnel.'; 787 } 788 description 'Tunnel statistics.' ; 789 } 790 description 'VXLAN tunnel info.'; 791 } 792 description 'VXLAN tunnel Info.'; 793 } 794 description 'Information of VXLAN state.'; 795 } 796 description 'Information of VXLAN state.'; 797 } 798 } 799 801 7. Security Considerations 803 8. Acknowledgements 805 9. IANA Considerations 807 This document requires no IANA Actions. Please remove this section 808 before RFC publication. 810 10. Normative References 812 [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for 813 the Network Configuration Protocol (NETCONF)", RFC 6020, 814 DOI 10.17487/RFC6020, October 2010, 815 . 817 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 818 and A. Bierman, Ed., "Network Configuration Protocol 819 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 820 . 822 [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", 823 RFC 6991, DOI 10.17487/RFC6991, July 2013, 824 . 826 [RFC7223] Bjorklund, M., "A YANG Data Model for Interface 827 Management", RFC 7223, DOI 10.17487/RFC7223, May 2014, 828 . 830 [RFC7348] Mahalingam, M., Dutt, D., Duda, K., Agarwal, P., Kreeger, 831 L., Sridhar, T., Bursell, M., and C. Wright, "Virtual 832 eXtensible Local Area Network (VXLAN): A Framework for 833 Overlaying Virtualized Layer 2 Networks over Layer 3 834 Networks", RFC 7348, DOI 10.17487/RFC7348, August 2014, 835 . 837 Authors' Addresses 839 Fangwei Hu 840 ZTE Corporation 841 No.889 Bibo Rd 842 Shanghai 201203 843 China 845 Phone: +86 21 68896273 846 Email: hu.fangwei@zte.com.cn 848 Ran Chen 849 ZTE Corporation 850 No.50 Software Avenue,Yuhuatai District 851 Nanjing, Jiangsu Province 210012 852 China 854 Phone: +86 025 88014636 855 Email: chen.ran@zte.com.cn 856 Mallik Mahalingam 857 Springpath 858 640 W. California Ave, Suite #110 859 Sunnyvale, CA 94086 860 USA 862 Email: mallik_mahalingam@yahoo.com 864 Zu Qiang 865 Ericsson 866 8400, boul. Decarie 867 Ville Mont-Royal, QC 868 Canada 870 Email: Zu.Qiang@Ericsson.com 872 Davari Shahram 873 yahoo 875 Email: davarish@yahoo.com 877 Xufeng Liu 878 Jabil 879 8281 Greensboro Drive,Suite 200 880 McLean, VA 22102 881 USA 883 Email: Xufeng_Liu@jabil.com