SHA-2 Algorithm for the TCP Authentication Option (TCP-AO)
draft-nayak-tcp-sha2-03

Document Type Active Internet-Draft (individual)
Last updated 2018-12-11
Stream (None)
Intended RFC status (None)
Formats plain text 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)
TCP Maintenance (TCPM)                                   A. Sujeet Nayak
Internet-Draft                                                   B. Weis
Intended status: Standards Track                           Cisco Systems
Expires: June 14, 2019                                 December 11, 2018

       SHA-2 Algorithm for the TCP Authentication Option (TCP-AO)
                        draft-nayak-tcp-sha2-03

Abstract

   The TCP Authentication Option (TCP-AO) relies on security algorithms
   to provide connection authentication between the two end-points.
   This document specifies how to use SHA-256 algorithm and attributes
   with TCP-AO.

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 June 14, 2019.

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
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Sujeet Nayak & Weis       Expires June 14, 2019                 [Page 1]
Internet-Draft         SHA-2 Algorithm for TCP-AO          December 2018

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Requirements  . . . . . . . . . . . . . . . . . . . . . . . .   2
     2.1.  Requirements Language . . . . . . . . . . . . . . . . . .   2
     2.2.  Algorithm Requirements  . . . . . . . . . . . . . . . . .   3
   3.  Algorithms Specified  . . . . . . . . . . . . . . . . . . . .   3
     3.1.  Key Derivation Functions (KDF)  . . . . . . . . . . . . .   3
       3.1.1.  KDF_HMAC_SHA256 . . . . . . . . . . . . . . . . . . .   4
       3.1.2.  Tips for User Interfaces Regarding KDFs . . . . . . .   4
     3.2.  MAC Algorithm . . . . . . . . . . . . . . . . . . . . . .   5
       3.2.1.  The Use of HMAC-SHA256-128  . . . . . . . . . . . . .   5
   4.  Interaction with TCP  . . . . . . . . . . . . . . . . . . . .   6
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   7
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   7
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   [RFC5925] describes TCP-AO mechanism to provide cryptographic
   authentication and message integrity verification between two end-
   points of a TCP connection.  [RFC5926] specifies HMAC-SHA-1-96 and
   AES-128-CMAC-96 message authentication codes (MACs) algorithms for
   TCP-AO.

   Although SHA-1 is considered safe for non-digital signature
   applications at the time of this writing [NIST-SP800-131A], there is
   a naturally growing demand, especially from the government and
   service provider community, for protecting their TCP sessions with
   SHA-2 family of authentication algorithms, which is considered to be
   relatively stronger.  SHA-256, being widely preferred and deployed,
   provides a reasonable alternative with stronger algorithm and larger
   MAC length.

   This document specifies usage of SHA-256 MAC algorithm on TCP-AO
   enabled connections.  It is a companion to [RFC5925] and [RFC5926].

2.  Requirements

2.1.  Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

Sujeet Nayak & Weis       Expires June 14, 2019                 [Page 2]
Internet-Draft         SHA-2 Algorithm for TCP-AO          December 2018

   When used in lowercase, these words convey their typical use in
   common language, and they are not to be interpreted as described in
Show full document text