Although I prefer it over some of the other names, discovery isn't making
too good an adjective here. How about Dynamic Secure VPN without over
qualifying dynamic ?
Thanks,
Manish
On 19/03/12 1:27 PM, Yoav Nir y...@checkpoint.com wrote:
As Tero pointed out, some of the use cases don't end up
Yoav == Yoav Nir y...@checkpoint.com writes:
Yoav As Tero pointed out, some of the use cases don't end up in a
Yoav full mesh, because sometimes administrators really want a
Yoav trunk, so the end result could be a mesh among nodes in the
Yoav same organization, and a trunk to
I agree that the meshing becomes messy. And thus, Yoav's comment on partial
mesh and such is valid.
Since the topology is, in my view, based on the use cases and the problem
statement as I have understood them, a somewhat nebulous thing, I would offer
up a very simple term for the goal:
] P2P VPN draft UNCLASSIFIED
I agree that the meshing becomes messy. And thus, Yoav's comment on partial
mesh and such is valid.
Since the topology is, in my view, based on the use cases and the problem
statement as I have understood them, a somewhat nebulous thing, I would offer
up a very
To: IPsecme WG
Subject: Re: [IPsec] P2P VPN draft UNCLASSIFIED
I agree that the meshing becomes messy. And thus, Yoav's comment on partial
mesh and such is valid.
Since the topology is, in my view, based on the use cases and the problem
statement as I have understood them, a somewhat nebulous thing, I
#part sign=pgpmime
Paul == Paul Hoffman paul.hoff...@vpnc.org writes:
Interesting. I always considered the requirement of a trust
relationship of some kind an inherent part of VPN (of any kind,
SSL, IPsec or otherwise), and assumed most people did.
Paul Mark, meet Michael
Paul == Paul Wouters p...@cypherpunks.ca writes:
Few of my suggestions here
1.) Cut through VPN 2.) Auto mesh VPN
Paul Coming from FreeS/WAN and Openswan, I'm tempted to call it
Paul OEVPN, where OE stands for Opportunistc Encryption.
It's not Opportunistic.
It's
On Wed, 14 Mar 2012, Michael Richardson wrote:
Paul == Paul Wouters p...@cypherpunks.ca writes:
Few of my suggestions here
1.) Cut through VPN 2.) Auto mesh VPN
Paul Coming from FreeS/WAN and Openswan, I'm tempted to call it
Paul OEVPN, where OE stands for Opportunistc
On Mar 14, 2012, at 11:20 AM, Paul Wouters wrote:
Guess that's what I get for not fully reading the doument yet.
A note to everyone: reading the document sooner rather than later will help
make our hour in Paris much more useful.
I assumed
P2P actually meant peer to peer which kinda assumes
...@cesg.gsi.gov.uk
Subject: Re: [IPsec] P2P VPN draft UNCLASSIFIED
Of course, you're right. The acronym DMVPN makes this a very bad choice. Thanks
for pointing that out.
I'll throw out a few ideas here:
Dynamic Direct VPN (DDVPN)
Shortcut VPN (SVPN)
Dynamic Scalable VPN (DSVPN)
Dynamic Efficient VPN (DEVPN
: ipsec@ietf.org; chris.ulli...@cesg.gsi.gov.uk
Subject: Re: [IPsec] P2P VPN draft UNCLASSIFIED
Steve,
I do not think changing the name to Dynamic Mesh VPN is a good idea.
The first thing that is going to happen is that it is going to be
shortened to DMVPN and then we have conflict
...@cesg.gsi.gov.ukmailto:chris.ulli...@cesg.gsi.gov.uk
Subject: Re: [IPsec] P2P VPN draft UNCLASSIFIED
Of course, you're right. The acronym DMVPN makes this a very bad choice. Thanks
for pointing that out.
I'll throw out a few ideas here:
Dynamic Direct VPN (DDVPN)
Shortcut VPN (SVPN)
Dynamic
[mailto:ipsec-boun...@ietf.org] On Behalf
Of Ulliott, Chris
Sent: Wednesday, March 07, 2012 4:53 PM
To: 'ipsec@ietf.org'
Subject: Re: [IPsec] P2P VPN draft UNCLASSIFIED
Classification:UNCLASSIFIED
How about dynamic mesh VPNs as a title as I think the dynamic part is
key here and probably
.
Thanks,
Steve
-Original Message-
From: Mike Sullenberger [mailto:m...@cisco.com]
Sent: Monday, March 12, 2012 6:57 PM
To: Stephen Hanna
Cc: ipsec@ietf.org; chris.ulli...@cesg.gsi.gov.uk
Subject: Re: [IPsec] P2P VPN draft UNCLASSIFIED
Steve,
I do not think changing the name
, Chris [mailto:chris.ulli...@cesg.gsi.gov.uk]
Sent: Monday, March 12, 2012 7:16 PM
To: 'm...@cisco.com'; Stephen Hanna
Cc: 'ipsec@ietf.org'
Subject: Re: [IPsec] P2P VPN draft UNCLASSIFIED
Classification:UNCLASSIFIED
Good catch!
I've also thought of an additional use case, as I extend
Classification:UNCLASSIFIED
How about dynamic mesh VPNs as a title as I think the dynamic part is key
here and probably an important aspect of the use cases.
Chris
[This message has been sent by a mobile device]
- Original Message -
From: Yaron Sheffer [mailto:yaronf.i...@gmail.com]
Fine with me.
Yaron
On 03/07/2012 11:52 PM, Ulliott, Chris wrote:
Classification:UNCLASSIFIED
How about dynamic mesh VPNs as a title as I think the dynamic part is key
here and probably an important aspect of the use cases.
Chris
[This message has been sent by a mobile device]
Sent: Wednesday, March 07, 2012 4:53 PM
To: 'ipsec@ietf.org'
Subject: Re: [IPsec] P2P VPN draft UNCLASSIFIED
Classification:UNCLASSIFIED
How about dynamic mesh VPNs as a title as I think the dynamic part is
key here and probably an important aspect of the use cases.
Chris
18 matches
Mail list logo
