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
Dunbar
From: BESS On Behalf Of Robert Raszuk
Sent: Monday, June 8, 2020 4:53 AM
To: slitkows.i...@gmail.com
Cc: draft-ietf-bess-datacenter-gate...@ietf.org; Adrian Farrel
; bess-cha...@ietf.org; BESS
Subject: Re: [bess] Closing on Stephane's open issue with
draft-ietf-bess-datacenter-ga
Stephane,
Two points ..
1. It is not clear to me that draft-ietf-bess-datacenter-gateway recommends
to use RTC for anything - do they ? If not there is no issue.
2. Also note that RTC can be enabled on a per AF basis hence even if you
use it say for SAFI 128 you do not need to use it for SAFI 1.
Hi Adrian,
My point is really tied to what will happen when RTC is enabled (considering
draft-ietf-idr-rtc-no-rt). The behavior will be to drop the routes that
don't have an RT which will break existing Internet families behavior.
" When RTC is applied, on a particular BGP session, to routes of ot
Hi,
John and I had a chat today about what we perceive is Stephane's open issue.
What we think the concern is is that we are using RTs in conjunction with
normal (i.e., non-VPN) routes. We do this to allow gateways to filter their
imports based on the RT that applies to the SR domain that it serv
