[Sis-ams] Interoperability testing - transfer protocols

[Ray, Timothy J. (GSFC-583.0)]

Scott,

 

I agree with your choices.  UDP delivers datagrams (complete messages)
to the application, so it is quite easy to get started with.  In fact, I
would recommend that our first attempts at interoperability testing use
UDP for both Meta-AMS and AMS messages.

 

One or two questions:  Given that TCP is a bitstream protocol, when it
is used to carry messages, there is typically some sort of header that
is added in front of each message (to allow the receiver to detect
message boundaries).  If we use TCP, will we add a header to the 'raw'
AMS message?  And if so, have we agreed on the format of that header?

 

Tim

 

________________________________

From: sis-ams-bounces at mailman.ccsds.org
[mailto:sis-ams-bounces at mailman.ccsds.org] On Behalf Of Scott Burleigh
Sent: Thursday, May 08, 2008 1:16 PM
To: sis-ams at mailman.ccsds.org
Subject: Re: [Sis-ams] Interoperability testing - transfer protocols

 

Ray, Timothy J. (GSFC-583.0) wrote: 

Hello all,

 

As an implementer of software to support interoperability testing, there
are certain decisions that I have to make.  Two key decisions are:

1)       What protocol(s) to support for transferring Meta-AMS messages

2)       What protocol(s) to support for transferring AMS messages
directly between nodes

 

Has our working group decided what, as a minimum, is required for our
interoperability testing?

My candidates would be UDP for (1) and both UDP and TCP for (2).  Lots
of others make sense in specialized contexts but might be hard to
provide to everyone involved in an interoperation test.

Scott

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ccsds.org/pipermail/sis-ams/attachments/20080508/8761bf48/attachment.htm