Hello All,
Below are the points discussed and concluded in today’s meeting. Please correct me If I have missed or captured few conclusions not as we concluded.
Discussion:
- Use of nexthop as leaf ref.
- FRR will have to satisfy nexthop being independent object and can be programed independently.
- Currently kernel supports this feature and so does FRR with nexthop groups.
- NULL0 attribute handling
- We may not need NULL0 as this special nexthop and we should only provide blackhole interface.
- Discussed about different type of interface avalible today in FRR.
- FRR interface yang v/s IETF yang
- Why was FRR interface yang defined while we could have used IETF yang and added augmented more leaf to it.
- It was done as a placeholder and we will need to revisit it.
- VRF usage
- Discussed VRF usage for protocols. Should VRF be top of the tree or should be used as leafref.
- Discussed different use of VRF being at top of tree and how it may help with configuration.
- IETF data models usage
- Use of IETF data models should not restrict any existing feature that FRR supports today.
- We should try to use existing IETF data model with deviations.
- We will conclude on Staticd review before PIM and IGMP data model.
Conclusion:
- Staticd Yang module will have leafref to nexthop. For this we need to deviate from IETF nexthop and have our own nexthop container defined.
- Null0 is not required and providing blockhole is enough.
- VRF should not be restricted on how it should be used with in FRR. It should be used as appropriate for a given protocol.
We will meet again on Friday to discuss over the next review items and questions will be published beforehand.
Thanks
Santosh P K