Re: [bess] new WGLC for draft-ietf-bess-evpn-inter-subnet-forwarding-05

"Ali Sajassi (sajassi)" <> Tue, 29 January 2019 23:19 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id C6EF412E7C1 for <>; Tue, 29 Jan 2019 15:19:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -17.064
X-Spam-Status: No, score=-17.064 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-4.553, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=1.989, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=unavailable autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Fv3beeN3y4HN for <>; Tue, 29 Jan 2019 15:19:48 -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 3A20D130EE0 for <>; Tue, 29 Jan 2019 15:19:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=22494; q=dns/txt; s=iport; t=1548803988; x=1550013588; h=from:to:subject:date:message-id:mime-version; bh=HI5fCtHybv/3DyPi4GDSKudaGVu59DrNDN7pojYtHa0=; b=Cy7fIxxtz93rCCG2Ai7BZtW0OXaFC9G1iYvqONOROui5FxyCGyssbngR BSq/boJei6bFUX1KrAERUfIONAgOdytshKzv7QMLWSxLvGQiwEhoHbWiG 7bSGxiSgqPi7/cpEyJMy5f6ji1OMEAPIDl5VWVpfJN/iOFJFS02l5RFwv Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.56,538,1539648000"; d="scan'208,217";a="232458157"
Received: from ([]) by with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 29 Jan 2019 23:19:47 +0000
Received: from ( []) by (8.15.2/8.15.2) with ESMTPS id x0TNJkcv030368 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 29 Jan 2019 23:19:46 GMT
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.1395.4; Tue, 29 Jan 2019 18:19:46 -0500
Received: from ([]) by ([]) with mapi id 15.00.1395.000; Tue, 29 Jan 2019 18:19:46 -0500
From: "Ali Sajassi (sajassi)" <>
To: "Luc Andre Burdet (lburdet)" <>, "" <>, "" <>
Thread-Topic: [bess] new WGLC for draft-ietf-bess-evpn-inter-subnet-forwarding-05
Thread-Index: AQHUuCkfmCdoPDeOUUiX20A6ITZGTQ==
Date: Tue, 29 Jan 2019 23:19:45 +0000
Message-ID: <>
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: multipart/alternative; boundary="_000_AD82501102534882A33648703925FA45ciscocom_"
MIME-Version: 1.0
Archived-At: <>
Subject: Re: [bess] new WGLC for draft-ietf-bess-evpn-inter-subnet-forwarding-05
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, 29 Jan 2019 23:19:52 -0000

Please refer to my replie inline marked with “AS>”

From: BESS <> on behalf of "Luc Andre Burdet (lburdet)" <>
Date: Tuesday, August 21, 2018 at 10:56 AM
To: "" <>, "" <>
Subject: Re: [bess] new WGLC for draft-ietf-bess-evpn-inter-subnet-forwarding-05


This is an important draft and is implemented;


  1.  ​I echo Acee's comment re: "Router MAC" for readability

AS> I also echo my reply to Acee’s comment ☺

(2) The document often refers to two Route-targets (MAC-VRF & IP-VRF) which is overly restrictive.

I would propose language more to the effect of MAC/IP must be advertised with two sets of RTs

AS> “two Route targets” are used when the document talks about Route-Type-2 – which is in context of a single EVI for MAC-VRF and IP-VRF.



    RFC7432:  EVPN route MAY carry one or more Route Target (RT) attributes.​

vs. for example:

   This route MUST be advertised with two route targets - one

   corresponding to the MAC-VRF of the tenant's subnet and another

   corresponding to the tenant's IP-VRF.


Luc André​ Burdet

From: BESS <> on behalf of <>
Sent: August 8, 2018 10:03 AM
Subject: [bess] new WGLC for draft-ietf-bess-evpn-inter-subnet-forwarding-05

Hello working group,

This email starts a two-week Working Group Last Call on draft-ietf-bess-evpn-inter-subnet-forwarding-05 [1].

A significant amount of update has been introduced since the previous WGLC. Please review the updates and provide your feedback.

This poll runs until *the 22th of August*.

Thank you

Stéphane, Matthew

bess chairs



Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.

Thank you.