Óscar González de Dios

Hi Smitha, The first step was to add the support for key-chain. Now, every protocol will be extended to use the key-chain as part of its authentication configuration. So, expect...

First proposal available in https://github.com/openconfig/public/pull/588 Please review and comment

> > My comments below are similar to Rob: > > * a single prefix-list should only include IPv4 prefixes or IPv6 prefixes, not both Oscar: Agree, let's go with...

Hi LeonGWang, I think the functionality is interesting and needed. Can you indicate in which platforms it is currently available? Please also check PR https://github.com/openconfig/public/pull/649 were aditionally I have proposed...

Hi! I agree that is easier to understand and more efficient having the options like invert in the conditions rather than in the set. Now, it is true that you...

Hi! As far as I know, in Openconfig you can only specify the protocol by with the route was learnt. I've check the IETF model and has also the same...

> Commit https://github.com/openconfig/public/pull/649/commits/669666de69716b62639ddc06892c5f765008637a adds the support for ipv6 prefix source and destination sets, as well as the ipv4 destination set.

> @oscargdd please update the PR description (the first comment in this PR) to provide the operational use case for this model. Please contrast with the acl-sets proposed in #693...

I have received via email the following comment via email, that I reproduce here: We suggest to change the type of the address leaf, there is no need to keep...

I have done a last pass to ensure consistency in naming. Now we are using “set” in the defined-set container and list in the matches. So .. I think we...