<HTML>
<HEAD>
<TITLE>Re: [Sis-ams] Interoperability testing - transfer protocols</TITLE>
</HEAD>
<BODY>
<FONT SIZE="4"><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>Tim,<BR>
<BR>
The GSFC flight architecture is based on UDP overall, so let’s start with that.<BR>
<BR>
Jane<BR>
<BR>
<BR>
On 5/8/08 1:27 PM, "Ray, Timothy J. (GSFC-583.0)" <timothy.j.ray@nasa.gov> wrote:<BR>
<BR>
</SPAN></FONT></FONT><BLOCKQUOTE><FONT SIZE="4"><FONT COLOR="#000080"><FONT FACE="Arial"><SPAN STYLE='font-size:10pt'>Scott,<BR>
<BR>
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.<BR>
<BR>
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?<BR>
<BR>
Tim<BR>
<BR>
</SPAN></FONT></FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>
</SPAN></FONT></FONT>
<P ALIGN=CENTER>
<FONT SIZE="5"><FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'><HR ALIGN=CENTER SIZE="2" WIDTH="100%"></SPAN></FONT></FONT>
<P>
<FONT SIZE="4"><FONT FACE="Tahoma, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:10pt'><B>From:</B> sis-ams-bounces@mailman.ccsds.org [<a href="mailto:sis-ams-bounces@mailman.ccsds.org]">mailto:sis-ams-bounces@mailman.ccsds.org]</a> <B>On Behalf Of </B>Scott Burleigh<BR>
<B>Sent:</B> Thursday, May 08, 2008 1:16 PM<BR>
<B>To:</B> sis-ams@mailman.ccsds.org<BR>
<B>Subject:</B> Re: [Sis-ams] Interoperability testing - transfer protocols<BR>
</SPAN></FONT></FONT><FONT SIZE="5"><FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'> <BR>
Ray, Timothy J. (GSFC-583.0) wrote: <BR>
</SPAN></FONT></FONT><FONT COLOR="#000080"><FONT SIZE="4"><FONT FACE="Arial"><SPAN STYLE='font-size:10pt'>Hello all,<BR>
<BR>
As an implementer of software to support interoperability testing, there are certain decisions that I have to make. Two key decisions are:<BR>
1)</SPAN></FONT></FONT><FONT SIZE="1"><FONT FACE="Times New Roman"><SPAN STYLE='font-size:7pt'> </SPAN></FONT></FONT><FONT SIZE="4"><FONT FACE="Arial"><SPAN STYLE='font-size:10pt'>What protocol(s) to support for transferring Meta-AMS messages<BR>
2)</SPAN></FONT></FONT><FONT SIZE="1"><FONT FACE="Times New Roman"><SPAN STYLE='font-size:7pt'> </SPAN></FONT></FONT><FONT SIZE="4"><FONT FACE="Arial"><SPAN STYLE='font-size:10pt'>What protocol(s) to support for transferring AMS messages directly between nodes<BR>
<BR>
Has our working group decided what, as a minimum, is required for our interoperability testing?<BR>
</SPAN></FONT></FONT></FONT><FONT SIZE="5"><FONT FACE="Times New Roman"><SPAN STYLE='font-size:12pt'>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.<BR>
<BR>
Scott<BR>
</SPAN></FONT></FONT><FONT SIZE="4"><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'><BR>
<HR ALIGN=CENTER SIZE="3" WIDTH="95%"></SPAN></FONT><FONT FACE="Consolas, Courier New, Courier"><SPAN STYLE='font-size:10pt'>_______________________________________________<BR>
Sis-ams mailing list<BR>
Sis-ams@mailman.ccsds.org<BR>
<a href="http://mailman.ccsds.org/cgi-bin/mailman/listinfo/sis-ams">http://mailman.ccsds.org/cgi-bin/mailman/listinfo/sis-ams</a><BR>
</SPAN></FONT></FONT></BLOCKQUOTE>
</BODY>
</HTML>