<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>Organization and Processes for the Consultative Committee for Space Data Systems</title>
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<div style="font-size: 14px; font-family: Calibri, sans-serif; color: rgb(0, 0, 0);">
Hi Gippo,</div>
<div style="font-size: 14px; font-family: Calibri, sans-serif; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-size: 14px; font-family: Calibri, sans-serif; color: rgb(0, 0, 0);">
Comments / replies in-line.</div>
<div style="font-size: 14px; font-family: Calibri, sans-serif; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-size: 14px; font-family: Calibri, sans-serif; color: rgb(0, 0, 0);">
Thanks, Peter</div>
<div style="font-size: 14px; font-family: Calibri, sans-serif; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-size: 14px; font-family: Calibri, sans-serif; color: rgb(0, 0, 0);">
<br>
</div>
<span id="OLK_SRC_BODY_SECTION" style="font-size: 14px; font-family: Calibri, sans-serif; color: rgb(0, 0, 0);">
<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 29, 2015 at 12:48 AM<br>
<span style="font-weight:bold">To: </span>CCSDS Engineering Steering Group - CESG Exec <<a href="mailto:cesg@mailman.ccsds.org">cesg@mailman.ccsds.org</a>><br>
<span style="font-weight:bold">Subject: </span>[CESG] Comments to SEA Area Strategic Plan<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">Dear Peter,</font> <br>
<font size="2" face="sans-serif"> a few comments here below in blue.</font><br>
<font size="2" face="sans-serif">Ciao</font> <br>
<br>
<font size="2" face="sans-serif">Gippo</font> <br>
<br>
<font size="1" color="#800080" face="sans-serif">----- Forwarded by Gian Paolo Calzolari/esoc/ESA on 28/09/2015 09:31 -----</font><br>
<br>
<font size="1" color="#5f5f5f" face="sans-serif">From: </font><font size="1" face="sans-serif">"Shames, Peter M (312B)" <<a href="mailto:peter.m.shames@jpl.nasa.gov">peter.m.shames@jpl.nasa.gov</a>></font><br>
<font size="1" color="#5f5f5f" face="sans-serif">To: </font><font size="1" face="sans-serif">"Brian Oliver" <<a href="mailto:briano@aiaa.org">briano@aiaa.org</a>>, "CCSDS Secretariat" <<a href="mailto:secretariat@mailman.ccsds.org">secretariat@mailman.ccsds.org</a>>,
</font><br>
<font size="1" color="#5f5f5f" face="sans-serif">Cc: </font><font size="1" face="sans-serif">"Nestor Peccia" <<a href="mailto:Nestor.Peccia@esa.int">Nestor.Peccia@esa.int</a>>, "Tai, Wallace S\(9000\)" <<a href="mailto:wallace.s.tai@jpl.nasa.gov">wallace.s.tai@jpl.nasa.gov</a>>,
"CCSDS Engineering Steering Group - CESG Exec" <<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">26/09/2015 00:27</font><br>
<font size="1" color="#5f5f5f" face="sans-serif">Subject: </font><font size="1" face="sans-serif">[CESG] Update to online strategic plan, WG charters, approved / draft projects: Part 1 SEA 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="Calibri">Brian, et al,</font> <br>
<br>
<font size="2" face="Calibri">As requested by Nestor I have been looking over the SEA Strategic Plan on the web site. I find that some of it is out of date, and that I cannot edit it. To be honest I am not sure if it is you who do these updates or if it is
done by someone else, like Nestor. Regardless, here are the changes that are needed for SEA, updated text is marked in
</font><font size="2" color="red" face="Calibri">red</font><font size="2" face="Calibri">:</font><br>
<br>
<font size="2" face="Calibri"><b>SYSTEMS ENGINEERING AREA</b></font>
<p><font size="2" face="Arial">The objective of the Systems Engineering Area (SEA) is to address system-wide architectural and engineering topics that are so pervasive that they span over all, or several, other CCSDS areas. This work includes development of
specific standards and guidelines, development of system architectures and models, coordination/collaboration with other areas, and otherwise supporting CCSDS
</font><font size="2" color="red" face="Arial">and CMC </font><font size="2" face="Arial">engineering and operational goals.</font><br>
<font size="2" color="blue" face="Arial">Why highlighting "and" CMC"? Do CMC have different goals than CCSDS? :o)
</font><br>
<font size="2" color="blue" face="Arial">I suggest deleting or writing separately that SEA has some specific CMC support tasks(if the latter is agreed by CESG).</font></p>
</div>
</div>
</blockquote>
</span>
<div style="font-size: 14px; font-family: Calibri, sans-serif; color: rgb(0, 0, 0);">
The SEA has a broadly defined responsibility in the YB. Quoted here:</div>
<div style="font-size: 14px; font-family: Calibri, sans-serif; color: rgb(0, 0, 0);">
<span style="color: rgb(0, 0, 255); font-family: TimesNewRomanPS; font-size: 12pt; font-weight: 700;"><br>
</span></div>
<div style="font-size: 14px; font-family: Calibri, sans-serif;"><span style="font-family: TimesNewRomanPS; font-size: 12pt; font-weight: 700;"><font color="#007f00">3.3.2 SYSTEMS ENGINEERING AREA</font></span></div>
<div>
<div class="page" title="Page 32">
<div class="layoutArea">
<div class="column">
<p style="font-size: 14px; font-family: Calibri, sans-serif;"><span style="font-size: 12pt; font-family: TimesNewRomanPSMT;"><font color="#007f00">The Systems Engineering Area (SEA) covers system-wide engineering aspects that are so pervasive that they span
both the Informatics and Telematics Domains. The AD has the prerogative to define, in alignment with the CCSDS Strategic Plan, the set of projects that this Area contains at any point in time.</font></span></p>
<p style="color: rgb(0, 0, 0);">There have been, and surely will continue to be, a number of tasks such as the SANA, XML, security, registries, and systems architecture, that are cross cutting. The CMC has approval over all CCSDS work, but no means to do
anything except to ask us, the CESG and the areas to do it. In the case of the SEA we wind up doing most of those cross cutting tasks since the other areas tend to have a more narrow, and domain specific, focus.</p>
</div>
</div>
</div>
</div>
<span id="OLK_SRC_BODY_SECTION" style="font-size: 14px; font-family: Calibri, sans-serif; color: rgb(0, 0, 0);">
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div>
<div>
<p><font size="2" color="red" face="Arial">The SEA system architecture tasks include end-to-end reference architecture, architecture analysis and description methods, and related cross cutting terminology topics. </font><font size="2" face="Arial">The SEA
security architecture and standards are to be used by other CCSDS areas requiring security guidance and services. The Delta-DOR services touch upon the Cross Support Services (CSS) and Space Link Services (SLS) areas, and Mission Operations and Information
Management Services (MOIMS) may be involved in planning for use of these services. The information architecture and
</font><font size="2" color="red" face="Arial">registry</font><font size="2" face="Arial"> services also cross cut MOIMS, CSS, Space Internetworking
</font><font size="2" color="red" face="Arial">(SIS), and other Services</font><font size="2" face="Arial">. Extensible Markup Language (XML) standards and guidelines and other special cross-cutting topics that are guided by SEA affect all of the other areas.
</font><font size="2" color="red" face="Arial">As </font><font size="2" face="Arial">system or
</font><font size="2" color="red" face="Arial">information</font><font size="2" face="Arial"> architecture standards
</font><font size="2" color="red" face="Arial">are developed</font><font size="2" face="Arial">, SEA will
</font><font size="2" color="red" face="Arial">coordinate with the other CCSDS areas and working groups to develop approaches that align with CCSDS goals for interoperability and cross support</font><font size="2" face="Arial">. The strategic goals of the SEA
are listed below.</font> </p>
<p><font size="2" color="blue" face="Arial">Why not listing in a bulleted list the coordination needs as done by other 4 areas? The uniform presentation would also allow an easier identification of the interface points by each Area.
</font><br>
<font size="2" color="blue" face="Arial">The sentence "</font><font size="2" face="Arial">SEA will
</font><font size="2" color="red" face="Arial">coordinate with the other CCSDS areas and working groups to develop approaches that align with CCSDS goals for interoperability and cross support</font><font size="2" face="Arial">.
</font><font size="2" color="blue" face="Arial">" looks as an open ended delegation to SEA for developing a lot of (now) undefined items I wonder whether "develop approaches" should be somehow reworded.</font></p>
</div>
</div>
</blockquote>
</span>
<div>I could list the other five areas since we tend to have interfaces with all of them. If that is what you want I’ll do it. SEA, much more than the other areas, is designed to have this cross cutting nature and that should not come as a surprise, it is
a characteristic of systems engineering in general, not just within CCSDS. This added text was intended to acknowledge that SEA has these cross cutting tasks, but also to state that we do intend to work them as closely as needed with the other areas. I thought
this was a positive thing, not an issue.</div>
<div><br>
</div>
<div>As for “developing a lot of undefined items”, it is the case that we are often the ones to point out issues from other areas, or to take on the job of trying to fix them. Because of the domain focus of the other areas they do not always look around at
other areas to see if there are other things they can, or should, align with. This “near-sighted” approach is why we have no real standards for XML and why we had ten different “organization” type and four different “person" type registries in place or planned
instead of one each well engineered ones. This is another cross cutting item that we are now working to fix.</div>
<div><br>
</div>
<div>Or, to put it another way, we do not have the luxury of just placing our focus on one or two specific, narrow, topics. Our task is to take the broad look to see that all the pieces fit together. This is also a part of the CESG role that all of the AD
have, but it is not always followed as diligently as it might be:</div>
<div><span style="color: rgb(0, 127, 0); font-size: 12pt; font-family: TimesNewRomanPS; font-weight: 700;"><br>
</span></div>
<div><span style="color: rgb(0, 127, 0); font-size: 12pt; font-family: TimesNewRomanPS; font-weight: 700;">2.3.2.2 </span><span style="color: rgb(0, 127, 0); font-family: TimesNewRomanPS; font-size: 12pt; font-weight: 700;">CESG Operating Principles </span></div>
<div>
<div class="page" title="Page 20">
<div class="layoutArea">
<div class="column">
<ol start="4" style="list-style-type: none">
<li>
<p><font color="#007f00"><span style="font-size: 12.000000pt; font-family: 'TimesNewRomanPSMT'">d) </span><span style="font-size: 12.000000pt; font-family: 'TimesNewRomanPS'; font-style: italic">Consistency</span><span style="font-size: 12.000000pt; font-family: 'TimesNewRomanPSMT'">.
<b><i>An important job of the CESG is to watch over the output of all of the WGs to help prevent CCSDS specifications that are at odds with each other.</i></b> This is why ADs and DADs are required to review the drafts coming out of Areas other than their own
as part of the consensus process leading up to their adoption into the program of work. The quality of the CCSDS Recommended Standards comes both from the review that they get in the WGs and the review that the WG products get from the CESG. </span></font></p>
</li></ol>
</div>
</div>
</div>
</div>
<div>I think that the SEA is trying to do just what we have been tasked to do. I hope that we can all find a way to make it work for the betterment of CCSDS and of the agencies that support us in these roles.</div>
<span id="OLK_SRC_BODY_SECTION" style="font-size: 14px; font-family: Calibri, sans-serif; color: rgb(0, 0, 0);">
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div>
<div>
<p><font size="2" color="blue" face="Arial"> </font><font size="3" face="Calibri"><b>…</b></font></p>
<p><font size="2" face="Calibri"><b>SEA GOAL 7</b></font> </p>
<p><font size="3" color="red" face="Calibri">Produce a consistent set of CCSDS architectures, information models, and policies.</font><font size="3" face="Calibri"> </font><font size="3" color="red" face="Calibri">Produce a
</font><font size="3" face="Calibri">CCSDS </font><font size="2" color="red" face="Calibri">Application Layer Architecture
</font><font size="3" face="Calibri">showing the relationships among </font><font size="3" color="red" face="Calibri">all of the application layer standards and services and their relationships to supporting standards for space communication and cross support</font><font size="3" face="Calibri">.
</font><font size="2" color="red" face="Calibri">This is a companion document to the Space Communication Cross Support architecture (SCCS-ADD) that documents SLS, SIS, CSS, and SEA standards relationships. Work with MOIMS and SOIS to document the relationships
between the standards in these two areas and with those already documented in the SCCS-ADD.</font><font size="3" face="Calibri"> Revise the CCSDS Reference Architecture for Space Data Systems (RASDS) to accomplish
</font><font size="3" color="red" face="Calibri">its</font><font size="3" face="Calibri"> 5-year review and</font><font size="3" color="red" face="Calibri">, in a second phase,</font><font size="3" face="Calibri"> augment the existing document with methods
using Model-Based System Engineering (MBSE) and SysML. </font><font size="3" color="red" face="Calibri">Working with the other areas, update the CCSDS Glossary to provide a self consistent and unambiguous set of terms. Create a Registry Management Policy
and related procedures and information models for managing the sets of registry information created by the other CCSDS areas.</font><br>
<font size="2" color="blue" face="Arial">This goal is very long (opposite to all previous ones) and heterogenous. I would favor a splitting into more dedicated items.<br>
As there is already a goal 4 for (reference) architecture could that goal be modified adding the architectural items mentioned above in goal 7?</font><br>
<font size="2" color="blue" face="Arial">I think that the maintenance activities (e.g. 5 years review) were agreed to be an inherent goal of each Area not deserving a dedicated mentioning.</font><br>
<font size="2" color="blue" face="Arial">MOIMS interaction, Glossary, Registries looks to me as deserving a dedicated goal..</font><br>
</p>
<p><font size="2" color="blue" face="Arial">.</font></p>
</div>
</div>
</blockquote>
</span>
<div>I agree that this is a large goal and that it could be broken into several smaller ones. At the same time, I also believe that all of these items are inter-related and that it is hardly possible to work on one without affecting in some way the others.
I could produce an information model of how these pieces all relate, and how they relate to the other areas and support topics. I do not know if that would help, and then we would have an information model in the Strat Plan for SEA and none for any of the
other areas. I do not know if that is satisfactory either. </div>
<div><br>
</div>
<div>Or do you wish to add an info model to SLS, and to add one to each of SIS, CSS, SOIS, and MOIMS, showing how these pieces all relate one to the other? I actually think that would be an excellent contribution, but did not want to try and impose it on all
other areas. I do think it would be very useful if each of the areas had a clear picture of how they relate to the other areas they touch upon, and having you each produce such a model is one way of accomplishing that. How about if you all do that to increase
the information flow and consistency across all topics?</div>
<div><br>
</div>
<div>Regards, Peter</div>
<div><br>
</div>
<div><b><br>
</b></div>
<div><b><br>
</b></div>
<div><b>Existing Recommended Standards / Practices</b></div>
<span id="OLK_SRC_BODY_SECTION" style="font-size: 14px; font-family: Calibri, sans-serif; color: rgb(0, 0, 0);">
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<ul>
<li><font size="2" face="Calibri">CCSDS 311.0-M-1 Reference Architecture for Space Data Systems</font></li><li><font size="2" color="red" face="Calibri">CCSDS 901.0-G-1 Space Communication Cross Support Architecture – Architecture Description Document</font></li><li><font size="2" color="red" face="Calibri">CCSDS 901.1-M-1 Space Communication Cross Support Architecture – Architecture Requirements Document</font></li><li><font size="2" color="red" face="Calibri">CCSDS 313.0-Y-1 Space Assigned Numbers Authority (SANA)-Role, Responsibilities, Policies and Procedures</font></li><li><font size="2" color="red" face="Calibri">CCSDS 320.0-B-6 CCSDS Global Spacecraft Identifier Field: Code Assignment Control Procedures</font></li><li><font size="2" color="red" face="Calibri">SANA Glossary, </font><a href="http://sanaregistry.org/r/terms"><font size="2" color="red" face="Calibri">http://sanaregistry.org/r/terms</font></a></li></ul>
<br>
<font size="2" face="Calibri"><b>Future Work</b></font> <br>
<font size="2" face="Calibri"> </font>
<table width="100%" style="border-collapse:collapse;">
<tbody>
<tr height="8">
<td width="98%" style="border-style:solid;border-color:#000000;border-width:0px 0px 0px 0px;padding:2px 2px;">
<ul>
<li><font size="2" face="Calibri">CCSDS 311.0-M Reference Architecture for Space Data Systems (Issue 2, reconfirmation)</font></li><li><font size="2" color="red" face="Calibri">CCSDS 311.0-M Reference Architecture for Space Data Systems (Issue 3, MBSE and other extensions)</font></li><li><font size="2" color="red" face="Calibri">CWE Doc. TBD CCSDS Application Layer Architecture (Magenta Book)</font></li><li><font size="2" color="red" face="Calibri">CWE Doc. TBD CCSDS Glossary updates (SANA)</font></li><li><font size="2" color="red" face="Calibri">CWE Doc. Registry Management Policy (including policy, procedures, and information models)</font></li><li><font size="2" color="red" face="Calibri">CCSDS 313.0-Y-1 Space Assigned Numbers Authority (SANA)-Role, Responsibilities, Policies and Procedures (Issue 2)</font></li><li><font size="2" color="red" face="Calibri">CCSDS 320.0-B-6 CCSDS Global Spacecraft Identifier Field: Code Assignment Control Procedures (issue 7)</font></li><li><font size="2" face="Calibri">Five year confirmation Review process for published recommended standards and practices</font></li></ul>
</td>
<td width="1%" style="border-style:solid;border-color:#000000;border-width:0px 0px 0px 0px;padding:2px 2px;">
</td>
</tr>
<tr height="8">
<td style="border-style:solid;border-color:#000000;border-width:0px 0px 0px 0px;padding:2px 2px;">
</td>
<td style="border-style:solid;border-color:#000000;border-width:0px 0px 0px 0px;padding:2px 2px;">
</td>
</tr>
<tr height="8">
<td style="border-style:solid;border-color:#000000;border-width:0px 0px 0px 0px;padding:2px 2px;">
</td>
<td style="border-style:solid;border-color:#000000;border-width:0px 0px 0px 0px;padding:2px 2px;">
</td>
</tr>
</tbody>
</table>
<font size="2" face="Calibri"><b>From: </b>Nestor Peccia <</font><a href="mailto:Nestor.Peccia@esa.int"><font size="2" color="blue" face="Calibri"><u>Nestor.Peccia@esa.int</u></font></a><font size="2" face="Calibri">><b><br>
Date: </b>Tuesday, September 15, 2015 at 11:10 PM<b><br>
To: </b>Peter Shames <</font><a href="mailto:peter.m.shames@jpl.nasa.gov"><font size="2" color="blue" face="Calibri"><u>peter.m.shames@jpl.nasa.gov</u></font></a><font size="2" face="Calibri">>, Hiroshi Takeuchi <</font><a href="mailto:takeuchi@isas.jaxa.jp"><font size="2" color="blue" face="Calibri"><u>takeuchi@isas.jaxa.jp</u></font></a><font size="2" face="Calibri">>,
"Weiss, Howard" <</font><a href="mailto:Howard.Weiss@parsons.com"><font size="2" color="blue" face="Calibri"><u>Howard.Weiss@parsons.com</u></font></a><font size="2" face="Calibri">>, Mattia Mercolino <</font><a href="mailto:Mattia.Mercolino@esa.int"><font size="2" color="blue" face="Calibri"><u>Mattia.Mercolino@esa.int</u></font></a><font size="2" face="Calibri">><b><br>
Cc: </b>CCSDS Engineering Steering Group - CESG Exec <</font><a href="mailto:cesg@mailman.ccsds.org"><font size="2" color="blue" face="Calibri"><u>cesg@mailman.ccsds.org</u></font></a><font size="2" face="Calibri">>, CMC <</font><a href="mailto:cmc@mailman.ccsds.org"><font size="2" color="blue" face="Calibri"><u>cmc@mailman.ccsds.org</u></font></a><font size="2" face="Calibri">>,
CCSDS Secretariat <</font><a href="mailto:secretariat@mailman.ccsds.org"><font size="2" color="blue" face="Calibri"><u>secretariat@mailman.ccsds.org</u></font></a><font size="2" face="Calibri">><b><br>
Subject: </b>CESG Chair Cross-check: online strategic plan, WG charters, approved / draft projects: Part 1 SEA Area</font><br>
<br>
<font size="2" face="sans-serif">Dear all,</font><font size="2" face="Calibri"> <br>
</font><font size="2" face="sans-serif"><br>
This is part 1 (out of 6) of the CESG sanity check on the above mentioned items.</font><font size="2" face="Calibri"><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="2" face="Calibri"><br>
</font><font size="4" face="sans-serif"><b><u><br>
SEA Area</u></b></font><font size="2" face="Calibri"> <br>
</font><font size="2" face="sans-serif"><b><u><br>
CWE CCSDS Strategic Plan</u></b></font><font size="2" face="Calibri"> </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><br>
<font size="2" face="sans-serif">1. SEA Content </font><font size="2" color="blue" face="sans-serif">Peter Shames / Hiroshi Takeuchi</font><font size="2" face="sans-serif"> to distribute updated text to CESG for review</font><br>
<font size="2" face="sans-serif">2. SEA Links </font><font size="2" color="blue" face="sans-serif">Peter Shames / Hiroshi Takeuchi</font><font size="2" face="sans-serif"> to update links as follows
</font>
<ul>
<li><font size="2" face="sans-serif">Document type 2 Add published GB (350-9-G-1 CCSDS Cryptographic Algorithm</font></li><li><font size="2" face="sans-serif">Document type 3 Delete Doc 353.1-G-1 Cryptographic algorithms</font></li><li><font size="2" face="sans-serif">Document type 5 Update Doc Symmetric key management recommendations from blue to magenta book<br>
Add Doc Delta-DOR Architectural Guidelines (MB)<br>
Add Doc Delta-DOR Raw Data Exchange Format (Issue 2) (BB)</font> </li><li><font size="2" face="sans-serif">Document Type 6 Add Doc CCSDS 311-0-M Reference Architecture for Space Data Systems (Issue 3)<br>
Add Doc CCSDS Authentication Credentials (BB)<br>
Add Doc Network layer Security over Space Packets (BB)<br>
Add Doc Secure Software Engineering for Space Missions (GB)</font></li></ul>
<font size="2" face="sans-serif"><b><u>CWE CCSDS Projects: All Draft Projects</u></b></font><br>
<font size="2" face="sans-serif">1. BOF2 System Architecture BoF </font><font size="2" color="blue" face="sans-serif">Peter Shames / Hiroshi Takeuchi</font><font size="2" face="sans-serif"> to create following Draft projects</font><font size="2" face="Calibri"></font>
<ul>
<li><font size="2" face="sans-serif">Reference Information Architecture , Infrastructure Services and Interfaces (MB)</font></li></ul>
<font size="2" face="sans-serif">2. (to be created) BOF </font><font size="2" color="blue" face="sans-serif">Peter Shames / Hiroshi Takeuchi</font><font size="2" face="sans-serif"> to create following Draft projects</font><font size="2" face="Calibri"></font>
<ul>
<li><font size="2" face="sans-serif">Timeline Data Standard (BB)</font><font size="2" face="Calibri"></font></li><li><font size="2" face="sans-serif">Time Service Architecture (MB)</font></li></ul>
<font size="2" face="sans-serif">3. CCSDS Authenticatin Credentials (BB) </font><font size="2" color="#008000" face="sans-serif">Howard Weiss</font><font size="2" face="sans-serif"> to check if end date "Jan 2017" is realistic</font><br>
<font size="2" face="sans-serif"><b><u><br>
CWE WG Charters</u></b> OK</font><font size="2" face="Calibri"><br>
</font><font size="2" face="sans-serif"><br>
If you need support to implement the changes please contact Brian Oliver</font><font size="2" face="Calibri"><br>
</font><font size="2" color="red" face="sans-serif"><b><u><br>
PLEASE UPDATE THE CWE SEA SECTIONS BY 29th SEPT 2015 COB AT THE LATEST</u></b></font><font size="2" face="Calibri"><br>
</font><font size="2" face="sans-serif"><br>
ciao</font><font size="2" face="Calibri"> </font><font size="2" face="sans-serif"><br>
nestor</font><font size="2" face="Calibri"> </font><br>
<font size="2" face="Calibri">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><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>
<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>
</blockquote>
</span>
</body>
</html>