DR interim meeting 6/15 10:00 - 11:30am ET
10:00 - 10:05 Bash Agenda
10:05 - 10:20 Presentation of Merged BGP Yang module
(Keyur Patel, Anees Shaikh, Rob Shakir)
Open Config reference:
10:10 - 10:25 Discussion of Merged BGP Module
- Benoit: OpenConfig discussion netmod interim meeting on thursday.
- We want to provide guidelines RFC6087bis - we want to provide guidelines.
- You metion draft-shaikh-rtwg-policy model, what is the status of the policy model draft?
- Keyur: The policy model draft has not been forwarded to rtgwg for adoption.
- It is stable draft progressing toward WG draft.
- Anees: This is correct. We just revised it. It is proceeding toward WG draft with the policy draft (draft-shaikh-rtgwg-policy-model-00).
- We are waiting for a WG draft to mature with vendors. The IDR draft we are proposing dues support that policy model.
- Rob: This model is the base configuration for the bgp policy. You just get anchor points within bgp to reference policies
- Our OpenConfig work pushes both bgp model and policy model. The two models are roughly equally mature. The BGP is slightly ahead due to the call for adoption this morning.
- Alex Zhdankin
- What is the link between this model and the routing draft?
- You should have some link to the routing model. You should put the BGP into the routing sub-tree.
- Why is it separate?
- Rob: We did not think that it was critical to have a link to the Routing model. The key thing is for the IDR model to agree on
- what is the BGP model, and when there is consensus on where it goes, we can place it with the routing model?
- Alex Zhdankin:
- For the implementation, it does matter what is in the routing model.
- Rob: It is agree that for the implementation, we will need both the routing model and the IDR.
- We are focused in IDR on deciding if it can express the right BGP policy,
- overall coordination can then decide on where that should be placed
- Keyur: Good morning Alex. This model only defines what BGP extensions to the routing policy draft (draft-shaikh-rtgwg-policy-model-00). The BGP model links to the policy draft.
- Alex: I am not concerned about the review, and I concerned about the implementation.
- Jeff: What is original it is this comes in from the OpenConfig work.
- Sue: it is now up for WG adoption so it is (becoming) an IETF draft.
- Jeff: the history helps answer Alex's question
- Sue: agreed
- Alex:There is devices that need to know how this links into the routing model.
- Rob: It is only a challenge to have multiple instances for VRF.
- Alex: There is a problem for implementation without having the routing policy link.
- Rob: I would love to have to have people adopt an iterated form of this BGP model for multiple lists.
- Acee: Propose moving this to the list.
- Keyur: No problem we will move this to the list.
- Benoit: Do you have any strong view on how you want to put status in Netmod devices, then please come to netmod meeting thursday.
- Benoit: Will you put Open Issues
- Sue: Open issues list to be created on wiki. Authors can update, it's an open wiki.
- Acee: Will you have another interim before IETF??
- Sue: On June 29th will be another interim.
10:25 am ET adjourn
Meeting number: 649 169 095
Meeting password: yang.for.life
Join by phone
1-877-668-4493 Call-in toll free number (US/Canada)
1-650-479-3208 Call-in toll number (US/Canada)
Access code: 649 169 095
Virtual Blue sheets
Please sign up on the virtual blue sheets.
[Please consider helping Sue and John during the interim discussion take minutes.
Join the etherpad and correct or work on the web]
10:05 meeting begins
10:06 keyur presenting yang data model updates (see slides)
sue: please go over explanatory slides
(bgp module organization slides)
benoit: openconfig op state is subject of netmod meeting this thursday, to provide guidelines