Update docs owned by Research Team #95
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lukevalenta
changed the title
wbl
approved these changes
Oct 15, 2020
wbl
left a comment
wbl
left a comment
There was a problem hiding this comment.
Looks good, but two or three little nits I noticed.
| --- | ||
|
|
||
| # How Access Workers | ||
| # How Access Works |
Contributor
Author
There was a problem hiding this comment.
Yeah, I'll ping Access team to see if they want me to keep this typo fix in this PR 👍
| The NTS protocol is divided into two-phases. The first phase is the NTS key exchange that establishes the necessary key material between the NTP client and the server. This phase uses the Transport Layer Security (TLS) handshake and relies on the same public key infrastructure as the web. Once the keys are exchanged, the TLS channel is closed and the protocol enters the second phase. In this phase the results of that TLS handshake are used to authenticate NTP time synchronization packets via extension fields. For more information, read the [Internet draft](https://tools.ietf.org/html/draft-ietf-ntp-using-nts-for-ntp-19). | ||
| Network Time Security (NTS) provides cryptographic security for the client-server mode of the Network Time Protocol (NTP). This enables users to obtain time in an authenticated manner. | ||
|
|
||
| The NTS protocol is divided into two-phases. The first phase is the NTS key exchange that establishes the necessary key material between the NTP client and the server. This phase uses the Transport Layer Security (TLS) handshake and relies on the same public key infrastructure as the web. Once the keys are exchanged, the TLS channel is closed and the protocol enters the second phase. In this phase the results of that TLS handshake are used to authenticate NTP time synchronization packets via extension fields. For more information, read the [Internet draft](https://tools.ietf.org/html/draft-ietf-ntp-using-nts-for-ntp-19). |
There was a problem hiding this comment.
I should have changed this to be RFC 8915 already https://tools.ietf.org/html/rfc8915
|
|
||
| ## NTS Client | ||
|
|
||
| You can use time.cloudflare.com as the source of time for all your devices today with NTP, while NTS clients are still under development. |
There was a problem hiding this comment.
Chrony now has support, so maybe we need to change this.
Update distributed-web, randomness-beacon, and time-services developer docs
Contributor
|
This looks really rad. Thank you! Please address the conflicts and I’d be happy to merge this in. |
Deploying cloudflare-docs with
|
| Latest commit: |
d1182f5
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://889d1411.cloudflare-docs-7ou.pages.dev |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Update distributed-web, randomness-beacon, and time-services developer docs