IETF Logo Mail Archive

[bess] Questions & comments on draft-boutros-bess-evpn-vpws-service-edge-gateway-02

"Jeffrey (Zhaohui) Zhang" <zzhang@juniper.net> Fri, 25 March 2016 01:20 UTC

Return-Path: <zzhang@juniper.net>
X-Original-To: bess@ietfa.amsl.com
Delivered-To: bess@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 45FC912D115 for <bess@ietfa.amsl.com>; Thu, 24 Mar 2016 18:20:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.903
X-Spam-Level:
X-Spam-Status: No, score=-1.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=junipernetworks.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SYPvmK3L86Ms for <bess@ietfa.amsl.com>; Thu, 24 Mar 2016 18:20:23 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2on0147.outbound.protection.outlook.com [207.46.100.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8412E12D0E6 for <bess@ietf.org>; Thu, 24 Mar 2016 18:20:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=junipernetworks.onmicrosoft.com; s=selector1-juniper-net; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=SfEDi3iY0leGWPcDN2BFXeKyEmU8EqjdpXG4miJrePU=; b=jg5ze1vQnHVmh1tqKiGATc3SgLh3T02y20XkON2CNkHaN58QRMqVWicRHUFSQRnyIyDmXHRL0t8sBG100wEUd+GHM9j88pOVi+9Uh2oe2T2o8F8XwsuuPPxGdo4Eq7Js034FNL0qWWOuoQu50aeZhm99kWBQZeHjIl55ZSAZ8Tk=
Received: from BLUPR0501MB1715.namprd05.prod.outlook.com (10.163.120.18) by BLUPR0501MB1713.namprd05.prod.outlook.com (10.163.120.16) with Microsoft SMTP Server (TLS) id 15.1.443.12; Fri, 25 Mar 2016 01:20:22 +0000
Received: from BLUPR0501MB1715.namprd05.prod.outlook.com ([10.163.120.18]) by BLUPR0501MB1715.namprd05.prod.outlook.com ([10.163.120.18]) with mapi id 15.01.0443.015; Fri, 25 Mar 2016 01:20:22 +0000
From: "Jeffrey (Zhaohui) Zhang" <zzhang@juniper.net>
To: "sboutros@vmware.com" <sboutros@vmware.com>, "bess@ietf.org" <bess@ietf.org>
Thread-Topic: Questions & comments on draft-boutros-bess-evpn-vpws-service-edge-gateway-02
Thread-Index: AdGGEHctEGRuORt7QSe3262I08E2kw==
Date: Fri, 25 Mar 2016 01:20:22 +0000
Message-ID: <BLUPR0501MB1715AC7A4C446719ED7CA996D4830@BLUPR0501MB1715.namprd05.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: vmware.com; dkim=none (message not signed) header.d=none;vmware.com; dmarc=none action=none header.from=juniper.net;
x-originating-ip: [66.129.241.14]
x-ms-office365-filtering-correlation-id: d4599214-89df-4efb-cf10-08d3544ba2fc
x-microsoft-exchange-diagnostics: 1; BLUPR0501MB1713; 5:gLwmtcRoM8RZP65qmQx433OsLDs/xxf0smfyuBKMzxn3bt8345by1SgbJrsluen9pB1xZFPigKTIXz8tqhu42MGYKQCIba+OK30rBVFOHukfLom6QjXnAhErr0YQBaKVc5q3eP1xjr9M36+JgdXU8A==; 24:wkaqNzL+adD7K/VuF+RAPurf3WvaRdjEReViHclMR2Qad1iqHtrX3vZKX2mdKYWcPp5ywLI7eJMw6LvS8hF0AOzJrjLzflnwjZ67mijIFzU=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BLUPR0501MB1713;
x-microsoft-antispam-prvs: <BLUPR0501MB17133C6D588F9B88233D6B4DD4830@BLUPR0501MB1713.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001); SRVR:BLUPR0501MB1713; BCL:0; PCL:0; RULEID:; SRVR:BLUPR0501MB1713;
x-forefront-prvs: 0892FA9A88
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(2900100001)(3660700001)(54356999)(1220700001)(87936001)(3280700002)(5008740100001)(50986999)(586003)(2906002)(3846002)(86362001)(5001770100001)(1096002)(76576001)(74316001)(77096005)(6116002)(102836003)(11100500001)(81166005)(99286002)(229853001)(230783001)(5003600100002)(92566002)(5002640100001)(5004730100002)(10400500002)(5890100001)(189998001)(122556002)(33656002)(107886002)(2501003)(66066001); DIR:OUT; SFP:1102; SCL:1; SRVR:BLUPR0501MB1713; H:BLUPR0501MB1715.namprd05.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en;
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 25 Mar 2016 01:20:22.1566 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR0501MB1713
Archived-At: <http://mailarchive.ietf.org/arch/msg/bess/gZG3eivkefT9Aj8xHdjMGsL4uj8>
Subject: [bess] Questions & comments on draft-boutros-bess-evpn-vpws-service-edge-gateway-02
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bess>, <mailto:bess-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bess/>
List-Post: <mailto:bess@ietf.org>
List-Help: <mailto:bess-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bess>, <mailto:bess-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Mar 2016 01:20:25 -0000

Sami and co-authors,

I have some comments & questions on this draft.

I noticed that the following terms are used in a mixed way and that adds confusion. Perhaps it could be straightened out?

  Service node, service edge node, service edge gateway, access node

Also in Figure 1, "AN" and "SE" are not marked in the figure.

There are a couple of places referring to "underlay EVI". Given that underlay typically refer to the underlying provider network, perhaps "transport EVI" or "VPWS EVI" would be better?

   This document describes how a service node can act as a gateway
   terminating dynamically EVPN virtual private wire service (VPWS) from
   access nodes and offering Layer 2, EVPN and Layer 3 VPN overlay
   services to Customer edge devices connected to the access nodes.

I take it that the gateway is offering "layer 2, EVPN and layer 3 VPN" services but instead of via local attachment circuits, it's via VPWS implemented via EVPN.

"4.2 Applicability to IP-VPN TBD" is empty, so I'll use EVPN for my understanding: the VPWS brings the customer connection (on the AN) to the EVPN on the gateway. There could be many VPWS from multiple ANs terminating into the same EVPN instance on the gateway. With that, I wonder if EVPN virtual hub and spoke could be used to implement the same? The ANs would be the spokes and the gateway would be the hub? Other EVPN PEs (not drawn in Figure 1) on the core side can be either spokes or hubs in the same EVPN instance?

If the above makes sense, then could the same be extended to IP-VPN service? You just need an IRB interface for the EVPN instance on the gateway?

Thanks.
Jeffrey

v2.23.0 | Report a Bug | By Email