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
Transfer time synchronisation scenarios into requirements (1:C.2.5 S) #150
Comments
@JavierEspina, @ToddCooper, @MartinKasp, @PeterKranich: I know that this is not strictly an SDC problem, but I belive it is central to making any system work properly. Please provide feedback to the linked issues as soon as possible. |
Added to Lübeck Discussion. May be in 1.1 or 1.2. |
* #151 add labeling requirements for ntp server configuration * Update CHANGELOG.md Co-authored-by: David Gregorczyk <54440227+d-gregorczyk@users.noreply.github.com> * Update asciidoc/volume1/use-cases/tf1-ch-c-use-case-stad.adoc Co-authored-by: David Gregorczyk <54440227+d-gregorczyk@users.noreply.github.com> * Update asciidoc/volume1/use-cases/tf1-ch-c-use-case-stad.adoc Co-authored-by: David Gregorczyk <54440227+d-gregorczyk@users.noreply.github.com> * Update asciidoc/volume1/use-cases/tf1-ch-c-use-case-stad.adoc Co-authored-by: David Gregorczyk <54440227+d-gregorczyk@users.noreply.github.com> * #150 fix notes for R1520 --------- Co-authored-by: David Gregorczyk <54440227+d-gregorczyk@users.noreply.github.com>
@ToddCooper: From my perspective, this can be closed. Could you double check? I'll add new, more specific ones for the results of the workshop discussions. |
@ToddCooper: Is there anything I've missed or can this be closed? |
In SDPi time synchronisation is a bit of an edge case, since it does not need SDC transactions to be specified. However, since we need ntp to work for all of our use cases, we have to make sure that enough content is provided for time synchronisation to work (e.g. define precision of the clock, how to handle connection loss).
The text was updated successfully, but these errors were encountered: