<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">While quantum VPN can serve as either
      client or server or both, there are big difference on requirements
      -- for example, a SSL VPN server needs to have an address pool,
      which is not required for clients.<br>
      <br>
      IMO, we need to first differentiate these use cases (server vs.
      client) before we decide what state fields should be covered.<br>
      <br>
      Yi<br>
      <br>
      On 4/17/13 9:58 AM, Sachin Thakkar wrote:<br>
    </div>
    <blockquote
cite="mid:23962145.1899.1366207131452.JavaMail.sthakkar@sthakkar-mbair.local"
      type="cite">
      <style type="text/css">p { margin: 0; }</style>
      <div style="font-family: arial,helvetica,sans-serif; font-size:
        10pt; color: #000000">I definitely agree with point (1) from Yi
        below. There are so many flavors and intricacies to VPNs that it
        would be to our advantage to decouple as much as possible.<br>
        <br>
        For (2), my understanding is that the quantum VPN could be
        either. Is your comment to add this explicit role in addition to
        the state fields?<br>
        <br>
        Sachin<br>
        <br>
        <hr id="zwchr">
        <div style="color: rgb(0, 0, 0); font-weight: normal;
          font-style: normal; text-decoration: none; font-family:
          Helvetica,Arial,sans-serif; font-size: 12pt;"><b>From: </b>"Yi
          Yang" <a class="moz-txt-link-rfc2396E" href="mailto:yyos1999@gmail.com"><yyos1999@gmail.com></a><br>
          <b>To: </b>"OpenStack Development Mailing List"
          <a class="moz-txt-link-rfc2396E" href="mailto:openstack-dev@lists.openstack.org"><openstack-dev@lists.openstack.org></a><br>
          <b>Sent: </b>Wednesday, April 17, 2013 12:42:35 AM<br>
          <b>Subject: </b>Re: [openstack-dev] [Quantum] Quantum VPN:
          Update from today's        discussion<br>
          <br>
          A couple of quick comments:<br>
          <br>
          1. IMHO, we should separate IPSec/SSL VPN use cases from MPLS
          VPN cases, <br>
          as the former adopts a server-client model while the latter
          doesn't.<br>
          <br>
          2. One thing missed in these use cases, except in use case 3,
          is the <br>
          "role"  -- does the quantum VPN act as a server or a client?<br>
          <br>
          Yi<br>
          <br>
          <br>
          <br>
          On 4/16/13 8:16 PM, Nachi Ueno wrote:<br>
          > Hi folks<br>
          ><br>
          > Thank you for  joining today's discussion.<br>
          > Based on today's discussion, we updated the slide.<br>
          ><br>
          >
<a class="moz-txt-link-freetext" href="https://docs.google.com/presentation/d/1LdL0Fy9PpEQXB9q_c47iJ6gyA1oZn7B6MKbzFyk73tI/edit#slide=id.gd23898b7_135">https://docs.google.com/presentation/d/1LdL0Fy9PpEQXB9q_c47iJ6gyA1oZn7B6MKbzFyk73tI/edit#slide=id.gd23898b7_135</a><br>
          ><br>
          > Changes<br>
          > -  Simplify use case<br>
          >     removed any router references because it deals with
          implementation<br>
          > - Simplify Generic VPNService model<br>
          >    removed any router references because it deals with
          service insertion<br>
          > - Update attributes of generic VPN Service<br>
          >      Layer2 or Layer3 mode etc<br>
          ><br>
          > Tommorows' discussion is<br>
          > 5:20 at OpenStack Networking room<br>
          >
<a class="moz-txt-link-freetext" href="http://openstacksummitapril2013.sched.org/event/a9264b0dd9470fba9335acc8a78ff61c#.UW3p1SvC82g">http://openstacksummitapril2013.sched.org/event/a9264b0dd9470fba9335acc8a78ff61c#.UW3p1SvC82g</a><br>
          ><br>
          > Thanks!<br>
          > Nachi<br>
          ><br>
          > _______________________________________________<br>
          > OpenStack-dev mailing list<br>
          > <a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
          >
          <a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
          <br>
          <br>
          _______________________________________________<br>
          OpenStack-dev mailing list<br>
          <a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
        </div>
        <br>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
OpenStack-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>