Heads up : IETF Last Call on "Auto Discovery VPN Problem Statement and Requirements"

"Adrian Farrel" <adrian@olddog.co.uk> Fri, 07 June 2013 14:31 UTC

From: Adrian Farrel <adrian@olddog.co.uk>
To: l2vpn@ietf.org, l3vpn@ietf.org, mpls@ietf.org, pwe3@ietf.org, idr@ietf.org
Subject: Heads up : IETF Last Call on "Auto Discovery VPN Problem Statement and Requirements"
Date: Fri, 07 Jun 2013 15:30:59 +0100
Message-ID: <0afa01ce638b$a2067820$e6136860$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: Ac5ji41bX64WTevZT8eVu8We0gvrYQ==
Content-Language: en-gb
Cc: draft-ietf-ipsecme-ad-vpn-problem.all@tools.ietf.org
Precedence: list
Reply-To: adrian@olddog.co.uk

Hi VPN-related working groups,

Please be aware of this document that is in IETF last call.

Comments should be sent following the instructions in the email below and *not*
to the mailing lists I have spammed.

Thanks,
Adrian

> -----Original Message-----
> From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-
> bounces@ietf.org] On Behalf Of The IESG
> Sent: 07 June 2013 15:00
> To: IETF-Announce
> Cc: ipsec@ietf.org
> Subject: Last Call: <draft-ietf-ipsecme-ad-vpn-problem-07.txt> (Auto Discovery
> VPN Problem Statement and Requirements) to Informational RFC
> 
> 
> The IESG has received a request from the IP Security Maintenance and
> Extensions WG (ipsecme) to consider the following document:
> - 'Auto Discovery VPN Problem Statement and Requirements'
>   <draft-ietf-ipsecme-ad-vpn-problem-07.txt> as Informational RFC
> 
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2013-06-21. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
> 
> Abstract
> 
> 
>    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 address of endpoints change
>    or the endpoints may be behind NAT gateways, making static
>    configuration impossible.  The Auto Discovery VPN solution will
>    address these requirements.
> 
> 
> 
> 
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-ipsecme-ad-vpn-problem/
> 
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-ipsecme-ad-vpn-problem/ballot/
> 
> 
> No IPR declarations have been submitted directly on this I-D.

Heads up : IETF Last Call on "Auto Discovery VPN … Adrian Farrel