Proposal to add support for SyncE (Synchronous Ethernet) Yang model and PTP model

[anukulverma]

IP Infusion Inc. wants to contribute Yang model for SyncE.

Synchronous Ethernet, also referred as SyncE, is an ITU-T standard for computer networking that facilitates the transference of clock signals over the Ethernet physical layer. This signal can then be made traceable to an external clock.

IP Infusion, the leader in disaggregated networking solutions, delivers enterprise and carrier-grade software solutions allowing network operators to reduce network costs, increase flexibility, and to deploy new features and services quickly. https://www.ipinfusion.com/about/

We are part of software vendors selected by TIP in OOPT as well DCSG groups which also expects OpenConfig as their standard Yang model.

We have proprietary Yang models for multiple networking protocols designed based on Openconfig styling, used on multiple platforms including UFI, QUMRAN, DELL etc.

We would like to contribute in openconfig community, starting with Synce model.

https://github.com/anukulverma/public/tree/master/release/models/synce

This issue is to get feedback on the proposed Synce model. Will be updating the PR# here to facilitate the discussion & review.

[anukulverma]

Also we want to contribute for PTP.

https://en.wikipedia.org/wiki/Precision_Time_Protocol

[aashaikh]

Can you please comment on your considerations to ensure your proposals are consistent OpenConfig's vendor-neutral approach? If the proposals are "proprietary Yang models for multiple networking protocols designed based on Openconfig styling", this may not quite meet the criteria. IP Infusion could always define and maintain a proprietary augmentation to the models to support SyncE/PTP in this case.

[santanukar2000]

I think it wasn't articulated correctly in the proposal. We have multiple proprietary yang models across protocols styled in OpenConfig guidelines which helps us extend the OpenConfig datamodels to support additional functionality not yet defined by OpenConfig.

However in context of 'SyncE' (Synchronous Ethernet) and PTP (Precision Time Protocol) currently there is no existing datamodel defined by OpenConfig. So we want to contribute back our 'SyncE' datamodel to OpenConfig community after following 'vendor-neutral' approach as a new separate datamodel. We are developing this as part of 'TIP' https://telecominfraproject.com/disaggregated-cell-site-gateways-ready-for-deployments/

The TIP community supports OpenConfig and want all their datamodels to be developed as per OpenConfig standards. Its developed on open vendor neutral whitebox networking hardware. So we feel contributing this back would greatly benefit TIP as well as OpenConfig community.

[aashaikh]

Thanks for the comments. I understand the desire to address the gap in current OpenConfig models and have no concerns with that. The request is to provide some data about how this model relates to currently available implementations in a way that is vendor neutral. Is the proposed data model based primarily on the IP Infusion implementation? Have you looked at other implementations to see how well they could be mapped to the proposed models? Or is it based on other published or in-progress models (e.g., from IEEE or IETF)? I hope that helps clarify the question.

[github-actions[bot]]

This issue is stale because it has been open 180 days with no activity. If you wish to keep this issue active, please remove the stale label or add a comment, otherwise will be closed in 14 days.

[proberts2022]

If this is revisited for addition into the openconfig mode, please review the work that has occurred within Q14/SG15 of the ITU-T which has developed a 'standard' data model for frequency clocks based on ITU-T G.781 recommendation