<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:x="urn:schemas-microsoft-com:office:excel" 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 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-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;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:250552152;
mso-list-type:hybrid;
mso-list-template-ids:-1953848418 67698705 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-text:"%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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">Hi Jonathan,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">If there is a DEM to SPP mapping that uses the standard SPP headers and adds the DEM as a packet secondary header that would be entirely suitable.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I'd like to encourage something like a two level approach to this:<o:p></o:p></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1">A registry for each SPP secondary header that is registered, with org, contact person, name of the project, and a pointer to the documentation<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l0 level1 lfo1">An XML schema (or JSON, your choice) that formalizes the secondary header structure, field names, data types, sizes, and definitions<o:p></o:p></li></ol>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">That way people can look it up, understand it, know where to find more info, etc. And, as I suggested, using the DoT would lend a certain regularity to the typing of the data.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Does his make sense to you guys? <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks, Peter<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-left:.5in"><b><span style="font-size:12.0pt;color:black">From:
</span></b><span style="font-size:12.0pt;color:black">SLS-SLP <sls-slp-bounces@mailman.ccsds.org> on behalf of Jonathan Wilmot via SLS-SLP <sls-slp@mailman.ccsds.org><br>
<b>Reply-To: </b>"Wilmot, Jonathan J. (GSFC-5820)" <Jonathan.J.Wilmot@NASA.gov><br>
<b>Date: </b>Thursday, February 28, 2019 at 7:28 AM<br>
<b>To: </b>Peter Shames <Peter.M.Shames@jpl.nasa.gov>, Scott Burleigh <Scott.C.Burleigh@jpl.nasa.gov>, "Greenberg, Edward" <Edward.Greenberg@jpl.nasa.gov>, "sls-slp@mailman.ccsds.org" <sls-slp@mailman.ccsds.org><br>
<b>Cc: </b>Lee Pitts <robert.l.pitts@nasa.gov><br>
<b>Subject: </b>Re: [Sls-slp] Call for Use Cases of Space Packet Protocol<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Peter and folks<br>
<br>
I agree with Peter's approach and would welcome moving forward with this. Hopefully before the missions finalize their implementation.
<br>
<br>
As I remember, the DEM did not adopt the SPP format but they did contain the same type of meta data that ECSS-PUS and the SPP proposal contain. The mapping between the Orion DEM and the SPP proposal format has been done and is in use at JSC for the LOP-G
prototyping efforts. <br>
<br>
Kind regards,<br>
<br>
Jonathan <br>
<br>
On 2/28/2019 10:14 AM, Shames, Peter M (312B) wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
Folks,<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
What we have proposed in the SPP revision is to create a SANA registry for local, agency, or even multi-agency packet secondary headers. This could include PUS, MAL packet mapping, Jonathan's LOP-G headers, and others. There is a proposal for a simple registry
structure in the draft SPP doc that would allow all of these to be registered. I suggest that you look at this and propose any needed metadata for the registry. You could try and engage in some sort of "normalization" effort for the field names, structures,
and contents, or at least try and do some sort of evaluation of the kinds of data and the different ways they are named and represented. I'll bet you will find that they are all over the map.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
By the way, the SOIS Dictionary of Terms (DoT) may prove to be useful as a source of standardized terms.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
Lastly, as I recall the Constellation DEM did not adhere to the SPP at all. I may be mis-remembering.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
Cheers, Peter<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<o:p></o:p></p>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<b>From: </b>SLS-SLP <a href="mailto:sls-slp-bounces@mailman.ccsds.org"><sls-slp-bounces@mailman.ccsds.org></a> on behalf of Jonathan Wilmot via SLS-SLP
<a href="mailto:sls-slp@mailman.ccsds.org"><sls-slp@mailman.ccsds.org></a><br>
<b>Reply-To: </b>"Wilmot, Jonathan J. (GSFC-5820)" <a href="mailto:Jonathan.J.Wilmot@NASA.gov">
<Jonathan.J.Wilmot@NASA.gov></a><br>
<b>Date: </b>Thursday, February 28, 2019 at 7:03 AM<br>
<b>To: </b>Scott Burleigh <a href="mailto:Scott.C.Burleigh@jpl.nasa.gov"><Scott.C.Burleigh@jpl.nasa.gov></a>, "Greenberg, Edward"
<a href="mailto:Edward.Greenberg@jpl.nasa.gov"><Edward.Greenberg@jpl.nasa.gov></a>,
<a href="mailto:sls-slp@mailman.ccsds.org">"sls-slp@mailman.ccsds.org"</a> <a href="mailto:sls-slp@mailman.ccsds.org">
<sls-slp@mailman.ccsds.org></a><br>
<b>Cc: </b>Peter Shames <a href="mailto:Peter.M.Shames@jpl.nasa.gov"><Peter.M.Shames@jpl.nasa.gov></a>, Lee Pitts
<a href="mailto:robert.l.pitts@nasa.gov"><robert.l.pitts@nasa.gov></a><br>
<b>Subject: </b>Re: [Sls-slp] Call for Use Cases of Space Packet Protocol<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
Ed, Scott,<br>
<br>
The CCSDS Space Packet is being used at NASA, ESA and CAST as end user application command and telemetry message. It contains information in the primary and secondary headers to allow end user applications to identify the data content and format, and also
allow mission architecture specific lower layers to transport user application data within a subnetworks or across networks.
<br>
<br>
As part of this discussion I would like to re-submit a proposal to create a secondary header that could be included as an optional header in the SPP Blue book or registered in SANA as a standard SPP secondary header type. (ECSS-PUS headers should also be
registered)<br>
<br>
Note: The LOP-G program, and other missions at JSC, GSFC, and ARC, are currently using the format in the attached proposal. This is an opportunity for CCSDS to improve mission interoperability by supporting the SPP uses cases that missions require.<br>
<br>
Kind Regards,<br>
<br>
Jonathan<br>
<br>
Jonathan Wilmot<br>
NASA/GSFC<br>
CCSDS SOIS Area Director<br>
<br>
On 4/22/2018 12:16 PM, Burleigh, Scott C (312B) wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
Ed, I think of the Space Packet as being the thing that the old Constellation project called a Data Exchange Message (DEM). I think it performs the same function in the stack, and I suspect that it could easily carry all the same metadata that the DEM was
supposed to carry.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
Scott<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<b>From:</b> Greenberg, Edward (312B) <br>
<b>Sent:</b> Sunday, April 22, 2018 7:37 AM<br>
<b>To:</b> <a href="mailto:sls-slp@mailman.ccsds.org">sls-slp@mailman.ccsds.org</a>;
<a href="mailto:Jonathan.J.Wilmot@NASA.gov">Jonathan.J.Wilmot@NASA.gov</a><br>
<b>Cc:</b> Lee Pitts <a href="mailto:robert.l.pitts@nasa.gov"><robert.l.pitts@nasa.gov></a><br>
<b>Subject:</b> Call for Use Cases of Space Packet Protocol<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
There seems to be lots of new Use Cases for Space Packets then were considered in the original specification. For example:<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
· ESA has PUS <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
· Space Station has its own secondary header <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
· Orion is looking for a secondary header <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
Originally the Space Packet was an envelope for data transferred over single link (includes tunneling), now the packet is being looked at for network data transfer, local onboard data transfer (including measurement broadcasting).
<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
It is possible that the role of the packet might change with the use of DTN bundles.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
Just to take the broadest view: We currently have two forms of packets, should there be more or should even these be examined to determine if they should be blended into a new packet design.
<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
Can we get each of you to send in your present and possibly desired Use Cases for our beloved Space Packet so that we could determine its future.
<o:p></o:p></p>
</div>
</blockquote>
<p style="margin-left:.5in"> <o:p></o:p></p>
</div>
</blockquote>
<p style="margin-left:.5in"><o:p> </o:p></p>
</div>
</body>
</html>