[frr] Today's Technical Meeting Agenda

[Philippe Guibert]

Hello Lou, all,

I dont' know if this call is necessary.
See below,

*coming back to RD/RT discussion*

I studied a bit the solutions to deploy BGP using vrf-policy.
I came to the following conclusions, that go in the same direction as
the FRR people involved in the 7th of february meeting, namely:
- adding route-map to vrf-policy, to make it consistent with the other
configuration case, ie bgp vrf use case

- Also, while I was insisting on having prefix keyword as a
configuration element from vrf-policy subnode, I realized it was less
important since there were already available commands to set per VRF
prefixes, namely add vrf <> prefix <> ...

So, to summarise, only route-map should be added.
(vrf-policy)# [no] route-map <>
I don't think it is needed to have route-map keyword somewhere else (
per label or per RD for instance).
Maybe to add route-map behind "add vrf <> prefix <>" command ?

To make it clear, all new prefixes matching the VRF will be applied (
if not) the vrf-policy settings, before being applied the configured
route-map.
And good news, it is already possible inside route-map to set a rt or
a soo, or a label. ( at least by configuration, maybe someone tried ?)

* other topics indirectly related to RD/RT discussion*
There are other separate topics that could be discussed separately,
for extensions of vrf-policy services ( and also bgp vrf use case if
not already supported):
a- support for ECMP ( or not) inside a vrf-policy
b- choice of signalisation method to carry vrf information : Encap, VPN, EVPN
( by the way, Lou, I don't find the proposal you were suggesting in a
previous github comment).
c- support for EVPN specific parameters

For the latter point, I propose to initiate some thread by mail to
discuss those specific points.
OK to pursue in that way?

Regards,

Philippe

On Tue, Feb 14, 2017 at 2:17 PM, Lou Berger <lberger at labn.net> wrote:
>
>
> On February 14, 2017 7:56:51 AM Donald Sharp <sharpd at cumulusnetworks.com>
> wrote:
>
>> 11 AM EST
>>
>> https://www.bluejeans.com/9192742159
>>
>> 1)  2.0 rc status
>>
>> 2)  Pull Requests Outstanding
>>
>> 3) RD/RT Discussion
>>
> As I mentioned in last week's call, I would like to put this discussion
> cannot be there today. Can we schedule another call on this topic some other
> time this week?
>
> Lou
>
>> Anything else people want to talk about?
>>
>> donald
>>
>> _______________________________________________
>> frr mailing list
>> frr at lists.nox.tf
>> https://lists.nox.tf/listinfo/frr
>
>
>
>
> _______________________________________________
> frr mailing list
> frr at lists.nox.tf
> https://lists.nox.tf/listinfo/frr