<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px;">
Dear all,</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px;">
<br>
</div>
<div><font face="Calibri,sans-serif">The document "</font><font face="sans-serif" size="2">CCSDS 320.0-B-6 CCSDFS Global Spacecraft Identification Field Code Assignment Control Procedure” is one of the documents that we have been reviewing and working on in
the SSG and SANA context. Tom can (and will) correct me if I am wrong, but I believe that this document is essentially a CMC Blue Book. It was created in the dawn of time before CCSDS had the SEA as an operating element for dealing with such cross cutting
issues. And it is Blue because it affects not just CCSDS internal operations, but also defines normative behavior for agencies using CCSDS standards.</font></div>
<div><font face="sans-serif" size="2"><br>
</font></div>
<div><font face="sans-serif" size="2">I have proposed making it a part of the body of work in the SEA SAWG that is now being re-started. It must be coordinated with the work otherwise being done by the SSG, the SANA, and the Secretariat to re-engineer several
of the “enterprise” type SANA registries so that they may be re-used by other WG. This specific document could be coordinated with the SLS and CSS, as the topic of broadening the SCID “namespace” by adopting seperate numbers for each frequency band has already
been coordinated. </font></div>
<div><font face="sans-serif" size="2"><br>
</font></div>
<div><font face="sans-serif" size="2">Or it could be assigned to SLS. Either way it must be coordinated as a part of this re-engineering of these registries.</font></div>
<div><font face="sans-serif" size="2"><br>
</font></div>
<div><font face="sans-serif" size="2">Regards, Peter</font></div>
<div><font face="sans-serif" size="2"><br>
</font></div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px;">
<br>
</div>
<span id="OLK_SRC_BODY_SECTION" style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px;">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span><<a href="mailto:cesg-bounces@mailman.ccsds.org">cesg-bounces@mailman.ccsds.org</a>> on behalf of Gian Paolo Calzolari <<a href="mailto:Gian.Paolo.Calzolari@esa.int">Gian.Paolo.Calzolari@esa.int</a>><br>
<span style="font-weight:bold">Date: </span>Tuesday, September 22, 2015 at 1:48 AM<br>
<span style="font-weight:bold">To: </span>Nestor Peccia <<a href="mailto:Nestor.Peccia@esa.int">Nestor.Peccia@esa.int</a>><br>
<span style="font-weight:bold">Cc: </span>Bernie Edwards <<a href="mailto:bernard.l.edwards@nasa.gov">bernard.l.edwards@nasa.gov</a>>, "<a href="mailto:cesg-bounces@mailman.ccsds.org">cesg-bounces@mailman.ccsds.org</a>" <<a href="mailto:cesg-bounces@mailman.ccsds.org">cesg-bounces@mailman.ccsds.org</a>>,
Aaron Kiely <<a href="mailto:Aaron.B.Kiely@jpl.nasa.gov">Aaron.B.Kiely@jpl.nasa.gov</a>>, Klaus-Juergen Schulz <<a href="mailto:Klaus-Juergen.Schulz@esa.int">Klaus-Juergen.Schulz@esa.int</a>>, CCSDS Engineering Steering Group - CESG Exec <<a href="mailto:cesg@mailman.ccsds.org">cesg@mailman.ccsds.org</a>>,
Dennis K Lee <<a href="mailto:Dennis.K.Lee@jpl.nasa.gov">Dennis.K.Lee@jpl.nasa.gov</a>>, CMC <<a href="mailto:cmc@mailman.ccsds.org">cmc@mailman.ccsds.org</a>>, Greg Kazz <<a href="mailto:Greg.J.Kazz@jpl.nasa.gov">Greg.J.Kazz@jpl.nasa.gov</a>>, "<a href="mailto:mark.wong@nasa.gov">mark.wong@nasa.gov</a>"
<<a href="mailto:mark.wong@nasa.gov">mark.wong@nasa.gov</a>>, "Weiss, Howard" <<a href="mailto:Howard.Weiss@parsons.com">Howard.Weiss@parsons.com</a>>, Tom Gannett <<a href="mailto:tomg@aiaa.org">tomg@aiaa.org</a>>, "<a href="mailto:Enrico.Vassallo@esa.int">Enrico.Vassallo@esa.int</a>"
<<a href="mailto:Enrico.Vassallo@esa.int">Enrico.Vassallo@esa.int</a>>, "<a href="mailto:Massimo.Bertinelli@esa.int">Massimo.Bertinelli@esa.int</a>" <<a href="mailto:Massimo.Bertinelli@esa.int">Massimo.Bertinelli@esa.int</a>><br>
<span style="font-weight:bold">Subject: </span>A few SLS questions: : [CESG] CESG Chair Cross-check: online strategic plan, WG charters, approved / draft projects: Part 6 SLS Area<br>
</div>
<div><br>
</div>
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div>
<div><font size="2" face="sans-serif">Nestor,</font> <br>
<font size="2" face="sans-serif"> I guess items 1 and 2 should read SLS and not SIS/SOIS.</font><br>
<font size="2" face="sans-serif">Correct?</font> <br>
<br>
<font size="2" face="sans-serif">CCSDS 320.0-B-6 CCSDFS Global Spacecraft Identification Field Code Assignment Control Procedure</font><br>
<font size="2" face="sans-serif">No problem for adding it but - as far as I remember - this document is not formally under SLS and it is considered a yellow book that erroneously was marked blue.</font><br>
<font size="2" face="sans-serif">Tom can shed some light on this. If confirmed that no other Area has formal responsibility we will add it.</font><br>
<br>
<font size="2" face="sans-serif">You ask to add some document (almost) ready for publication.</font><br>
<font size="2" face="sans-serif">As the relevant CMC poll expires on 28 September it will be impossible to add them by 29 September :o)</font><br>
<br>
<font size="2" face="sans-serif">Ciao</font> <br>
<br>
<font size="2" face="sans-serif">Gian Paolo</font> <br>
<br>
<br>
<br>
<font size="1" color="#5f5f5f" face="sans-serif">From: </font><font size="1" face="sans-serif"><a href="mailto:Nestor.Peccia@esa.int">Nestor.Peccia@esa.int</a></font><br>
<font size="1" color="#5f5f5f" face="sans-serif">To: </font><font size="1" face="sans-serif"><a href="mailto:Gian.Paolo.Calzolari@esa.int">Gian.Paolo.Calzolari@esa.int</a>, "Moury Gilles" <<a href="mailto:Gilles.Moury@cnes.fr">Gilles.Moury@cnes.fr</a>>,
<a href="mailto:Enrico.Vassallo@esa.int">Enrico.Vassallo@esa.int</a>, <a href="mailto:Dennis.K.Lee@jpl.nasa.gov">
Dennis.K.Lee@jpl.nasa.gov</a>, <a href="mailto:Massimo.Bertinelli@esa.int">Massimo.Bertinelli@esa.int</a>,
<a href="mailto:Aaron.B.Kiely@jpl.nasa.gov">Aaron.B.Kiely@jpl.nasa.gov</a>, <a href="mailto:mark.wong@nasa.gov">
mark.wong@nasa.gov</a>, <a href="mailto:Greg.J.Kazz@jpl.nasa.gov">Greg.J.Kazz@jpl.nasa.gov</a>, "Weiss, Howard" <<a href="mailto:Howard.Weiss@parsons.com">Howard.Weiss@parsons.com</a>>,
<a href="mailto:Bernard.L.Edwards@nasa.gov">Bernard.L.Edwards@nasa.gov</a>, <a href="mailto:Klaus-Juergen.Schulz@esa.int">
Klaus-Juergen.Schulz@esa.int</a>, </font><br>
<font size="1" color="#5f5f5f" face="sans-serif">Cc: </font><font size="1" face="sans-serif"><a href="mailto:cmc@mailman.ccsds.org">cmc@mailman.ccsds.org</a>,
<a href="mailto:cesg@mailman.ccsds.org">cesg@mailman.ccsds.org</a></font><br>
<font size="1" color="#5f5f5f" face="sans-serif">Date: </font><font size="1" face="sans-serif">18/09/2015 12:21</font><br>
<font size="1" color="#5f5f5f" face="sans-serif">Subject: </font><font size="1" face="sans-serif">[CESG] CESG Chair Cross-check: online strategic plan, WG charters, approved / draft projects: Part 6 SLS Area</font><br>
<font size="1" color="#5f5f5f" face="sans-serif">Sent by: </font><font size="1" face="sans-serif"><a href="mailto:cesg-bounces@mailman.ccsds.org">cesg-bounces@mailman.ccsds.org</a></font><br>
<hr noshade="">
<br>
<br>
<br>
<font size="2" face="sans-serif">Dear all,</font><font size="3"> <br>
</font><font size="2" face="sans-serif"><br>
This is part 6 (out of 6) of the CESG sanity check on the above mentioned items.</font><font size="3"><br>
</font><font size="2" face="sans-serif"><br>
Goal is to deliver a consistent short-, medium- and long-term Strategic Plan to the CMC on 1st Oct 2015</font><font size="3"><br>
</font><font size="4" face="sans-serif"><b><u><br>
SLS Area</u></b></font><font size="3"> <br>
</font><font size="2" face="sans-serif"><b><u><br>
CWE CCSDS Strategic Plan</u></b></font><font size="3"> </font><font size="2" face="sans-serif"><br>
<i><u>Note:</u></i> AD/DAD to follow update procedure distributed by Secretariat (i.e. Brian Oliver)</font><font size="3"></font><br>
<font size="2" face="sans-serif">1. SIS Content </font><font size="2" color="blue" face="sans-serif">Gian Paolo Calzolari / Gilles Moury</font><font size="2" face="sans-serif"> to update text according to CESG comments</font><font size="3"></font><br>
<font size="2" face="sans-serif">2. SOIS Links </font><font size="2" color="blue" face="sans-serif">Gian Paolo Calzolari / Gilles Moury</font><font size="2" face="sans-serif"><b> </b>to update links as follows
</font>
<ul>
<li><font size="2" face="sans-serif">Document type 2 Add (once on-going CMC poll is successfully completed) CCSDS 130.2-G-3, Space Data Link Protocols—Summary of Concept and Rationale (Green Book, Issue 3)</font><font size="3"></font></li><li><font size="2" face="sans-serif">Document type 3 Add published Doc CCSDS 320.0-B-6 CCSDFS Global Spacecraft Identification Field Code Assignment Control Procedure</font><font size="3"></font><font size="2" face="sans-serif"><br>
Add published Doc CCSDS 131.5-O-1 Erasure Correcting Codes for use in Near-Earth and Deep Space Communications</font><font size="3"></font><font size="2" face="sans-serif"><br>
Add published doc CCSDS 231.1-O-1 Short Block Length LDPC Codes for TC Synchronization and Channel Coding</font><font size="3"></font><font size="2" face="sans-serif"><br>
Add (once on-going CMC poll is successfully completed) CCSDS 355.0-B-1, Space Data Link Security Protocol (Blue Book, Issue 1) </font><font size="3"></font></li><li><font size="2" face="sans-serif">Document type 4 Check why there are 2 docs while in CWE Approved Projects only 1 is listed</font><font size="3"></font><br>
<font size="2" face="sans-serif">1. CWE Doc.401.0-B Radio Frequency and Modulation Systems--Part 1: Earth Stations and Spacecraft (Blue Book) (Issue 24) (including a set of modulation schemes for 26 GHz)
</font><br>
<font size="2" face="sans-serif">2. CWE Doc. 401.0-B Radio Frequency and Modulation Systems--Part 1: Earth Stations and Spacecraft (Blue Book) (Issue 24) (including simultaneous transmission of high rate telemetry and ranging signals)</font></li><li><font size="2" face="sans-serif">Document type 5 Once CMC on going polls are completed successfully, the following Projects will be transferred to the view "completed projects"
</font><br>
<font size="2" face="sans-serif">1. CCSDS 355.0-B-1, Space Data Link Security Protocol (Blue Book, Issue 1)
</font><br>
<font size="2" face="sans-serif">2. CCSDS 132.0-B-2, TM Space Data Link Protocol (Blue Book, Issue 2)</font><font size="3"></font><br>
<font size="2" face="sans-serif">3. CCSDS 232.0-B-3, TC Space Data Link Protocol (Blue Book, Issue 3)</font><font size="3"></font><br>
<font size="2" face="sans-serif">4. CCSDS 732.0-B-3, AOS Space Data Link Protocol (Blue Book, Issue 3)</font><br>
<font size="2" face="sans-serif">Delete CWE Doc 700.1- G Next Generation Space Data Link protocol (GB)</font><font size="3"></font><font size="2" face="sans-serif"><br>
Add a CCSDS doc if approved project. Otherwise delete it</font><font size="3"> </font>
<br>
<font size="2" face="sans-serif">1. Development of new synchronization and channel coding schemes to be used with the Telecommand (TC) Space Data Link Protocol over ground-to-space communications links to improve performance in terms of distance and
data rate</font> </li><li><font size="2" face="sans-serif">Document Type 6 Space Data Link Security Concept of Operation, Issue 2
</font><font size="2" color="#008000" face="sans-serif"> Add this doc that is in the view Draft Projects</font><font size="3"></font><font size="2" face="sans-serif"><br>
Delete <br>
Delete Doc <br>
Delete <br>
Add </font></li></ul>
<font size="2" face="sans-serif"><b><u><br>
CWE CCSDS Projects: All Draft Projects</u></b></font><font size="3"> </font><br>
<font size="2" face="sans-serif">1. 5..01<b> RFM WG</b></font><font size="2" color="#008000" face="sans-serif"></font><font size="2" face="sans-serif"> </font><font size="2" color="#008000" face="sans-serif">Enrico Vassallo / Dennis Lee</font><font size="3"></font>
<ul>
<li><font size="2" face="sans-serif">CWE Doc. 440.0-G Planetary Communications Systems
</font><font size="2" color="#008000" face="sans-serif">Update start / end dates well in the future</font><font size="3"></font></li><li><font size="2" color="#008000" face="sans-serif">Create the following draft Projects (that are described in the startegic plac, SLS Links Doc type 6)</font><font size="3"></font>
<ul>
<li><font size="2" face="sans-serif">CWE Doc. 401.0-B Radio Frequency and Modulation Systems--Part 1: Earth Stations and Spacecraft (Blue Book) (Issue XX) (including standards on Multiple Spacecraft Per Aperture [MSPA] techniques, on 22 GHz modulations, and
on emergency communications) </font></li><li><font size="2" face="sans-serif">CWE Doc. 401.0-B Radio Frequency and Modulation Systems--Part 1: Earth Stations and Spacecraft (Blue Book) (Issue XX) (including recommendations of higher-order modulations for deep space applications)
</font></li></ul>
</li></ul>
<font size="2" face="sans-serif">2. 5.09<b> SDLS WG</b> </font><font size="2" color="#008000" face="sans-serif">Gilles Moury / Howard Weiss</font><font size="3"></font>
<ul>
<li><font size="2" face="sans-serif">Space Data Link Security Concept of Operation, Issue 2 </font><font size="2" color="#008000" face="sans-serif">Update start / end dates (currently in the past)</font></li></ul>
<font size="2" face="sans-serif">3. 5.0.4 SLP WG</font><font size="2" color="#008000" face="sans-serif"> Greg Kazz</font><font size="3"></font>
<ul>
<li><font size="2" face="sans-serif">There is no future work planned for this WG.
</font><font size="2" color="#008000" face="sans-serif">Please discuss it within the WG.</font><font size="3"></font></li></ul>
<font size="2" face="sans-serif"><b><u><br>
CWE WG Charters</u></b> </font><font size="3"> </font><br>
<font size="2" face="sans-serif">1. <b>SDLS WG Charter</b> </font><font size="2" color="#008000" face="sans-serif">Gilles Moury / Howard Weiss</font><font size="3"></font>
<ul>
<li><font size="2" face="sans-serif">Suggestion to include some text in the charter to cover security at physical layer</font></li></ul>
<font size="2" face="sans-serif"><br>
If you need support to implement the changes please contact Brian Oliver</font><font size="3"><br>
</font><font size="2" color="red" face="sans-serif"><b><u><br>
PLEASE UPDATE THE CWE SLS SECTIONS BY 29th SEPT 2015 COB AT THE LATEST</u></b></font><font size="3"><br>
</font><font size="2" face="sans-serif"><br>
ciao</font><font size="3"> </font><font size="2" face="sans-serif"><br>
nestor</font> <br>
<tt><font size="3">This message and any attachments are intended for the use of the addressee or addressees only.<br>
The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its<br>
content is not permitted.<br>
If you received this message in error, please notify the sender and delete it from your system.<br>
Emails can be altered and their integrity cannot be guaranteed by the sender.<br>
<br>
Please consider the environment before printing this email.<br>
</font></tt><tt><font size="2">_______________________________________________<br>
CESG mailing list<br>
<a href="mailto:CESG@mailman.ccsds.org">CESG@mailman.ccsds.org</a><br>
</font></tt><a href="http://mailman.ccsds.org/mailman/listinfo/cesg"><tt><font size="2">http://mailman.ccsds.org/mailman/listinfo/cesg</font></tt></a><tt><font size="2"><br>
</font></tt><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>
</div>
</div>
</blockquote>
</span>
</body>
</html>