idnits 2.17.1 draft-vikjac-bmwg-evpnmultest-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 : ---------------------------------------------------------------------------- ** There are 19 instances of too long lines in the document, the longest one being 15 characters in excess of 72. 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 (February 4, 2019) is 1901 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 632, but no explicit reference was found in the text == Unused Reference: 'RFC2899' is defined on line 637, but no explicit reference was found in the text == Unused Reference: 'RFC7432' is defined on line 643, but no explicit reference was found in the text ** Downref: Normative reference to an Informational RFC: RFC 2544 ** Downref: Normative reference to an Informational RFC: RFC 2899 Summary: 3 errors (**), 0 flaws (~~), 5 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 V. Nagarajan 4 Intended status: Standards Track Juniper Networks 5 Expires: August 8, 2019 February 4, 2019 7 Benchmarking Methodology for EVPN Multicasting 8 draft-vikjac-bmwg-evpnmultest-00 10 Abstract 12 This document defines methodologies for benchmarking IGMP proxy 13 performance over EVPN-VXLAN. IGMP proxy over EVPN is defined in 14 draft-ietf-bess-evpn-igmp-mld-proxy-02, and is being deployed in data 15 center networks. Specifically this document defines the 16 methodologies for benchmarking IGMP proxy convergence, leave latency 17 Scale,Core isolation, high availability and longevity. 19 Status of This Memo 21 This Internet-Draft is submitted in full conformance with the 22 provisions of BCP 78 and BCP 79. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF). Note that other groups may also distribute 26 working documents as Internet-Drafts. The list of current Internet- 27 Drafts is at https://datatracker.ietf.org/drafts/current/. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 This Internet-Draft will expire on August 8, 2019. 36 Copyright Notice 38 Copyright (c) 2019 IETF Trust and the persons identified as the 39 document authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal 42 Provisions Relating to IETF Documents 43 (https://trustee.ietf.org/license-info) in effect on the date of 44 publication of this document. Please review these documents 45 carefully, as they describe your rights and restrictions with respect 46 to this document. Code Components extracted from this document must 47 include Simplified BSD License text as described in Section 4.e of 48 the Trust Legal Provisions and are provided without warranty as 49 described in the Simplified BSD License. 51 Table of Contents 53 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 54 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3 55 1.2. Terminologies . . . . . . . . . . . . . . . . . . . . . . 3 56 2. Test Topology . . . . . . . . . . . . . . . . . . . . . . . . 3 57 3. Test Cases . . . . . . . . . . . . . . . . . . . . . . . . . 5 58 3.1. How long it takes to learn ( X1...Xn) IGMP join messages 59 in DUT . . . . . . . . . . . . . . . . . . . . . . . . . 5 60 3.2. How long it takes to clear the (*,G) entries in the DUT . 6 61 3.3. How long it takes the DUT to stop forwarding the 62 traffic(Measuring the leave latency) . . . . . . . . . . 6 63 3.4. How long it takes to learn (X1...Xn) IGMP join messages 64 for N vlans in DUT . . . . . . . . . . . . . . . . . . . 7 65 3.5. How long it takes to clear the (*,G) entries in the DUT 66 for N vlans . . . . . . . . . . . . . . . . . . . . . . . 8 67 3.6. How long it takes the DUT to stop forwarding the traffic 68 for N vlans(Measuring the leave latency) . . . . . . . . 8 69 3.7. How long it takes to learn (X1...Xn) IGMP join messages 70 for N vlans in DUT working EVPN AA mode . . . . . . . . . 9 71 3.8. How long it takes to clear the (*,G) entries for N vlans 72 in DUT working EVPN AA . . . . . . . . . . . . . . . . . 10 73 3.9. How long it takes the DUT operating in EVPN AA to stop 74 forwarding the traffic for N vlans(Measuring the leave 75 latency) . . . . . . . . . . . . . . . . . . . . . . . . 10 76 4. Link Flap . . . . . . . . . . . . . . . . . . . . . . . . . . 11 77 4.1. To Measure the multicast packet loss in EVPN AA scenario 78 on a CE link failure . . . . . . . . . . . . . . . . . . 11 79 5. Scale Convergence . . . . . . . . . . . . . . . . . . . . . . 12 80 5.1. To measure the packet loss during the core link failure. 12 81 6. High Availability . . . . . . . . . . . . . . . . . . . . . . 12 82 6.1. To Record the whether there is traffic loss due to 83 routing engine failover for redundancy test. . . . . . . 12 84 7. SOAK Test . . . . . . . . . . . . . . . . . . . . . . . . . . 13 85 7.1. To Measure the stability of the DUT with scale and 86 traffic. . . . . . . . . . . . . . . . . . . . . . . . . 13 87 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 14 88 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 89 10. Security Considerations . . . . . . . . . . . . . . . . . . . 14 90 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 14 91 11.1. Normative References . . . . . . . . . . . . . . . . . . 14 92 11.2. Informative References . . . . . . . . . . . . . . . . . 14 93 Appendix A. Appendix . . . . . . . . . . . . . . . . . . . . . . 14 94 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14 96 1. Introduction 98 IGMP proxy over EVPN-VXLAN is defined in draft-ietf-bess-evpn-igmp- 99 mld-proxy-02,and is being deployed in data center networks. 100 Specifically this document defines the methodologies for benchmarking 101 IGMP proxy convergence,leave latency Scale,Core isolation, high 102 availability and longevity. 104 1.1. Requirements Language 106 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 107 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 108 document are to be interpreted as described in RFC 2119 [RFC2119]. 110 1.2. Terminologies 112 Leaf A layer 2 or layer 3 capable device 114 Spine layer 3 capable device which is used to inter connect leaves 116 CE Customer Router/Devices/Switch. 118 AA EVPN Terminologies AA All-Active. 120 AC Attachment Circuit 122 RT Router Tester. 124 DUT Device under Test. 126 Sub Interface Each physical Interfaces is subdivided in to Logical 127 units. 129 EVI EVPN Instances which will be running on sub interface or physical 130 port of the provider Edge routers. 132 DF Designated Forwarder. 134 ESI Ethernet Segment Identifier. 136 2. Test Topology 138 EVPN Overlay Network running on leaf1, leaf2 leaf3,spine1 and spine 2 139 : 141 Topology Diagram 142 RT 143 +--------------+ +--------------+ 144 RT | | | +-------------------+ 145 +---------+ spine1 +----------------------------------+ 146 | | | spine2 | | 147 | | | | | 148 +----+---------+---------+ +----+----+----+------------------+ 149 | | | | | | 150 | | | | | | 151 | | | | | | 152 | | | | | | 153 | | | | | | 154 RT +---------+-----+---------+---+-------+----++ +--+-----------+----+ 155 +-------------+ | | | | leaf3 | 156 ++ leaf1 | | leaf2 | | | 157 | DUT | | | | | 158 +----+----------+ +---+--------+----+ +--------+----------+ 159 | | | | 160 | | | | 161 | | | | 162 | | | | 163 +-+-----------------+------+ | | 164 | | +--+ RT ++ RT 165 | CE | RT 166 | +-------+ 167 +-------------------+ 168 CE connected to leaf1 and leaf2 in EVPN AA mode. 170 Topology 1 172 Topology Diagram 174 Figure 1 176 There are six routers in the topology. Leaf1,leaf2, 177 leaf3,spine1,spine2 emulating a data center network. CE is a 178 customer device connected to leaf1 and leaf2, it is configured with 179 bridge domains in different vlans. The router tester is connected to 180 CE,leaf1,leaf2,leaf3,spine1 and spine 2 to emulate multicast source 181 and host generating igmp join/leave. 183 All routers except CE are configured with EBGP for the underlay 185 All router are configured with EVPN-VXLAN overlay 187 All leaves and spine must be configured "N" EVPN-VXLAN instances 188 depends up on the cases. 190 Leaf1 and Leaf2 must be configured with ESI per vlan or ESI on IFD. 192 Leaf1 and leaf2 are running Active Active mode of EVPN-VXLAN. 194 CE is acting as bridge configured with vlans 196 Depends up on the test multicast traffic/host will be emulated by RT 198 The above configuration will serve as base configuration for all the 199 test cases. 201 3. Test Cases 203 The following tests are conducted to measure the learning rate,leave 204 rate,leave latency of IGMP messages which propagates in leaf and 205 spine. 207 3.1. How long it takes to learn ( X1...Xn) IGMP join messages in DUT 209 Objective: 211 To Record the time taken to learn X1...Xn igmp join generated by 212 host/hosts. 214 Topology : Topology 1 216 Procedure: 218 Configure "N" evpn-vxlan in leaf1,leaf2,leaf3,spine1 and spine2.Leaf1 219 and leaf2 are connected to CE which are working in EVPN AA mode. 220 Configure a vlan in RT which is present in leaf1 then send igmp join 221 messages for groups X1... Xn from RT to this vlan present in leaf1. 222 Measure the time taken to learn X1..Xn (*,G) entries in the DUT. 224 Measurement : 226 Measure the time taken to learn the X1....Xn groups creating (*,G) 227 entries in the DUT. 229 Repeat these test and plot the data. The test is repeated for "N" 230 times and the values are collected. The time is calculated by 231 averaging the values obtained from "N" samples. 233 Time taken by DUT to learn and create X1...Xn (*,G ) entries in DUT 234 which is measured in sec = (T1+T2+..Tn/N) 236 3.2. How long it takes to clear the (*,G) entries in the DUT 238 Objective: 240 To Record the time taken to clear the X1... Xn (*,G) entries in DUT. 242 Topology : Topology 1 244 Procedure: 246 Configure "N" evpn-vxlan in leaf1,leaf2,leaf3,spine1 and spine2. 247 Leaf1 and leaf2 are connected to CE which are working in EVPN AA 248 mode. Configure a vlan in RT which is present in leaf1, then send 249 igmp join messages for groups ranging from X1...Xn from RT to this 250 vlan present in leaf1 Then stop these igmp join messages from RT. 252 Measurement : 254 Measure the time taken to flush these X1...Xn (*,G) entries in DUT. 256 Repeat these test and plot the data. The test is repeated for "N" 257 times and the values are collected. The time is calculated by 258 averaging the values obtained from "N" samples. 260 Time taken by DUT to flush these X1...Xn (*,G) entries in sec = 261 (T1+T2+..Tn/N) 263 3.3. How long it takes the DUT to stop forwarding the traffic(Measuring 264 the leave latency) 266 Objective: 268 To Record the time taken by the DUT to stop forwarding the multicast 269 traffic during the receipt of IGMP leave from RT. 271 Topology : Topology 1 273 Procedure: 275 Configure "N" evpn-vxlan in leaf1,leaf2,leaf3,spine1 and spine2. 276 Leaf1 and leaf2 are connected to CE which are working in EVPN AA 277 mode. Configure a vlan in RT which is present in leaf1, then send 278 igmp join from RT for this vlan to leaf1 for groups ranging from 279 "X1....Xn". Then send traffic to these groups from spine1. Traffic 280 flows from spine1 to leaf1. Send IGMP leave messages for these 281 groups from RT to leaf1. Measure the time taken by the DUT to stop 282 these multicast traffic to RT. 284 Measurement : 286 Measure the time taken by DUT to stop the multicast traffic flowing 287 towards RT. 289 Repeat these test and plot the data. The test is repeated for "N" 290 times and the values are collected. The time is calculated by 291 averaging the values obtained from "N" samples. 293 Time taken by DUT to stop the traffic towards RT connected in leaf1 294 in sec = (T1+T2+..Tn/N) 296 3.4. How long it takes to learn (X1...Xn) IGMP join messages for N 297 vlans in DUT 299 Objective: 301 To Record the time taken to learn X1...Xn IGMP join generated by 302 host/hosts located in N vlans. 304 Topology : Topology 1 306 Procedure: 308 Configure "N" evpn-vxlan in leaf1,leaf2,leaf3,spine1 and spine2. 309 Leaf1 and leaf2 are connected to CE which are working in EVPN AA 310 mode. Configure N vlans in RT, these vlans must be present in leaf1, 311 then send igmp join messages for the groups ranging from X1...Xn for 312 these N vlans from RT. Measure the time taken to learn these X1..Xn 313 (*,G) entries in the DUT for N vlans. 315 Measurement : 317 Measure the time taken to learn the X1....Xn groups creating (*,G) 318 entries in the DUT for N vlans. 320 Repeat these test and plot the data. The test is repeated for "N" 321 times and the values are collected. The time is calculated by 322 averaging the values obtained from "N" samples. 324 Time taken by DUT to learn and create X1...Xn (*,G ) entries for N 325 vlans in DUT which is measured in sec = (T1+T2+..Tn/N) 327 3.5. How long it takes to clear the (*,G) entries in the DUT for N 328 vlans 330 Objective: 332 To Record the time taken to clear the X1... Xn (*,G) entries in DUT 333 for N vlans. 335 Topology : Topology 1 337 Procedure: 339 Configure "N" evpn-vxlan in leaf1,leaf2,leaf3,spine1 and spine2. 340 Leaf1 and leaf2 are connected to CE which are working in AA mode. 341 Configure N vlans in RT, these vlans must be present in leaf1, then 342 send igmp join messages for groups ranging from X1...Xn for these N 343 vlans from RT. Then stop these IGMP messages. 345 Measurement : 347 Measure the time taken to flush these X1...Xn (*,G) entries in DUT. 349 Repeat these test and plot the data. The test is repeated for "N" 350 times and the values are collected. The time is calculated by 351 averaging the values obtained from "N" samples. 353 Time taken by DUT to flush these X1...Xn (*,G) entries in sec = 354 (T1+T2+..Tn/N) 356 3.6. How long it takes the DUT to stop forwarding the traffic for N 357 vlans(Measuring the leave latency) 359 Objective: 361 To Record the time taken by the DUT to stop forwarding the multicast 362 traffic to N vlans during the receipt of IGMP leave messages from RT. 364 Topology : Topology 1 366 Procedure: 368 Configure "N" evpn-vxlan in leaf1,leaf2,leaf3,spine1 and spine2.Leaf1 369 and leaf2 are connected to CE which are working in EVPN AA mode. 370 Configure N vlans in RT which are present in leaf1, then send igmp 371 join messages from RT for groups ranging from X1...Xn to these vlans 372 present in leaf1. Then send traffic to these groups from spine1. 373 Traffic flows from spine1 to leaf1. Send the IGMP leave messages for 374 these groups in all vlans. Measure the time taken by the DUT to stop 375 the traffic for these group flowing towards RT. 377 Measurement : 379 Measure the time taken by DUT to stop the multicast traffic flowing 380 towards RT. 382 Repeat these test and plot the data. The test is repeated for "N" 383 times and the values are collected. The time is calculated by 384 averaging the values obtained from "N" samples. 386 Time taken by DUT to stop the traffic towards RT in sec = 387 (T1+T2+..Tn/N) 389 3.7. How long it takes to learn (X1...Xn) IGMP join messages for N 390 vlans in DUT working EVPN AA mode 392 Objective: 394 To Record the time taken to learn X1...Xn IGMP join generated by 395 host/hosts located in N vlans in DUT operating in EVPN AA mode. 397 Topology : Topology 1 399 Procedure: 401 Configure "N" evpn-vxlan in leaf1,leaf2,leaf3,spine1 and spine2. 402 Leaf1 and leaf2 are connected to CE which are working in EVPN AA 403 mode. Configure N vlans in RT, these vlans must be present in 404 leaf1,leaf2, then send igmp join messages for the groups ranging from 405 X1...Xn for these N vlans from RT to CE connected to leaf1 and leaf2 406 working EVPN AA mode.Measure the time taken to learn these X1..Xn 407 (*,G) entries in the DUT for N vlans. 409 Measurement : 411 Measure the time taken to learn the X1....Xn groups by creating (*,G) 412 entries in the DUT for N vlans. 414 Repeat these test and plot the data. The test is repeated for "N" 415 times and the values are collected. The time is calculated by 416 averaging the values obtained from "N" samples. 418 Time taken by DUT to learn and create X1...Xn (*,G ) entries for N 419 vlans which is measured in sec = (T1+T2+..Tn/N) 421 3.8. How long it takes to clear the (*,G) entries for N vlans in DUT 422 working EVPN AA 424 Objective: 426 To Record the time taken to clear the X1... Xn (*,G) entries in DUT 427 for N vlans. 429 Topology : Topology 1 431 Procedure: 433 Configure "N" evpn-vxlan in leaf1,leaf2,leaf3,spine1 and spine2. 434 Leaf1 and leaf2 are connected to CE which are working in AA mode. 435 Configure N vlans in RT, these vlans must be present in leaf1, then 436 send igmp join messages for groups ranging from X1...Xn for these N 437 vlans from RT to CE which is connected to leaf1 and leaf2 working in 438 EVPN AA mode.Then stop these IGMP messages. 440 Measurement : 442 Measure the time taken to flush these X1...Xn (*,G) entries in DUT. 444 Repeat these test and plot the data. The test is repeated for "N" 445 times and the values are collected. The time is calculated by 446 averaging the values obtained from "N" samples. 448 Time taken by DUT to flush these X1...Xn (*,G) entries in sec = 449 (T1+T2+..Tn/N) 451 3.9. How long it takes the DUT operating in EVPN AA to stop forwarding 452 the traffic for N vlans(Measuring the leave latency) 454 Objective: 456 To Record the time taken by the DUT to stop forwarding the multicast 457 traffic to N vlans during the receipt of IGMP leave messages from RT. 459 Topology : Topology 1 461 Procedure: 463 Configure "N" evpn-vxlan in leaf1,leaf2,leaf3,spine1 and spine2.Leaf1 464 and leaf2 are connected to CE which are working in EVPN AA mode. 465 Configure N vlans in RT which are present in leaf1, then send igmp 466 join messages from RT connected to CE for groups ranging from X1...Xn 467 to these vlans. The CE in turn forwards the igmp messages to leaf1 468 and leaf2 operating in EVPN AA mode. Then send traffic to these 469 groups from spine1. Traffic flows from spine1 to CE. Send the IGMP 470 leave messages for these groups in all vlans from RT connected to CE. 471 Measure the time taken by the DUT to stop the traffic for these group 472 flowing towards RT. 474 Measurement : 476 Measure the time taken by DUT to stop the multicast traffic flowing 477 towards RT. 479 Repeat these test and plot the data. The test is repeated for "N" 480 times and the values are collected. The time is calculated by 481 averaging the values obtained from "N" samples. 483 Time taken by DUT to stop the traffic towards RT in sec = 484 (T1+T2+..Tn/N) 486 4. Link Flap 488 4.1. To Measure the multicast packet loss in EVPN AA scenario on a CE 489 link failure 491 Objective: 493 To measure the packet loss during the CE to DF link failure. 495 Topology : Topology 1 497 Procedure: 499 Configure "N" evpn-vxlan in leaf1,leaf2,leaf3,spine1 and spine2.Leaf1 500 and leaf2 are connected to CE which are working in EVPN AA mode. 501 Configure N vlans in RT which are present in leaf1, then send igmp 502 join messages from RT connected to CE for groups ranging from X1...Xn 503 to these vlans. The CE in turn forwards the igmp messages to leaf1 504 and leaf2 operating in EVPN AA mode. Then send traffic to these 505 groups from spine1. Traffic flows from spine1 to CE. Fail the DF-CE 506 link. The NON DF now will act as DF and start forwarding the 507 multicast traffic. 509 Measurement : 511 Measure the multicast packet loss during the link failure.Repeat the 512 test "N" times and plot the data.The packet loss is calculated by 513 averaging the values obtained from "N" samples. 515 Packet loss in sec = (T1+T2+..Tn/N) 517 5. Scale Convergence 519 5.1. To measure the packet loss during the core link failure. 521 Objective: 523 To Measure the convergence at a higher number of vlans and igmp 524 joins. 526 Topology : Topology 1 528 Procedure: 530 Configure "N" evpn-vxlan in leaf1,leaf2,leaf3,spine1 and spine2.Leaf1 531 and leaf2 are connected to CE which are working in EVPN AA mode. 532 Configure N vlans in RT which are present in leaf1, then send igmp 533 join messages from RT connected to CE for groups ranging from X1...Xn 534 to these vlans. The CE in turn forwards the igmp messages to leaf1 535 and leaf2 operating in EVPN AA mode. Then send traffic to these 536 groups from spine1. Traffic flows from spine1 to CE. Fail the core 537 link of DF. The NON DF now will act as DF and start forwarding the 538 multicast traffic. The vlans and the multicast groups must be a 539 higher value of N taken at random. 541 Measurement : 543 Measure the packet loss in seconds once the core link is 544 restored.Repeat the test "N" times and plot the data.The packet loss 545 is calculated by averaging the values obtained from "N" samples. 547 Packet loss in sec = (T1+T2+..Tn/N) 549 6. High Availability 551 6.1. To Record the whether there is traffic loss due to routing engine 552 failover for redundancy test. 554 Objective: 556 To record traffic loss during routing engine failover. 558 Topology : Topology 3 560 Procedure: 562 Configure "N" evpn-vxlan in leaf1,leaf2,leaf3,spine1 and spine2.Leaf1 563 and leaf2 are connected to CE which are working in EVPN AA mode. 564 Configure N vlans in RT which are present in leaf1, then send igmp 565 join messages from RT connected to CE for groups ranging from X1...Xn 566 to these vlans. The CE in turn forwards the igmp messages to leaf1 567 and leaf2 operating in EVPN AA mode. Then send traffic to these 568 groups from spine1. Traffic flows from spine1 to CE. Then perform a 569 routing engine failure. 571 Measurement : 573 There should be 0 traffic loss which is the ideal case, No change in 574 the DF role. DUT should not withdraw any routes.Repeat the test "N" 575 times and plot the data.The packet loss is calculated by averaging 576 the values obtained from "N" samples. 578 Packet loss in sec = (T1+T2+..Tn/N) 580 7. SOAK Test 582 This is measuring the performance of DUT running with scaled 583 configuration with traffic over a peroid of time "T'". In each 584 interval "t1" the parameters measured are CPU usage, memory usage, 585 crashes. 587 7.1. To Measure the stability of the DUT with scale and traffic. 589 Objective: 591 To measure the stability of the DUT in a scaled environment with 592 traffic. 594 Topology : Topology 3 596 Procedure: 598 Configure "N" evpn-vxlan in leaf1,leaf2,leaf3,spine1 and spine2.Leaf1 599 and leaf2 are connected to CE which are working in EVPN AA mode. 600 Configure N vlans in RT which are present in leaf1, then send igmp 601 join messages from RT connected to CE for groups ranging from X1...Xn 602 to these vlans. The CE in turn forwards the igmp messages to leaf1 603 and leaf2 operating in EVPN AA mode. Then send traffic to these 604 groups from spine1. Traffic flows from spine1 to CE. 606 Measurement : 608 Take the hourly reading of CPU, process memory. There should not be 609 any leak, crashes, CPU spikes. 611 8. Acknowledgements 613 We would like to thank Al and Sarah for the support. 615 9. IANA Considerations 617 This memo includes no request to IANA. 619 10. Security Considerations 621 There is no additional consideration from RFC 6192. 623 11. References 625 11.1. Normative References 627 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 628 Requirement Levels", BCP 14, RFC 2119, 629 DOI 10.17487/RFC2119, March 1997, 630 . 632 [RFC2544] Bradner, S. and J. McQuaid, "Benchmarking Methodology for 633 Network Interconnect Devices", RFC 2544, 634 DOI 10.17487/RFC2544, March 1999, 635 . 637 [RFC2899] Ginoza, S., "Request for Comments Summary RFC Numbers 638 2800-2899", RFC 2899, DOI 10.17487/RFC2899, May 2001, 639 . 641 11.2. Informative References 643 [RFC7432] Sajassi, A., Ed., Aggarwal, R., Bitar, N., Isaac, A., 644 Uttaro, J., Drake, J., and W. Henderickx, "BGP MPLS-Based 645 Ethernet VPN", RFC 7432, DOI 10.17487/RFC7432, February 646 2015, . 648 Appendix A. Appendix 650 Authors' Addresses 651 Sudhin Jacob (editor) 652 Juniper Networks 653 Bangalore, Karnataka 560103 654 India 656 Phone: +91 8061212543 657 Email: sjacob@juniper.net 659 Vikram Nagarajan 660 Juniper Networks 661 Bangalore, Karnataka 560103 662 India 664 Phone: +91 8061212543 665 Email: vikramna@juniper.net