<!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] Section 8
Revisions</title></head><body>
<div>Chris,</div>
<div><br></div>
<div>These protocols, including NORM, can function just fine without a
contemporaneous return link from the client to the server.
Certainly, at some point, there must be a link for NACKs to be
returned to the server, but this return link can occur at any
arbitrary point even long after the server has sent the entire
file.</div>
<div><br></div>
<div>So, I should have included the word "contemporaneous"
in what I said in my previous email.</div>
<div><br></div>
<div>For whatever it is worth, the RFC is at
http://norm.pf.itd.nrl.navy.mil/rfc3940.pdf.</div>
<div><br></div>
<div>Cheers...</div>
<div>Jim</div>
<div><br></div>
<div><br></div>
<div>At 2:47 PM -0400 9/15/05, Krupiarz, Christopher wrote:</div>
<blockquote type="cite" cite>Content-class:
urn:content-classes:message<br>
Content-Type: multipart/alternative;<br>
<x-tab>
</x-tab>boundary="----_=_NextPart_001_01C5BA25.E222020A"<br>
</blockquote>
<blockquote type="cite" cite><font face="Arial"
color="#0000FF">Jim,</font></blockquote>
<blockquote type="cite" cite> </blockquote>
<blockquote type="cite" cite><font face="Arial" color="#0000FF">Sure
thing, I'll make the change. One question: I'm not sure
what you meant by reliable file transfer where a return link is not
available. If the loop isn't closed, how is the file delivery
reliable? (Feel free to just say read the NORM spec if that's
what's in there)</font></blockquote>
<blockquote type="cite" cite> </blockquote>
<blockquote type="cite" cite><font face="Arial"
color="#0000FF">Thanks,</font></blockquote>
<blockquote type="cite" cite> </blockquote>
<blockquote type="cite" cite><font face="Arial"
color="#0000FF">Chris</font><br>
<blockquote><font face="Tahoma">-----Original Message-----<br>
<b>From:</b> sis-csi-bounces@mailman.ccsds.org
[mailto:sis-csi-bounces@mailman.ccsds.org]<b> On Behalf Of</b> James
L. Rash<br>
<b>Sent:</b> Thursday, September 15, 2005 2:38 PM<br>
<b>To:</b> sis-csi@mailman.ccsds.org<br>
<b>Subject:</b> Re: [Sis-csi] Section 8 Revisions</font><br>
<font face="Tahoma"></font></blockquote>
<blockquote>At 12:08 AM -0400 9/15/05, Krupiarz, Christopher
wrote:<br>
<blockquote type="cite" cite>Enclosed are revisions to section 8 for
review. My attempt was to take<br>
Keith's bulleted comments and put them into paragraph form. <br>
<br>
Chris<br>
<br>
<br>
Content-Type: application/msword;<br>
<x-tab>
</x-tab>name="CSI_GB_Draft_0.8-sec8.doc"<br>
Content-Description: CSI_GB_Draft_0.8-sec8.doc<br>
Content-Disposition: attachment;<br>
<x-tab>
</x-tab>filename="CSI_GB_Draft_0.8-sec8.doc"<br>
</blockquote>
</blockquote>
<blockquote>
<blockquote>Attachment converted: Macintosh HD:CSI_GB_Draft_0.8-sec8
1.doc (WDBN/MSWD) (000BB0CD)<br>
_______________________________________________<br>
Sis-CSI mailing list<br>
</blockquote>
<blockquote>Sis-CSI@mailman.ccsds.org<br>
</blockquote>
<blockquote>http://mailman.ccsds.org/cgi-bin/mailman/listinfo/sis-csi<br
>
</blockquote>
</blockquote>
<blockquote><br></blockquote>
<blockquote>Chris,</blockquote>
<blockquote><br></blockquote>
<blockquote>I suggest that the title of section 8.1.1.2 should be
changed from</blockquote>
<blockquote><br></blockquote>
<blockquote> <font face="Times New Roman"
size="+1" color="#000000"><b> 8.1.1.2</b></font><font face="Arial"
size="+1" color="#000000"><b><x-tab>
</x-tab></b></font><font face="Times New Roman" size="+1"
color="#000000"><b>CFDP Transmission from Instrument to
User</b></font></blockquote>
<blockquote><br></blockquote>
<blockquote>to</blockquote>
<blockquote><br></blockquote>
<blockquote> <font face="Times New Roman"
size="+1" color="#000000"><b> 8.1.1.2</b></font><font face="Arial"
size="+1" color="#000000"><b><x-tab>
</x-tab></b></font><font face="Times New Roman" size="+1"
color="#000000"><b>Reliable File Transfer from Instrument to
User</b></font></blockquote>
<blockquote><br></blockquote>
<blockquote>This works better because it more clearly indicates in
more general terms what the section is about. CFDP is not
the only alternative for reliable file transfer when, for example, a
return link is unavailable, and starting in the third sentence, the
use of CFDP is amply specified for the given example
anyway.</blockquote>
<blockquote><br></blockquote>
<blockquote>I would also suggest adding the following sentence in this
section:</blockquote>
<blockquote><br>
<blockquote>NORM (<font color="#000000">NACK-Oriented</font> Reliable
Multicast) (RFC 3940) can also be considered as an alternative choice
for a reliable file and stream delivery protocol over IP.</blockquote>
<blockquote><br></blockquote>
</blockquote>
<blockquote><br></blockquote>
<blockquote>This sentence is appropriate for a Green Book, as it
serves to promote the reader's understanding through additional
relevant information.</blockquote>
<blockquote><tt>--</tt></blockquote>
<blockquote><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>
</blockquote>
</blockquote>
<blockquote type="cite" cite><br>
_______________________________________________<br>
Sis-CSI mailing list<br>
Sis-CSI@mailman.ccsds.org<br>
http://mailman.ccsds.org/cgi-bin/mailman/listinfo/sis-csi</blockquote>
<div><br></div>
<div><br></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>