Session Security Envelope
draft-moskowitz-sse-05

Document Type Active Internet-Draft (individual)
Last updated 2017-06-27
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)
SSE BOF                                                     R. Moskowitz
Internet-Draft                                            HTT Consulting
Intended status: Standards Track                             I. Faynberg
Expires: December 29, 2017                    Stargazers Consulting, LLC
                                                                   H. Lu
                                                                 Retired
                                                                S. Hares
                                                 Hickory Hill Consulting
                                                             P. Giacomin
                                                               FreeLance
                                                           June 27, 2017

                       Session Security Envelope
                         draft-moskowitz-sse-05

Abstract

   This memo specifies the details of the Session Security Envelope
   (SSE).  SSE is a session protocol aiming to guarantee
   confidentiality, integrity and authentication completely
   independently by the underlying context, namely network and transport
   layers.  A single session using the SEE protocol can include a single
   transport session or multiple transport sessions.  This mean that SSE
   can survive the break-down in network and transport layers or to
   attacks carried against them.  SSE is also applicable in networks
   lacking in classic inter-networking and transport protocols SSE
   relies on modern AEAD block cipher modes of operations, a class of
   block cipher modes which allows, at the same time, to authenticate
   the message while encrypting a part of it.

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 http://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 29, 2017.

Moskowitz, et al.       Expires December 29, 2017               [Page 1]
Internet-Draft          Session Security Envelope              June 2017

Copyright Notice

   Copyright (c) 2017 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
   (http://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.  Terms and Definitions . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Requirements Terminology  . . . . . . . . . . . . . . . .   3
     2.2.  Notations . . . . . . . . . . . . . . . . . . . . . . . .   3
     2.3.  Definitions . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  SSE Security Boundary . . . . . . . . . . . . . . . . . . . .   3
   4.  API . . . . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   5.  Packet format . . . . . . . . . . . . . . . . . . . . . . . .   5
     5.1.  SSE compact format  . . . . . . . . . . . . . . . . . . .   5
     5.2.  SSE Large Format  . . . . . . . . . . . . . . . . . . . .   6
     5.3.  SSE Extreme Format  . . . . . . . . . . . . . . . . . . .   7
     5.4.  Header Fields . . . . . . . . . . . . . . . . . . . . . .   8
     5.5.  AEAD integration  . . . . . . . . . . . . . . . . . . . .   9
   6.  Packet processing and State Machine . . . . . . . . . . . . .   9
     6.1.  Establishing a session  . . . . . . . . . . . . . . . . .   9
     6.2.  Processing Outgoing Application Data  . . . . . . . . . .   9
     6.3.  Processing Incoming Application Data  . . . . . . . . . .   9
   7.  Negotiating SSE . . . . . . . . . . . . . . . . . . . . . . .  10
     7.1.  Using IKEv2 . . . . . . . . . . . . . . . . . . . . . . .  10
     7.2.  Using HIP . . . . . . . . . . . . . . . . . . . . . . . .  10
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .  10
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  11
     10.1.  Normative References . . . . . . . . . . . . . . . . . .  11
Show full document text