Re: [IPsec] Mesh VPN I-D (temporary name) - new author

2012-05-09 Thread Izaac
On Tue, May 08, 2012 at 11:22:07PM -0400, John Leser wrote: particular destination seems unworkable. It would be more reasonable, and probably more useful, for a client to automatically locate the nearest VPN server to itself (that alone would be an interesting and potentially useful

Re: [IPsec] Mesh VPN I-D (temporary name) - new author

2012-05-09 Thread Vishwas Manral
Hi Izaac/ John, Thanks for the great inputs you provide. I agree we may not see changes in the way packets would traverse the network in either the transport/ tunnel mode. Like you mention Routing in such topologies is an issue for sure (especially in the Hub and Spoke topology) and there are

[IPsec] Mesh VPN I-D (temporary name) - new author

2012-05-08 Thread Yaron Sheffer
Hi everybody, Vishwas Manral has agreed to join Steve Hanna as co-author of this draft, now at -00 ( http://tools.ietf.org/html/draft-ietf-ipsecme-p2p-vpn-problem-00). I'd like to thank them both. While Vishwas and Steve are busy working on the next version, feel free to read and comment

Re: [IPsec] Mesh VPN I-D (temporary name) - new author

2012-05-08 Thread Izaac
On Tue, May 08, 2012 at 10:46:24PM +0300, Yaron Sheffer wrote: While Vishwas and Steve are busy working on the next version, feel free to read and comment on the current version. In what way is this problem not addressed by transport mode, despite it's being far less commonly deployed? But

Re: [IPsec] Mesh VPN I-D (temporary name) - new author

2012-05-08 Thread John Leser
On 05/08/12 22:17, Izaac wrote: On Tue, May 08, 2012 at 10:46:24PM +0300, Yaron Sheffer wrote: While Vishwas and Steve are busy working on the next version, feel free to read and comment on the current version. In what way is this problem not addressed by transport mode, despite it's being