draft-gleeson-vpn-framework-01.txt
Bryan Gleeson <BGleeson@shastanets.com> Tue, 02 March 1999 06:06 UTC
Received: from portal.ex.tis.com (portal.ex.tis.com [192.94.214.101]) by mail.proper.com (8.8.8/8.8.5) with ESMTP id WAA02587; Mon, 1 Mar 1999 22:06:59 -0800 (PST)
Received: by portal.ex.tis.com (8.9.1/8.9.1) id WAA16559 for ipsec-outgoing; Mon, 1 Mar 1999 22:35:41 -0500 (EST)
Message-ID: <EBE4A6EB7EB0D1118D1C00A0C98313328BC1EF@shasta-pc.shastanets.com>
From: Bryan Gleeson <BGleeson@shastanets.com>
To: vpn@BayNetworks.COM
Cc: l2tp@ipsec.org, ipsec@tis.com, mpls@uu.net
Subject: draft-gleeson-vpn-framework-01.txt
Date: Mon, 01 Mar 1999 19:54:34 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain; charset="iso-8859-1"
Sender: owner-ipsec@ex.tis.com
Precedence: bulk
The draft "A Framework for IP based Virtual Private Networks" <draft-gleeson-vpn-framework-01.txt> has been updated. It is available at http://www.shastanets.com/company/PDFs/draft-gleeson-vpn-framework-01.txt and should shortly be available in the Internet Draft directories. It has been updated to reflect and reference some of the vpn related work done since the previous version, notably the VPN-ID draft <now draft-ietf-ion-vpn-id-00.txt>, and a number of specific VPN proposals (a number of which were presented at the last IETF). It also covers extranets and discusses the issues surounding voluntary tunneling in considerably more detail. As before, the intent is that this should provide a framework for discussion of the vpn related standards work needed by the IETF. Unfortunately there is no VPN WG as such in which to discuss the draft and some of the issues it raises, however we intend to submit the draft for publication as an Informational RFC, and would welcome any comments anyone may have. One issue in particular that is raised in the draft and that has been the focus of some recent L2TP/IPSEC mailing list activity is that of the the protocol stack to be used for secure remote access using voluntary tunneling (i.e. choice of PPP/L2TP/UDP/IPSEC/IP, or IPSEC/IP with the "xauth" extensions, or PPP directly over IPSEC, or perhaps some other combination). Right now there are quite a number of proprietary client solutions commercially available, so this area is one that would certainly benefit from some work in order to allow for interoperable implementations. Bryan Gleeson Shasta Networks
- draft-gleeson-vpn-framework-01.txt Bryan Gleeson