Subject: Re: [bess] Closing on Stephane's open issue with draft-ietf-bess-datacenter-gateway

From: "Adrian Farrel" <[email-masked]>
Date: Tue, 11 Aug 2020 15:31:44 +0100

Hi Linda,

Sorry that I missed this question from you…

Adrian: 

On page 6, the second Bullet says that 

“Each GW constructs an import filtering rule to import any route that carries a route target with the same SR domain identifier that the GW itself uses”

How about routes associated to a VPN and to a SR domain? The VPN and the SR might use different RTs. Can you have two different Route Target in one advertisement?

AF > We certainly don’t want to restrict wider applicability, but our focus is only on connecting together SR domains. We weren’t looking to solve the multi-homed VPN “problem”.

AF > The RT is an extended community. Extended communities are carried in the Extended Communities Attribute. The Extended Communities Attribute can carry more than one extended community.

Best,

Adrian