29/05/2020

  1. Discussed about libyang performance issues. 
    1. FRR infra might need to undergo a change as libyang API that we are using currently does no do well with scale. 
    2. FRR infra API's might need to have shim layer so that changes to API should not impact user.
    3. Other suggestions came in as having two API where protocols like RIP may use old API as they do not scale and protocols like static and BGP can use new API which will have scaled config.
  2. Discussed about solutions proposed by libyang developer for issue raised  https://github.com/CESNET/libyang/issues/1094
  3. Discussed PR  https://github.com/FRRouting/frr/pull/6438
    1. With encryption passwords set and get will not be same so how do we handle it in yang.
    2. IETF does not have any solution for the same.
    3. In frr it can be handled with hooks which protocol can call to encrypt and decrypt and display the same.
    4. More discussion will happen over slack.

Public Last updated: 2020-06-05 02:57:23 PM