LIME Minutes 4/5/2016
Scribe: Sanjoy Bardhan <sbardhan@infinera.com>
Status
WG – 4 documents
Update from Ron
Worried about energy in the WG
Progress the 2 YANG models quickly
CO Yang not ready for last call – pretty close – get a virual interim and spin one version and in Berlin have a last call
CO applicability statement – copy from here into Yang model
CL Yang – spin another version by next IETF
CL applicability – get new data
Carlos
Success of the group – customers use the model – protocol specific OAM
Created a wiki – tracking all the protocols
In the wiki want to see more –
- Most of the folks are using old drafts – need to capture what is being used
- Capture all dependent YANG models
LIME CO OAM Yang Model Update
- Split Generic model in to CO and CL models
- CO
- Removed IPv4 and IPv6 from CO
- Included TRILL and MPLS TP
- Comments
- Greg (Ericsson)
- Location of test points that define the path and operation and state
- Try to do some abstraction between CO and CL
- Information necessary for the client layer to the server layer
- Ron request – post to mail list with the suggestion
CL OAM Yang Model – Qin WU
- Discussed the CL OAM Model Design
- Comments
- Greg (Ericsson)
- BFD Yang model adopted by BFD WG – would this be duplication of effort ? - LIME is specific generic – authors need to coordinate
- Deepak
- ??
- UP/DN/Intermediate attribute – need to figure to incorporate or not
- Ron
- If 2 technologies have the same attributes should we try to make it common
- More collaboration is needed
- Have not consider Performance management – we can add them and bring to the ML
- Carlos
- All 3 - PM, Active/Passive, On demand vs Continuous need discussion
- PM for CO and CL - have discussion in ML
- Poll
- Some have read the doc – 8
- The WG take this up – around 8
- Doc starting point – less
Next Steps/Recap
- Progressing CO and CL independently
- Will not progress on Applicability
- Reach out to other WG
- Virtual Interim for CO and last call for CO OAM - 6