IP Traffic Flow Security Using Aggregation and Fragmentation
draft-ietf-ipsecme-iptfs-05

Document Type Active Internet-Draft (ipsecme WG)
Author Christian Hopps 
Last updated 2020-12-19
Replaces draft-hopps-ipsecme-iptfs
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf htmlized (tools) htmlized bibtex
Reviews
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                           C. Hopps
Internet-Draft                                   LabN Consulting, L.L.C.
Intended status: Standards Track                       December 20, 2020
Expires: June 23, 2021

      IP Traffic Flow Security Using Aggregation and Fragmentation
                      draft-ietf-ipsecme-iptfs-05

Abstract

   This document describes a mechanism to enhance IPsec traffic flow
   security by adding traffic flow confidentiality to encrypted IP
   encapsulated traffic.  Traffic flow confidentiality is provided by
   obscuring the size and frequency of IP traffic using a fixed-sized,
   constant-send-rate IPsec tunnel.  The solution allows for congestion
   control as well as non-constant send-rate usage.

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 23, 2021.

Copyright Notice

   Copyright (c) 2020 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

Hopps                     Expires June 23, 2021                 [Page 1]
Internet-Draft          IP Traffic Flow Security           December 2020

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

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Terminology & Concepts  . . . . . . . . . . . . . . . . .   3
   2.  The IP-TFS Tunnel . . . . . . . . . . . . . . . . . . . . . .   4
     2.1.  Tunnel Content  . . . . . . . . . . . . . . . . . . . . .   4
     2.2.  Payload Content . . . . . . . . . . . . . . . . . . . . .   5
       2.2.1.  Data Blocks . . . . . . . . . . . . . . . . . . . . .   6
       2.2.2.  No Implicit End Padding Required  . . . . . . . . . .   6
       2.2.3.  Fragmentation, Sequence Numbers and All-Pad Payloads    6
       2.2.4.  Empty Payload . . . . . . . . . . . . . . . . . . . .   7
       2.2.5.  IP Header Value Mapping . . . . . . . . . . . . . . .   8
       2.2.6.  IP Time-To-Live (TTL) and Tunnel errors . . . . . . .   8
       2.2.7.  Effective MTU of the Tunnel . . . . . . . . . . . . .   8
     2.3.  Exclusive SA Use  . . . . . . . . . . . . . . . . . . . .   8
     2.4.  Modes of Operation  . . . . . . . . . . . . . . . . . . .   9
       2.4.1.  Non-Congestion Controlled Mode  . . . . . . . . . . .   9
       2.4.2.  Congestion Controlled Mode  . . . . . . . . . . . . .   9
   3.  Congestion Information  . . . . . . . . . . . . . . . . . . .  10
     3.1.  ECN Support . . . . . . . . . . . . . . . . . . . . . . .  12
   4.  Configuration . . . . . . . . . . . . . . . . . . . . . . . .  12
     4.1.  Bandwidth . . . . . . . . . . . . . . . . . . . . . . . .  12
     4.2.  Fixed Packet Size . . . . . . . . . . . . . . . . . . . .  12
     4.3.  Congestion Control  . . . . . . . . . . . . . . . . . . .  12
   5.  IKEv2 . . . . . . . . . . . . . . . . . . . . . . . . . . . .  13
     5.1.  USE_AGGFRAG Notification Message  . . . . . . . . . . . .  13
   6.  Packet and Data Formats . . . . . . . . . . . . . . . . . . .  13
     6.1.  AGGFRAG_PAYLOAD Payload . . . . . . . . . . . . . . . . .  13
       6.1.1.  Non-Congestion Control AGGFRAG_PAYLOAD Payload Format  14
       6.1.2.  Congestion Control AGGFRAG_PAYLOAD Payload Format . .  15
       6.1.3.  Data Blocks . . . . . . . . . . . . . . . . . . . . .  16
       6.1.4.  IKEv2 USE_AGGFRAG Notification Message  . . . . . . .  18
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  19
     7.1.  AGGFRAG_PAYLOAD Sub-Type Registry . . . . . . . . . . . .  19
     7.2.  USE_AGGFRAG Notify Message Status Type  . . . . . . . . .  19
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  19
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  20
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .  20
     9.2.  Informative References  . . . . . . . . . . . . . . . . .  20
Show full document text