TLS 1.3 Authentication and Integrity only Ciphersuites
draft-camwinget-tls-ts13-macciphersuites-00

Document Type Active Internet-Draft (individual)
Last updated 2018-06-28
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
TLS                                                        N. Cam-Winget
Internet-Draft                                             Cisco Systems
Intended status: Informational                                 J. Visoky
Expires: December 30, 2018                                          ODVA
                                                           June 28, 2018

         TLS 1.3 Authentication and Integrity only Ciphersuites
              draft-camwinget-tls-ts13-macciphersuites-00

Abstract

   There are use cases, specifically in Internet of Things (IoT) and
   constrained environments that do not require confidentiality, though
   mutual authentication during tunnel establishment and message
   integrity is still mandated.  This document defines the use of HMAC
   only as ciphersuites in TLS 1.3.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on December 30, 2018.

Copyright Notice

   Copyright (c) 2018 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of

Cam-Winget & Visoky     Expires December 30, 2018               [Page 1]
Internet-Draft                 IoT Ciphers                     June 2018

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Applicability Statement . . . . . . . . . . . . . . . . . . .   3
   4.  Using Integrity only Cipher Suites  . . . . . . . . . . . . .   4
   5.  Record Payload Protection for Integrity only Cipher Suites  .   4
   6.  Key Schedule when using Integrity only Cipher Suites  . . . .   5
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   8.  Security and Privacy Considerations . . . . . . . . . . . . .   5
   9.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   5
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     10.1.  Normative References . . . . . . . . . . . . . . . . . .   6
     10.2.  Informative Reference  . . . . . . . . . . . . . . . . .   6
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   There are several use cases in which communications privacy is not
   strictly needed, although authenticity of the communications
   transport is still very important.  For example, within the
   Industrial Automation space there could be TCP or UDP communications
   which command a robotic arm to move a certain distance at a certain
   speed.  Without authenticity guarantees an attacker could modify the
   packets to change the movement of the robotic arm, potentially
   causing physical damage.  However, the motion control commands are
   not considered to be sensitive information and thus there is no
   requirement to provide confidentiality.  Another IoT example with no
   strong requirement for confidentiality is the reporting of weather
   information; however, message authenticity is required to ensure
   integrity of the message..

   Besides having a strong need for authenticity and a weak need for
   confidentiality, many of these systems also have serious latency
   requirements.  Furthermore, several IoT devices (industrial or
   otherwise) have limited processing capability.  However, these IoT
   systems still gain great benefit from leveraging TLS 1.3 for secure
   communications.  Given the reduced need for confidentiality TLS 1.3
   [I-D.ietf-tls-tls13] cipher suites that maintain data integrity
   without confidentiality are described in this document.

Cam-Winget & Visoky     Expires December 30, 2018               [Page 2]
Internet-Draft                 IoT Ciphers                     June 2018

2.  Terminology

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
Show full document text