Bruno,
> 2. On the iBGP side, (re-) advertises the path received over
> the eBGP session being shutdown with a low LOCAL_PREF.
Sounds good.
Btw what is "low" ? Is 0 low ? Is 5 low ? Should we at least recommend
some value if you are assuming automation in g-shut to local pref
translation ?
Jakob, Jeff,
> This is for ebgp only, not ibgp. right?
I was assuming this is mostly for ibgp.
If this is also for ebgp are you suggesting that we will receive from
the peer a single error in UPDATE message for SAFI X/X and then it will
trigger full re-advertisement of all of our routes for all of our SAFIs
over such session to this peer with g-shut ?
The way I read what Jeff proposed is this:
1. We are receiving N errors and just treat-as-withdraw or drop errored
optional attributes when applicable
2. When N becomes more then X send g-shut to eBGP peer and lower local
pref towards iBGP then re-advertise
3. After time T shut EBGP session.
Questions: What is value of X and T above ?
Thx,
R.
_______________________________________________
GROW mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/grow
