Geneve Security Requirements
draft-mglt-nvo3-geneve-security-requirements-04

Document Type Active Internet-Draft (individual)
Last updated 2018-10-12
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)
NVO3                                                          D. Migault
Internet-Draft                                                  Ericsson
Intended status: Informational                                S. Boutros
Expires: April 15, 2019                                         D. Wings
                                                            VMware, Inc.
                                                             S. Krishnan
                                                                  Kaloom
                                                        October 12, 2018

                      Geneve Security Requirements
            draft-mglt-nvo3-geneve-security-requirements-04

Abstract

   The document defines the security requirements to protect tenants
   overlay traffic against security threats from the NVO3 network
   components that are interconnected with tunnels implemented using
   Generic Network Virtualization Encapsulation (Geneve).

   The document provides two sets of security requirements: 1.
   requirements to evaluate the data plane security of a given
   deployment of Geneve overlay.  Such requirements are intended to
   Geneve overlay provider to evaluate a given deployment.
   2. requirement a security mechanism need to fulfill to secure any
   deployment of Geneve overlay deployment

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 April 15, 2019.

Migault, et al.          Expires April 15, 2019                 [Page 1]
Internet-Draft        Geneve Security Requirements          October 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
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Requirements Notation . . . . . . . . . . . . . . . . . . . .   2
   2.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   6
   4.  Security Threats  . . . . . . . . . . . . . . . . . . . . . .   6
     4.1.  Passive Attacks . . . . . . . . . . . . . . . . . . . . .   6
     4.2.  Active Attacks  . . . . . . . . . . . . . . . . . . . . .   7
   5.  Requirements for Security Mitigations . . . . . . . . . . . .   8
     5.1.  Protection Against Traffic Sniffing . . . . . . . . . . .   8
     5.2.  Protecting Against Traffic Injection  . . . . . . . . . .  10
     5.3.  Protecting Against Traffic Redirection  . . . . . . . . .  11
     5.4.  Protecting Against Traffic Replay . . . . . . . . . . . .  12
     5.5.  Security Management . . . . . . . . . . . . . . . . . . .  13
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  13
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  14
     7.1.  TLS . . . . . . . . . . . . . . . . . . . . . . . . . . .  14
     7.2.  IPsec . . . . . . . . . . . . . . . . . . . . . . . . . .  15
   8.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  15
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  15
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .  15
     9.2.  Informative References  . . . . . . . . . . . . . . . . .  16
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  17

1.  Requirements Notation

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described BCP 14
   [RFC2119] [RFC8174] when, and only when, they appear in all capitals,
   as shown here.

Migault, et al.          Expires April 15, 2019                 [Page 2]
Internet-Draft        Geneve Security Requirements          October 2018

2.  Introduction

   The network virtualization overlay over Layer 3 (NVO3) as depicted in
Show full document text