idnits 2.17.1 draft-kishjac-bmwg-pbbevpn-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 88 has weird spacing: '...routing engin...' == Line 90 has weird spacing: '...roperly after...' == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (June 16, 2016) is 2872 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: 'RFC2544' is defined on line 584, but no explicit reference was found in the text == Unused Reference: 'RFC7432' is defined on line 591, but no explicit reference was found in the text ** Downref: Normative reference to an Informational RFC: RFC 2544 Summary: 1 error (**), 0 flaws (~~), 6 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force S. Jacob, Ed. 3 Internet-Draft K. Tiruveedhula 4 Intended status: Standards Track Juniper Networks 5 Expires: December 18, 2016 June 16, 2016 7 Benchmarking Methodology for PBB-EVPN 8 draft-kishjac-bmwg-pbbevpn-00 10 Abstract 12 This document defines the methodologies for benchmarking performance 13 of PBB-EVPN.PBB-EVPN is defined in RFC 7623. It is being deployed in 14 provider network.This document provides the benchmarking 15 methodologies for PBB-EVPN convergance,data plane,control plane 16 learning of mac. 18 Status of This Memo 20 This Internet-Draft is submitted in full conformance with the 21 provisions of BCP 78 and BCP 79. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF). Note that other groups may also distribute 25 working documents as Internet-Drafts. The list of current Internet- 26 Drafts is at http://datatracker.ietf.org/drafts/current/. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 This Internet-Draft will expire on December 18, 2016. 35 Copyright Notice 37 Copyright (c) 2016 IETF Trust and the persons identified as the 38 document authors. All rights reserved. 40 This document is subject to BCP 78 and the IETF Trust's Legal 41 Provisions Relating to IETF Documents 42 (http://trustee.ietf.org/license-info) in effect on the date of 43 publication of this document. Please review these documents 44 carefully, as they describe your rights and restrictions with respect 45 to this document. Code Components extracted from this document must 46 include Simplified BSD License text as described in Section 4.e of 47 the Trust Legal Provisions and are provided without warranty as 48 described in the Simplified BSD License. 50 Table of Contents 52 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 53 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3 54 2. Test Topology . . . . . . . . . . . . . . . . . . . . . . . . 3 55 3. Network . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 56 4. Test Procedure . . . . . . . . . . . . . . . . . . . . . . . 5 57 4.1. Customer MAC Learning in Data Plane and B-MAC in control 58 plane . . . . . . . . . . . . . . . . . . . . . . . . . . 5 59 4.2. MAC flush for locally learned and remote learned MAC . . 5 60 4.3. High Availablity . . . . . . . . . . . . . . . . . . . . 5 61 4.4. Reliablity . . . . . . . . . . . . . . . . . . . . . . . 5 62 4.5. Convergence Time . . . . . . . . . . . . . . . . . . . . 5 63 4.6. Scale . . . . . . . . . . . . . . . . . . . . . . . . . . 6 64 4.7. SOAK . . . . . . . . . . . . . . . . . . . . . . . . . . 6 65 4.8. Measurement Statistics . . . . . . . . . . . . . . . . . 6 66 5. Test Cases . . . . . . . . . . . . . . . . . . . . . . . . . 6 67 5.1. MAC Learning in Control plane and Data Plane . . . . . . 6 68 5.1.1. To check the time taken to learn the mac address in 69 DUT . . . . . . . . . . . . . . . . . . . . . . . . . 6 70 5.1.2. To check the time taken to learn 100,000 routes from 71 remote peer by DUT. . . . . . . . . . . . . . . . . . 7 72 5.1.3. To check the time taken to flush the local entry due 73 to CE link failure . . . . . . . . . . . . . . . . . 7 74 5.1.4. To check the time taken by DUT to flush 100,000 75 macs learned from remote PE after R1 traffic 76 generator link failure . . . . . . . . . . . . . . . 8 77 5.1.5. To measure the mac ageing time. . . . . . . . . . . . 8 78 5.1.6. To check the time taken by DUT to age from 79 remote PE after stopping the traffic at remote PE. . 9 80 5.2. Convergence . . . . . . . . . . . . . . . . . . . . . . . 9 81 5.2.1. To check the time taken by DUT to learn 100,000 82 routes from local and 100,000 from remote and 83 measure the time of flood from DUT. . . . . . . . . . 9 84 5.2.2. To measure the time taken to elect a new DF by adding 85 a a MHPE. . . . . . . . . . . . . . . . . . . . . . . 10 86 5.3. Reliability . . . . . . . . . . . . . . . . . . . . . . . 10 87 5.3.1. To check the whether there is traffic loss due to 88 routing engine failover for redundancy test. . . . . 10 89 5.3.2. To check the whether DF election is taking place 90 properly after the one of the MH PE reboot. . . . . 11 91 5.4. Scale . . . . . . . . . . . . . . . . . . . . . . . . . . 11 92 5.4.1. To Scale the DUT to 4k PBB-EVPN instances and clear 93 bgp in DUT without traffic. . . . . . . . . . 11 94 5.4.2. To Scale the DUT to 4k PBB-EVPN instances and clear 95 bgp in DUT with traffic. Measure the convergence 96 time . . . . . . . . . . . . . . . . . . . . . . . . 12 97 5.5. Soak Test . . . . . . . . . . . . . . . . . . . . . . . . 12 98 5.5.1. To Scale the DUT to 4k PBB-EVPN instances in DUT with 99 traffic and run the set up for 24hrs . . . . . 13 100 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 13 101 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 102 8. Security Considerations . . . . . . . . . . . . . . . . . . . 13 103 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 13 104 9.1. Normative References . . . . . . . . . . . . . . . . . . 13 105 9.2. Informative References . . . . . . . . . . . . . . . . . 14 106 Appendix A. Appendix . . . . . . . . . . . . . . . . . . . . . . 14 107 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14 109 1. Introduction 111 PBB-EVPN which is defined in RFC 7623 which describes procedures for 112 BGP MPLS-based PBB-EVPN.This document defines the methodologies for 113 benchmarking performance of PBB-EVPN.PBB-EVPN has been implemented 114 with many varying designs in order to achieve their intended network 115 functionality.The scope of this document is to provide methodologies 116 for benchmarking pbb-evpn data, control plane mac learning, mac 117 flush, mac ageing, convergence, high availablity, reliablity,scale. 119 1.1. Requirements Language 121 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 122 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 123 document are to be interpreted as described in RFC 2119 [RFC2119]. 125 2. Test Topology 126 Topology Diagram 128 | Traffic Generator 129 +----------+ 130 | | 131 | R1 | 132 | | 133 +----------+ 134 | 135 | 136 +----------+ 137 | | 138 | RR | 139 | | 140 +----------+-------------| 141 | | 142 | | 143 +----------+ +-----------+ 144 | | | MHPE2 | 145 | DUT | | | 146 | MHPE1 | | | 147 +----------+ +-----------+ 148 | | 149 +----------+------------ 150 | | 151 | CE | 152 | | 153 +----------+------------ Traffic Generator 155 Topology Diagram 157 Figure 1 159 3. Network 161 The network consists of 5 routers and 2 traffic generator ports. DUT 162 is acting as one of MH PE to CE.The RR is acting as route reflector 163 and core router.R1 is a Single home router running pbbevpn. All four 164 routers except CE are running mpls,bgp. CE is a dual home connected 165 to DUT and MH PE1. The testing will be done on DUT to bench mark the 166 service.DUT and MHPE2 is running PBB-EVPN with SA/AA with CE.The DUT 167 and and other PE's will be running 100 PBB-EVN instances on 100 sub 168 interfaces. 170 4. Test Procedure 172 The test defined to bench mark the performance of PBB-EVPN mac 173 learning in control pland and data plane. Mac flush,High 174 Availablity, convergence time in link failures,Reliablity,scale 175 scenarios. 177 4.1. Customer MAC Learning in Data Plane and B-MAC in control plane 179 The Customer MAC will be learned in data plane, test is to measure 180 the time taken to learn the "X" number of mac's in time "T". The 181 data plane learning will from the locally connected interface. The 182 control plane learning of B-MAC is through BGP advertisements from 183 the remote PE.Let the local learning time be "T" and control plane 184 learning of the B-MAC time be "T'". 186 4.2. MAC flush for locally learned and remote learned MAC 188 The time taken to flush the "X" locally learned mac, let it be "T1" 189 once the traffic is stopped. The time taken flush the remote mac 190 which learned by data plane that "X" macs when the traffic is 191 stopped at remote side.Let the measured time is "T2". 193 4.3. High Availablity 195 The traffic is flowing bi direction. The bgp is converged, let the 196 "X" numbers of macs learned locally and remotely. Then traffic is 197 flowing at "P" packets per sec. The traffic generator is measuring 198 the Tx and Rx packets, while the routing engine failover there should 199 not any packet loss the router tester must show both "P" packet per 200 seconds. 202 4.4. Reliablity 204 This is to measure during any events like adding a new PE or 205 rebooting on of the MHPE in the same ethernet segment,there should 206 not any issues in DF election. There should not be any loop. The DF 207 elction must take place in t time where 4>t>3. The DF election must 208 work on V mod N. There should not be any loop in traffic. 210 4.5. Convergence Time 212 During any events like link failure, hard reset measure the time 213 taken to learn "X" mac's locally and remotely or time taken to learn 214 "X" mac locally and remote. 216 4.6. Scale 218 This is to measure the performance of DUT in scaling to "X" PBB-EVPN 219 instances. The measured parameters are CPU usage, memory 220 leak,crashes. 222 4.7. SOAK 224 This is measuring the performance of DUT running with scaled 225 configuration with traffic over a peroid of time "T'". In each 226 interval "t1" the parameters measured are CPU usage, memory usage, 227 crashes. 229 4.8. Measurement Statistics 231 The test is repeated for "N" times and the value is taken by 232 averaging the values. 234 5. Test Cases 236 5.1. MAC Learning in Control plane and Data Plane 238 The following tests are conducted to measure mac learning local and 239 remote. 241 5.1.1. To check the time taken to learn the mac address in DUT 243 Objective: 245 To check the time taken to learn the mac address locally and time 246 taken to send the locally learned routes to peers. 248 a. Send 100,000 unicast frames from CE to MHPE1(DUT) working in SA 249 mode where DUT is the DF so that it can forward the traffic with 250 different source and destination address,Measure the time taken 251 to learn these mac in forwarding table. 253 Procedure: 255 Configure PBB-EVPN EVI in R1,MHPE2,DUT.All 4 routers except CE are 256 running mpls,bgp,RR is acting as route reflector to R1,MHPE2 and 257 DUT.Once the bgp comes up check the DUT evpn table.For MH PE ESI must 258 be configured per IFD/Interface. Using RT (traffic generator) to 259 send the traffic to the routers. Measurement The DUT mac table must 260 learn the 100,000 mac address. Measurement The DUT mac table must 261 learn the 100,000 measure the time taken to learn the 100,000 mac 262 address from locally. 264 5.1.2. To check the time taken to learn 100,000 routes from remote peer 265 by DUT. 267 Objective: 269 Send 100,000 frames with different SA and DA to DUT from R1 using 270 traffic generator. Measure the time taken to learn these 100,000 271 macs from remote peer and program the mac address table. 273 Procedure: 275 Configure PBB-EVPN EVI in R1, MHPE2, DUT. All 4 routers except CE 276 are running mpls, bgp, RR is acting as route reflector to R1, MHPE2 277 and DUT.Once the bgp comes up check the DUT mac table. For MH PE ESI 278 must be configured per IFD/Interface. Using RT(traffic generator) to 279 send the traffic to the routers. 281 Measurement: 283 The DUT mac table must learn the 100,000 measure the time taken to 284 learn the 100,000 mac address from remote peers. 286 5.1.3. To check the time taken to flush the local entry due to CE link 287 failure 289 Objective: 291 Send 100,000 frames with different SA and DA to DUT from CE using 292 traffic generator. Then wait to learn all 100,000 mac address. Then 293 fail the DUT CE link and measure the time taken to flush these 294 100,000 routes from the mac table. 296 Procedure: 298 Configure PBB-EVPN EVI in R1,MHPE2,DUT. All 4 routers except CE are 299 running mpls,bgp,RR is acting as route reflector to R1,MHPE2 and DUT. 300 Once the bgp comes up check the DUT mac table. For MH PE ESI must 301 be configured per IFD/Interface. Using RT(traffic generator) to send 302 the traffic to the routers. 304 Measurement: 306 The DUT mac table must learn the 100,000 measure the time taken for 307 flushing these 100,000 mac address. 309 5.1.4. To check the time taken by DUT to flush 100,000 routes learned 310 from remote PE after R1 traffic generator link failure 312 Objective: 314 Send 100,000 frames with different SA and DA to DUT from R1 using 315 traffic generator. Bring down the link between R1 and traffic 316 generator. Then measure the time taken to flush the DUT mac address 317 table. 319 Procedure: 321 Configure PBB-EVPN EVI in R1,MHPE2,DUT. All 4 routers except CE are 322 running mpls,bgp,RR is acting as route reflector to R1,MHPE2 and 323 DUT.Once the bgp comes up check the DUT mac table.For MH PE ESI must 324 be configured per IFD/Interface. Using RT(traffic generator) to send 325 the traffic to the routers. 327 Measurement: 329 Measure the time taken to flush 100,000 remote routes from mac table 330 of DUT. 332 5.1.5. To measure the mac ageing time. 334 Objective: 336 Send 100,000 frames with different SA and DA to DUT from CE using 337 traffic generator. Then wait to learn all 100,000 mac address. Then 338 stop the traffic.Wait to see how long it takes to flush these mac 339 entries due to ageing. 341 Procedure: 343 Configure PBB-EVPN EVI in R1,MHPE2,DUT. All 4 routers except CE are 344 running mpls,bgp,RR is acting as route reflector to R1,MHPE2 and 345 DUT.Once the bgp comes up check the DUT mac table. For MH PE ESI 346 must be configured per IFD/Interface. Using RT(traffic generator) to 347 send the traffic to the routers. 349 Measurement: 351 The DUT mac table must learn the 100,000 measure the time taken for 352 flushing these 100,000 mac address due to ageing. 354 5.1.6. To check the time taken by DUT to age from remote PE after 355 stopping the traffic at remote PE. 357 Objective: 359 Send 100,000 frames with different SA and DA to DUT from R1 using 360 traffic generator.After stopping the traffic at remote PE(R1) traffic 361 generator.Measure the time taken to remove these macs from DUT mac 362 table. 364 Procedure: 366 Configure PBB-EVPN EVI in R1,MHPE2,DUT.All 4 routers except CE are 367 running mpls,bgp,RR is acting as route reflector to R1,MHPE2 and 368 DUT.Once the bgp comes up check the DUT mac table.For MH PE ESI must 369 be configured per IFD/Interface. Using RT(traffic generator) to send 370 the traffic to the routers. 372 Measurement: 374 Measure the time taken to flush 100,000 remote macs from mac table of 375 DUT due to ageing. 377 5.2. Convergence 379 The following tests are executed to measure the convergence time in 380 case of an event or by lerning the mac without any external trigger. 382 5.2.1. To check the time taken by DUT to learn 100,000 macs from 383 local and 100,000 from remote and measure the time of flood from 384 DUT. 386 Objective: 388 Send 100,000 frames with different SA and DA to DUT from R1 using 389 traffic generator. Send 100,000 frames with different SA and DA from 390 traffic generator connected to CE. The SA and DA of flows must be 391 complimentary to have unicast flows. Measure the time taken by the 392 DUT to learn 200,000 in mac table.Measure the flood time period of 393 DUT. 395 Procedure: 397 Configure PBB-EVPN EVI in R1,MHPE2,DUT.All 4 routers except CE are 398 running mpls,bgp,RR is acting as route reflector to R1,MHPE2 and 399 DUT.Once the bgp comes up check the DUT evpn table. For MH PE ESI 400 must be configured per IFD/Interface. Using RT(traffic generator) to 401 send the traffic to the routers. 403 Measurement: 405 Measure the time taken to learn 200,000 mac address table in DUT. 406 and measure the flood time of DUT. 408 5.2.2. To measure the time taken to elect a new DF by adding a a MHPE. 410 Objective: 412 Send 100,000 frames from CE to DUT from traffic generator with 413 different SA and DA. Wait to learn all 100,000 mac address. Then 414 add R1 to the same Ethernet segment by configuring the same ESI value 415 configured in DUT,MHPE2 in IFD. Then the new DF election take place 416 during that time there should not be any loop and measure the time 417 taken to come up the new DF.Measure the time taken to elect the new 418 DF. 420 Procedure: 422 Configure PBB-EVPN EVI in R1,MHPE2,DUT.All 4 routers except CE are 423 running mpls,bgp,RR is acting as route reflector to R1,MHPE2 and 424 DUT.Once the bgp comes up check the DUT evpn table. For MH PE ESI 425 must be configured per IFD/Interface. Using RT(traffic generator) to 426 send the traffic to the routers. 428 Measurement: 430 Measure the time taken for new DF election in DUT and there should 431 not be any loop or forwarding the BUM traffic back to the same 432 segment. 434 5.3. Reliability 436 These tests are conducted to check after an event there wont be any 437 change in functionality. 439 5.3.1. To check the whether there is traffic loss due to routing engine 440 failover for redundancy test. 442 Objective: 444 Send 100,000 frames from CE to DUT from traffic generator with 445 different SA and DA. Send 100,000 frames from traffic generator to 446 R1 with different SA and DA so that 200,000 mac address will be 447 learned in DUT. There is a bi directional traffic flow with 100,000 448 pps in each direction. Then do a routing engine failover. 449 Procedure: 451 Configure PBB-EVPN EVI in R1,MHPE2,DUT.All 4 routers except CE are 452 running mpls,bgp,RR is acting as route reflector to R1,MHPE2 and 453 DUT.Once the bgp comes up check the DUT evpn table.For MH PE ESI must 454 be configured per IFD/Interface. Using RT(traffic generator) to send 455 the traffic to the routers. 457 Measurement: 459 There should not be any traffic loss,No change in the DF role. No 460 withdraw of any routes. 462 5.3.2. To check the whether DF election is taking place properly after 463 the one of the MH PE reboot. 465 Objective: 467 Send 100,000 frames from CE to DUT from traffic generator with 468 different SA and DA. Send 100,000 frames from traffic generator to 469 R1 with different SA and DA so that 200,000 mac address will be 470 learned in DUT. There is a bi directional traffic flow with 100,000 471 pps in each direction. Then reboot DUT since there are 2 MH PE's the 472 other PE will become the DF then after DUT comes back, then DF 473 election has to re initiate. 475 Procedure: 477 Configure PBB-EVPN EVI in R1,MHPE2,DUT.All 4 routers except CE are 478 running mpls,bgp,RR is acting as route reflector to R1,MHPE2 and 479 DUT.Once the bgp comes up check the DUT evpn table.For MH PE ESI must 480 be configured per IFD/Interface. Using RT(traffic generator) to send 481 the traffic to the routers. 483 Measurement 485 The DF election has to take place again once the DUT comes back 486 online.There should not be any DF stuck casefor 100 PBB-EVPN 487 instances. 489 5.4. Scale 491 5.4.1. To Scale the DUT to 4k PBB-EVPN instances and clear bgp in DUT 492 without traffic. 494 Objective: 496 The main purpose of the test the DUT performance to scale 4k PBB-EVPN 497 instances. Then clear bgp neighbor. There should not be any loss of 498 routes or any crashes. 500 Procedure: 502 Configure PBB-EVPN instances in R1,MHPE2,DUT.All 4 routers except CE 503 are running mpls,bgp,RR is acting as route reflector to R1,MHPE2 and 504 DUT.Once the bgp comes up check the DUT evpn table.For MH PE ESI must 505 be configured per IFD/Interface. Using RT(traffic generator) to send 506 the traffic to the routers. 508 Measurement 510 There should not be any loss of route types 2,3 and 4 in DUT. 512 5.4.2. To Scale the DUT to 4k PBB-EVPN instances and clear bgp in DUT 513 with traffic. Measure the convergence time 515 Objective: 517 The main purpose of the test the DUT performance to scale 4k pbb-evpn 518 instances with traffic.Then clear bgp neighbor.There should not be 519 any loss of routes or any crashes. Send 100,000 frames from CE to 520 DUT from traffic generator with different SA and DA for 5 pbb-evpn 521 instances.Send 100,000 frames from traffic generator to R1 with 522 different SA and DA for 5 pbb-evpn instances.so that 1,000,000 mac 523 address will be learned in DUT. There is a bi directional traffic 524 flow with 500,000 pps in each direction. Then clear the bgp nei in 525 DUT after the bgp comes up and started learning the routes, measure 526 the time taken to learn all 1,000,000 macs in DUT. 528 Procedure: 530 Configure PBB-EVPN instances in R1,MHPE2,DUT.All 4 routers except CE 531 are running mpls,bgp,RR is acting as route reflector to R1,MHPE2 and 532 DUT.Once the bgp comes up check the DUT evpn table.For MH PE ESI must 533 be configured per IFD/Interface. Using RT(traffic generator) to send 534 the traffic to the routers. 536 Measurement: 538 The DUT must learn all 1,000,000 mac address.Measure the time taken 539 to learn 1,000,000 mac in DUT, measure the flood traffic time "T" of 540 DUT 542 5.5. Soak Test 543 5.5.1. To Scale the DUT to 4k PBB-EVPN instances in DUT with traffic 544 and run the set up for 24hrs 546 Objective: 548 Configure PBB-EVPN instances in R1,MHPE2,DUT.All 4 routers except CE 549 are running mpls,bgp,RR is acting as route reflector to R1,MHPE2 and 550 DUT.Once the bgp comes up check the DUT evpn table.For MH PE ESI must 551 be configured per IFD/Interface. Using RT(traffic generator) to send 552 the traffic to the routers. 554 Procedure: 556 Measurement: 558 Take the hourly reading of CPU,process memory.There should not be any 559 leak,crashes,CPU spikes. 561 6. Acknowledgements 563 We would like to thank Al Morton of (ATT) for their support and 564 encouragement. We would like to thank Fioccola Giuseppe of Telecom 565 Italia reviewing our draft and commenting it. 567 7. IANA Considerations 569 This memo includes no request to IANA. 571 8. Security Considerations 573 There is no additional consideration from RFC 6192. 575 9. References 577 9.1. Normative References 579 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 580 Requirement Levels", BCP 14, RFC 2119, 581 DOI 10.17487/RFC2119, March 1997, 582 . 584 [RFC2544] Bradner, S. and J. McQuaid, "Benchmarking Methodology for 585 Network Interconnect Devices", RFC 2544, 586 DOI 10.17487/RFC2544, March 1999, 587 . 589 9.2. Informative References 591 [RFC7432] Sajassi, A., Ed., Aggarwal, R., Bitar, N., Isaac, A., 592 Uttaro, J., Drake, J., and W. Henderickx, "BGP MPLS-Based 593 Ethernet VPN", RFC 7432, DOI 10.17487/RFC7432, February 594 2015, . 596 Appendix A. Appendix 598 Authors' Addresses 600 Sudhin Jacob (editor) 601 Juniper Networks 602 Bangalore 603 India 605 Phone: +91 8061212543 606 Email: sjacob@juniper.net 608 Kishore Tiruveedhula 609 Juniper Networks 610 10 Technology Park Dr 611 Westford, MA 01886 612 USA 614 Phone: +1 9785898861 615 Email: kishoret@juniper.net