Re: [CCAMP] A Recap of Update to Draft "YANG Data Model for FlexE Interface Management"

[Jiangyuanlong <[e-mail]>]

Hi Daniele,

I will update the slides with a highlight page as you kindly proposed.
BTW, I could not attend the IETF 105th meeting on site, but my colleague Zitao will present the slides for us, and I will try my best to join the CCAMP session remotely.

Thanks much,
Yuanlong

From: Daniele Ceccarelli [mailto:[e-mail]]
Sent: Tuesday, July 23, 2019 8:39 PM
To: Jiangyuanlong <[e-mail]>; CCAMP ([e-mail]) <[e-mail]>
Cc: [e-mail]
Subject: RE: A Recap of Update to Draft "YANG Data Model for FlexE Interface Management"

Hi authors,

Thanks a lot for the update and summary of one of the two drafts. During your presentations @IETF105 could you please make sure to highlight what are the commonalities between the two drafts (the parts you agree on) and the parts you don't agree on and that didn't make a merge possible?
Many thanks,

Daniele

From: CCAMP <[e-mail]<mailto:[e-mail]>> On Behalf Of Jiangyuanlong
Sent: den 15 juli 2019 08:29
To: CCAMP ([e-mail]<mailto:[e-mail]>) <[e-mail]<mailto:[e-mail]>>
Cc: [e-mail]<mailto:[e-mail]>
Subject: [CCAMP] A Recap of Update to Draft "YANG Data Model for FlexE Interface Management"

Dear CCAMPers,

After the IETF 104th meeting, some authors of draft-jiang-ccamp-flexe-yang and draft-xiaobn-ccamp-flexe-yang-mod had twice met and discussed the possibility of combining these two drafts. But authors of the two drafts had quite different opinions on the target and methodology of the FlexE YANG model, thus we decided to update the drafts in its own right until our WG makes a decision on how this work shall be proceeded.

Here is a brief summary of draft-jiang-ccamp-flexe-yang ("YANG Data Model for FlexE Interface Management"):
1. the philosophy of the model is treating a whole FlexE Group as an interface, and treating the Flex Clients in a FlexE Group as sub-interfaces, so that the same interface logic applies (i.e., familiar flavor).
2. Since a FlexE client is decoupled from the FlexE PHYs, it is modeled as a new type of interface, so that new FlexE clients can be more appropriately modeled, and more easily be augmented to support some new MAC layer features, such as flow control, and etc.
3. it is modeled as a simple flat tree, and leave out internal data plane implementation dependent artifacts where management and control planes do not care much, such as FlexE Instance, Calendar A and B.
3. it uses the nomenclatures which are more compatible with the YANG style in the IETF.

Please see https://tools.ietf.org/html/draft-jiang-ccamp-flexe-yang-01 for the details. Your comments and involvements will be much appreciated.

Best regards,
Yuanlong