Authenticated Chunks for the Stream Control Transmission Protocol (SCTP) bis
draft-nagesh-sctp-auth-4895bis-00

Document Type Active Internet-Draft (individual)
Last updated 2019-07-22
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized 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)
tsvwg                                                    N. Shamnur, Ed.
Internet-Draft                                                    Huawei
Obsoletes: 4895 (if approved)                              July 21, 2019
Updates: 4895 (if approved)
Intended status: Standards Track
Expires: January 22, 2020

Authenticated Chunks for the Stream Control Transmission Protocol (SCTP)
                                  bis
                   draft-nagesh-sctp-auth-4895bis-00

Abstract

   This document obsoletes RFC4895 if approved.  This document describes
   a new chunk type, several parameters, and procedures for the Stream
   Control Transmission Protocol (SCTP).  This new chunk type can be
   used to authenticate SCTP chunks by using shared keys between the
   sender and receiver.  The new parameters are used to establish the
   shared keys.

   This document describes the limitations with the current SCTP AUTH
   RFC4895 and thus enhances the document to resolve such ambiguities
   and thus strengthen the overall AUTH procedure.

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 January 22, 2020.

Copyright Notice

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

Shamnur                 Expires January 22, 2020                [Page 1]
Internet-Draft      Authenticated Chunks for SCTP bis          July 2019

   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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Conventions . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  New Parameter Types . . . . . . . . . . . . . . . . . . . . .   4
     3.1.  Random Parameter (RANDOM) . . . . . . . . . . . . . . . .   4
     3.2.  Chunk List Parameter (CHUNKS) . . . . . . . . . . . . . .   5
     3.3.  Requested HMAC Algorithm Parameter (HMAC-ALGO)  . . . . .   6
     3.4.  Supported Extensions Parameter  . . . . . . . . . . . . .   7
   4.  New Error Cause . . . . . . . . . . . . . . . . . . . . . . .   7
     4.1.  Unsupported HMAC Identifier Error Cause . . . . . . . . .   8
   5.  New Chunk Type  . . . . . . . . . . . . . . . . . . . . . . .   8
     5.1.  Authentication Chunk (AUTH) . . . . . . . . . . . . . . .   9
   6.  Procedures  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     6.1.  Establishment of an Association Shared Key  . . . . . . .  10
     6.2.  Negotiation of Auth Procedure . . . . . . . . . . . . . .  11
       6.2.1.  Receiving INIT containing AUTH parameters when AUTH
               extension is not supported  . . . . . . . . . . . . .  12
       6.2.2.  Receiving INIT-ACK without AUTH parameters when AUTH
               extension was sent in INIT chunk  . . . . . . . . . .  12
       6.2.3.  Receiving INIT without AUTH parameters when AUTH is
               supported locally . . . . . . . . . . . . . . . . . .  12
     6.3.  Association Initialization Collision  . . . . . . . . . .  12
     6.4.  Sending Authenticated Chunks  . . . . . . . . . . . . . .  12
     6.5.  Receiving Authenticated Chunks  . . . . . . . . . . . . .  13
   7.  Examples  . . . . . . . . . . . . . . . . . . . . . . . . . .  15
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  16
     8.1.  A New Chunk Type  . . . . . . . . . . . . . . . . . . . .  16
     8.2.  Three New Parameter Types . . . . . . . . . . . . . . . .  17
     8.3.  A New Error Cause . . . . . . . . . . . . . . . . . . . .  17
     8.4.  A New Table for HMAC Identifiers  . . . . . . . . . . . .  17
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .  18
   10. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  19
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .  19
     11.1.  Normative References . . . . . . . . . . . . . . . . . .  19
Show full document text