Informational RFC to be: draft-touch-ipsec-vpn-05.txt

[RFC Editor <rfc-editor@rfc-editor.org>]

IESG,

This RFC-to-be was submitted to the RFC Editor to be published as
Informational: draft-touch-ipsec-vpn-05.txt


Four week timeout is initiated (22 July 2003).


            Use of IPsec Transport Mode for Dynamic Routing

   This document addresses the use of IPsec to secure the links of a
   virtual (private) network (VN/VPN). It describes how virtual links
   established by IPsec tunnel mode conflict with routing and
   forwarding inside the VN, due to the IP routing dependence on
   references to interfaces and next-hop IP addresses.

   This document proposes a solution, called IIPtran, in which IPIP
   encapsulation separate from IPsec is used together with transport-
   mode IPsec. IPIP tunnel encapsulation occurs as a separate initial
   step, based on a forwarding lookup of the VN packet. After the
   forwarding lookup, IPsec transport mode processes the resulting
   (tunneled) IP packet with an SA determined through a security
   association database (SAD) match on the tunnel header.

   IIPtran supports dynamic routing inside the VN without changes to
   the current IPsec architecture, by establishing a complete virtual 
   topology with IPIP tunnels that supports static and dynamic
   routing, and then securing it with IPsec transport mode.

   The document also discusses how IIPtran compares to several
   alternative mechanisms for VN routing, and their respective impact
   on IPsec, routing, policy enforcement and interactions with the
   Internet Key Exchange (IKE), among other issues.

   This document is a product of the X-Bone and DynaBone projects at
   USC/ISI [N5][N8]. Comments are solicited and should be addressed to
   the authors.


Please note that the RFC Editor will work with the authors to shorten
the Abstract prior to publication.

Sincerely,

Sandy Ginoza - USC/ISI
Request for Comments Documents