[Sis-csi] Section 8 Revisions

[James L. Rash]

Chris,

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.

So, I should have included the word "contemporaneous" in what I said 
in my previous email.

For whatever it is worth, the RFC is at 
http://norm.pf.itd.nrl.navy.mil/rfc3940.pdf.

Cheers...
Jim


At 2:47 PM -0400 9/15/05, Krupiarz, Christopher wrote:
>Content-class: urn:content-classes:message
>Content-Type: multipart/alternative;
>	boundary="----_=_NextPart_001_01C5BA25.E222020A"
>
>Jim,
>
>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)
>
>Thanks,
>
>Chris
>
>-----Original Message-----
>From: sis-csi-bounces at mailman.ccsds.org 
>[mailto:sis-csi-bounces at mailman.ccsds.org] On Behalf Of James L. Rash
>Sent: Thursday, September 15, 2005 2:38 PM
>To: sis-csi at mailman.ccsds.org
>Subject: Re: [Sis-csi] Section 8 Revisions
>
>At 12:08 AM -0400 9/15/05, Krupiarz, Christopher wrote:
>
>>Enclosed are revisions to section 8 for review.  My attempt was to take
>>Keith's bulleted comments and put them into paragraph form. 
>>
>>Chris
>>
>>
>>Content-Type: application/msword;
>>	name="CSI_GB_Draft_0.8-sec8.doc"
>>Content-Description: CSI_GB_Draft_0.8-sec8.doc
>>Content-Disposition: attachment;
>>	filename="CSI_GB_Draft_0.8-sec8.doc"
>>
>Attachment converted: Macintosh HD:CSI_GB_Draft_0.8-sec8 1.doc 
>(WDBN/MSWD) (000BB0CD)
>_______________________________________________
>Sis-CSI mailing list
>
>Sis-CSI at mailman.ccsds.org
>
>http://mailman.ccsds.org/cgi-bin/mailman/listinfo/sis-csi
>
>
>Chris,
>
>I suggest that the title of section 8.1.1.2 should be changed from
>
>      8.1.1.2	CFDP Transmission from Instrument to User
>
>to
>
>      8.1.1.2	Reliable File Transfer from Instrument to User
>
>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.
>
>I would also suggest adding the following sentence in this section:
>
>NORM (NACK-Oriented Reliable Multicast) (RFC 3940) can also be 
>considered as an alternative choice for a reliable file and stream 
>delivery protocol over IP.
>
>
>This sentence is appropriate for a Green Book, as it serves to 
>promote the reader's understanding through additional relevant 
>information.
>--
>
>James L. Rash
>Building 23, Room E403
>Code 588 -- Advanced Architectures and Automation Branch
>NASA Goddard Space Flight Center
>Greenbelt, MD  20771
>301-286-5246 (voice)     301-286-1768 (fax)
>
>
>_______________________________________________
>Sis-CSI mailing list
>Sis-CSI at mailman.ccsds.org
>http://mailman.ccsds.org/cgi-bin/mailman/listinfo/sis-csi


-- 

James L. Rash
Building 23, Room E403
Code 588 -- Advanced Architectures and Automation Branch
NASA Goddard Space Flight Center
Greenbelt, MD  20771
301-286-5246 (voice)     301-286-1768 (fax)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ccsds.org/pipermail/sis-csi/attachments/20050915/b772d9b7/attachment.htm