<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=iso-8859-1"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
span.EmailStyle23
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle24
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='color:#1F497D'>Dear CESG Members:<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Conditions for approval of CESG-P-2017-08-007 Approval to publish CCSDS 524.2-B-1, Mission Operations—Message Abstraction Layer Binding to TCP/IP Transport and Split Binary Encoding (Blue Book, Issue 1) have been resolved to the satisfaction of the AD who voted to approve with conditions. The Secretariat will now proceed with CMC polling.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><div><div style='mso-element:para-border-div;border:none;border-bottom:solid windowtext 1.0pt;padding:0in 0in 1.0pt 0in'><p class=MsoNormal style='border:none;padding:0in'><span style='font-size:12.0pt;font-family:"Times New Roman","serif";color:#1F497D'><o:p> </o:p></span></p></div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman","serif";color:#1F497D'>Thomas Gannett<o:p></o:p></span></p><p class=MsoNormal><a href="mailto:thomas.gannett@tgannett.net"><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'>thomas.gannett@tgannett.net</span></a><span style='font-size:12.0pt;font-family:"Times New Roman","serif";color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman","serif";color:#1F497D'>+1 443 472 0805<o:p></o:p></span></p></div><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> </span><a href="mailto:Mario.Merri@esa.int"><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>Mario.Merri@esa.int</span></a><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> [</span><a href="mailto:Mario.Merri@esa.int"><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>mailto:Mario.Merri@esa.int</span></a><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>] <br><b>Sent:</b> Friday, October 13, 2017 2:01 PM<br><b>To:</b> Thomas Gannett<br><b>Cc:</b> Danford S. Smith; Sam Cooper<br><b>Subject:</b> Fwd: MAL to TCP-IP binding<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Hi Tom,<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Could you please proceed with the required steps for publication? <o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Please let me know if we need to add the extra bullet agreed with Scott or if you could do it.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt'>Many thanks,<o:p></o:p></p><div id=AppleMailSignature><p class=MsoNormal>__Mario<o:p></o:p></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt'><br>Begin forwarded message:<o:p></o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=MsoNormal style='margin-bottom:12.0pt'><b>From:</b> "Burleigh, Scott C (312B)" <<a href="mailto:scott.c.burleigh@jpl.nasa.gov">scott.c.burleigh@jpl.nasa.gov</a>><br><b>Date:</b> 13 October 2017 at 17:06:19 CEST<br><b>To:</b> "<a href="mailto:Mario.Merri@esa.int">Mario.Merri@esa.int</a>" <<a href="mailto:Mario.Merri@esa.int">Mario.Merri@esa.int</a>><br><b>Cc:</b> "<a href="mailto:Cesar.Coelho@esa.int">Cesar.Coelho@esa.int</a>" <<a href="mailto:Cesar.Coelho@esa.int">Cesar.Coelho@esa.int</a>>, "<a href="mailto:dan.smith@nasa.gov">dan.smith@nasa.gov</a>" <<a href="mailto:dan.smith@nasa.gov">dan.smith@nasa.gov</a>>, "<a href="mailto:Jose.Luis.Feiteirinha@esa.int">Jose.Luis.Feiteirinha@esa.int</a>" <<a href="mailto:Jose.Luis.Feiteirinha@esa.int">Jose.Luis.Feiteirinha@esa.int</a>>, "<a href="mailto:Mehran.Sarkarati@esa.int">Mehran.Sarkarati@esa.int</a>" <<a href="mailto:Mehran.Sarkarati@esa.int">Mehran.Sarkarati@esa.int</a>>, "Champsavoir Nicolas " <<a href="mailto:Nicolas.Champsavoir@cnes.fr">Nicolas.Champsavoir@cnes.fr</a>>, "Sam Cooper" <<a href="mailto:sam@brightascension.com">sam@brightascension.com</a>><br><b>Subject:</b> <b>RE: MAL to TCP-IP binding</b><o:p></o:p></p></div></blockquote><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=MsoNormal>Thanks, Mario, I think the additional bullet is a helpful change; at least the reader will be directed to the appropriate supplemental specification. My condition is satisfied. It is possible that others may raise similar objections during Agency review, but let’s not delay that review any further.<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>Scott<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal><b>From:</b> <a href="mailto:Mario.Merri@esa.int">Mario.Merri@esa.int</a> [<a href="mailto:Mario.Merri@esa.int">mailto:Mario.Merri@esa.int</a>] <br><b>Sent:</b> Friday, October 13, 2017 3:44 AM<br><b>To:</b> Burleigh, Scott C (312B) <<a href="mailto:scott.c.burleigh@jpl.nasa.gov">scott.c.burleigh@jpl.nasa.gov</a>><br><b>Cc:</b> <a href="mailto:Cesar.Coelho@esa.int">Cesar.Coelho@esa.int</a>; <a href="mailto:dan.smith@nasa.gov">dan.smith@nasa.gov</a>; <a href="mailto:Jose.Luis.Feiteirinha@esa.int">Jose.Luis.Feiteirinha@esa.int</a>; <a href="mailto:Mehran.Sarkarati@esa.int">Mehran.Sarkarati@esa.int</a>; Champsavoir Nicolas <<a href="mailto:Nicolas.Champsavoir@cnes.fr">Nicolas.Champsavoir@cnes.fr</a>>; Sam Cooper <<a href="mailto:sam@brightascension.com">sam@brightascension.com</a>><br><b>Subject:</b> RE: MAL to TCP-IP binding<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Hi Scott,</span> <br><br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>thanks for resolving your condition. Nevertheless, since we take seriously your comment, I have discussed the matter further with Cesar and we came up with a small change that could better address your condition. Basically, it consists of modifying the Scope section by adding the bullet in red (see below).</span> <br><br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Would that work for you?</span> <br><br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Thanks,</span> <br><br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>__Mario</span> <br><br><b><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>1.2 SCOPE</span></b> <br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>The scope of this Recommended Standard is the specification of the binding in terms of technology mapping to the Transmission Control Protocol (TCP) over Internet Protocol (IP) of:</span> <br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>a) MAL message;</span> <br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>b) MAL Transport Interface.</span> <br><br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>The MAL Blue Book (reference [1]) specifies the MAL protocol in an abstract way, i.e., without defining the concrete protocol data units. The MAL binding to TCP/IP Transport protocol and the Split Binary Encoding specify a complete and unambiguous mapping of:</span> <br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>a) the MAL message to a binary Protocol Data Unit to be transmitted over TCP/IP;</span> <br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>b) the MAL transport interface to the TCP/IP interface;</span> <br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>c) the MAL data types to a binary encoding format (split binary encoding).</span> <br><br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>This Recommended Standard does not specify:</span> <br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>a) individual implementations or products;</span> <br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>b) the implementation of entities or interfaces within real systems.</span> <br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>c) recommendations nor best practices for deploying systems with proxies and/or firewalls.</span> <br><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:red'>d) a direct mapping to the sockets API as the TCP Protocol Specification (reference [4]) is unambiguously used for the mapping.</span> <br><br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>In a concrete deployment, on the wire interoperability between application layer MO Service consumer and provider will be achieved by encoding the abstract MAL messages in the concrete split binary encoding and transmitting them by means of TCP/IP PDUs, as defined in this Recommended Standard.</span> <br><br><br><br><span style='font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F'>From: </span><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>"Burleigh, Scott C (312B)" <</span><a href="mailto:scott.c.burleigh@jpl.nasa.gov"><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>scott.c.burleigh@jpl.nasa.gov</span></a><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>></span> <br><span style='font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F'>To: </span><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>"</span><a href="mailto:Cesar.Coelho@esa.int"><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>Cesar.Coelho@esa.int</span></a><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>" <</span><a href="mailto:Cesar.Coelho@esa.int"><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>Cesar.Coelho@esa.int</span></a><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>></span> <br><span style='font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F'>Cc: </span><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>Sam Cooper <</span><a href="mailto:sam@brightascension.com"><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>sam@brightascension.com</span></a><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>>, "</span><a href="mailto:dan.smith@nasa.gov"><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>dan.smith@nasa.gov</span></a><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>" <</span><a href="mailto:dan.smith@nasa.gov"><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>dan.smith@nasa.gov</span></a><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>>, "</span><a href="mailto:Mario.Merri@esa.int"><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>Mario.Merri@esa.int</span></a><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>" <</span><a href="mailto:Mario.Merri@esa.int"><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>Mario.Merri@esa.int</span></a><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>>, "</span><a href="mailto:Jose.Luis.Feiteirinha@esa.int"><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>Jose.Luis.Feiteirinha@esa.int</span></a><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>" <</span><a href="mailto:Jose.Luis.Feiteirinha@esa.int"><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>Jose.Luis.Feiteirinha@esa.int</span></a><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>>, "Champsavoir Nicolas" <</span><a href="mailto:Nicolas.Champsavoir@cnes.fr"><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>Nicolas.Champsavoir@cnes.fr</span></a><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>>, "</span><a href="mailto:Mehran.Sarkarati@esa.int"><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>Mehran.Sarkarati@esa.int</span></a><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>" <</span><a href="mailto:Mehran.Sarkarati@esa.int"><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>Mehran.Sarkarati@esa.int</span></a><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>></span> <br><span style='font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F'>Date: </span><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>11/10/2017 17:44</span> <br><span style='font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F'>Subject: </span><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>RE: MAL to TCP-IP binding</span> <o:p></o:p></p><div class=MsoNormal align=center style='text-align:center'><hr size=3 width="100%" noshade style='color:#A0A0A0' align=center></div><p class=MsoNormal><br><br><br><span style='font-size:10.0pt;color:#004080'>Hi, César. I think my comment is actually pretty self-explanatory: I believe the specification would be easier to implement if you mapped the MAL functions to the socket API, with which developers are very familiar, rather than to the formal TCP specification. You are free to take this suggestion or not, as you see fit; you have considered my suggestion, so please consider my condition satisfied. I certainly don’t have spare time for writing any new text for you to review.</span> <br><span style='font-size:10.0pt;color:#004080'> </span> <br><span style='font-size:10.0pt;color:#004080'>Scott</span> <br><a name="_MailEndCompose"></a><span style='font-size:10.0pt;color:#004080'> </span> <br><b><span style='font-size:10.0pt'>From:</span></b><span style='font-size:10.0pt'> </span><a href="mailto:Cesar.Coelho@esa.int"><span style='font-size:10.0pt'>Cesar.Coelho@esa.int</span></a><span style='font-size:10.0pt'> [</span><a href="mailto:Cesar.Coelho@esa.int"><span style='font-size:10.0pt'>mailto:Cesar.Coelho@esa.int</span></a><span style='font-size:10.0pt'>] <b><br>Sent:</b> Wednesday, October 11, 2017 8:03 AM<b><br>To:</b> Burleigh, Scott C (312B) <</span><a href="mailto:scott.c.burleigh@jpl.nasa.gov"><span style='font-size:10.0pt'>scott.c.burleigh@jpl.nasa.gov</span></a><span style='font-size:10.0pt'>><b><br>Cc:</b> Sam Cooper <</span><a href="mailto:sam@brightascension.com"><span style='font-size:10.0pt'>sam@brightascension.com</span></a><span style='font-size:10.0pt'>>; </span><a href="mailto:dan.smith@nasa.gov"><span style='font-size:10.0pt'>dan.smith@nasa.gov</span></a><span style='font-size:10.0pt'>; </span><a href="mailto:Mario.Merri@esa.int"><span style='font-size:10.0pt'>Mario.Merri@esa.int</span></a><span style='font-size:10.0pt'>; </span><a href="mailto:Jose.Luis.Feiteirinha@esa.int"><span style='font-size:10.0pt'>Jose.Luis.Feiteirinha@esa.int</span></a><span style='font-size:10.0pt'>; Champsavoir Nicolas <</span><a href="mailto:Nicolas.Champsavoir@cnes.fr"><span style='font-size:10.0pt'>Nicolas.Champsavoir@cnes.fr</span></a><span style='font-size:10.0pt'>>; </span><a href="mailto:Mehran.Sarkarati@esa.int"><span style='font-size:10.0pt'>Mehran.Sarkarati@esa.int</span></a><b><span style='font-size:10.0pt'><br>Subject:</span></b><span style='font-size:10.0pt'> Fw: MAL to TCP-IP binding</span> <br><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'> </span> <br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Dear Scott,</span><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'> <br></span><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>I was asked to agree with you on the new changes and write them in the book.</span><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'> </span><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>However, I must confess that I am a bit confused with the whole exchange of emails, so please bear with me.</span><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'> <br></span><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>In the original comment, one reads:</span><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'> </span><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>"It was not clear to me which MAL operations map to initiation and acceptance of TCP connections using "socket" terminology. I think most TCP developers</span><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'> </span><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>are more familiar with the socket API than with the TCP protocol specification, so I think adding some notes on this mapping might improve implementation success."</span><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'> <br></span><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>I understand that developers are more familiar with the socket API (<u>SOCKET, BIND, LISTEN, ACCEPT, CONNECT</u>, SEND, RECEIVE, CLOSE) specification than with the TCP (<u>OPEN</u>, SEND, RECEIVE, CLOSE) specification as you state. However throughout the document, the TCP specification was used (RFC 793).</span><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'> <br></span><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>The establishment of the connections is present in page 49 and 51 for TRANSMIT REQUEST and RECEIVE INDICATION respectively. It uses the TCP OPEN primitive, as this is the specification the book is mapping to.</span><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'> <br></span><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>What exactly would you like to see in the book?</span><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'> </span><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>It would be great if you could propose your changes to be included and we would review them.</span><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'> <br></span><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>Thank you very much for your time.</span><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'> <br></span><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>Best regards,</span><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'> </span><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>César Coelho</span><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'> <br><br><br><br><br><br><br></span><span style='font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F'><br>From: </span><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>"Burleigh, Scott C (312B)" <</span><a href="mailto:scott.c.burleigh@jpl.nasa.gov"><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>scott.c.burleigh@jpl.nasa.gov</span></a><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>></span><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'> </span><span style='font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F'><br>To: </span><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>"</span><a href="mailto:Mehran.Sarkarati@esa.int"><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>Mehran.Sarkarati@esa.int</span></a><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>" <</span><a href="mailto:Mehran.Sarkarati@esa.int"><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>Mehran.Sarkarati@esa.int</span></a><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>></span><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'> </span><span style='font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F'><br>Cc: </span><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>Sam Cooper <</span><a href="mailto:sam@brightascension.com"><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>sam@brightascension.com</span></a><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>>, "</span><a href="mailto:dan.smith@nasa.gov"><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>dan.smith@nasa.gov</span></a><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>" <</span><a href="mailto:dan.smith@nasa.gov"><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>dan.smith@nasa.gov</span></a><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>>, "</span><a href="mailto:Mario.Merri@esa.int"><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>Mario.Merri@esa.int</span></a><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>" <</span><a href="mailto:Mario.Merri@esa.int"><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>Mario.Merri@esa.int</span></a><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>>, "</span><a href="mailto:Jose.Luis.Feiteirinha@esa.int"><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>Jose.Luis.Feiteirinha@esa.int</span></a><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>" <</span><a href="mailto:Jose.Luis.Feiteirinha@esa.int"><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>Jose.Luis.Feiteirinha@esa.int</span></a><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>>, "Champsavoir Nicolas" <</span><a href="mailto:Nicolas.Champsavoir@cnes.fr"><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>Nicolas.Champsavoir@cnes.fr</span></a><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>></span><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'> </span><span style='font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F'><br>Date: </span><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>05/10/2017 17:53</span><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'> </span><span style='font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F'><br>Subject: </span><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>RE: MAL to TCP-IP binding</span><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'> </span><o:p></o:p></p><div class=MsoNormal align=center style='text-align:center'><hr size=3 width="100%" noshade style='color:#A0A0A0' align=center></div><p class=MsoNormal><br><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'><br><br></span><span style='font-size:10.0pt'><br>Mehran, I think your assumption (at the bottom of this email) is correct, and I think there just ought to be a sentence or two to this effect somewhere at the start of the specification.</span><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'> </span><span style='font-size:10.0pt'><br></span><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'> </span><span style='font-size:10.0pt'><br>Scott</span><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'> </span><span style='font-size:10.0pt'><br></span><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'> </span><b><span style='font-size:10.0pt'><br>From:</span></b><span style='font-size:10.0pt'> </span><a href="mailto:Mehran.Sarkarati@esa.int"><span style='font-size:10.0pt'>Mehran.Sarkarati@esa.int</span></a><span style='font-size:10.0pt'> [</span><a href="mailto:Mehran.Sarkarati@esa.int"><span style='font-size:10.0pt'>mailto:Mehran.Sarkarati@esa.int</span></a><span style='font-size:10.0pt'>] <b><br>Sent:</b> Thursday, October 5, 2017 4:12 AM<b><br>To:</b> Burleigh, Scott C (312B) <</span><a href="mailto:scott.c.burleigh@jpl.nasa.gov"><span style='font-size:10.0pt'>scott.c.burleigh@jpl.nasa.gov</span></a><span style='font-size:10.0pt'>><b><br>Cc:</b> Sam Cooper <</span><a href="mailto:sam@brightascension.com"><span style='font-size:10.0pt'>sam@brightascension.com</span></a><span style='font-size:10.0pt'>>; </span><a href="mailto:dan.smith@nasa.gov"><span style='font-size:10.0pt'>dan.smith@nasa.gov</span></a><span style='font-size:10.0pt'>; </span><a href="mailto:Mario.Merri@esa.int"><span style='font-size:10.0pt'>Mario.Merri@esa.int</span></a><span style='font-size:10.0pt'>; </span><a href="mailto:Jose.Luis.Feiteirinha@esa.int"><span style='font-size:10.0pt'>Jose.Luis.Feiteirinha@esa.int</span></a><span style='font-size:10.0pt'>; Champsavoir Nicolas <</span><a href="mailto:Nicolas.Champsavoir@cnes.fr"><span style='font-size:10.0pt'>Nicolas.Champsavoir@cnes.fr</span></a><span style='font-size:10.0pt'>><b><br>Subject:</b> Fw: MAL to TCP-IP binding</span><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'> </span><span style='font-size:10.0pt'><br></span><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'> </span><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>Dear Scott,</span><span style='font-size:10.0pt'> </span><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br><br>We have been discussing on our side the condition, which you had raised during the review of the MAL to TCP/IP binding book:</span><span style='font-size:10.0pt'> </span><span style='font-size:12.0pt;font-family:"Courier New"'><br><br>It was not clear to me which MAL operations map to initiation and acceptance of TCP connections using "socket" terminology. I think most TCP developers<br>are more familiar with the socket API than with the TCP protocol specification, so I think adding some notes on this mapping might improve implementation success."</span><span style='font-size:10.0pt'> </span><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br><br>To be honest, I am not sure if we have fully and correctly understood your condition and I have to say I am no expert in this domain.</span><span style='font-size:10.0pt'> </span><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br><br>The best answer I have gathered so far is from our experts is the one below. Please have a look and let me know if this is answering your condition sufficiently? If so, we can certainly add a corresponding explanation in the book to explain what is at the level of the binding and what a typical implementation would do.</span><span style='font-size:10.0pt'> </span><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br><br>Kind Regards</span><span style='font-size:10.0pt'> </span><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>Mehran</span><span style='font-size:10.0pt'> <br></span><span style='font-size:7.5pt;font-family:"Arial","sans-serif";color:purple'><br><br>----- Forwarded by Mehran Sarkarati/esoc/ESA on 05/10/2017 13:02 -----</span><span style='font-size:10.0pt'> </span><span style='font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F'><br><br>From: </span><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>José Luís Feiteirinha <</span><a href="mailto:jose.luis.feiteirinha@esa.int"><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>jose.luis.feiteirinha@esa.int</span></a><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>></span><span style='font-size:10.0pt'> </span><span style='font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F'><br>To: </span><a href="mailto:Mehran.Sarkarati@esa.int"><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>Mehran.Sarkarati@esa.int</span></a><span style='font-size:10.0pt'> </span><span style='font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F'><br>Cc: </span><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>"</span><a href="mailto:Cesar.Coelho@esa.int"><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>Cesar.Coelho@esa.int</span></a><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>" <</span><a href="mailto:Cesar.Coelho@esa.int"><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>Cesar.Coelho@esa.int</span></a><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>>, Thomas Pignede <</span><a href="mailto:thomas.pignede@hotmail.de"><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>thomas.pignede@hotmail.de</span></a><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>>, Dario Lucia <</span><a href="mailto:Dario.Lucia@telespazio-vega.de"><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>Dario.Lucia@telespazio-vega.de</span></a><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>>, </span><a href="mailto:Mario.Merri@esa.int"><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>Mario.Merri@esa.int</span></a><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>, Sam Cooper <</span><a href="mailto:sam@brightascension.com"><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>sam@brightascension.com</span></a><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>></span><span style='font-size:10.0pt'> </span><span style='font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F'><br>Date: </span><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>05/10/2017 08:55</span><span style='font-size:10.0pt'> </span><span style='font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F'><br>Subject: </span><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>Re: Fwd: TCP-IP binding</span><span style='font-size:10.0pt'> </span><o:p></o:p></p><div class=MsoNormal align=center style='text-align:center'><hr size=3 width="100%" noshade style='color:#A0A0A0' align=center></div><p class=MsoNormal><br><span style='font-size:10.0pt'><br><br></span><span style='font-size:12.0pt'><br><br>HI Mehran,</span><span style='font-size:10.0pt'> </span><o:p></o:p></p><p>From what I recall from Thomas, this can be a common misconception. I'll go through it briefly and explain my current understanding. <o:p></o:p></p><p>Typical sockets work the following way: <o:p></o:p></p><p>1) There is socket server running on a specific TCP port, let's call it the TCP-Server. <o:p></o:p></p><p>2) When 'someone' connects to a TCP-server, a <b>random</b> port (between <span style='font-size:13.5pt'>32768 and 65535) is attributed to the client. Let's call it the TCP-client.</span> <o:p></o:p></p><p><span style='font-size:13.5pt'>3) Afterwards all messages from the TCP-server to the TCP-client set the "TCP Destination Port" to be the <i>randomly </i>attributed TCP-client's port and vice-versa.</span> <o:p></o:p></p><p>Now, for the TCP IP binding we mapped the "URI From" and "URI To" <i>partially</i> to the corresponding TCP/IP port. <u>But we do not expect that the consumer's URI will be randomly defined by the socket layer</u>. <o:p></o:p></p><p>For this reason the sockets are not instantiated as for typical TCP sockets, rather than that, we specifically tell, we'd like a TCP-IP client to be established from that specific port (the one we've agreed in the URI). <o:p></o:p></p><p>I think that above covers it, assuming my understanding is correct. <o:p></o:p></p><p>That was also what I briefly intended to cover when I wrote: <i>"The concept of the MAL TCP/IP binding is independent from the typical TCP/IP server/client socket configuration (i.e. doesn't care who is the socket server or client in case the link was established using traditional sockets) . However it can work on top of any existing TCP/IP sockets so-long the mapping of URI to TCP (port) and IP(address) are respected."</i> <o:p></o:p></p><p style='margin-bottom:12.0pt'><br>Cheers,<br>José<br><br><br>On 03/10/2017 8:49 PM, <a href="mailto:Mehran.Sarkarati@esa.int">Mehran.Sarkarati@esa.int</a> wrote: <span style='font-family:"Courier New"'><br><br><br><br><br>Hi ,<br><br>I have very little understanding of the TCP/IP protocol and the socket API.<br><br>Reading he RID raised by Scott, I understand he is asking "Who and how is the<br>TCP/IP connection established". As we do not have a "connect" operation like<br>in SLE, I understand his question to be how is the tcp/ip hand-shake done and<br>the connection initiated as there is no corresponding MAL operation for this.<br><br>Am I right in assuming that someone "as part of the implementation" must<br>initiate the TCP/IP connection and open a connection before MAL interactions<br>can happen?<br><br>If yes, is the book clear on how this is supposed to happen?<br><br>@Dario, Thomas: I would appreciate an answer from your side as well.<br><br>Cheers<br>Mehran<br><br></span><br><span style='font-size:10.0pt;font-family:"Courier New"'><br>This message and any attachments are intended for the use of the addressee or addressees only.</span> <span style='font-size:10.0pt;font-family:"Courier New"'><br>The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its</span> <span style='font-size:10.0pt;font-family:"Courier New"'><br>content is not permitted.</span> <span style='font-size:10.0pt;font-family:"Courier New"'><br>If you received this message in error, please notify the sender and delete it from your system.</span> <span style='font-size:10.0pt;font-family:"Courier New"'><br>Emails can be altered and their integrity cannot be guaranteed by the sender.</span> <span style='font-size:10.0pt;font-family:"Courier New"'><br></span> <span style='font-size:10.0pt;font-family:"Courier New"'><br>Please consider the environment before printing this email.</span> <span style='font-size:10.0pt;font-family:"Courier New"'><br></span> <br><span style='font-size:10.0pt;font-family:"Courier New"'>This message and any attachments are intended for the use of the addressee or addressees only.</span> <br><span style='font-size:10.0pt;font-family:"Courier New"'>The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its</span> <br><span style='font-size:10.0pt;font-family:"Courier New"'>content is not permitted.</span> <br><span style='font-size:10.0pt;font-family:"Courier New"'>If you received this message in error, please notify the sender and delete it from your system.</span> <br><span style='font-size:10.0pt;font-family:"Courier New"'>Emails can be altered and their integrity cannot be guaranteed by the sender.</span> <br><span style='font-size:10.0pt;font-family:"Courier New"'> </span> <br><span style='font-size:10.0pt;font-family:"Courier New"'>Please consider the environment before printing this email.</span> <br><span style='font-size:10.0pt;font-family:"Courier New"'> </span> <o:p></o:p></p><pre>This message and any attachments are intended for the use of the addressee or addressees only.<o:p></o:p></pre><pre>The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its<o:p></o:p></pre><pre>content is not permitted.<o:p></o:p></pre><pre>If you received this message in error, please notify the sender and delete it from your system.<o:p></o:p></pre><pre>Emails can be altered and their integrity cannot be guaranteed by the sender.<o:p></o:p></pre><pre> <o:p></o:p></pre><pre>Please consider the environment before printing this email.<o:p></o:p></pre><pre> <o:p></o:p></pre></div></blockquote></div><pre>This message and any attachments are intended for the use of the addressee or addressees only.<o:p></o:p></pre><pre>The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its<o:p></o:p></pre><pre>content is not permitted.<o:p></o:p></pre><pre>If you received this message in error, please notify the sender and delete it from your system.<o:p></o:p></pre><pre>Emails can be altered and their integrity cannot be guaranteed by the sender.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Please consider the environment before printing this email.<o:p></o:p></pre><pre><o:p> </o:p></pre></div></body></html>