Hi Roland, To wrap up our exchange (I think)... On 7/6/2011 10:46 AM, Roland Bless wrote:
Hi Joe and all,
...
IMO, a VPN extends an existing network to add a new node, or ties two existing networks together, i.e., it's a way to add a single private link to a new node.Further, VPN nodes are always a member of exactly one VPN.Usually, yes, though one can think of VPN concentrators providing access to several different VPNs
Oh - yes. But hosts are generally attached to only one VPN at a time. VPN concentrators are a lot like virtual machine devices that emulate separate VPN "attachment" points. Ultimately, though, every end system is a member of only one VPN, which differentiates it from a VN, IMO.
What do you see is important for the RG right now or what is missing?See above, but maybe we should also consider questions such as what interfaces and protocols are needed for creating inter-provider virtual networks.That seems to presume we know what an intra-provider VN is, and I'm not sure we're all on a single page there... ;-)Ok, I meant a VN spanning several substrate providers (or to use 4WARD terminology: Infrastructure Providers - InPs) in contrast to a VN inside a single InP, which can be provided by using proprietary protocols.
Oh - certainly. A given VPN can be homogeneous or include hereogeneous components, and can either be internetworked (as IP goes over multiple link layers) or use gateways to translate between clouds (as the old Catenet did).
Joe
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.