Benchmarking Methodology for EVPN VPWS
draft-kishjac-bmwg-evpnvpwstest-00

Document Type Active Internet-Draft (individual)
Last updated 2018-10-08
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Internet Engineering Task Force                            S. Jacob, Ed.
Internet-Draft                                           K. Tiruveedhula
Intended status:Informational                            Juniper Networks
Expires: April 11, 2019                                  October 8, 2018

                 Benchmarking Methodology for EVPN VPWS
                   draft-kishjac-bmwg-evpnvpwstest-00

Abstract

   This document defines methodologies for benchmarking EVPN-VPWS
   performance.  EVPN-VPWS is defined in RFC 8214, and is being deployed
   in Service Provider networks.  Specifically this document defines the
   methodologies for benchmarking EVPN-VPWS Scale convergence,
   Scale,Core isolation, high availability and longevity.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on April 11, 2019.

Copyright Notice

   Copyright (c) 2018 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Jacob & Tiruveedhula     Expires April 11, 2019                 [Page 1]
Internet-Draft     EVPN-VPWS Benchmarking Methodology       October 2018

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
     1.2.  Terminologies . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Test Topology . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Test Cases  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     3.1.  How long it takes to switch from primary to backup during
           local link failure  . . . . . . . . . . . . . . . . . . .   7
     3.2.  How long it takes to remote PE to switch traffic from
           primary to back up path during link failure in CE . . . .   8
     3.3.  How long it takes to remote PE to switch traffic from
           primary to back up path during core failure . . . . . . .   8
     3.4.  How long it takes to primary PE to regain control after
           the local link flap . . . . . . . . . . . . . . . . . . .   9
   4.  Activate/deactivate AC's  . . . . . . . . . . . . . . . . . .  10
     4.1.  To Add  M number of attachment circuits.  . . . . . . . .  10
     4.2.  Deactivate/Activate M number of attachment circuits.  . .  10
   5.  Scale Convergence . . . . . . . . . . . . . . . . . . . . . .  11
     5.1.  To Record the whether there is traffic loss due to
           routing engine failover for redundancy test.  . . . . . .  11
   6.  High Availability . . . . . . . . . . . . . . . . . . . . . .  11
     6.1.  To Record the whether there is traffic loss due to
           routing engine failover for redundancy test.  . . . . . .  12
   7.  SOAK Test . . . . . . . . . . . . . . . . . . . . . . . . . .  12
     7.1.  To Measure the stability of the DUT with scale and
           traffic.  . . . . . . . . . . . . . . . . . . . . . . . .  12
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  13
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  13
   10. Security Considerations . . . . . . . . . . . . . . . . . . .  13
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .  13
     11.1.  Normative References . . . . . . . . . . . . . . . . . .  13
     11.2.  Informative References . . . . . . . . . . . . . . . . .  13
   Appendix A.  Appendix . . . . . . . . . . . . . . . . . . . . . .  14
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  14

1.  Introduction

   EVPN-VPWS is defined in RFC 8214,discusses how VPWS can be combined
   with EVPNs to provide a new/combined solution.  This draft defines
   methodologies that can be used to benchmark RFC 8214 solutions.
   Further, this draft provides methodologies for benchmarking the
   performance of EVPN VPWS Scale,Scale Convergence, Core isolation,
Show full document text