Auto Discovery VPN Problem Statement
draft-ietf-ipsecme-p2p-vpn-problem-01

The information below is for an old version of the document
Document Type Active Internet-Draft (ipsecme WG)
Last updated 2012-05-25
Replaces draft-nir-ipsecme-p2p
Replaced by RFC 7018, RFC 7018
Stream IETF
Intended RFC status (None)
Formats pdf htmlized bibtex
Stream WG state WG Document
Document shepherd None
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
IPsecME Working Group                                           S. Hanna
Internet-Draft                                                   Juniper
Intended status: Informational                                 V. Manral
Expires: November 26, 2012                                            HP
                                                            May 25, 2012

                  Auto Discovery VPN Problem Statement
                 draft-ietf-ipsecme-p2p-vpn-problem-01

Abstract

   This document describes the problem of enabling a large number of
   systems to communicate directly using IPsec to protect the traffic
   between them.  Manual configuration of all possible tunnels is too
   cumbersome in many such cases.  In other cases the IP address of end
   points change or the end points may be behind NAT gateways, making
   static configuration impossible.  The Auto Discovery VPN solution is
   chartered to address these requirements.

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 November 26, 2012.

Copyright Notice

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

Hanna & Manral          Expires November 26, 2012               [Page 1]

Internet-Draft    Auto Discovery VPN Problem Statement          May 2012

   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
     1.1.  Terminology  . . . . . . . . . . . . . . . . . . . . . . .  3
     1.2.  Conventions Used in This Document  . . . . . . . . . . . .  4
   2.  Use Cases  . . . . . . . . . . . . . . . . . . . . . . . . . .  5
     2.1.  Endpoint-to-Endpoint P2P VPN Use Case  . . . . . . . . . .  5
     2.2.  Gateway-to-Gateway AD VPN Use Case . . . . . . . . . . . .  5
     2.3.  Endpoint-to-Gateway AD VPN Use Case  . . . . . . . . . . .  6
   3.  Inadequacy of Existing Solutions . . . . . . . . . . . . . . .  7
     3.1.  Exhaustive Configuration . . . . . . . . . . . . . . . . .  7
     3.2.  Star Topology  . . . . . . . . . . . . . . . . . . . . . .  7
     3.3.  Proprietary Approaches . . . . . . . . . . . . . . . . . .  8
   4.  Requirements . . . . . . . . . . . . . . . . . . . . . . . . .  9
   5.  Security Considerations  . . . . . . . . . . . . . . . . . . . 10
   6.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 11
   7.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 12
   8.  Normative References . . . . . . . . . . . . . . . . . . . . . 13
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 14

Hanna & Manral          Expires November 26, 2012               [Page 2]

Internet-Draft    Auto Discovery VPN Problem Statement          May 2012

1.  Introduction

   IPsec [RFC4301] is used in several different cases, including tunnel-
   mode site-to-site VPNs and Remote Access VPNs.  Host to host
   communication employing transport mode also exists, but is far less
   commonly deployed.

   The subject of this document is the problem presented by large scale
   deployments of IPsec.  These may be a large collection of VPN
   gateways connecting various sites, a large number of remote endpoints
   connecting to a number of gateways or to each other, or a mix of the
   two.  The gateways and endpoints may belong to a single
   administrative domain or several domains with a trust relationship.

   Section 4.4 of RFC 4301 describes the major IPsec databases needed
   for IPsec processing.  It requires an extensive configuration for
   each tunnel, so manually configuring a system of many gateways and
   endpoints becomes infeasible and inflexible.
Show full document text