idnits 2.17.1 draft-stenn-ntp-tcp-services-keyexchange-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (July 2, 2018) is 2119 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'RFC5905' is defined on line 115, but no explicit reference was found in the text == Unused Reference: 'RFC5906' is defined on line 120, but no explicit reference was found in the text ** Downref: Normative reference to an Informational RFC: RFC 5906 Summary: 1 error (**), 0 flaws (~~), 3 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force H. Stenn 3 Internet-Draft D. Mills 4 Intended status: Standards Track P. Prindeville 5 Expires: January 3, 2019 Network Time Foundation 6 July 2, 2018 8 Network Time Protocol: TCP Services: Key Exchange 9 draft-stenn-ntp-tcp-services-keyexchange-00 11 Abstract 13 This document describes the Key Exchange commands that are included 14 in the NTP TCP Services protocol, which is used to implement the 15 Secure Network Time protocol. 17 Status of This Memo 19 This Internet-Draft is submitted in full conformance with the 20 provisions of BCP 78 and BCP 79. 22 Internet-Drafts are working documents of the Internet Engineering 23 Task Force (IETF). Note that other groups may also distribute 24 working documents as Internet-Drafts. The list of current Internet- 25 Drafts is at https://datatracker.ietf.org/drafts/current/. 27 Internet-Drafts are draft documents valid for a maximum of six months 28 and may be updated, replaced, or obsoleted by other documents at any 29 time. It is inappropriate to use Internet-Drafts as reference 30 material or to cite them other than as "work in progress." 32 This Internet-Draft will expire on January 3, 2019. 34 Copyright Notice 36 Copyright (c) 2018 IETF Trust and the persons identified as the 37 document authors. All rights reserved. 39 This document is subject to BCP 78 and the IETF Trust's Legal 40 Provisions Relating to IETF Documents 41 (https://trustee.ietf.org/license-info) in effect on the date of 42 publication of this document. Please review these documents 43 carefully, as they describe your rights and restrictions with respect 44 to this document. Code Components extracted from this document must 45 include Simplified BSD License text as described in Section 4.e of 46 the Trust Legal Provisions and are provided without warranty as 47 described in the Simplified BSD License. 49 Table of Contents 51 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 52 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 2 53 2. NTP TCP Services: Key Exchange . . . . . . . . . . . . . . . 2 54 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 55 4. Security Considerations . . . . . . . . . . . . . . . . . . . 3 56 5. Normative References . . . . . . . . . . . . . . . . . . . . 3 57 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 3 59 1. Introduction 61 The NTP Secure Network Time proposal relies on the secure pre- 62 exchange of information to create and validate NTP MACs, 64 This secure pre-exchange is performed using NTP TCP Services. 66 This document describes that protocol. 68 1.1. Requirements Language 70 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 71 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 72 document are to be interpreted as described in RFC 2119 [RFC2119]. 74 2. NTP TCP Services: Key Exchange 76 To perform the key exchange for Secure Network Time, one side opens a 77 TCP connection to the other host, performs any initial handshake, and 78 SHOULD issue a STARTTLS directive to create a secure channel between 79 the two processes. 81 Once that has been done, ... 83 RFC 5705 [RFC5705] 85 RFC 7301 [RFC7301] 87 [Show how this works for Client/Server mode] 89 [Show how this works for symmetric mode] 91 [Show how this work for manycast/multicast] 93 [Show how this would work for broadcast mode where the client can 94 open a connection to the server] 96 3. IANA Considerations 98 TBD 100 4. Security Considerations 102 Additional information TBD 104 5. Normative References 106 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 107 Requirement Levels", BCP 14, RFC 2119, 108 DOI 10.17487/RFC2119, March 1997, 109 . 111 [RFC5705] Rescorla, E., "Keying Material Exporters for Transport 112 Layer Security (TLS)", RFC 5705, DOI 10.17487/RFC5705, 113 March 2010, . 115 [RFC5905] Mills, D., Martin, J., Ed., Burbank, J., and W. Kasch, 116 "Network Time Protocol Version 4: Protocol and Algorithms 117 Specification", RFC 5905, DOI 10.17487/RFC5905, June 2010, 118 . 120 [RFC5906] Haberman, B., Ed. and D. Mills, "Network Time Protocol 121 Version 4: Autokey Specification", RFC 5906, 122 DOI 10.17487/RFC5906, June 2010, 123 . 125 [RFC7301] Friedl, S., Popov, A., Langley, A., and E. Stephan, 126 "Transport Layer Security (TLS) Application-Layer Protocol 127 Negotiation Extension", RFC 7301, DOI 10.17487/RFC7301, 128 July 2014, . 130 Authors' Addresses 132 Harlan Stenn 133 Network Time Foundation 134 P.O. Box 918 135 Talent, OR 97540 136 US 138 Email: stenn@nwtime.org 139 David L. Mills 140 Network Time Foundation 141 P.O. Box 918 142 Talent, OR 97540 143 US 145 Email: mills@udel.edu 147 Philip Prindeville 148 Network Time Foundation 149 P.O. Box 918 150 Talent, OR 97540 151 US 153 Email: prindeville@ntp.org