<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.2722" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=490065017-13102005><FONT face=Arial
color=#0000ff size=2>I agree with Mike's analysis. But I'd also like to point
out that even</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=490065017-13102005><FONT face=Arial
color=#0000ff size=2>when source compatability is not a requirement, source
familiarity</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=490065017-13102005><FONT face=Arial
color=#0000ff size=2>is. That is, even when recoding is feasible the API should
only</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=490065017-13102005><FONT face=Arial
color=#0000ff size=2>introduce new concepts as required to improve efficiency.
The</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=490065017-13102005><FONT face=Arial
color=#0000ff size=2>shift from socket model to QP/CQ is challenging enough as
is.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=490065017-13102005><FONT face=Arial
color=#0000ff size=2>It's also where the benefit is. Changing how the
application</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=490065017-13102005><FONT face=Arial
color=#0000ff size=2>requests and accepts connections is just piling on more
things</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=490065017-13102005><FONT face=Arial
color=#0000ff size=2>for the developers to learn onto an already very full
plate, and</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=490065017-13102005><FONT face=Arial
color=#0000ff size=2>with nowhere near the same benefit.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=490065017-13102005><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=490065017-13102005><FONT face=Arial
color=#0000ff size=2>The simple, IP/DNS-centric methods that Mike outlined
will</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=490065017-13102005><FONT face=Arial
color=#0000ff size=2>work on either iWARP or IB, and are very easily
understood</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=490065017-13102005><FONT face=Arial
color=#0000ff size=2>by those familiar with existing sockets/IP network
development.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=490065017-13102005><FONT face=Arial
color=#0000ff size=2>The more complex models provide minor enhancements
for</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=490065017-13102005><FONT face=Arial
color=#0000ff size=2>very corner cases at the very heavy concept of requiring
</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=490065017-13102005><FONT face=Arial
color=#0000ff size=2>the developer to understand a lot more about network
topology.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN
class=490065017-13102005></SPAN> </DIV></BODY></HTML>