<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=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><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: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";}
tt
{mso-style-priority:99;
font-family:"Courier New";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
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-family:"Calibri","sans-serif";color:#1F497D'>Dear Gian Paolo,<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:#1F497D'>Thank you for your note.<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:#1F497D'>I agree 100% with your statement: “</span><tt><span style='font-size:10.0pt'>The services offered by the TM and AOS Space Data Link Protocols (and therefore by their Transfer Frames formats) are largely equivalent and share similar limitations. Therefore any limitation to constrain optical links to single frame format should have a very sound rationale.”</span></tt><br><br><span style='font-family:"Calibri","sans-serif";color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:#1F497D'>I agree it is not critical that everybody use AOS and it is doubtful everybody will (as in the case of RF systems and interoperability). However, that was NASA’s “opening recommendation” going back to the OLSG. ESA, TESAT, DLR, and NASA met today and we agree that it is not a necessity. Thus I do agree that it is something that needs to be looked at by CCSDS and NASA’s opening recommendation may be too restrictive! <o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:#1F497D'>Sincerely,<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:#1F497D'>Bernie Edwards<o:p></o:p></span></p><p class=MsoNormal><span style='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"'> Gian.Paolo.Calzolari@esa.int [mailto:Gian.Paolo.Calzolari@esa.int] <br><b>Sent:</b> Monday, March 11, 2013 11:00 AM<br><b>To:</b> Edwards, Bernard L. (GSFC-5600)<br><b>Cc:</b> sls-com@mailman.ccsds.org; sls-com-bounces@mailman.ccsds.org<br><b>Subject:</b> Re: [Sls-ocm] Help with OLSG Action Concerning Applicable CCSDS Protocols / Tranfer Frame vs. AOS Frame<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><tt><span style='font-size:10.0pt'>> As part of this action, NASA has proposed to the OLSG group that </span></tt><span style='font-size:10.0pt;font-family:"Courier New"'><br><tt>> future optical communications links use the CCSDS standard AOS at </tt><br><tt>> the frame level. That will ensure that all CCSDS protocols above </tt><br><tt>> AOS will be compatible with future optical communications links. </tt><br><tt>> This is what is currently being done on NASA’s Laser Communications </tt><br><tt>> Relay Demonstration (LCRD) project in development. If this is </tt><br><tt>> accepted by the group, then the group can focus on standards needed </tt><br><tt>> below the frame level.</tt></span> <br><tt><span style='font-size:10.0pt'>> </span></tt> <br><tt><span style='font-size:10.0pt'>Dear Bernie,</span></tt> <br><tt><span style='font-size:10.0pt'> I must say that I am a little puzzled by the NASA proposed approach. </span></tt> <br><br><tt><span style='font-size:10.0pt'>CCSDS has developed four protocols for the Data Link Protocol Sublayer of the Data Link Layer:</span></tt> <br><tt><span style='font-size:10.0pt'>a)TM Space Data Link Protocol </span></tt><br><tt><span style='font-size:10.0pt'>b)TC Space Data Link Protocol </span></tt><br><tt><span style='font-size:10.0pt'>c)AOS Space Data Link Protocol </span></tt><br><tt><span style='font-size:10.0pt'>d)Proximity-1 Space Link Protocol—Data Link Layer </span></tt><br><br><tt><span style='font-size:10.0pt'>The TM and AOS Space Data Link Protocols use fixed-length Transfer Frames to facilitate robust synchronization procedures over a noisy link, while the TC</span></tt> <br><tt><span style='font-size:10.0pt'>Space Data Link Protocol and the Proximity-1 Space Link Protocol use variable-length Transfer Frames to facilitate reception of short messages with a short delay. </span></tt><br><br><tt><span style='font-size:10.0pt'>The services offered by the TM and AOS Space Data Link Protocols (and therefore by their Transfer Frames formats) are largely equivalent and share similar limitations. Therefore any limitation to constrain optical links to single frame format should have a very sound rationale.</span></tt> <br><br><tt><span style='font-size:10.0pt'>Moreover, the Coding and Synchronization standards applied to the downlink are independent from the frame format used at the upper layer.</span></tt> <br><tt><span style='font-size:10.0pt'>The only constraints applied are the fixed-length and the minimum/maximum) size of the frames provided.</span></tt> <br><tt><span style='font-size:10.0pt'>Therefore I am really puzzled by an approach that would design the Data Link Coding & Sync Sublayer (for optical links) based on a single frame structure.</span></tt> <br><tt><span style='font-size:10.0pt'>Note that this would not only be a limitation for the current CCSDS asset, but may even jeopardize further evolution of the Data Link Protocol Sublayer if its lower (sub)layer is too rigid.</span></tt> <br><br><tt><span style='font-size:10.0pt'>To summarize, I find perfectly admissible that the NASA’s Laser Communications Relay Demonstration (LCRD) project selects the AOS format, but I do not see enough element to justify this choice as the only allowed one.</span></tt> <br><br><tt><span style='font-size:10.0pt'>Most likely this will be something to be investigated in CCSDS.</span></tt> <br><br><tt><span style='font-size:10.0pt'>Best regards</span></tt> <br><br><tt><span style='font-size:10.0pt'>Gian Paolo</span></tt><o:p></o:p></p><pre>This message and any attachments are intended for the use of the addressee or addressees only. The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its content is not permitted. If you received this message in error, please notify the sender and delete it from your system. 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></div></body></html>