[Git][NTPsec/ntpsec][master] 2 commits: More NTS requirements.

[Eric S. Raymond]

Eric S. Raymond pushed to branch master at NTPsec / ntpsec


Commits:
ef27cff7 by Eric S. Raymond at 2019-01-06T15:07:45Z
More NTS requirements.

- - - - -
aacec42a by Eric S. Raymond at 2019-01-06T19:23:20Z
Give the agents names.

- - - - -


1 changed file:

- devel/nts.adoc


Changes:

=====================================
devel/nts.adoc
=====================================
@@ -1,9 +1,22 @@
 = NTS support specification =
 
-The relevant RFC draft is
+== Cisco's Statement of Work requirements ==
 
-https://tools.ietf.org/html/draft-ietf-ntp-using-nts-for-ntp
+The NTS implementation shall:
 
+* Use OpenSSL 1.1.1 for its crypto functions.
+
+* Address RFC5705 Keying Material Exporting and AES_SIV (RFC5297) code
+  support which may not be natively supported in OpenSSL.
+
+* Comply with the standardized specification of NTS
+  https://tools.ietf.org/html/draft-ietf-ntp-using-nts-for-ntp
+
+* Be interoperable with the other reference implementations in IETF hackathons.
+
+== System Partitioning ==
+
+Hal wrote:
 > My understanding is that there are to be four agents: the client ntpd, a NTS
 > symbiont communicating locally with the client ntpd, the server ntpd, and a
 > symbiont communicating locally with the server ntpd.
@@ -16,17 +29,21 @@ https://tools.ietf.org/html/draft-ietf-ntp-using-nts-for-ntp
 
 4 boxes.  My ASCII art is weak.  C for client, S for server.
 
-   NTS-C----NTS-S
-      |                  |
-   NTP-C----NTP-S
+   Bravo                       Delta
+   NTS client ---------------- NTS server
+      |                         |
+   Alpha                       Charlie
+   NTP client ---------------- NTP server
 
-NTS-C-NTS-S is our stuff in TLS over TCP.  Everything we need to know is in
-the draft.  It's pretty simple.
+NTS-C-NTS-S (Bravo to Delta and back) is our stuff in TLS over TCP.
+Everything we need to know is in the draft.  It's pretty simple.
 
-NTP-C to NTS-C is pretty simple.  NTP sends host name, or something like that.
- It gets back an IP Address (maybe more than 1) and a bunch of cookies.
+NTP-C to NTS-C (Bravo to Alpha) is pretty simple.  NTP sends host
+name, or something like that.  It gets back an IP Address (maybe more
+than 1) and a bunch of cookies.
 
-NTP-S to NTS-S Is only an occasional ?????.  I don't have the right word
-handy.  It's whatever is needed to verify the cookie from the NTP-C.
+NTP-S to NTS-S (Charlie to Delta) Is only an occasional ?????.  I
+don't have the right word handy.  It's whatever is needed to verify
+the cookie from Alpha.
 
-NTP-C to NTP-S is in the draft.
+NTP-C to NTP-S (Alpha to Charlie) is in the draft.



View it on GitLab: https://gitlab.com/NTPsec/ntpsec/compare/6359280cee85b6b78313f69fca51a030a821fffa...aacec42a3442d0b0c618505e56430230ea52fd87

-- 
View it on GitLab: https://gitlab.com/NTPsec/ntpsec/compare/6359280cee85b6b78313f69fca51a030a821fffa...aacec42a3442d0b0c618505e56430230ea52fd87
You're receiving this email because of your account on gitlab.com.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ntpsec.org/pipermail/vc/attachments/20190106/4681b328/attachment-0001.html>