[Sis-csi] Text for Transport Layer Section

[Scott, Keith L.]

Scott can better answer this, but I think that CFDP without the
store-and-forward overlay procedures really wants to have an instance
of CFDP per link, so misordering isn't a consideration.

		--keith 

> -----Original Message-----
> From: sis-csi-bounces at mailman.ccsds.org 
> [mailto:sis-csi-bounces at mailman.ccsds.org] On Behalf Of Lloyd Wood
> Sent: Tuesday, April 25, 2006 5:33 PM
> To: Scott Burleigh
> Cc: sis-csi at mailman.ccsds.org
> Subject: Re: [Sis-csi] Text for Transport Layer Section
> 
> At Tuesday 2006-04-25 13:48 -0700, Scott Burleigh wrote:
> >Lloyd Wood wrote:
> >
> >>" CFDP can run over TCP"
> >>
> >>has anyone ever used CFDP over TCP?
> >
> >I believe a TCP "UT layer" adapter for CFDP has been built 
> and tested 
> >at JPL, but I'm pretty sure it's never been used in any operational 
> >sense.
> 
> so this wouldn't meet the "two interoperable independent 
> implementations needed to make a standard" requirement, then?
> 
> >Unacknowledged CFDP over TCP isn't quite as outlandish a stack as it

> >might seem: TCP assures the in-order data arrival that the CFDP 
> >procedures rely on (which on rare occasions produces some surprising

> >behavior in acknowledged CFDP over UDP),
> 
> surprising behaviour? not bugs/design flaws?
> 
> L.
> 
> >  and the file fragmentation and reassembly, record boundary 
> detection 
> > and preservation, and metadata features of CFDP are as useful in 
> > unacknowledged mode as they are in acknowledged mode.
> >
> >Scott
> 
> _______________________________________________
> Sis-CSI mailing list
> Sis-CSI at mailman.ccsds.org
> http://mailman.ccsds.org/cgi-bin/mailman/listinfo/sis-csi
>