simple VPN solution using Multi-point Security Association
draft-yamaya-ipsecme-mpsa-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2013-02-18
Stream (None)
Intended RFC status (None)
Formats 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)
IP Security Maintenance and Extensions                   A. Yamaya, Ed.
(ipsecme)                                                       K. Ueki
Internet-Draft                                                 T. Murai
Intended status: Informational          Furukawa Network Solution Corp.
Expires: August 18, 2013                              February 18, 2013

         simple VPN solution using Multi-point Security Association
                    draft-yamaya-ipsecme-mpsa-00.txt

Abstract
   This document describes the over-lay network solution by utilizing 
   dynamically established IPsec multi-point Security Association (SA)
   without individual connection.
   
   Multi-point SA technology provides the simplified mechanism of the 
   Auto Discovery and Configuration function. 
   This is applicable for any IPsec tunnels such as IPv4 over IPv4, 
   IPv4 over IPv6, IPv6 over IPv4 and IPv6 over IPv6.
   

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  August 18, 2013.

Copyright Notice

   Copyright (c) 2013 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 . . . . . . . . . . . . . . . . . . . . . . . . .  
     1.1  Terminology . . . . . . . . . . . . . . . . . . . . . . . .
   2.  Motivation   . . . . . . . . . . . . . . . . . . . . . . . . .  
   3.  Procedure  . . . . . . . . . . . . . . . . . . . . . . . . . . 
     3.1.  Sequence . . . . . . . . . . . . . . . . . . . . . . . . .
     3.2.  Extended Format  . . . . . . . . . . . . . . . . . . . . .
     3.2.1 Vendor ID  . . . . . . . . . . . . . . . . . . . . . . . . 
     3.2.2 MPSA_PUT   . . . . . . . . . . . . . . . . . . . . . . . .
     3.3   Multi-point SA Management  . . . . . . . . . . . . . . . .
     3.3.1 Gateway  . . . . . . . . . . . . . . . . . . . . . . . . .
     3.3.2 Endpoint . . . . . . . . . . . . . . . . . . . . . . . . .
     3.3.3 Rekeying   . . . . . . . . . . . . . . . . . . . . . . . . 
     3.4.  Forwarding . . . . . . . . . . . . . . . . . . . . . . . .
   4.  Security Considerations  . . . . . . . . . . . . . . . . . . .  
   5.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 
   6.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 
   7.   Normative References. . . . . . . . . . . . . . . . . . . . . 
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 
   

1. Introduction
   As described in the problem statement document[ad-vpn-problem], 
   dynamic, secure and scalable system for establishing SAs is needed.
  
   With multi-point SA, an endpoint automatically discovers other 
   endpoints. The endpoints also share a multi-point SA within the same 
   group, and there is no individual connection between them.
  
   It can avoid the exhaustive configuration for endpoints/ gateways. 
   No reconfiguration is needed when a new endpoint is added, removed, 
   or changed. It can avoid high load on the gateways.
    
 1.1.  Terminology   
   Multi-point SA - This is similar 
   to Dynamic Full Mesh topology described in [ad-vpn-problem]; 
   direct connections exist in a hub and spoke manner, but only one SA 
   for data transfer is shared with all endpoints.

2. Motivation
   There are two major topologies - Star topology and full-mesh topology - 
   to communicate securely on over-lay network by using IPsec. 
   
   Figure.1 shows star topology. The number of IPsec connection is the 
   same as the number of endpoints (EP). Authentication, Authorization 
   and Accounting (AAA) of each endpoint can be achieved on the gateway.
    
   The problem of the star topology is all the traffic go through the 
   gateway, then it causes high load and latency.  
Show full document text