<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Sure! Glad to work with you Nachi. Anything I can do to help out on the project!<div><br></div><div>I'll start looking at strongswan and how to configure.</div><div><br><div><br></div><div>Regards,</div><div><br><div apple-content-edited="true">
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">PCM (Paul Michali)<br><br></span></div><div apple-content-edited="true"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><br></span></div><div><div>On May 10, 2013, at 12:35 PM, Nachi Ueno wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>Hi Paul<br><br>Sounds Great.<br><br>The first driver will be strong-swan based.<br><a href="http://www.strongswan.org/">http://www.strongswan.org/</a><br><br>How about work with me to implement strong-swan vpn driver?<br>Honestly, i'm new to strong-swan, so I'm very appreciate if you<br>could try strong-swan on ubuntu and share how to configure it based on<br>current API model.<br><br>Thanks<br>Nachi<br><br><br><br><br><br><br><br>2013/5/10 Paul Michali <pcm@cisco.com>:<br><blockquote type="cite">Naci, Mark, Swami, Sachin, et al,<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Any suggestions on where/how I can help on this? I'm new to OS (just working<br></blockquote><blockquote type="cite">it for a few months), so no specific expertise area, but have bandwidth to<br></blockquote><blockquote type="cite">contribute.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Also, any pointers to information that will help me get up to speed on this<br></blockquote><blockquote type="cite">would be appreciated (Mark gave me link to Amazon URL for info on what they<br></blockquote><blockquote type="cite">provide for VPNaaS). I was going to look at LBaaS code next week and have<br></blockquote><blockquote type="cite">been monitoring those discussions, as there seem to be some parallels there.<br></blockquote><blockquote type="cite">If there are companion info that you think would help, let me know.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Regards,<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">PCM (Paul Michali)<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">On May 9, 2013, at 9:12 PM, Nachi Ueno wrote:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Hi Folks<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">We have meeting about VPN today.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">#Conclusions<br></blockquote><blockquote type="cite">1. We agreed ipsec api<br></blockquote><blockquote type="cite">https://blueprints.launchpad.net/quantum/+spec/vpnaas-python-apis<br></blockquote><blockquote type="cite">2. Swami will push api CRUD code to review (continue discussion on code)<br></blockquote><blockquote type="cite"> https://blueprints.launchpad.net/quantum/+spec/vpnaas-python-apis<br></blockquote><blockquote type="cite">3. We agreed first implementation vpn architecture<br></blockquote><blockquote type="cite">4. Next meeting is 5/13 PST 5:00 PM on #openstack-meetings<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">#Questions for IPSec API<br></blockquote><blockquote type="cite">1 psk_key -> psk (agreed)<br></blockquote><blockquote type="cite">2 For ipsecpolicy table, suggest to split lifetime into two parts<br></blockquote><blockquote type="cite">lifetime_s(per seconds) and lifetime_b(per kilobytes) -> updated<br></blockquote><blockquote type="cite">table (agreed)<br></blockquote><blockquote type="cite">3 change back "cidrs" from subnet (or network) -> check marks's thought<br></blockquote><blockquote type="cite">4 For APIs, can we shorten the naming such as change -> keep current<br></blockquote><blockquote type="cite">longer style for reability<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">#Project Management (Task)<br></blockquote><blockquote type="cite"> - move doc to wiki (Swami)<br></blockquote><blockquote type="cite"> - Register BP and get approval by Mark (Swami)<br></blockquote><blockquote type="cite"> - check default value for lifetime value (Swami)<br></blockquote><blockquote type="cite"> - Discuss Archtecture<br></blockquote><blockquote type="cite"> - Implement Data Model (Swami will push code to the gerrit)<br></blockquote><blockquote type="cite"> - Driver (Nachi?)<br></blockquote><blockquote type="cite"> - CLI (python-quantum client) work (Swami will push code to the gerrit)<br></blockquote><blockquote type="cite"> - Write openstack network api document wiki (Sachin)<br></blockquote><blockquote type="cite"> - Devstack support<br></blockquote><blockquote type="cite"> - Horizon work<br></blockquote><blockquote type="cite"> - Tempest<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">https://docs.google.com/a/ntti3.com/presentation/d/1J7k1eI13-3pQVwp5XgZDWPfzUvuSqczRdK0lEZKQOKk/edit#slide=id.p<br></blockquote><blockquote type="cite">Nachi<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">2013/5/7 Qin Li <qili@vmware.com>:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Hi Swami,<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Thanks for your comments. All look good to me except local_cidrs,<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">peer_cidrs. "cidrs" may be clear for value type and validation, but it is<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">unfamiliar for the existing VPN administrators. I think we might use<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">subnets or networks to avoid introducing a new concept for users.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Regards<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">QinLi<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">-----Original Message-----<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">From: Vasudevan, Swaminathan (PNB Roseville)<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">[mailto:swaminathan.vasudevan@hp.com]<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Sent: 2013年5月8日 1:25<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">To: OpenStack Development Mailing List<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Subject: Re: [openstack-dev] VPNaaS<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Hi Qin Li,<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">See my answers inline.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Thanks.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">-----Original Message-----<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">From: Qin Li [mailto:qili@vmware.com]<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Sent: Monday, May 06, 2013 8:37 PM<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">To: OpenStack Development Mailing List<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Subject: Re: [openstack-dev] [Quantum] [Networking] VPNaaS<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">I'd like to share some of my comments on data models, tables, APIs defined<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">in link<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">https://docs.google.com/a/ntti3.com/document/d/1Jphcvnn7PKxqFEFFZQ1_PYkEx5<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">J4aO5J5Q74R_PwgV8/edit .<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">1. For VPNServiceConnection table<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">a. suggest to remove psk(Boolean) key defined in VPNServiceConnection<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">table. There is already key auth_mode defined in ikepolicy table.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">"auth_mode" can be "psk" or "certificate". By default, if not set, it is<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">psk mode for authentication. Still keeping psk_key inside<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">VPNServiceConnection since psk_key is different per remote peer.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Authentication mode is a part of IKE property.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Swami - Yes we had both the auth_mode and psk_key as part of the IKEPolicy<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">table. We moved both the fields to the connection table since, we just<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">wanted to re-use the IKEPolicy for different connections if only the PSK<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">key changes or the auth_mode changes. Also in the document we make<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">necessary changes to the table definition, but I need to make the change<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">also in the datamodel table.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">b. suggest to change local_cidrs and peer_cidrs to local_networks(or<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">local_subnets) and peer_networks(per_subnets) in VPNServiceConnection<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">table. Cidrs is not a familiar keyword to users in IPSec industry. Some<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">IPSec VPN vendors use subnets, some use networks.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Swami - Yes we had initially defined it as peer_subnets and local_subnets,<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">but based on yesterday's discussion we moved it to "cidrs", since it would<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">be clear.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">c. suggest to change psk_key to psk, psk already means pre-shared key.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Swami - Accepted we will change this.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">2. For ipsecpolicy table, suggest to split lifetime into two parts<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">lifetime_s(per seconds) and lifetime_b(per kilobytes).<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Swami - Yes we can discuss about this in Thursday's meeting.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">3. Can we shorten the naming of keywords? Such as change<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Swami - We can discuss about this in Thursday's meeting. The reason we<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">don't want to have abbreviated keys is for people to understand the keys<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">properly.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> In vpnserviceconnections table<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> vpnservice_ipsecpolicy_id to ipsecpolicy_id<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> vpnservice_ikepolicy_id to ikepolicy_id<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> vpnservice_certificiate_id to certificate_id<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> In ikepolicys table<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> auth_algorithm to auth_alg<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> encryption_algorithm to enc_alg<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> phraseI_negotiation_mode to phraseI_mode<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> In ipsecpolicys table<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> transform_protocol to protocol<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> auth_algorithm to auth_alg<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> encryption_algorithm to enc_alg<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> encapsulation_mode to mode or encap_mode<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">4. There might be some updates to set proper length for each value in the<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">tables. Such as change<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> auth_algorithm VARCHAR2(255) to auth_alg VARCHAR2(8) ; for<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">example "sha1" etc.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> encryption_algorithm VARCHAR2(255) to enc_alg VARCHAR2(16) ; for<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">example "aes128-cbc", "aes256-cbc" etc.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> name VARCHAR2(255) to name VARCHAR2(64)<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Swami - Yes we will make the necessary changes in the table.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">5. What do "dh" and "tls" keywords mean in table vpnservicecertficates?<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Swami - This was mainly included in the certificate table to address the<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">"Openvpn" certificate requirements. This will be dropped for now. Also we<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">are not considering to implement the certificates for this release. We<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">will clean up the tables.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">6. For APIs, can we shorten the naming such as change<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> /v1.0/vpnservicecertificates/vpnservice_certificate_id to<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">/v1.0/vpncerts/certificate_id<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> /v1.0/vpnserviceconnections/vpnservice_conn_id to<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">/v1.0/vpnsrvconns/conn_id<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Swami: We can discuss in Thursday's meeting.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Thanks & Regards<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Qin<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">-----Original Message-----<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">From: Nachi Ueno [mailto:nachi@ntti3.com]<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Sent: 2013年5月7日 9:07<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">To: OpenStack Development Mailing List<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Subject: Re: [openstack-dev] [Quantum] [Networking] VPNaaS<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Hi folks<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">In today's meeting, we are almost finished to define data models.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">https://docs.google.com/a/ntti3.com/document/d/1Jphcvnn7PKxqFEFFZQ1_PYkEx5<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">J4aO5J5Q74R_PwgV8/edit<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">If you have any concerns, please commet it on the doc or question on the<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">mailing list.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">We will have meeting at<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">5/9 (Thu) 5:00 (PST)<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">In the next meeting, we will discuss more project management oriented<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">discussion.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Thanks<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Nachi<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">2013/5/6 Nachi Ueno <nachi@ntti3.com>:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Hi folks<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Here is note from the meeting at 2nd meeting on VPN # sorry I thought<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">I have sent it to the mailing list, but it looks not delivery.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">1) FirstStep SSL-VPN or IPSec? -> IPSec<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">- all atenndes agrees with IPSec first step<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">- IPSec is widely used so, this is big win to the community<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">- IPSec can support remote user use case<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">- SSL-VPN (CloudPipe) can be supported by OpenVPN VM with floating ips<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">2) GenricService API -> Agreed<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">-id<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">-name<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">-tenant_id<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">-type (VPN type)<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">type has namespace (should be flat)<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">l2 vpn -> l2.*** (l2.l2tp)<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">l3 vpn -> l3.** (l3.ipsec)<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">3) IPSec API set<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Start discussion for IPSec api on the google doc<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">https://docs.google.com/a/ntti3.com/document/d/1Jphcvnn7PKxqFEFFZQ1_PY<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">kEx5J4aO5J5Q74R_PwgV8/edit<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">4) Next meeting time<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">PST Monday 5PM (Sactin@VMWare will reserve conf-call)<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Meeting Agenda and Note<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">https://docs.google.com/presentation/d/1J7k1eI13-3pQVwp5XgZDWPfzUvuSqc<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">zRdK0lEZKQOKk/edit#slide=id.p<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Thanks!<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">2013/5/1 Sachin Thakkar <sthakkar@vmware.com>:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Thanks folks for joining today. We've made some good progress on the<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">IPsec VPN object model. Nachi has sent out the meeting notes to the<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">alias as well.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">We'll need another follow up to continue the discussion. The meeting<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">will be at 5pm Pacific time on Monday, May 6.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">The same bridge below will be used.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Thanks,<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Sachin<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">________________________________<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">From: "Sachin Thakkar" <sthakkar@vmware.com><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">To: "OpenStack Development Mailing List (openstack-dev@lists.openstack.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">org)"<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><openstack-dev@lists.openstack.org><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Sent: Thursday, April 25, 2013 11:43:30 PM<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Subject: [openstack-dev] [Quantum] [Networking] VPNaaS<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Trying the new Networking tag in the subject :)<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Anyway, we have a kickoff call for VPNaaS scheduled next Wednesday @<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">5pm Pacific time. We will be discussing over the phone:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Participant Passcode: 697 737 3510<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Call-in toll-free number (Premiere): 1-866-715-6501 (US) Additional<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">International Numbers:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">http://pages.pgi-email.com/page.aspx?qs=5c591a8916642e738e03c25585184<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">f841174bd68edc7b376f211065726f20c4087d2dbd294c95628953b9ebd93c298f8a5<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">9d287357f683bc937b0420662c826d43f873082e5033f476121c74d72cc5ed151c4b3<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">0a31fa1b2<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">To all interested, hope to see you there.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Cheers,<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Sachin<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">_______________________________________________<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">OpenStack-dev mailing list<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">OpenStack-dev@lists.openstack.org<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">_______________________________________________<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">OpenStack-dev mailing list<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">OpenStack-dev@lists.openstack.org<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">_______________________________________________<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">OpenStack-dev mailing list<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">OpenStack-dev@lists.openstack.org<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">_______________________________________________<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">OpenStack-dev mailing list<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">OpenStack-dev@lists.openstack.org<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">_______________________________________________<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">OpenStack-dev mailing list<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">OpenStack-dev@lists.openstack.org<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">_______________________________________________<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">OpenStack-dev mailing list<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">OpenStack-dev@lists.openstack.org<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">_______________________________________________<br></blockquote><blockquote type="cite">OpenStack-dev mailing list<br></blockquote><blockquote type="cite">OpenStack-dev@lists.openstack.org<br></blockquote><blockquote type="cite">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">_______________________________________________<br></blockquote><blockquote type="cite">OpenStack-dev mailing list<br></blockquote><blockquote type="cite">OpenStack-dev@lists.openstack.org<br></blockquote><blockquote type="cite">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<br></blockquote><blockquote type="cite"><br></blockquote><br>_______________________________________________<br>OpenStack-dev mailing list<br>OpenStack-dev@lists.openstack.org<br>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<br></div></blockquote></div><br></div></div></body></html>