<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">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:<br>
</div>
<blockquote type="cite"
cite="mid:8f46b707d7074aa5b1fa0912ab9612f1@jpl.nasa.gov">
<meta http-equiv="Context-Type" content="text/html;
charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<div class="WordSection1">
<p class="MsoNormal"><span>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.</span></p>
<p class="MsoNormal"><span> </span></p>
<p class="MsoNormal"><span>Scott</span></p>
<p class="MsoNormal"><span> </span></p>
<div>
<div>
<p class="MsoNormal"><b><span>From:</span></b><span>
Greenberg, Edward (312B)
<br>
<b>Sent:</b> Sunday, April 22, 2018 7:37 AM<br>
<b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:sls-slp@mailman.ccsds.org">sls-slp@mailman.ccsds.org</a>;
<a class="moz-txt-link-abbreviated" href="mailto:Jonathan.J.Wilmot@NASA.gov">Jonathan.J.Wilmot@NASA.gov</a><br>
<b>Cc:</b> Lee Pitts <a class="moz-txt-link-rfc2396E" 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</span></p>
</div>
</div>
<p class="MsoNormal"> </p>
<p class="MsoNormal">There seems to be lots of new Use Cases for
Space Packets then were considered in the original
specification. For example:</p>
<ul type="disc">
<li class="MsoNormal">ESA has PUS</li>
<li class="MsoNormal">Space Station has its own secondary
header</li>
<li class="MsoNormal">Orion is looking for a secondary header</li>
</ul>
<p class="MsoNormal">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).
</p>
<p class="MsoNormal">It is possible that the role of the packet
might change with the use of DTN bundles.</p>
<p class="MsoNormal">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.
</p>
<p class="MsoNormal"><span>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.</span>
</p>
</div>
</blockquote>
<p><br>
</p>
</body>
</html>