Re: [bmwg] REG: draft-morton-bmwg-multihome-evpn/

"MORTON, ALFRED C (AL)" <> Tue, 02 July 2019 20:25 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id C29A61206CB for <>; Tue, 2 Jul 2019 13:25:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id GFjgsS4yGeDz for <>; Tue, 2 Jul 2019 13:25:39 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 4DFB2120172 for <>; Tue, 2 Jul 2019 13:25:39 -0700 (PDT)
Received: from pps.filterd ( []) by ( with SMTP id x62KHYNM008878; Tue, 2 Jul 2019 16:25:35 -0400
Received: from ( []) by with ESMTP id 2tgdu9rpgr-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 02 Jul 2019 16:25:34 -0400
Received: from (localhost []) by (8.14.5/8.14.5) with ESMTP id x62KPWbc045467; Tue, 2 Jul 2019 15:25:33 -0500
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id x62KPTah045400 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 2 Jul 2019 15:25:29 -0500
Received: from ( []) by (Service) with ESMTP id 7EA96400A0A7; Tue, 2 Jul 2019 20:25:29 +0000 (GMT)
Received: from (unknown []) by (Service) with ESMTP id 5F98C400A0A2; Tue, 2 Jul 2019 20:25:29 +0000 (GMT)
Received: from (localhost []) by (8.14.5/8.14.5) with ESMTP id x62KPTbq010300; Tue, 2 Jul 2019 15:25:29 -0500
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id x62KPOIL009970; Tue, 2 Jul 2019 15:25:24 -0500
Received: from ( []) by (Postfix) with ESMTP id B95CEE0A12; Tue, 2 Jul 2019 16:24:57 -0400 (EDT)
Received: from ([fe80::b09c:ff13:4487:78b6]) by ([fe80::8c6b:4b77:618f:9a01%11]) with mapi id 14.03.0439.000; Tue, 2 Jul 2019 16:24:39 -0400
From: "MORTON, ALFRED C (AL)" <>
To: Sudhin Jacob <>, "" <>
Thread-Topic: REG: draft-morton-bmwg-multihome-evpn/
Thread-Index: AdUnclVAoyFo7+yQQU+WhqmYlahLPgJfKe+gAAlEMyA=
Date: Tue, 2 Jul 2019 20:24:38 +0000
Message-ID: <>
References: <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_4D7F4AD313D3FC43A053B309F97543CFA0AA6F32njmtexg5researc_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-07-02_09:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1907020226
Archived-At: <>
Subject: Re: [bmwg] REG: draft-morton-bmwg-multihome-evpn/
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Benchmarking Methodology Working Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 02 Jul 2019 20:25:41 -0000

Adding Jim's address to the thread,

From: bmwg [] On Behalf Of MORTON, ALFRED C (AL)
Sent: Tuesday, July 2, 2019 3:06 PM
To: Sudhin Jacob <>rg>;
Subject: Re: [bmwg] REG: draft-morton-bmwg-multihome-evpn/

Hi Sudhin,

Thanks very much for your review of our draft,
and your willingness to meet on the phone to
sort-out some high-level questions first.
I think we saved a lot of time here.

Please see our replies below, and the draft
with updates will follow shortly.

Jim and Al(as a participant)

From: bmwg [] On Behalf Of Sudhin Jacob
Sent: Thursday, June 20, 2019 10:27 AM
Subject: [bmwg] REG: draft-morton-bmwg-multihome-evpn/

Hi Al/Jim,

I had gone through the draft. Could you please clarify on measuring the throughput of multi home evpn services(How to do the test this requires some expansion in the current draft)..
Yes, of course. Keep in mind that we are heavily
re-using the procedures of RFC 2889 for fully-meshed traffic.

The current draft is not clear in connecting the RT ports in order to measure the flow. Could you please provide some information regarding that. For effective measurement of throughput of multihome evpn services we must take in to account of reducing the network elements in the topology.
Figure 1 is very minimal, one CE and 2 PE, sufficient for testing
a multi-homed CE scenario.

Figure 2 needs more network equipment to test address withdrawal. We showed the connection to CE_2 more clearly now (PE_3 if that's what you want below).


1.     If the remote PE is Single home and there must be a router tester connected to it.
Are you suggesting that we remove the single-homed CE_2 in Figure 2? We can do that, but then we lose a simple and symmetrical test case.

2.     Another method is if we place a single home interface and multihome interface in the same routing instance which reduces the other routers/elements.
So, a new setup like Figure 2 should include a CE which is single-homed to PE1 with ESI=0 ??  This new scenario could be used to reduce the test equipment needed, and it is supported by the EVPN technology. (We could do this in a new Figure 3)

Or, the CE would have two links to the same Router or PE?

We're not sure how that affects the performance we are trying to measure...

Then send unicast traffic from the single home to multiihome . Take the measurements in router ports.
It is good to clarify that we are testing with Unicast flows, and
we have made that point now, and many other key references to
RFCs and other specs that will help.


Juniper Internal