Auto-Discovery VPN Problem Statement and Requirements
Draft of message to be sent after approval:
From: The IESG <email@example.com> To: IETF-Announce <firstname.lastname@example.org> Cc: RFC Editor <email@example.com>, ipsecme mailing list <firstname.lastname@example.org>, ipsecme chair <email@example.com> Subject: Document Action: 'Auto Discovery VPN Problem Statement and Requirements' to Informational RFC (draft-ietf-ipsecme-ad-vpn-problem-09.txt) The IESG has approved the following document: - 'Auto Discovery VPN Problem Statement and Requirements' (draft-ietf-ipsecme-ad-vpn-problem-09.txt) as Informational RFC This document is the product of the IP Security Maintenance and Extensions Working Group. The IESG contact persons are Sean Turner and Stephen Farrell. A URL of this Internet Draft is: http://datatracker.ietf.org/doc/draft-ietf-ipsecme-ad-vpn-problem/
Technical Summary The document lists the requirements and likely use cases for auto-discovery IPsec VPNs. These VPNs automate configuration when a very large number of hosts and networks must communicate over IPsec in environments where static configuration is not appropriate. There are already a number of proprietary solutions to this problem, and this document is meant as a precursor to the IETF possibly working on a standardized interoperable solution. Working Group Summary The document was reviewed by many people in the WG over many months and there is strong consensus to publish. There is one possible open issue from one WG participant, but that can be dealt with during IETF review. Document Quality It's a problem statement. Personnel Paul Hoffman is the document shepherd. Sean Turner is the responsible AD.