Deepak Kumar Zitao Wang Qin Wu Reshad Rahman Srihari Raghavan LIME Connectionless Model Updates draft-ietf-lime-yang-connectionless-oam-02 draft-ietf-lime-yang-connectionless-oam-methods-00 Deepak Kumar Zitao Wang Qin Wu Reshad Rahman Srihari Raghavan IETF 97

Activities since IETF 96 Three interim meetings One for CO model One for CL model One for BFD & Lime Several discussions in email list Split the model into two; The relationship with technology specific models; Augment vs Schema Mount, etc. Have requested YANG doctor/coordinator review IETF 97

Updates since IETF 96 Split CL model into two One for CL model One for retrieval method Add a section to introduce CL model applicability Use both model defined in protocol working group and CL model as basis and augment the “CL" model with technology specific groupings. Update the CL model according to previous discussions. Added some descriptions to explain the relationship with topo model The "tools" attributes were modified to "ro" (read only). Some CO related attributes(e.g. tools-mpls-tp, L3VPN cases) were removed from CL model. IETF 97

relationship with other OAM YANG model work How do we describe the relationship between them? The model described in protocol working group (like BFD, etc) is defined as standalone models, Users can augment the LIME model with technology specific details (groupings defined in technology specific model) to support LIME scenarios. IETF 97

Other Questions (2) Augment method VS Schema Mount method CL base model augment CL base model Schema mount Reusing grouping Technology specific model Technology specific models like bfd single-hop model, bfd Multi-hop model, etc. Technology specific Groupings are defined in technology specific model Reusing grouping Technology specific model Reusing grouping Fig 1. Augment method Fig 2. schema mount method Pro Con Augment base model Supported by YANG 1.0 and YANG 1.1, mature N/A Schema mount Allow one model to be inserted into another model Premature, It doesn’t support specific module be mounted under a mount point yet in the current version. IETF 97