Re: [bess] Suresh Krishnan's No Objection on draft-ietf-bess-evpn-vpls-seamless-integ-05: (with COMMENT)

"Ali Sajassi (sajassi)" <> Tue, 22 January 2019 09:20 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id E7E66130E9F; Tue, 22 Jan 2019 01:20:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -14.642
X-Spam-Status: No, score=-14.642 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.142, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id zJ1FhTQ2M2ok; Tue, 22 Jan 2019 01:20:45 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 5D6F512DF72; Tue, 22 Jan 2019 01:20:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=3330; q=dns/txt; s=iport; t=1548148845; x=1549358445; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=OX+Zeo1mJH22sf4WEFVKdxtC4elZkdSREuWkry+3d2I=; b=KBjduxt/SrG2ReHY+eo0xp8GD48W7MYuKUBcUSvz7UQa8b1j946QxqCU xc2GRakNj9lU1OJzMzIVuzQ3aiJxpTwWsZ/Ai2Iqq/Ras9O1Oq9xxbgDP G3SE+PaVsF0CbdQcF+bxyqT4mMOifCd4tpaXJhGrxCZ2v0V3rWyKUWNtn 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0ADAADu30Zc/5hdJa1jGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQcBAQEBAQGBUQQBAQEBAQsBggNmgQInCoN3iBqLaJoOFIFnCwEBJYR?= =?us-ascii?q?HAheCUCI0CQ0BAwEBAgEBAm0cDIVLBiMRRRACAQgaAiYCAgIwFRACBAENBYM?= =?us-ascii?q?iAYIBD6wfgS+EQkGFHwWBC4s2F4F/gRABJx+CTIMeAgECAYEqARIBgygxgiY?= =?us-ascii?q?CiWWXZlUJAociincYgWaFLosAigSFHItWAhEUgScfOGVYEQhwFWUBgkGCJxc?= =?us-ascii?q?TiEyFP0ExAYhegR+BHwEB?=
X-IronPort-AV: E=Sophos;i="5.56,505,1539648000"; d="scan'208";a="508034685"
Received: from ([]) by with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 22 Jan 2019 09:20:44 +0000
Received: from ( []) by (8.15.2/8.15.2) with ESMTPS id x0M9KhJL017031 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 22 Jan 2019 09:20:44 GMT
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.1395.4; Tue, 22 Jan 2019 04:20:43 -0500
Received: from ([]) by ([]) with mapi id 15.00.1395.000; Tue, 22 Jan 2019 04:20:43 -0500
From: "Ali Sajassi (sajassi)" <>
To: Suresh Krishnan <>, The IESG <>
CC: "" <>, Matthew Bocci <>, "" <>, "" <>
Thread-Topic: Suresh Krishnan's No Objection on draft-ietf-bess-evpn-vpls-seamless-integ-05: (with COMMENT)
Thread-Index: AQHUqJloKrwHhK/Kv0yG/noqq0dYpqW65AAA
Date: Tue, 22 Jan 2019 09:20:43 +0000
Message-ID: <>
References: <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: []
Content-Type: text/plain; charset="utf-8"
Content-ID: <>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <>
Subject: Re: [bess] Suresh Krishnan's No Objection on draft-ietf-bess-evpn-vpls-seamless-integ-05: (with COMMENT)
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: BGP-Enabled ServiceS working group discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 22 Jan 2019 09:20:48 -0000

Thanks for your review and your comments. Please refer to my replies below marked with "AS>".

On 1/9/19, 8:03 PM, "Suresh Krishnan" <> wrote:

    Suresh Krishnan has entered the following ballot position for
    draft-ietf-bess-evpn-vpls-seamless-integ-05: No Objection
    When responding, please keep the subject line intact and reply to all
    email addresses included in the To and CC lines. (Feel free to cut this
    introductory paragraph, however.)
    Please refer to
    for more information about IESG DISCUSS and COMMENT positions.
    The document, along with other ballot positions, can be found here:
    * Section 3.3 MAC Mobility
    The handling of MAC mobility between the EVPN and VPLS PEs seems a bit, for a
    lack of a better term, "not seamless" to me. While only using EVPN a MAC that
    has moved will get propagated out without *initiating* any sort of BUM traffic
    itself as described Section 15 of RFC7432. If I understand this document
    correctly, if a MAC moves onto a segment with a VPLS PE, traffic towards it
    will be blackholed until it initiates BUM traffic which is not the case when
    the MAC moves between EVPN PEs. Did I get this right? If so, I think this
    limitation needs to be highlighted a bit more prominently.
  AS>  Section 3.3 describes two MAC move scenarios: move from EVPN PE to VPLS PE (1st para) and move from VPLS PE to EVPN PE (2nd para). In the first scenario, it says that if the moved MAC address doesn't initiate any BUM traffic (it only initiates known unicast traffic), then there can be black-holing for both EVPN and VPLS PEs. However, for the 2nd scenario, the black-holing can happen only for VPLS PEs. To clarify this point further, I added a sentence to each of the paragraph. 
1st para: Such black-holing happens for traffic destined to the moved C-MAC from both EVPN and VPLS PEs.
2nd para: Such black-holing happens for traffic destined to the moved C-MAC for only VPLS PEs but not for EVPN PEs.