<!doctype html public "-//W3C//DTD W3 HTML//EN">
<html><head><style type="text/css"><!--
blockquote, dl, ul, ol, li { padding-top: 0 ; padding-bottom: 0 }
--></style><title>Re: [Sis-csi] Green book
thoughts</title></head><body>
<div>At 6:06 PM -0700 4/19/06, Scott Burleigh wrote:</div>
<blockquote type="cite" cite><a
href="mailto:Lee.Neitzel@EmersonProcess.com"
>Lee.Neitzel@EmersonProcess.com</a> wrote:<br>
<blockquote type="cite" cite>RE: [Sis-csi] Green book thoughts<br>
</blockquote>
<blockquote type="cite" cite><font face="Arial" color="#000080">As you
know, there are significant fixed and variable costs associated with
design, implementation, testing, and deployment of each layer
protocol.</font><br>
</blockquote>
</blockquote>
<blockquote type="cite" cite>In my mind, this is the key point in this
discussion.<br>
</blockquote>
<blockquote type="cite" cite>....</blockquote>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>So in this architecture document I think
we want *not* to encourage every flight software manager to look at
each mission as yet another opportunity to demonstrate what fools the
designers of TCP were. The architecture needs to support the
insertion of alternatives to TCP where they are needed, but the fewer
the better. Suppose we leave it at that?</blockquote>
<div><br></div>
<div>Scott,</div>
<div><br></div>
<div>If I understand what you have been saying, it boils down to the
following. We as architects should aim towards saving the
mission community from making costly and/or dumb choices about rolling
their own re-transmission protocols. We should accomplish this
by (a) developing/adopting a small set of re-transmission protocols
that will meet all-but-the-most-usual-mission-needs for the future and
(b) disallow future missions from using any other re-transmission
protocols over the infrastructure we are
"architecting"<b>.</b></div>
<div><br></div>
<div>My apologies if I have misinterpreted your thesis, and I am happy
to be corrected.</div>
<x-sigsep><pre>--
</pre></x-sigsep>
<div><br>
James L. Rash<br>
Building 23, Room E403<br>
Code 588 -- Advanced Architectures and Automation Branch<br>
NASA Goddard Space Flight Center<br>
Greenbelt, MD 20771<br>
301-286-5246 (voice) 301-286-1768 (fax)<br>
</div>
</body>
</html>