<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
On the web page there is a typo, the words “particular on” are run together as “particularon” — but your email version seems to have fixed this, so I guess you already caught this typo.
<div><br>
</div>
<div>For goal 4 (data compression):</div>
<div>- I might suggest changing “data rates and volume reduction” to “data rates and data volume reduction” to be slightly more clear.</div>
<div>- The phrase “maximize the usage of available space links bandwidth and onboard storage capacity” maybe change to “optimize the usage of available space links bandwidth and onboard storage capacity”. (We can “maximize” the usage of a link by just sending
random bits all the time, the idea is to make better use of those bits, so “optimize” or some other word might convey the meaning.)</div>
<div><br>
</div>
<div>In any case, I don’t think there will be much confusion about why data compression can provide some benefits, so the precise wording isn’t critical.</div>
<div><br>
</div>
<div>Regards,</div>
<div>Aaron</div>
<div><br>
<br>
<div>
<div>On Jul 2, 2015, at 1:04 AM, <a href="mailto:Gian.Paolo.Calzolari@esa.int">Gian.Paolo.Calzolari@esa.int</a> wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite"><font size="2" face="sans-serif">Dear All,</font> <br>
<font size="2" face="sans-serif"> CMC and CESG Chair has requested to review the Area contents (Area content tab) and goals in the CWE on-line strategic plan.</font>
<br>
<font size="2" face="sans-serif">For SLS you can find this information here: </font><a href="http://cwe.ccsds.org/fm/sp/Lists/SLSContent/AllItems.aspx"><font size="2" face="sans-serif">http://cwe.ccsds.org/fm/sp/Lists/SLSContent/AllItems.aspx</font></a><font size="2" face="sans-serif">
and at the bottom of this mil for your convenience.</font> <br>
<font size="2" face="sans-serif">Keeping in mind that we have six goals (i.e. one per WG), can you please review the general description of SLS Area and (at least) the goal related to your WG?</font>
<br>
<br>
<font size="2" face="sans-serif">I think the contents below are quite stable and I would expect only minor changes (if any).</font>
<br>
<br>
<font size="2" face="sans-serif"><b>I would appreciate receiving any comment by 10 July 2015.</b></font>
<br>
<br>
<font size="2" face="sans-serif">Thank you all for the collaboration.</font> <br>
<br>
<font size="2" face="sans-serif">Gian Paolo</font> <br>
<br>
<font size="2" face="sans-serif">==================================</font> <br>
<font size="2" face="sans-serif"><b>SPACE LINK SERVICES AREA</b></font> <br>
<font size="2" face="sans-serif">The objective of the SLS area is to address all of the point-to-point communications links and protocols that interconnect a spacecraft with its ground-support system, or with another spacecraft, by developing standards for
efficient and reliable space link communications systems addressing nominal as well as emergency scenarios. Specific attention is given by SLS to needs for higher data rates and better link performances, a standard security mechanism, and lower cost, mass,
and power.</font> <br>
<br>
<font size="2" face="sans-serif">SLS area objectives focus on Layers 1 & 2 (of the Open Systems Interconnection [OSI] protocol stack)—i.e., the Physical Layer and the Data Link Layer. This means that SLS concentrates in particular on radio-frequency and optical
systems, modulation, synchronization and channel coding, and data link protocols, for both long-haul (e.g., spacecraft-to-ground) and proximity links (e.g., orbiter-to-lander). Moreover SLS concentrates also on two additional functions essential on the space
link: data compression for end-to-end data transfer optimization, and ranging for accurate orbit determination.</font>
<br>
<br>
<font size="2" face="sans-serif">The SLS area needs to coordinate:</font> <br>
<font size="2" face="sans-serif"> with CSS for the identification of relevant parameters for service management;</font>
<br>
<font size="2" face="sans-serif"> with CSS for the inner behavior (i.e., the implementation aspects and not the terrestrial interface characteristics) of the CSTS to be made available to other agencies;</font>
<br>
<font size="2" face="sans-serif"> with SEA for Delta-DOR issues;</font> <br>
<font size="2" face="sans-serif"> with MOIMS and CSS if the need of standardized exchange of meteorological and orbital data will be required for optical communications;</font>
<br>
<font size="2" face="sans-serif"> with SEA for adoption and integration of security-related recommended standards and practices;</font>
<br>
<font size="2" face="sans-serif"> the SANA-recommended practices for registries and repositories.</font>
<br>
<br>
<font size="2" face="sans-serif">The strategic goals of the SLS area are presented below.</font>
<br>
<br>
<font size="2" face="sans-serif"><b>SLS GOAL 1</b></font> <br>
<font size="2" face="sans-serif"> Enable efficient bi-directional transmission for near-Earth spacecraft (including missions to—and/or orbiting around—the Moon and at Lagrange points) and deep-space spacecraft (especially Mars missions) by developing
appropriate modulation schemes for telecommand, telemetry, and ranging signals in the applicable frequency bands while providing narrower bandwidth and higher data returns.</font>
<br>
<br>
<font size="2" face="sans-serif"><b>SLS GOAL 2</b></font> <br>
<font size="2" face="sans-serif"> Produce efficient standards for coding schemes and synchronization, providing new generations of space missions with telecommand and telemetry capabilities beyond current technologies, such that spacecraft interconnection
with its ground support system, or with another spacecraft, can accommodate higher data rates and better link performances, together with lower cost, mass, and power.</font>
<br>
<br>
<font size="2" face="sans-serif"><b>SLS GOAL 3</b></font> <br>
<font size="2" face="sans-serif"> To provide efficient space data link protocols capable of satisfying the needs of current and future missions; i.e., to produce or maintain standards to support smoothly higher data rates with seamless interface to
both user applications and communication technologies over radio frequency (RF) and/or optical links.</font>
<br>
<font size="2" face="sans-serif"> </font><br>
<font size="2" face="sans-serif"><b>SLS GOAL 4</b></font> <br>
<font size="2" face="sans-serif"> Develop data compression standards enabling efficient data rates and volume reduction to maximize the usage of available space links bandwidth and onboard storage capacity. These internationally agreed data compression
standards will foster interoperability and multi-mission development of compression functions.</font>
<br>
<font size="2" face="sans-serif"> </font><br>
<font size="2" face="sans-serif"><b>SLS GOAL 5</b></font> <br>
<font size="2" face="sans-serif"> Provide security functions operating at Layers 1 & 2 (of the OSI protocol stack) of CCSDS space links. The targeted security services include authentication, integrity check, anti-replay, and confidentiality both for
uplink and downlink. The corresponding security protocols/functions shall be compatible with CCSDS TM, TC, and AOS data link protocols and be independent from any specific cryptographic algorithm. Develop associated management functions for monitoring and
control, key and security association management. Security at Physical Layer level should also be considered.</font>
<br>
<font size="2" face="sans-serif"> </font><br>
<font size="2" face="sans-serif"><b>SLS GOAL 6</b></font> <br>
<font size="2" face="sans-serif"> Establish a common framework of standardized services for space optical communications for interoperability and cross support by creating new standards for optical links (ISO Layers 1 & 2), taking into account the uniqueness
of these types of links, such as very high data rates, geographic station diversity, and atmosphere (“weather”) influences. Consider also the services to be offered/required to/by space data link protocols and relevant procedures. Finally, identify the needed
coordination with other CCSDS areas.</font> <br>
<br>
<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.
Please consider the environment before printing this email.
</pre>
_______________________________________________<br>
SLS mailing list<br>
<a href="mailto:SLS@mailman.ccsds.org">SLS@mailman.ccsds.org</a><br>
http://mailman.ccsds.org/mailman/listinfo/sls<br>
</blockquote>
</div>
<br>
</div>
</body>
</html>