Thanks. Wednesday (11th Dec 2019) we will have call at same time as Tuesday regular call. We can use Donald’s meeting link for the same.

 

Thanks

Santosh P K

 

From: Quentin Young <qlyoung@cumulusnetworks.com>
Date: Monday, 9 December 2019 at 11:15 AM
To: Santosh P K <sapk@vmware.com>
Cc: FRRouting-Dev <dev@lists.frrouting.org>
Subject: Re: [dev] Northbound work reviews and progress

 

That's better, 7 PST is a bit too early ATC.

 

 

On Mon, Dec 9, 2019, 12:34 AM Santosh P K <sapk@vmware.com> wrote:

Quentin there were request to postpone this to Wednesday same time as Tuesday call. Does that time work for you?

 

Thanks

Santosh P K

 

From: Quentin Young <qlyoung@cumulusnetworks.com>
Date: Saturday, 7 December 2019 at 2:16 AM
To: Santosh P K <sapk@vmware.com>
Cc: "dev@lists.frrouting.org" <dev@lists.frrouting.org>
Subject: Re: [dev] Northbound work reviews and progress

 

I think this is appropriate. Probably an hour will be sufficient.

 

Does the hour before next week's technical meeting work for you?

 

On Fri, Dec 6, 2019 at 3:28 AM Santosh P K via dev <dev@lists.frrouting.org> wrote:




---------- Forwarded message ----------
From: Santosh P K <sapk@vmware.com>
To: "dev@lists.frrouting.org" <dev@lists.frrouting.org>
Cc: 
Bcc: 
Date: Fri, 6 Dec 2019 08:27:37 +0000
Subject: Northbound work reviews and progress

Hello All,

    I would like to know if it makes sense to have a call for all the northbound work going on against branch  nb_conversions. We have received comments for staticd yang PR https://github.com/FRRouting/frr/pull/5460 we can discuss them as well. We are ready with PIM Yang file which we would like to raise PR but before that if we wanted to have common understanding of  how VRF needs to be handled for protocols.

 

There are different data models around and FRR RIP using VRF in different way.

  1. In case of IETF – uses VRF at top level and all protocols are under that.
  2. In case of Openconfig – uses VRF at the top level and all protocols are under that.

 

+--rw network-instances

     +--rw network-instance* [name]

        +--rw name                       -> ../config/name

        +--rw protocols

           +--rw protocol* [identifier name]

              +--rw identifier    -> ../config/identifier

              +--rw name          -> ../config/name

              +--rw config

              |  +--rw identifier?       identityref

              |  +--rw name?             string

              |  +--rw enabled?          boolean

              |  +--rw default-metric?   uint32

              +--ro state

                 +--ro identifier?       identityref

                 +--ro name?             string

                 +--ro enabled?          boolean

                 +--ro default-metric?   uint32

 

 

  1. In case of FRR rip – uses VRF as a list under RIP.

 

module: frr-ripd

  +--rw ripd

     +--rw instance* [vrf]

        +--rw vrf                              string

 

 

Also I see that there is a new PR for VRF https://github.com/FRRouting/frr/pull/5492 and we have one defined in staticd Yang (as it was not there before). To have common understanding and avoid duplicate effort a call would help.

 

@Donald Sharp Can we use next week Tuesday slot for this discussion? Or shall we schedule a separate meeting on Wednesday or Friday? Please do suggest.

 

Thanks

Santosh P K




---------- Forwarded message ----------
From: Santosh P K via dev <dev@lists.frrouting.org>
To: "dev@lists.frrouting.org" <dev@lists.frrouting.org>
Cc: 
Bcc: 
Date: Fri, 06 Dec 2019 00:28:16 -0800 (PST)
Subject: [dev] Northbound work reviews and progress
_______________________________________________
dev mailing list
dev@lists.frrouting.org
https://lists.frrouting.org/listinfo/dev