<html>
Hi All,<br><br>
I did not provide inputs nor will I be in a position to due so before the
end of the week.<br><br>
Sorry, I have cleared some other things and am starting to work on
the document now.<br><br>
Rick<br><br>
At 05:08 AM 9/27/2005, Steve Parkes wrote:<br><br>
<blockquote type=cite class=cite cite><font face="arial" size=2>Dear
All,<br>
</font><br>
<font face="arial" size=2> <br>
</font><br>
<font face="arial" size=2>The Intra-Network Service document was still in
something of a mess at the end of the Atlanta meeting&<br>
</font><br>
<font face="arial" size=2>I have thoroughly edited the book cutting out
all the stuff that was not at all relevant, writing missing sections and
making everything consistent. This has taken a while because much of the
material was from our original transport/network layer document. Anyway
we now have what I think is a reasonable draft. Note that I have tracked
changes just so you can see the changes from the Atlanta version. I
suggest that before making modifications or comments you accept all
changes, otherwise we will end up in a Microsoft mire.<br>
</font><br>
<font face="arial" size=2> <br>
</font><br>
<font face="arial" size=2>Dai,<br>
</font><br>
<font face="arial" size=2>I understand that you have some funding from
ESTEC to work on the TCONS red books. Would you please read through the
Intra-Network Service red book and let me know if the service interfaces
are ok and if you have any other comments? Are the primitives sufficient?
What about registering the receiving protocols (End Systems) so that they
can be passed the data? What about identifying the send (e.g. with a
transaction ID) so that the sender knows which error is for which send?
Is this just assumed in the primitives or do we need to specify it
explicitly? Do we need to include some sequence diagrams?<br>
</font><br>
<font face="arial" size=2> <br>
</font><br>
<font face="arial" size=2>Greg, Jane,<br>
</font><br>
<font face="arial" size=2>Would you please read through and let me have
comments? Would you then please start work on the API book which should
provide the API for the four Intra-Network services? This will raise many
questions that we have not addressed, like do we register a protocol to
receive data from the intra-network service. My initial thought is that
we should make the API as close as possible to the previous one that we
had for the TCONS transport and network layer. Try to work it through and
find our what the questions are. We can then have a teleconference to
discuss the particular issues.<br>
</font><br>
<font face="arial" size=2> <br>
</font><br>
<font face="arial" size=2>Rick,<br>
</font><br>
<font face="arial" size=2>Would you also please let me have your
comments? I think that the document is now as you intended. One thing
that I would appreciate you working on is the Failure Metadata . In your
original work on the Intra-Network service you had gone into substantial
detail on this, but it was not put into the red book. I think that it
would be good to add it in.<br>
</font><br>
<font face="arial" size=2> <br>
</font><br>
<font face="arial" size=2>Max,<br>
</font><br>
<font face="arial" size=2>Your comments would be very welcome too.<br>
</font><br>
<font face="arial" size=2> <br>
</font><br>
<font face="arial" size=2>I need everyone s input on this by the middle
of October (17<sup>th</sup>) so that I can put all the comments together
and have the red book ready to send out to SOIS etc by the start of
November. The API book can be finished after this, but the main thing is
to have made a good start on it so we know that it will fit in with the
Intra-Network Service book and will not need changes to the Service book.
<br>
</font><br>
<font face="arial" size=2> <br>
</font><br>
<font face="arial" size=2>Regards<br>
</font><br>
<font face="arial" size=2> <br>
</font><br>
<font face="arial" size=2>Steve<br>
</font><br>
<font face="arial" size=2> <br>
</font><br>
<font face="Times New Roman, Times">------------------------------------------<br>
</font><br>
<font face="Times New Roman, Times">Steve Parkes<br>
</font><br>
<font face="Times New Roman, Times">Space Technology Centre<br>
</font><br>
<font face="Times New Roman, Times">Applied Computing, University of
Dundee<br>
</font><br>
<font face="Times New Roman, Times">Dundee, DD1 4HN, Scotland, UK<br>
</font><br>
<font face="Times New Roman, Times">Tel: +44 1382 345194<br>
</font><br>
<font face="Times New Roman, Times">Fax: +44 1382 348838<br>
</font><br>
<font face="Times New Roman, Times">Mobile: +44 784 138 3779<br>
</font><br>
<font face="Times New Roman, Times"> <br>
</font><br>
-- <br>
This message has been scanned for viruses and <br>
dangerous content by
<a href="http://www.mailscanner.info/"><b>MailScanner</a></b>, and is
<br>
believed to be clean. <br>
MailScanner thanks <a href="http://www.transtec.co.uk/">transtec
Computers</a> for their support. </blockquote>
<x-sigsep><p></x-sigsep>
Richard G Schnurr Jr<br>
Chief Architect<br>
Electrical Systems Center<br>
Applied Engineering and Technology Directorate<br>
NASA GSFC Code 560.0<br>
Greenbelt MD 20771<br><br>
(301)-286-1852</html>