<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=utf-8"><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:"MS Mincho";
panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
{font-family:"MS Mincho";
panose-1:2 2 6 9 4 2 5 8 3 4;}
@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;}
@font-face
{font-family:Georgia;
panose-1:2 4 5 2 5 4 5 2 3 3;}
@font-face
{font-family:"\@MS Mincho";
panose-1:2 2 6 9 4 2 5 8 3 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","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;}
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";}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
font-family:"Calibri","sans-serif";}
@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='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Dear CESG Members:<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Conditions for approval of CESG-P-2017-06-004 Approval to release CCSDS 524.4-R-1, Mission Operations—Message Abstraction Layer Binding to ZMTP Transport (Red Book, Issue 1) for CCSDS Agency review have been resolved to the satisfaction of the ADs 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='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><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='color:#1F497D'><o:p> </o:p></span></p></div><p class=MsoNormal><span style='color:#1F497D'>Thomas Gannett<o:p></o:p></span></p><p class=MsoNormal><a href="mailto:thomas.gannett@tgannett.net">thomas.gannett@tgannett.net</a><span style='color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>+1 443 472 0805<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><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"'> Barkley, Erik J (3970) [<a href="mailto:erik.j.barkley@jpl.nasa.gov">mailto:erik.j.barkley@jpl.nasa.gov</a>] <br><b>Sent:</b> Thursday, October 12, 2017 1:10 PM<br><b>To:</b> Champsavoir Nicolas; Shames, Peter M (312B); Burleigh, Scott C (312B); <a href="mailto:Gian.Paolo.Calzolari@esa.int">Gian.Paolo.Calzolari@esa.int</a><br><b>Cc:</b> <a href="mailto:thomas.gannett@tgannett.net">thomas.gannett@tgannett.net</a>; <a href="mailto:Mario.Merri@esa.int">Mario.Merri@esa.int</a>; Behal Brigitte; Smith, Danford S. (GSFC-5800); Sam Cooper (<a href="mailto:sam@brightascension.com">sam@brightascension.com</a>); <a href="mailto:Cesar.Coelho@esa.int">Cesar.Coelho@esa.int</a>; <a href="mailto:Mehran.Sarkarati@esa.int">Mehran.Sarkarati@esa.int</a>; <a href="mailto:Philip.Brabbin@esa.int">Philip.Brabbin@esa.int</a>; <a href="mailto:dominik.marszk@esa.int">dominik.marszk@esa.int</a><br><b>Subject:</b> RE: CCSDS 524.4-R-1 (MAL Binding to ZMTP) Comments Disposition<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-family:"Georgia","serif";color:#1F497D'>Dear Nicolas,<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Georgia","serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Georgia","serif";color:#1F497D'>The new annex retires my condition for the poll. My thanks to you and the working group for providing the new annex.<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Georgia","serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Georgia","serif";color:#1F497D'>Best regards,<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Georgia","serif";color:#1F497D'>-Erik<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><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> Thursday, October 05, 2017 12:40 PM<br><b>To:</b> </span><a href="mailto:thomas.gannett@tgannett.net"><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>thomas.gannett@tgannett.net</span></a><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'><br><b>Cc:</b> </span><a href="mailto:sam@brightascension.com"><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>sam@brightascension.com</span></a><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>; </span><a href="mailto:danford.s.smith@nasa.gov"><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>danford.s.smith@nasa.gov</span></a><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'><br><b>Subject:</b> Re: CCSDS 524.4-R-1 (MAL Binding to ZMTP) Comments Disposition<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Hi Tom,</span> <br><br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>I guess with these emails you can proceed with calling the Agency Review.</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><span style='font-size:7.5pt;font-family:"Arial","sans-serif";color:purple'>----- Forwarded by Mario Merri/esoc/ESA on 05/10/2017 18:38 -----</span> <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"'>"Shames, Peter M (312B)" <</span><a href="mailto:peter.m.shames@jpl.nasa.gov"><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>peter.m.shames@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"'>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"'>>, "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><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'>Cc: </span><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>Behal Brigitte <</span><a href="mailto:Brigitte.Behal@cnes.fr"><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>Brigitte.Behal@cnes.fr</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><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"'>>, "Smith, Danford S. (GSFC-5800)" <</span><a href="mailto:danford.s.smith@nasa.gov"><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>danford.s.smith@nasa.gov</span></a><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>>, "</span><a href="mailto:dominik.marszk@esa.int"><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>dominik.marszk@esa.int</span></a><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>" <</span><a href="mailto:dominik.marszk@esa.int"><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>dominik.marszk@esa.int</span></a><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>>, "Barkley, Erik J (3970)" <</span><a href="mailto:erik.j.barkley@jpl.nasa.gov"><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>erik.j.barkley@jpl.nasa.gov</span></a><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>>, "</span><a href="mailto:Gian.Paolo.Calzolari@esa.int"><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>Gian.Paolo.Calzolari@esa.int</span></a><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>" <</span><a href="mailto:Gian.Paolo.Calzolari@esa.int"><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>Gian.Paolo.Calzolari@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: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"'>>, 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:Philip.Brabbin@esa.int"><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>Philip.Brabbin@esa.int</span></a><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>" <</span><a href="mailto:Philip.Brabbin@esa.int"><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>Philip.Brabbin@esa.int</span></a><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>>, "</span><a href="mailto:thomas.gannett@tgannett.net"><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>thomas.gannett@tgannett.net</span></a><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>" <</span><a href="mailto:thomas.gannett@tgannett.net"><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>thomas.gannett@tgannett.net</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"'>05/10/2017 17:51</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: CCSDS 524.4-R-1 (MAL Binding to ZMTP) Comments Disposition</span> <o:p></o:p></p><div class=MsoNormal align=center style='text-align:center'><hr size=2 width="100%" noshade style='color:#A0A0A0' align=center></div><p class=MsoNormal><br><br><br><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>I agree as well. </span> <br><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'> </span> <br><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>After looking back at some of the other MO materials it appears that you use the term "transport service" a rather broad reference and not "transport layer", which would normally be read as a reference to the ISO Transport Layer. I think that "transfer service" would be even better, since you use a very broad description of what this means and this avoids the confusion altogether.</span> <br><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'> </span> <br><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>Regards, Peter</span> <br><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'> </span> <br><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'> </span> <br><b>From: </b>Sam Cooper <<a href="mailto:sam@brightascension.com">sam@brightascension.com</a>><b><br>Date: </b>Thursday, October 5, 2017 at 8:36 AM<b><br>To: </b>Scott Burleigh <<a href="mailto:scott.c.burleigh@jpl.nasa.gov">scott.c.burleigh@jpl.nasa.gov</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>><b><br>Cc: </b>Brigitte Behal <<a href="mailto:Brigitte.Behal@cnes.fr">Brigitte.Behal@cnes.fr</a>>, "<a href="mailto:Cesar.Coelho@esa.int">Cesar.Coelho@esa.int</a>" <<a href="mailto:Cesar.Coelho@esa.int">Cesar.Coelho@esa.int</a>>, Dan Smith <<a href="mailto:danford.s.smith@nasa.gov">danford.s.smith@nasa.gov</a>>, "<a href="mailto:dominik.marszk@esa.int">dominik.marszk@esa.int</a>" <<a href="mailto:dominik.marszk@esa.int">dominik.marszk@esa.int</a>>, Erik Barkley <<a href="mailto:erik.j.barkley@jpl.nasa.gov">erik.j.barkley@jpl.nasa.gov</a>>, Gian Paolo Calzolari <<a href="mailto:Gian.Paolo.Calzolari@esa.int">Gian.Paolo.Calzolari@esa.int</a>>, Mario Merri <<a href="mailto:Mario.Merri@esa.int">Mario.Merri@esa.int</a>>, Champsavoir Nicolas <<a href="mailto:Nicolas.Champsavoir@cnes.fr">Nicolas.Champsavoir@cnes.fr</a>>, Peter Shames <<a href="mailto:peter.m.shames@jpl.nasa.gov">peter.m.shames@jpl.nasa.gov</a>>, "<a href="mailto:Philip.Brabbin@esa.int">Philip.Brabbin@esa.int</a>" <<a href="mailto:Philip.Brabbin@esa.int">Philip.Brabbin@esa.int</a>>, Tom Gannett <<a href="mailto:thomas.gannett@tgannett.net">thomas.gannett@tgannett.net</a>><b><br>Subject: </b>Re: CCSDS 524.4-R-1 (MAL Binding to ZMTP) Comments Disposition <br><span style='font-size:10.0pt'> </span> <br>Hi Scott,<br><br>I was wondering if we could move this condition to a review RID item? In our WG teleconference yesterday we thought that this issue is something the working group could discuss at the technical workshop seeing as yourself and Peter have identified it as a wider issue with MO.<br><br>My view is that whilst it is important it does not have an effect on the technical content of the red book so we should continue the agency review and deal with it during that, if that is ok with you?<br><br>Cheers,<br>Sam.<br><br>On 05/10/2017 01:19, Burleigh, Scott C (312B) wrote: <br><span style='font-size:10.0pt;font-family:"Calibri","sans-serif";color:#004080'>Nicolas, how about this? I am fine with calling ZMTP a “transport service”, which I think is consistent with the MO operations concept. Let’s just not say it is at the “transport layer” or call it a “transport protocol”, which I believe has a specific meaning to the world beyond MO.</span> <br><span style='font-size:10.0pt;font-family:"Calibri","sans-serif";color:#004080'> </span> <br><span style='font-size:10.0pt;font-family:"Calibri","sans-serif";color:#004080'>Scott</span> <br><a name="_MailEndCompose"></a><span style='font-size:10.0pt;font-family:"Calibri","sans-serif";color:#004080'> </span> <br><b><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'> </span><a href="mailto:Mehran.Sarkarati@esa.int"><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>Mehran.Sarkarati@esa.int</span></a><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'> [</span><a href="mailto:Mehran.Sarkarati@esa.int"><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>mailto:Mehran.Sarkarati@esa.int</span></a><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>] <b><br>Sent:</b> Tuesday, October 3, 2017 1:35 PM<b><br>To:</b> Burleigh, Scott C (312B) </span><a href="mailto:scott.c.burleigh@jpl.nasa.gov"><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'><scott.c.burleigh@jpl.nasa.gov></span></a><b><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'><br>Cc:</span></b><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'> Behal Brigitte </span><a href="mailto:Brigitte.Behal@cnes.fr"><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'><Brigitte.Behal@cnes.fr></span></a><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>; </span><a href="mailto:Cesar.Coelho@esa.int"><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>Cesar.Coelho@esa.int</span></a><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>; Smith, Danford S. (GSFC-5800) </span><a href="mailto:danford.s.smith@nasa.gov"><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'><danford.s.smith@nasa.gov></span></a><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>; </span><a href="mailto:dominik.marszk@esa.int"><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>dominik.marszk@esa.int</span></a><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>; Barkley, Erik J (3970) </span><a href="mailto:erik.j.barkley@jpl.nasa.gov"><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'><erik.j.barkley@jpl.nasa.gov></span></a><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>; </span><a href="mailto:Gian.Paolo.Calzolari@esa.int"><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>Gian.Paolo.Calzolari@esa.int</span></a><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>; </span><a href="mailto:Mario.Merri@esa.int"><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>Mario.Merri@esa.int</span></a><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>; Champsavoir Nicolas </span><a href="mailto:Nicolas.Champsavoir@cnes.fr"><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'><Nicolas.Champsavoir@cnes.fr></span></a><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>; Shames, Peter M (312B) </span><a href="mailto:peter.m.shames@jpl.nasa.gov"><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'><peter.m.shames@jpl.nasa.gov></span></a><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>; </span><a href="mailto:Philip.Brabbin@esa.int"><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>Philip.Brabbin@esa.int</span></a><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>; Sam Cooper (</span><a href="mailto:sam@brightascension.com"><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>sam@brightascension.com</span></a><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>) </span><a href="mailto:sam@brightascension.com"><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'><sam@brightascension.com></span></a><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>; </span><a href="mailto:thomas.gannett@tgannett.net"><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'>thomas.gannett@tgannett.net</span></a><b><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'><br>Subject:</span></b><span style='font-size:10.0pt;font-family:"Calibri","sans-serif"'> RE: CCSDS 524.4-R-1 (MAL Binding to ZMTP) Comments Disposition</span> <br> <br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Dear all,</span> <br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>All so far published MO books, including the reference architecture, the concept book, the MAL, the COM and other binding books such as SPP refer to what is below MAL as "Transport".</span> <br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>This is also the adopted terminology for http and tcp/ip binding.</span> <br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>I do not think this is wrong. This is a different level of abstraction than OSI and does not contradict that what we refer to as "transport" is itself broken into other layers in OSI terminology. This can be made clear in the book.</span> <br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>While understanding the point from Scott, I would find it a bad idea and extremely confusing, if we now start in one particular book to change it while all other MO books refer to MAL to "Transport" interface.</span> <br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>Seen from MAL, MAL has an API to what is below. This interface is pretty simple: send Message and receive Message. Now depending on what we are binding the MAL to, we are at different layers of OSI.</span> <br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>I suggest to record this and in the five years update of the MAL and in the currently ongoing update of the green book explain this better.</span> <br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>Anything else would break the consistency of the MO standards and all published books.</span> <br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>Regards</span> <span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>Mehran</span> <br><br><br><br><br><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:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F'><br>To: </span><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>"Shames, Peter M (312B)" <</span><a href="mailto:peter.m.shames@jpl.nasa.gov"><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>peter.m.shames@jpl.nasa.gov</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:Gian.Paolo.Calzolari@esa.int"><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>Gian.Paolo.Calzolari@esa.int</span></a><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>" <</span><a href="mailto:Gian.Paolo.Calzolari@esa.int"><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>Gian.Paolo.Calzolari@esa.int</span></a><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>>, "Barkley, Erik J (3970)" <</span><a href="mailto:erik.j.barkley@jpl.nasa.gov"><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>erik.j.barkley@jpl.nasa.gov</span></a><span style='font-size:7.5pt;font-family:"Arial","sans-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"'>"</span><a href="mailto:thomas.gannett@tgannett.net"><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>thomas.gannett@tgannett.net</span></a><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>" <</span><a href="mailto:thomas.gannett@tgannett.net"><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>thomas.gannett@tgannett.net</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"'>>, Behal Brigitte <</span><a href="mailto:Brigitte.Behal@cnes.fr"><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>Brigitte.Behal@cnes.fr</span></a><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>>, "Smith, Danford S. (GSFC-5800)" <</span><a href="mailto:danford.s.smith@nasa.gov"><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>danford.s.smith@nasa.gov</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><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: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><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><a href="mailto:Philip.Brabbin@esa.int"><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>Philip.Brabbin@esa.int</span></a><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>" <</span><a href="mailto:Philip.Brabbin@esa.int"><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>Philip.Brabbin@esa.int</span></a><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>>, "</span><a href="mailto:dominik.marszk@esa.int"><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>dominik.marszk@esa.int</span></a><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>" <</span><a href="mailto:dominik.marszk@esa.int"><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>dominik.marszk@esa.int</span></a><span style='font-size:7.5pt;font-family:"Arial","sans-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"'>03/10/2017 22:18</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: CCSDS 524.4-R-1 (MAL Binding to ZMTP) Comments Disposition</span> <o:p></o:p></p><div class=MsoNormal align=center style='text-align:center'><hr size=2 width="100%" noshade style='color:#A0A0A0' align=center></div><p class=MsoNormal style='margin-bottom:12.0pt'><br><br><br><span style='font-family:"Arial","sans-serif";color:#004080'><br>Hi, Nicolas. To echo Peter, I too favor standards consistency, and unfortunately the standard use of the term “transport” is apparently not the way MO uses that term. There may be some strong argument for adopting terminology in MOIMS that is at variance with the terminology used by the rest of the world, but I’m not yet aware of that argument.</span> <span style='font-family:"Arial","sans-serif";color:#004080'><br></span> <span style='font-family:"Arial","sans-serif";color:#004080'><br>Scott</span> <span style='font-family:"Arial","sans-serif";color:#004080'><br></span> <b><span style='font-family:"Arial","sans-serif"'><br>From:</span></b><span style='font-family:"Arial","sans-serif"'> Shames, Peter M (312B) <b><br>Sent:</b> Tuesday, October 3, 2017 8:32 AM<b><br>To:</b> Champsavoir Nicolas <</span><a href="mailto:Nicolas.Champsavoir@cnes.fr"><span style='font-family:"Arial","sans-serif"'>Nicolas.Champsavoir@cnes.fr</span></a><span style='font-family:"Arial","sans-serif"'>>; Burleigh, Scott C (312B) <</span><a href="mailto:scott.c.burleigh@jpl.nasa.gov"><span style='font-family:"Arial","sans-serif"'>scott.c.burleigh@jpl.nasa.gov</span></a><span style='font-family:"Arial","sans-serif"'>>; </span><a href="mailto:Gian.Paolo.Calzolari@esa.int"><span style='font-family:"Arial","sans-serif"'>Gian.Paolo.Calzolari@esa.int</span></a><span style='font-family:"Arial","sans-serif"'>; Barkley, Erik J (3970) <</span><a href="mailto:erik.j.barkley@jpl.nasa.gov"><span style='font-family:"Arial","sans-serif"'>erik.j.barkley@jpl.nasa.gov</span></a><span style='font-family:"Arial","sans-serif"'>><b><br>Cc:</b> </span><a href="mailto:thomas.gannett@tgannett.net"><span style='font-family:"Arial","sans-serif"'>thomas.gannett@tgannett.net</span></a><span style='font-family:"Arial","sans-serif"'>; </span><a href="mailto:Mario.Merri@esa.int"><span style='font-family:"Arial","sans-serif"'>Mario.Merri@esa.int</span></a><span style='font-family:"Arial","sans-serif"'>; Behal Brigitte <</span><a href="mailto:Brigitte.Behal@cnes.fr"><span style='font-family:"Arial","sans-serif"'>Brigitte.Behal@cnes.fr</span></a><span style='font-family:"Arial","sans-serif"'>>; Smith, Danford S. (GSFC-5800) <</span><a href="mailto:danford.s.smith@nasa.gov"><span style='font-family:"Arial","sans-serif"'>danford.s.smith@nasa.gov</span></a><span style='font-family:"Arial","sans-serif"'>>; Sam Cooper (</span><a href="mailto:sam@brightascension.com"><span style='font-family:"Arial","sans-serif"'>sam@brightascension.com</span></a><span style='font-family:"Arial","sans-serif"'>) <</span><a href="mailto:sam@brightascension.com"><span style='font-family:"Arial","sans-serif"'>sam@brightascension.com</span></a><span style='font-family:"Arial","sans-serif"'>>; </span><a href="mailto:Cesar.Coelho@esa.int"><span style='font-family:"Arial","sans-serif"'>Cesar.Coelho@esa.int</span></a><span style='font-family:"Arial","sans-serif"'>; </span><a href="mailto:Mehran.Sarkarati@esa.int"><span style='font-family:"Arial","sans-serif"'>Mehran.Sarkarati@esa.int</span></a><span style='font-family:"Arial","sans-serif"'>; </span><a href="mailto:Philip.Brabbin@esa.int"><span style='font-family:"Arial","sans-serif"'>Philip.Brabbin@esa.int</span></a><span style='font-family:"Arial","sans-serif"'>; </span><a href="mailto:dominik.marszk@esa.int"><span style='font-family:"Arial","sans-serif"'>dominik.marszk@esa.int</span></a><b><span style='font-family:"Arial","sans-serif"'><br>Subject:</span></b><span style='font-family:"Arial","sans-serif"'> Re: CCSDS 524.4-R-1 (MAL Binding to ZMTP) Comments Disposition</span> <br> <span style='font-family:"Arial","sans-serif"'><br>Dear All,</span> <span style='font-family:"Arial","sans-serif"'><br></span> <span style='font-family:"Arial","sans-serif"'><br>I must agree with Scott that ZMTP, and any other similar data (or message) transfer layer is not a "transport" layer in the common and widely used ISO BRM definition of the term. Yes, we do know that the ISO BRM does not, per se, define a "messaging layer". That said, the functions that are defined in the ISO BRM Session Layer are, I believe, really much like what is defined as "MAL" functions.</span> <span style='font-family:"Arial","sans-serif"'><br></span> <span style='font-family:"Arial","sans-serif"'><br>I would draw your attention to the following quote from Sec 7.3.3 of the ISO BRM, ISO/IEC 7498-1.</span> <span style='font-family:"Arial","sans-serif"'><br></span> <b><span style='font-family:"Arial","sans-serif"'><br>7.3.3 Services provided to the Presentation Layer <span style='color:red'>[by the Session Layer]</span></span></b> <b><span style='font-family:"Arial","sans-serif"'><br>7.3.3.1 General <br>7.3.3.1.1 </span></b><span style='font-family:"Arial","sans-serif"'><br>In connection-mode, the services provided by the Session Layer are described below: <br>a) session-connection establishment;</span><span style='font-family:"MS Mincho"'>
</span> <span style='font-family:"Arial","sans-serif"'><br>b) session-connection release;</span><span style='font-family:"MS Mincho"'>
</span> <span style='font-family:"Arial","sans-serif"'><br>c) normal data transfer; <br>d) expedited data transfer;</span><span style='font-family:"MS Mincho"'>
</span> <span style='font-family:"Arial","sans-serif"'><br>e) token management;</span><span style='font-family:"MS Mincho"'>
</span> <span style='font-family:"Arial","sans-serif"'><br>f) session-connection synchronization; <br>g) exception reporting;</span><span style='font-family:"MS Mincho"'>
</span> <span style='font-family:"Arial","sans-serif"'><br>h) activity management;</span><span style='font-family:"MS Mincho"'>
</span> <span style='font-family:"Arial","sans-serif"'><br>j) typed data transfer; and</span><span style='font-family:"MS Mincho"'>
</span> <span style='font-family:"Arial","sans-serif"'><br>k) resynchronization. <br></span> <span style='font-family:"Arial","sans-serif"'><br>I'd suggest looking at this, and at the rest of the ISO BRM definitions, to see if there isn't some natural alignment with the Session Layer definition, and, for that matter, with the Presentation Layer definition as well which relates to various MAL encoding options.</span> <span style='font-family:"Arial","sans-serif"'><br></span> <span style='font-family:"Arial","sans-serif"'><br>As for "<span style='color:#4181C0'>I would personally favor standards consistency over “OSI-correctness”</span>." I think that is exactly where both Scott and I are coming from. I would certainly favor "standards consistency" too. The whole of the Internet uses the terms transport, network, and link layer in the way that the ISO BRM defines them. And the whole of the CCSDS literature also references the ISO BRM and uses these same terms in the way that they are defined in that document. Aside from the inconvenience imposed by correcting this error, which all of us apparently missed, it is difficult to see that there is any benefit to all the rest of our CCSDS standards to allow SM&C to redefine this widely used and understood term for its own narrow purposes. I think that only sows confusion.</span> <span style='font-family:"Arial","sans-serif"'><br></span> <span style='font-family:"Arial","sans-serif"'><br>Best regards, Peter</span> <span style='font-family:"Arial","sans-serif"'><br></span> <span style='font-family:"Arial","sans-serif"'><br></span> <span style='font-family:"Arial","sans-serif"'><br></span> <b><br>From: </b>Champsavoir Nicolas <<a href="mailto:Nicolas.Champsavoir@cnes.fr">Nicolas.Champsavoir@cnes.fr</a>><b><br>Date: </b>Tuesday, October 3, 2017 at 12:40 AM<b><br>To: </b>Scott Burleigh <<a href="mailto:scott.c.burleigh@jpl.nasa.gov">scott.c.burleigh@jpl.nasa.gov</a>>, Peter Shames <<a href="mailto:peter.m.shames@jpl.nasa.gov">peter.m.shames@jpl.nasa.gov</a>>, Gian Paolo Calzolari <<a href="mailto:Gian.Paolo.Calzolari@esa.int">Gian.Paolo.Calzolari@esa.int</a>>, Erik Barkley <<a href="mailto:erik.j.barkley@jpl.nasa.gov">erik.j.barkley@jpl.nasa.gov</a>><b><br>Cc: </b>Tom Gannett <<a href="mailto:thomas.gannett@tgannett.net">thomas.gannett@tgannett.net</a>>, Mario Merri <<a href="mailto:Mario.Merri@esa.int">Mario.Merri@esa.int</a>>, Brigitte Behal <<a href="mailto:Brigitte.Behal@cnes.fr">Brigitte.Behal@cnes.fr</a>>, Dan Smith <<a href="mailto:danford.s.smith@nasa.gov">danford.s.smith@nasa.gov</a>>, "Sam Cooper (<a href="mailto:sam@brightascension.com">sam@brightascension.com</a>)" <<a href="mailto:sam@brightascension.com">sam@brightascension.com</a>>, "<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:Mehran.Sarkarati@esa.int">Mehran.Sarkarati@esa.int</a>" <<a href="mailto:Mehran.Sarkarati@esa.int">Mehran.Sarkarati@esa.int</a>>, "<a href="mailto:Philip.Brabbin@esa.int">Philip.Brabbin@esa.int</a>" <<a href="mailto:Philip.Brabbin@esa.int">Philip.Brabbin@esa.int</a>>, "<a href="mailto:dominik.marszk@esa.int">dominik.marszk@esa.int</a>" <<a href="mailto:dominik.marszk@esa.int">dominik.marszk@esa.int</a>><b><br>Subject: </b>RE: CCSDS 524.4-R-1 (MAL Binding to ZMTP) Comments Disposition <br> <span style='font-family:"Arial","sans-serif";color:#004080'><br>Hi Scott.</span> <span style='font-family:"Arial","sans-serif";color:#004080'><br></span> <span style='font-family:"Arial","sans-serif";color:#004080'><br>I understand your concerns. The change was made to be consistent with the other MO books and the terminology of the MAL. In the MO stack, anything below MAL is called "transport". This is not obvious and very unfortunate as it does not align with the OSI layers. If we were to talk in OSI layers, then I fully agree with you that TCP is a transport-layer protocol, and ZMTP is an application-layer protocol. But I would personally favor standards consistency over “OSI-correctness”.</span> <br> <span style='font-family:"Arial","sans-serif";color:#004080'><br>If we were to add a paragraph explaining exactly this at the beginning of the document. Would that solve your issue? <br></span> <span style='font-family:"Arial","sans-serif";color:#004080'><br>Best regards,</span> <span style='font-family:"Arial","sans-serif";color:#004080'><br>Nicolas</span> <span style='font-family:"Arial","sans-serif";color:#004080'><br></span> <b><span style='font-family:"Tahoma","sans-serif"'><br>De :</span></b><span style='font-family:"Tahoma","sans-serif"'> Burleigh, Scott C (312B) [</span><a href="mailto:scott.c.burleigh@jpl.nasa.gov"><span style='font-family:"Tahoma","sans-serif"'>mailto:scott.c.burleigh@jpl.nasa.gov</span></a><span style='font-family:"Tahoma","sans-serif"'>] <b><br>Envoyé :</b> mardi 3 octobre 2017 01:28<b><br>À :</b> Champsavoir Nicolas; Shames, Peter M (312B); </span><a href="mailto:Gian.Paolo.Calzolari@esa.int"><span style='font-family:"Tahoma","sans-serif"'>Gian.Paolo.Calzolari@esa.int</span></a><span style='font-family:"Tahoma","sans-serif"'>; Barkley, Erik J (3970)<b><br>Cc :</b> </span><a href="mailto:thomas.gannett@tgannett.net"><span style='font-family:"Tahoma","sans-serif"'>thomas.gannett@tgannett.net</span></a><span style='font-family:"Tahoma","sans-serif"'>; </span><a href="mailto:Mario.Merri@esa.int"><span style='font-family:"Tahoma","sans-serif"'>Mario.Merri@esa.int</span></a><span style='font-family:"Tahoma","sans-serif"'>; Behal Brigitte; Smith, Danford S. (GSFC-5800); Sam Cooper (</span><a href="mailto:sam@brightascension.com"><span style='font-family:"Tahoma","sans-serif"'>sam@brightascension.com</span></a><span style='font-family:"Tahoma","sans-serif"'>); </span><a href="mailto:Cesar.Coelho@esa.int"><span style='font-family:"Tahoma","sans-serif"'>Cesar.Coelho@esa.int</span></a><span style='font-family:"Tahoma","sans-serif"'>; </span><a href="mailto:Mehran.Sarkarati@esa.int"><span style='font-family:"Tahoma","sans-serif"'>Mehran.Sarkarati@esa.int</span></a><span style='font-family:"Tahoma","sans-serif"'>; </span><a href="mailto:Philip.Brabbin@esa.int"><span style='font-family:"Tahoma","sans-serif"'>Philip.Brabbin@esa.int</span></a><span style='font-family:"Tahoma","sans-serif"'>; </span><a href="mailto:dominik.marszk@esa.int"><span style='font-family:"Tahoma","sans-serif"'>dominik.marszk@esa.int</span></a><b><span style='font-family:"Tahoma","sans-serif"'><br>Objet :</span></b><span style='font-family:"Tahoma","sans-serif"'> RE: CCSDS 524.4-R-1 (MAL Binding to ZMTP) Comments Disposition</span> <br> <span style='font-family:"Arial","sans-serif";color:#004080'><br>Hi, Nicolas. Unfortunately the resolution you have proposed to my review condition is exactly the wrong one. TCP is a transport-layer protocol. ZMTP, when it runs on top of TCP, is a TCP application; it is not a transport protocol. ZMTP is not at the Transport Layer; it is at some other layer, maybe a “messaging” sub-layer of the Application Layer, in the same way that the CCSDS Asynchronous Message Service is.</span> <span style='font-family:"Arial","sans-serif";color:#004080'><br></span> <span style='font-family:"Arial","sans-serif";color:#004080'><br>Scott</span> <span style='font-family:"Arial","sans-serif";color:#004080'><br></span> <b><span style='font-family:"Arial","sans-serif"'><br>From:</span></b><span style='font-family:"Arial","sans-serif"'> Champsavoir Nicolas [</span><a href="mailto:Nicolas.Champsavoir@cnes.fr"><span style='font-family:"Arial","sans-serif"'>mailto:Nicolas.Champsavoir@cnes.fr</span></a><span style='font-family:"Arial","sans-serif"'>] <b><br>Sent:</b> Monday, October 2, 2017 6:16 AM<b><br>To:</b> Shames, Peter M (312B) <</span><a href="mailto:peter.m.shames@jpl.nasa.gov"><span style='font-family:"Arial","sans-serif"'>peter.m.shames@jpl.nasa.gov</span></a><span style='font-family:"Arial","sans-serif"'>>; Burleigh, Scott C (312B) <</span><a href="mailto:scott.c.burleigh@jpl.nasa.gov"><span style='font-family:"Arial","sans-serif"'>scott.c.burleigh@jpl.nasa.gov</span></a><span style='font-family:"Arial","sans-serif"'>>; </span><a href="mailto:Gian.Paolo.Calzolari@esa.int"><span style='font-family:"Arial","sans-serif"'>Gian.Paolo.Calzolari@esa.int</span></a><span style='font-family:"Arial","sans-serif"'>; Barkley, Erik J (3970) <</span><a href="mailto:erik.j.barkley@jpl.nasa.gov"><span style='font-family:"Arial","sans-serif"'>erik.j.barkley@jpl.nasa.gov</span></a><span style='font-family:"Arial","sans-serif"'>><b><br>Cc:</b> </span><a href="mailto:thomas.gannett@tgannett.net"><span style='font-family:"Arial","sans-serif"'>thomas.gannett@tgannett.net</span></a><span style='font-family:"Arial","sans-serif"'>; </span><a href="mailto:Mario.Merri@esa.int"><span style='font-family:"Arial","sans-serif"'>Mario.Merri@esa.int</span></a><span style='font-family:"Arial","sans-serif"'>; Behal Brigitte <</span><a href="mailto:Brigitte.Behal@cnes.fr"><span style='font-family:"Arial","sans-serif"'>Brigitte.Behal@cnes.fr</span></a><span style='font-family:"Arial","sans-serif"'>>; Smith, Danford S. (GSFC-5800) <</span><a href="mailto:danford.s.smith@nasa.gov"><span style='font-family:"Arial","sans-serif"'>danford.s.smith@nasa.gov</span></a><span style='font-family:"Arial","sans-serif"'>>; Sam Cooper (</span><a href="mailto:sam@brightascension.com"><span style='font-family:"Arial","sans-serif"'>sam@brightascension.com</span></a><span style='font-family:"Arial","sans-serif"'>) <</span><a href="mailto:sam@brightascension.com"><span style='font-family:"Arial","sans-serif"'>sam@brightascension.com</span></a><span style='font-family:"Arial","sans-serif"'>>; </span><a href="mailto:Cesar.Coelho@esa.int"><span style='font-family:"Arial","sans-serif"'>Cesar.Coelho@esa.int</span></a><span style='font-family:"Arial","sans-serif"'>; </span><a href="mailto:Mehran.Sarkarati@esa.int"><span style='font-family:"Arial","sans-serif"'>Mehran.Sarkarati@esa.int</span></a><span style='font-family:"Arial","sans-serif"'>; </span><a href="mailto:Philip.Brabbin@esa.int"><span style='font-family:"Arial","sans-serif"'>Philip.Brabbin@esa.int</span></a><span style='font-family:"Arial","sans-serif"'>; </span><a href="mailto:dominik.marszk@esa.int"><span style='font-family:"Arial","sans-serif"'>dominik.marszk@esa.int</span></a><b><span style='font-family:"Arial","sans-serif"'><br>Subject:</span></b><span style='font-family:"Arial","sans-serif"'> CCSDS 524.4-R-1 (MAL Binding to ZMTP) Comments Disposition</span> <br> <span style='font-family:"Arial","sans-serif";color:#004080'><br>Dear Peter, Scott, Gian and Erik.</span> <span style='font-family:"Arial","sans-serif";color:#004080'><br></span> <span style='font-family:"Arial","sans-serif";color:#004080'><br>Please find enclosed an excel spreadsheet with a list of proposed actions to address the comments you made on the CCSDS 524.4-R-1 (MAL Binding to ZMTP) document. You will also find enclosed a new version (1.1) of this document that implements the actions listed in the excel spreadsheet.</span> <span style='font-family:"Arial","sans-serif";color:#004080'><br></span> <span style='font-family:"Arial","sans-serif";color:#004080'><br>Could you please confirm that the provided responses properly address your comments, and that the revised version of the document is ready to enter agency review? In case you have comments on the new version, could you please send them to me so that I can address them?</span> <span style='font-family:"Arial","sans-serif";color:#004080'><br></span> <span style='font-family:"Arial","sans-serif";color:#004080'><br>Thank you very much in advance,</span> <span style='font-family:"Arial","sans-serif";color:#004080'><br>Best regards,</span> <span style='font-family:"Arial","sans-serif";color:#004080'><br>Nicolas</span> <span style='font-family:"Arial","sans-serif";color:#004080'><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> <br><br><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></body></html>