Subject: VPN4DC

From: "So, Ning" <[email-masked]>
Date: Tue, 4 Oct 2011 15:14:02 -0400

All,

I would like to start the conversation on the topic of VPN4DC since we are still working on the drafts (problem statement, requirements, and use case drafts).  Below is a very high level description of what we want to do.  The scope of work has been narrowed significantly if you have followed this work in OPSAWG before, so that we can better focus our attention to have forward progress.  Hopefully it can stir up some interests and additional participation and contributions.

The purpose of VPN4DC is to define requirements and solutions for hosts and applications in Data Centers to automatically join or leave an IP VPN which interconnects multiple customer premises and data centers. 

Today when two or more data centers are inter-connected through VPNs or any WAN networks, hosts or VMs within data centers are managed separately from the VPN provider's management system.  The provisioning process for services provided by Service Providers' data centers to join enterprise VPNs, is often manual, and thus has long turn up time. Security, scalability, and operational efficiency are issues due to lack of standardized automation procedure for hosts in provider data centers to join VPN.
 
Modern data-centers require multi-tenant support for applications. For security and administrative reasons it is desirable to isolate the resources associated with a particular tenant in a VPN. This WG will define requirements and protocol solutions to enable hosts in a data center to join a specific layer 3 VPN automatically through control protocols, using IP VPN to provide secure any to any connections. The VPN Gateway function which provides seamless VPN connectivity between the segments of the networks will be defined.

There are two ways for hosts/applications within a data center to join a specific VPN which interconnect multiple sites: via Management plane or via in-band data plane. 

1.	Management Plane: i.e. having the wide area VPN's management system communicate with data center management system to allow a group of hosts or applications to join a specific VPN. 
If the two management systems can communicate directly to allow a group of VMs in a Data Center to join a VPN, then the automation can be achieved without any new protocol work for IETF. 
2.	In-band data plane: However, several service providers have indicated that their VPN management system can't communicate with Data Center management system automatically. They want the automation to go through in-band signal between DC gateway and VPN PEs. Then new protocol work is needed for IETF: like request to join (or leave), authentication, etc.

The design principle for the protocols and solution development is to leverage existing layer 3 VPN technologies already defined in IETF whenever possible, including various IP and MPLS VPN technologies. This work supports the creation of new protocols, extension to existing protocols, and solutions proposed to use new and existing protocols.
 
Best regards,
 
Ning So
Verizon Corporate Technology
(office) 972-729-7905
(Cell) 972-955-0914

-----Original Message-----
From: [email-masked] [mailto:[email-masked]] On Behalf Of [email-masked]
Sent: Tuesday, October 04, 2011 2:00 PM
To: [email-masked]
Subject: L3VPN Digest, Vol 88, Issue 2

If you have received this digest without all the individual message attachments you will need to update your digest options in your list subscription.  To do so, go to 

https://www.ietf.org/mailman/listinfo/l3vpn

Click the 'Unsubscribe or edit options' button, log in, and set "Get MIME or Plain Text Digests?" to MIME.  You can set this option globally for all the list digests you receive at this point.

Send L3VPN mailing list submissions to
	[email-masked]

To subscribe or unsubscribe via the World Wide Web, visit
	https://www.ietf.org/mailman/listinfo/l3vpn
or, via email, send a message with subject or body 'help' to
	[email-masked]

You can reach the person managing the list at
	[email-masked]

When replying, please edit your Subject line so it is more specific than "Re: Contents of L3VPN digest..."

Today's Topics:

   1. VPN4DC at L3VPN in Taipei. (Marshall Eubanks)
   2. RE: VPN4DC at L3VPN in Taipei. (Luyuan Fang (lufang))

----------------------------------------------------------------------

Message: 1
Date: Tue, 4 Oct 2011 14:20:30 -0400
From: Marshall Eubanks <[email-masked]>
To: L3VPN <[email-masked]>, [email-masked],	Adrian Farrel
	<[email-masked]>
Subject: VPN4DC at L3VPN in Taipei.
Message-ID:
	<[email-masked]>
Content-Type: text/plain; charset=ISO-8859-1

Stewart Bryant has requested that we hold an L3VPN meeting at IETF 82 to consider and discuss VPN4DC.
Specifically, we would

"need to emerge understanding the problem, the usage, the requirements, and the necessary charter changes."

This would be preparation for VPN4DC becoming a BOF.

Adrian set up some requirements for this meeting :

The problem needs to be discussed on the L3VPN list.

You need to have viable  -00 drafts before the cutoff.

Luyuan Fang has promised a draft before the cutoff.

If there is not significant discussion here on this issue, the session is likely to be canceled.

Please keep discussion of VPN4DC here on the L3VPN list.

Due to the tentative nature and special purpose of this meeting I don't think it is appropriate to make a general call for papers. However, if you would like to speak on VPN4DC, please prepare  a draft and let us (the WG Co-chairs) know.

Regards
Marshall

P.S. Some background :

http://www6.ietf.org/proceedings/81/slides/opsawg-3.pdf (page 17) http://tools.ietf.org/id/draft-so-vdcs-01.txt

------------------------------

Message: 2
Date: Tue, 4 Oct 2011 13:36:06 -0500
From: "Luyuan Fang (lufang)" <[email-masked]>
To: "Marshall Eubanks" <[email-masked]>, "L3VPN"
	<[email-masked]>, 	"Adrian Farrel" <[email-masked]>
Subject: RE: VPN4DC at L3VPN in Taipei.
Message-ID:
	<[email-masked]>
Content-Type: text/plain;	charset="us-ascii"

Marshall,

I forwarded your mail to folks currently working on / interested in vpn4dc project.
Thanks,
Luyuan

> -----Original Message-----
> From: Marshall Eubanks [mailto:[email-masked]]
> Sent: Tuesday, October 04, 2011 2:21 PM
> To: L3VPN; Luyuan Fang (lufang); Adrian Farrel
> Subject: VPN4DC at L3VPN in Taipei.
> 
> Stewart Bryant has requested that we hold an L3VPN meeting at IETF 82 
> to consider and discuss VPN4DC.
> Specifically, we would
> 
> "need to emerge understanding the problem, the usage, the 
> requirements, and the necessary charter changes."
> 
> This would be preparation for VPN4DC becoming a BOF.
> 
> Adrian set up some requirements for this meeting :
> 
> The problem needs to be discussed on the L3VPN list.
> 
> You need to have viable  -00 drafts before the cutoff.
> 
> Luyuan Fang has promised a draft before the cutoff.
> 
> If there is not significant discussion here on this issue, the session 
> is likely to be canceled.
> 
> Please keep discussion of VPN4DC here on the L3VPN list.
> 
> Due to the tentative nature and special purpose of this meeting I 
> don't think it is appropriate to make a general call for papers. 
> However, if you would like to speak on VPN4DC, please prepare  a draft 
> and let us (the WG Co-chairs) know.
> 
> Regards
> Marshall
> 
> P.S. Some background :
> 
> http://www6.ietf.org/proceedings/81/slides/opsawg-3.pdf (page 17) 
> http://tools.ietf.org/id/draft-so-vdcs-01.txt

------------------------------

_______________________________________________
L3VPN mailing list
[email-masked]
https://www.ietf.org/mailman/listinfo/l3vpn

End of L3VPN Digest, Vol 88, Issue 2
************************************