<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
tt
{mso-style-priority:99;
font-family:"Courier New";}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">Mohammad Banikazemi wrote:<br>
<br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif""><o:p></o:p></span></p>
<p><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D">></span><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">in Atlanta the support was overwhelmingly positive in my opinion. I just wanted to make sure this does not
get <span style="color:#1F497D">></span>lost in our discussions. </span><br>
<br>
<span style="color:#1F497D"><o:p></o:p></span></p>
<p><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Absolutely. I hadn’t been following the group policy discussions prior to the summit but I was very impressed with what I saw and heard.<o:p></o:p></span></p>
<p><br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D">></span><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">to in particular discuss the possibility of making the code less tightly coupled with Neutron core.</span><tt><span style="font-size:10.0pt">
<o:p></o:p></span></tt></p>
<p><tt><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">+1 to making it less tightly coupled (although I haven’t been inside the code to have an opinion on how tightly coupled it is now)<o:p></o:p></span></tt></p>
<p><tt><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Let’s keep in mind OSI-like layers and well defined interfaces between them. Coming from a hardware networking background I find it very convenient to think in terms of ports,
networks, subnets and routers. Those concepts should continue to be basic building blocks of software defined networks. The layer 4+ stuff should be added on top with clean interfaces that don’t entangle functionality up and down the stack.<o:p></o:p></span></tt></p>
<p><tt><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Strict OSI layer compliance has never been a great success, but the general concept has been very useful for a long time All the most painful protocols for a network person
to deal with are the ones like SIP where clean separation of layers was indiscriminately violated.<o:p></o:p></span></tt></p>
</div>
</body>
</html>