<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)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><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;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 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;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
tt
{mso-style-priority:99;
font-family:"Courier New";}
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.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle22
{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:1535119494;
mso-list-type:hybrid;
mso-list-template-ids:718031346 -1905594346 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-number-format:alpha-upper;
mso-level-text:"%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.75in;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Arial",sans-serif;
mso-fareast-font-family:"Times New Roman";}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:1.25in;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
margin-left:1.75in;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:2.25in;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:2.75in;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
margin-left:3.25in;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:3.75in;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:4.25in;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
margin-left:4.75in;
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 Gippo,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">At the risk of having us not (quite) agree on this, I think you stated something different in your item A) than what I intended. You said:<o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p> </o:p></span></p>
<ol style="margin-top:0in" start="1" type="A">
<li class="MsoListParagraph" style="margin-left:.25in;mso-list:l0 level1 lfo1"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">The secondary header section is SPP will inform that a number of secondary-header-types are registered with SANA and
the actual contents of the secondary header are (somehow) "managed" at <b>SPP service user</b> level (Note 1)</span>
<br>
<br>
<o:p></o:p></li></ol>
<p class="MsoNormal">If we are not going to break existing uses or the SPP secondary header, then I think this statement must read like this:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">A) The secondary header
<span style="color:red">flag in </span>SPP will inform that a secondary <span style="color:red">
header is in use</span>. <span style="color:red">A number </span>of secondary-header-types
<span style="color:red">will be </span>registered with SANA and the actual contents of the secondary header are (somehow) "managed" at
<b>SPP service user</b> level (Note 1)</span> <br>
<br>
<o:p></o:p></p>
<p class="MsoNormal">Your wording suggested that the secondary header section <span style="color:red">
itself </span>would signal that there are a number of secondary header types. In order to do that we would have to all adopt some new secondary header format that had such an "I am using secondary header type = 3" field. Right now the SPP itself, and the
current users of SPP do not include such a field. So this would "break" those uses, including the SPP nominal one, the PUS, and the JPL uses.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I suggested that we could potentially create a new "standard" SPP secondary header that had such a field, but was not proposing that we force this change on existing users.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Can you accept that? As one of the ESA members I would be surprised if you would accept a change that required a modification of PUS.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Regards, Peter<o:p></o:p></p>
<p class="MsoNormal"><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">Gian Paolo Calzolari <Gian.Paolo.Calzolari@esa.int><br>
<b>Date: </b>Friday, March 1, 2019 at 3:21 AM<br>
<b>To: </b>SLS-SLP Mailing List <sls-slp@mailman.ccsds.org><br>
<b>Cc: </b>"Greenberg, Edward" <Edward.Greenberg@jpl.nasa.gov>, "Wilmot, Jonathan J. (GSFC-5820)" <Jonathan.J.Wilmot@NASA.gov>, Lee Pitts <robert.l.pitts@nasa.gov>, Scott Burleigh <Scott.C.Burleigh@jpl.nasa.gov>, Peter Shames <Peter.M.Shames@jpl.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>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Dear,</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"> after so many e-mail I would like to make the point of the situation (as far as I understand it) with the caveat that there shall be something wrong in this story as it looks that Peter and
I agree on something. :o)</span> <br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">The envisaged approach by Peter is that</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">A) The secondary header section is SPP will inform that a number of secondary-header-types are registered with SANA and the actual contents of the secondary header are (somehow) "managed" at
<b>SPP service user</b> level (Note 1)</span> <br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">B) Secondary Header Types will be registered in SANA with
</span>a two level approach : <br>
1. A registry for each SPP secondary header that is registered, with org, contact person, name of the project, and a pointer to the documentation
<br>
2. An XML schema (or JSON, your choice) that formalizes the secondary header structure, field names, data types, sizes, and definitions
<br>
<br>
<b><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Is this the common understanding for everybody?</span></b>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Best regards and have a nice week end</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Gian Paolo</span> <br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Note1: In fact the service user of the SPP Packet Service provides the SPP service provider with a "pre cooked" space packet in the PACKET.request while the service user of the SPP Octet String Service
provides the SPP service provider with a "pre cooked" space packet data field and a Secondary Header Indicator in the OCTET_STRING.request</span>
<br>
<br>
<br>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">From: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"Shames, Peter M \(312B\) via SLS-SLP" <sls-slp@mailman.ccsds.org></span>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">To: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">Jonathan Wilmot <Jonathan.J.Wilmot@NASA.gov>, "Burleigh, Scott C (312B)" <Scott.C.Burleigh@jpl.nasa.gov>,
"Greenberg, Edward (312B)" <Edward.Greenberg@jpl.nasa.gov>, "sls-slp@mailman.ccsds.org" <sls-slp@mailman.ccsds.org></span>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">Cc: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">Lee Pitts <robert.l.pitts@nasa.gov></span>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">Date: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">28-02-19 17:13</span>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">Subject: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">Re: [Sls-slp] Call for Use Cases of Space Packet Protocol</span>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">Sent by: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"SLS-SLP" <sls-slp-bounces@mailman.ccsds.org></span>
<o:p></o:p></p>
<div class="MsoNormal" align="center" style="margin-left:.5in;text-align:center">
<hr size="0" width="100%" noshade="" style="color:#A0A0A0" align="center">
</div>
<p class="MsoNormal" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in">
<o:p> </o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
Hi Jonathan,<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
I think you missed my point. There are existing SPP secondary header formats that are already in use. The ESA has PUS, the CCSDS MAL has theirs (not in wide use, but defined), and JPL has "standard" ways of using the SPP secondary header to transmit time
codes. This last is a sort of "CCSDS standard" in that it is recommended, but not required, in the SPP spec.<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<o:p></o:p></p>
<div>
<p class="MsoNormal" style="margin-left:.5in"><b><span style="font-size:12.0pt;font-family:"Times New Roman",serif">4.1.3.2.1.5 </span></b><span style="font-size:12.0pt;font-family:"Times New Roman",serif">If present, the Packet Secondary Header shall consist
of either:</span> <o:p></o:p></p>
<p style="mso-margin-top-alt:2.5in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<span style="font-size:12.0pt;font-family:"Times New Roman",serif">a) a Time Code Field (variable length) only;</span><o:p></o:p></p>
<p style="mso-margin-top-alt:2.5in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<span style="font-size:12.0pt;font-family:"Times New Roman",serif">b) an Ancillary Data Field (variable length) only; or</span><o:p></o:p></p>
<p style="mso-margin-top-alt:2.5in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<span style="font-size:12.0pt;font-family:"Times New Roman",serif">c) a Time Code Field followed by an Ancillary Data Field.</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
I believe you must accept this, and suggest that trying to change it at this point will doom you to failure. There will surely be ESA feedback.<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
I will point out, however, that ESA effectively adopted option b) for the MAL SPP mapping, and that contains a "Version Number" in the first field of the Secondary Header. I have not looked to see if that is sufficiently general that it could be co-opted
for this purpose.<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
Peter<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<b><span style="font-size:12.0pt">From: </span></b><span style="font-size:12.0pt">SLS-SLP <sls-slp-bounces@mailman.ccsds.org> on behalf of Jonathan Wilmot via SLS-SLP <sls-slp@mailman.ccsds.org><b><br>
Reply-To: </b>"Wilmot, Jonathan J. (GSFC-5820)" <Jonathan.J.Wilmot@NASA.gov><b><br>
Date: </b>Thursday, February 28, 2019 at 8:00 AM<b><br>
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><b><br>
Cc: </b>Lee Pitts <robert.l.pitts@nasa.gov><b><br>
Subject: </b>Re: [Sls-slp] Call for Use Cases of Space Packet Protocol</span><o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
Peter,<br>
<br>
I understand that "managed" will be the initial approach similar to the compromise for spacecraft ID's being only unique within an assigned spectrum. Something we can do now is maybe have a version indication in the first byte(s) of the secondary header.
And although I hate to say it, maybe even use an SDNV?<br>
<br>
Kind regards,<br>
<br>
Jonathan <br>
<br>
On 2/28/2019 10:51 AM, Shames, Peter M (312B) wrote:<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
Hi Jonathan,<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
I get that you would like this, but that would mean changing all of the existing header structures that are already in wide use. I think what we should do it to treat this like a "managed parameter" where you have to know which of the formats you are processing.<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
That said, for any new / future formats you could certainly include some sort of standard "secondary header type" flag, but for current ones I think you must accept the "managed" approach. Otherwise this will never get off the ground.<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
Peter<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<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><b><br>
Reply-To: </b>"Wilmot, Jonathan J. (GSFC-5820)" <a href="mailto:Jonathan.J.Wilmot@NASA.gov">
<Jonathan.J.Wilmot@NASA.gov></a><b><br>
Date: </b>Thursday, February 28, 2019 at 7:43 AM<b><br>
To: </b>Peter Shames <a href="mailto:Peter.M.Shames@jpl.nasa.gov"><Peter.M.Shames@jpl.nasa.gov></a>, 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><b><br>
Cc: </b>Lee Pitts <a href="mailto:robert.l.pitts@nasa.gov"><robert.l.pitts@nasa.gov></a><b><br>
Subject: </b>Re: [Sls-slp] Call for Use Cases of Space Packet Protocol<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
Peter,<br>
<br>
If we have agreement I will start rapidly moving in that direction. The schema will be the SOIS EDS and SOIS DoT. For true interoperability I think we need something in the headers that indicate which one of the secondary headers is being used so it can
be parsed at run-time.<br>
<br>
Kind regards,<br>
<br>
Jonathan<br>
<br>
On 2/28/2019 10:36 AM, Shames, Peter M (312B) wrote:<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
Hi Jonathan,<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
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 style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
I'd like to encourage something like a two level approach to this:<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><br>
1. A registry for each SPP secondary header that is registered, with org, contact person, name of the project, and a pointer to the documentation
<br>
2. An XML schema (or JSON, your choice) that formalizes the secondary header structure, field names, data types, sizes, and definitions
<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
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 style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
Does his make sense to you guys? <o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
Thanks, Peter<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<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><b><br>
Reply-To: </b>"Wilmot, Jonathan J. (GSFC-5820)" <a href="mailto:Jonathan.J.Wilmot@NASA.gov">
<Jonathan.J.Wilmot@NASA.gov></a><b><br>
Date: </b>Thursday, February 28, 2019 at 7:28 AM<b><br>
To: </b>Peter Shames <a href="mailto:Peter.M.Shames@jpl.nasa.gov"><Peter.M.Shames@jpl.nasa.gov></a>, 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><b><br>
Cc: </b>Lee Pitts <a href="mailto:robert.l.pitts@nasa.gov"><robert.l.pitts@nasa.gov></a><b><br>
Subject: </b>Re: [Sls-slp] Call for Use Cases of Space Packet Protocol<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
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>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
Folks,<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
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 style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
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 style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
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 style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
Cheers, Peter<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<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><b><br>
Reply-To: </b>"Wilmot, Jonathan J. (GSFC-5820)" <a href="mailto:Jonathan.J.Wilmot@NASA.gov">
<Jonathan.J.Wilmot@NASA.gov></a><b><br>
Date: </b>Thursday, February 28, 2019 at 7:03 AM<b><br>
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><b><br>
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><b><br>
Subject: </b>Re: [Sls-slp] Call for Use Cases of Space Packet Protocol<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
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>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
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 style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
Scott<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<b>From:</b> Greenberg, Edward (312B) <b><br>
Sent:</b> Sunday, April 22, 2018 7:37 AM<b><br>
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><b><br>
Cc:</b> Lee Pitts <a href="mailto:robert.l.pitts@nasa.gov"><robert.l.pitts@nasa.gov></a><b><br>
Subject:</b> Call for Use Cases of Space Packet Protocol<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
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 style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
· ESA has PUS <o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
· Space Station has its own secondary header <o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
· Orion is looking for a secondary header <o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
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 style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
It is possible that the role of the packet might change with the use of DTN bundles.<o:p></o:p></p>
<p style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
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 style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt">
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>
<p class="MsoNormal" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in">
<br>
<span style="font-size:12.0pt"> </span> <br>
<span style="font-size:12.0pt"> </span> <br>
<span style="font-size:12.0pt"> </span> <br>
<span style="font-size:12.0pt"> </span> <br>
<tt><span style="font-size:10.0pt">_______________________________________________</span></tt><span style="font-size:10.0pt;font-family:"Courier New""><br>
<tt>SLS-SLP mailing list</tt><br>
<tt>SLS-SLP@mailman.ccsds.org</tt><br>
</span><a href="https://mailman.ccsds.org/cgi-bin/mailman/listinfo/sls-slp"><tt><span style="font-size:10.0pt">https://mailman.ccsds.org/cgi-bin/mailman/listinfo/sls-slp</span></tt></a><span style="font-size:10.0pt;font-family:"Courier New""><br>
<br>
</span><o:p></o:p></p>
</div>
<pre style="margin-left:.5in">This message is intended only for the recipient(s) named above. It may contain proprietary information and/or<o:p></o:p></pre>
<pre style="margin-left:.5in">protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received<o:p></o:p></pre>
<pre style="margin-left:.5in">this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect<o:p></o:p></pre>
<pre style="margin-left:.5in">personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (dpo@esa.int).<o:p></o:p></pre>
</div>
</body>
</html>