答复: YANG model for protocol independent OAM

[Haoweiguo <[e-mail]>]

Hi Tissa,

Thanks for your presenting the detail Yang model of TRILL OAM. After read the draft, i have some comments and problems as follows.



1. There is no MIP data model in this draft, in TRILL OAM Framework MIP is definitely defined to filter OAM packet based on MIP level.

2. The range of MEP ID is from 1 to 8191. In TRILL OAM framework, trill base mode is defined to generate MD, MA, and MEP automatically, MEP ID can use RB's nickname and will be beyond 8191, how can it be managed through Yang model?

3. In trill base mode, the default name for MD is "TrillBaseMode", the default name for MA is "FFFC". If they are conflicted with the configuration data, how can we solve this issue?

Thanks

weiguo

________________________________
发件人: mpls [[e-mail]] 代表 Tissa Senevirathne (tsenevir) [[e-mail]]
发送时间: 2014年4月2日 10:57
收件人: [e-mail]; [e-mail]; [e-mail]
主题: [mpls] YANG model for protocol independent OAM

All

In the draft below we present YANG model to abstract protocol dependent aspects of OAM and create a unified OAM API set. In a nutshell, ping is ping and traceroute is traceroute and so on. Protocol independent API ‘s allow users to exercise these OAM tools in the same manner across different technologies and allow to integrate to their operations platforms.

Appreciate your time on reviewing and providing comments, both on API’s and YANG model as well as OAM framework in it self.

http://www.ietf.org/id/draft-tissa-netmod-oam-00.txt

Thanks
Tissa