<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <p><br>
    </p>
    <div class="moz-forward-container"><br>
      <br>
      -------- Forwarded Message --------
      <table class="moz-email-headers-table" border="0" cellpadding="0"
        cellspacing="0">
        <tbody>
          <tr>
            <th align="RIGHT" nowrap="nowrap" valign="BASELINE">Subject:
            </th>
            <td>Re: [P4-design] Portable Switch Architecture proposal</td>
          </tr>
          <tr>
            <th align="RIGHT" nowrap="nowrap" valign="BASELINE">Date: </th>
            <td>Fri, 4 Nov 2016 09:24:27 -0700</td>
          </tr>
          <tr>
            <th align="RIGHT" nowrap="nowrap" valign="BASELINE">From: </th>
            <td>Nick McKeown <a class="moz-txt-link-rfc2396E" href="mailto:nickm@stanford.edu"><nickm@stanford.edu></a></td>
          </tr>
          <tr>
            <th align="RIGHT" nowrap="nowrap" valign="BASELINE">To: </th>
            <td>Calin Cascaval <a class="moz-txt-link-rfc2396E" href="mailto:cascaval@barefootnetworks.com"><cascaval@barefootnetworks.com></a>,
              <a class="moz-txt-link-abbreviated" href="mailto:p4-design@lists.p4.org">p4-design@lists.p4.org</a></td>
          </tr>
        </tbody>
      </table>
      <br>
      <br>
      <meta http-equiv="Content-Type" content="text/html;
        charset=windows-1252">
      <p>Thanks, Calin and team. I think this is a very good direction
        to go. We need to find the right blend of portability, while
        still allowing for different architectures. Having a base set of
        functions created for a baseline/portable architecture -
        features that we can expect to work on a variety of forwarding
        planes - will let different teams write code they can expect to
        re-use (completely or mostly). I think we're all conscious of
        not trying to boil the ocean; the proposal seems like a good
        step forward.<br>
      </p>
      <p>Over time, I expect/hope there will be other baseline
        architectures for P4-16, representing different use cases. For
        now, I like the idea of focusing on something as you propose, to
        get the ball rolling and help us build a community together.</p>
      <p>As for a name, I think Portable or Baseline or PISA are all
        good. PISA has the advantage of being known already and used in
        the context of P4-14, and so would be my preference. It would
        also help PISA to be a generic name for an architecture, rather
        than just a name for one design.<br>
      </p>
      <p>Thanks</p>
      <p>- Nick<br>
      </p>
      <br>
      <div class="moz-cite-prefix">On 11/3/16 9:57 PM, Calin Cascaval
        wrote:<br>
      </div>
      <blockquote
        cite="mid:24DD04D8-5B00-4A21-9D52-F83B488ADF6A@barefootnetworks.com"
        type="cite"> Hello P4 designers,
        <div class=""><br class="">
        </div>
        <div class="">We made some progress toward defining the standard
          switch architecture (therein named Portable Switch
          Architecture in order to avoid the overbearing connotations of
          the word Standard) and I would like to propose that we set
          aside some time to discuss the attached proposal at our next
          working group meeting on Mon 11/7. Early feedback is welcomed
          and encouraged.<br class="">
          <div class="">
            <div style="color: rgb(0, 0, 0); font-family: Helvetica;
              font-size: 12px; font-style: normal; font-variant-caps:
              normal; font-weight: normal; letter-spacing: normal;
              orphans: auto; text-align: start; text-indent: 0px;
              text-transform: none; white-space: normal; widows: auto;
              word-spacing: 0px; -webkit-text-stroke-width: 0px;"
              class=""><br class="Apple-interchange-newline">
              --</div>
            <div style="color: rgb(0, 0, 0); font-family: Helvetica;
              font-size: 12px; font-style: normal; font-variant-caps:
              normal; font-weight: normal; letter-spacing: normal;
              orphans: auto; text-align: start; text-indent: 0px;
              text-transform: none; white-space: normal; widows: auto;
              word-spacing: 0px; -webkit-text-stroke-width: 0px;"
              class="">Thanks, Calin</div>
          </div>
          <div class=""><br class="webkit-block-placeholder">
          </div>
        </div>
        <br>
        <fieldset class="mimeAttachmentHeader"></fieldset>
        <br>
        <br>
        <fieldset class="mimeAttachmentHeader"></fieldset>
        <br>
        <pre wrap="">_______________________________________________
P4-design mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:P4-design@lists.p4.org">P4-design@lists.p4.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://lists.p4.org/mailman/listinfo/p4-design_lists.p4.org">http://lists.p4.org/mailman/listinfo/p4-design_lists.p4.org</a>

</pre>
      </blockquote>
      <br>
    </div>
  
<br /><br />
<hr style='border:none; color:#909090; background-color:#B0B0B0; height: 1px; width: 99%;' />
<table style='border-collapse:collapse;border:none;'>
        <tr>
                <td style='border:none;padding:0px 15px 0px 8px'>
                        <a href="https://www.avast.com/antivirus">
                                <img border=0 src="http://static.avast.com/emails/avast-mail-stamp.png" alt="Avast logo" />
                        </a>
                </td>
                <td>
                        <p style='color:#3d4d5a; font-family:"Calibri","Verdana","Arial","Helvetica"; font-size:12pt;'>
                                Ezt az e-mailt az Avast víruskereső szoftver átvizsgálta.
                                <br><a href="https://www.avast.com/antivirus">www.avast.com</a>
                        </p>
                </td>
        </tr>
</table>
<br />
</body>
</html>