<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: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:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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:12.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
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:12.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;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle24
{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:410349298;
mso-list-type:hybrid;
mso-list-template-ids:-251502876 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
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="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt">The information that probably is necessary source. The APID can ID the location on the source but if the packet transfer through a network then you need a source. Time etc is covered in current secondary
header. But there are constructs that might be interesting for local distribution if they are not using AMS.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt">From:</span></b><span style="font-size:11.0pt"> Shames, Peter M (312B)
<br>
<b>Sent:</b> Monday, April 23, 2018 3:49 PM<br>
<b>To:</b> Burleigh, Scott C (312B) <Scott.C.Burleigh@jpl.nasa.gov>; Greenberg, Edward (312B) <Edward.Greenberg@jpl.nasa.gov>; sls-slp@mailman.ccsds.org; Jonathan.J.Wilmot@NASA.gov<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"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt">The DEM was indeed Constellation's locally grown variant on the SPP, with added features similar to PUS. But please keep in mind that Constellation intended to use TCP/IP as a network and transport protocol,
and the DEM was to be used on top of those layers. Because of this it had no need to provide it's own routing and network functions, it just had to accommodate application layer exchanges, operations, and message topics.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">They could equally easily used SPP with secondary header extensions for the same purpose. I think we really must be careful to not overload this extensible application layer data structure with features that
really belong at other layers in the protocol stack. We have a rich set of protocols, starting from physical layer of the ISO stack, including data link, network/transport, messages & files, and these application layer data structures. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Let's not get them confused any more than they already are.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Peter<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></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="color:black">From: </span>
</b><span style="color:black">SLS-SLP <<a href="mailto:sls-slp-bounces@mailman.ccsds.org">sls-slp-bounces@mailman.ccsds.org</a>> on behalf of Scott Burleigh <<a href="mailto:scott.c.burleigh@jpl.nasa.gov">scott.c.burleigh@jpl.nasa.gov</a>><br>
<b>Date: </b>Monday, April 23, 2018 at 9:08 AM<br>
<b>To: </b>"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>>,
"Wilmot, Jonathan J. (GSFC-5820)" <<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>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"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal" style="margin-left:.5in"><a name="_MailOriginalBody"><span style="font-size:11.0pt">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><o:p></o:p></a></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:11.0pt"> </span><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:11.0pt">Scott</span><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:11.0pt"> </span><o:p></o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-left:.5in"><span style="mso-bookmark:_MailOriginalBody"><b><span style="font-size:11.0pt">From:</span></b></span><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:11.0pt"> Greenberg, Edward (312B)
<br>
<b>Sent:</b> Sunday, April 22, 2018 7:37 AM<br>
<b>To:</b> </span></span><a href="mailto:sls-slp@mailman.ccsds.org"><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:11.0pt">sls-slp@mailman.ccsds.org</span></span><span style="mso-bookmark:_MailOriginalBody"></span></a><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:11.0pt">;
</span></span><a href="mailto:Jonathan.J.Wilmot@NASA.gov"><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:11.0pt">Jonathan.J.Wilmot@NASA.gov</span></span><span style="mso-bookmark:_MailOriginalBody"></span></a><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:11.0pt"><br>
<b>Cc:</b> Lee Pitts <</span></span><a href="mailto:robert.l.pitts@nasa.gov"><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:11.0pt">robert.l.pitts@nasa.gov</span></span><span style="mso-bookmark:_MailOriginalBody"></span></a><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:11.0pt">><br>
<b>Subject:</b> Call for Use Cases of Space Packet Protocol</span><o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal" style="margin-left:.5in"><span style="mso-bookmark:_MailOriginalBody"> <o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="mso-bookmark:_MailOriginalBody">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></span></p>
<p class="MsoNormal" style="margin-left:1.0in;text-indent:-.25in;mso-list:l0 level1 lfo2">
<span style="mso-bookmark:_MailOriginalBody"><![if !supportLists]><span style="font-family:Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]>ESA has PUS<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:1.0in;text-indent:-.25in;mso-list:l0 level1 lfo2">
<span style="mso-bookmark:_MailOriginalBody"><![if !supportLists]><span style="font-family:Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]>Space Station has its own secondary header<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:1.0in;text-indent:-.25in;mso-list:l0 level1 lfo2">
<span style="mso-bookmark:_MailOriginalBody"><![if !supportLists]><span style="font-family:Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]>Orion is looking for a secondary header<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="mso-bookmark:_MailOriginalBody">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></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="mso-bookmark:_MailOriginalBody">It is possible that the role of the packet might change with the use of DTN bundles.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="mso-bookmark:_MailOriginalBody">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></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="mso-bookmark:_MailOriginalBody"><span style="background:yellow;mso-highlight:yellow">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> </span><o:p></o:p></p>
</div>
</body>
</html>