[IPsec] RFC 7018 on Auto-Discovery VPN Problem Statement and Requirements
rfc-editor@rfc-editor.org Wed, 04 September 2013 23:25 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ipsec@ietfa.amsl.com
Delivered-To: ipsec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F93911E81FB; Wed, 4 Sep 2013 16:25:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.262
X-Spam-Level:
X-Spam-Status: No, score=-102.262 tagged_above=-999 required=5 tests=[AWL=0.338, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qJCJlFIVMMFX; Wed, 4 Sep 2013 16:25:34 -0700 (PDT)
Received: from rfc-editor.org (unknown [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 07C5A11E820B; Wed, 4 Sep 2013 16:25:22 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 060E08E01F; Wed, 4 Sep 2013 16:19:42 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20130904231942.060E08E01F@rfc-editor.org>
Date: Wed, 04 Sep 2013 16:19:42 -0700
Cc: ipsec@ietf.org, drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
Subject: [IPsec] RFC 7018 on Auto-Discovery VPN Problem Statement and Requirements
X-BeenThere: ipsec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Discussion of IPsec protocols <ipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipsec>, <mailto:ipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipsec>
List-Post: <mailto:ipsec@ietf.org>
List-Help: <mailto:ipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipsec>, <mailto:ipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Sep 2013 23:25:34 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7018
Title: Auto-Discovery VPN Problem Statement and
Requirements
Author: V. Manral, S. Hanna
Status: Informational
Stream: IETF
Date: September 2013
Mailbox: vishwas.manral@hp.com,
shanna@juniper.net
Pages: 12
Characters: 27284
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-ipsecme-ad-vpn-problem-09.txt
URL: http://www.rfc-editor.org/rfc/rfc7018.txt
This document describes the problem of enabling a large number of
systems to communicate directly using IPsec to protect the traffic
between them. It then expands on the requirements for such a
solution.
Manual configuration of all possible tunnels is too cumbersome in
many such cases. In other cases, the IP addresses of endpoints
change, or the endpoints may be behind NAT gateways, making static
configuration impossible. The Auto-Discovery VPN solution will
address these requirements.
This document is a product of the IP Security Maintenance and Extensions Working Group of the IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
http://www.ietf.org/mailman/listinfo/ietf-announce
http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see http://www.rfc-editor.org/search/rfc_search.php
For downloading RFCs, see http://www.rfc-editor.org/rfc.html
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC