Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ST2110 PTP domain should not be optional #25

Open
jonvmey opened this issue Jan 27, 2020 · 0 comments · Fixed by AMWA-TV/sdpoker#5
Open

ST2110 PTP domain should not be optional #25

jonvmey opened this issue Jan 27, 2020 · 0 comments · Fixed by AMWA-TV/sdpoker#5

Comments

@jonvmey
Copy link

jonvmey commented Jan 27, 2020

According to ST2110-10:2017 Section 8.2:

Devices which are referenced to IEEE1588-2008 shall use the ts-refclk:ptp form, signaling either the grandmaster clockIdentity and domain, or signaling that the PTP is traceable (if it is).

From that it would seem to me that including the PTP domain is not optional when not using the traceable form of the ts-refclk attribute for ST2110 streams. The current ST2110 PTP checking permits the domain to be an optional field as it's optional within RFC7273.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant