<span style=" font-size:10pt;font-family:sans-serif">Dear,</span>
<br><span style=" font-size:10pt;font-family: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:10pt;font-family:sans-serif">The envisaged
approach by Peter is that</span>
<br><span style=" font-size:10pt;font-family: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:10pt;font-family:sans-serif">B) Secondary Header
Types will be registered in SANA with </span><span style=" font-size:11pt;font-family:Calibri">a
two level approach :</span>
<br><span style=" font-size:11pt;font-family:Calibri">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
</span>
<br><span style=" font-size:11pt;font-family:Calibri">2.    
  An XML schema (or JSON, your choice) that formalizes the secondary
header structure, field names, data types, sizes, and definitions </span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif"><b>Is this the
common understanding for everybody?</b></span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Best regards and
have a nice week end</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Gian Paolo</span>
<br>
<br><span style=" font-size:10pt;font-family: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:9pt;color:#5f5f5f;font-family:sans-serif">From:
       </span><span style=" font-size:9pt;font-family:sans-serif">"Shames,
Peter M \(312B\) via SLS-SLP" <sls-slp@mailman.ccsds.org></span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">To:
       </span><span style=" font-size:9pt;font-family: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:9pt;color:#5f5f5f;font-family:sans-serif">Cc:
       </span><span style=" font-size:9pt;font-family:sans-serif">Lee
Pitts <robert.l.pitts@nasa.gov></span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Date:
       </span><span style=" font-size:9pt;font-family:sans-serif">28-02-19
17:13</span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Subject:
       </span><span style=" font-size:9pt;font-family:sans-serif">Re:
[Sls-slp] Call for Use Cases of Space Packet Protocol</span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Sent
by:        </span><span style=" font-size:9pt;font-family:sans-serif">"SLS-SLP"
<sls-slp-bounces@mailman.ccsds.org></span>
<br>
<hr noshade>
<br>
<br>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">Hi
Jonathan,</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">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.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<div><span style=" font-size:12pt;font-family:Times New Roman"><b>4.1.3.2.1.5
 </b>If present, the Packet Secondary Header shall consist of either:</span>
<p style="margin-top:180pt;margin-Bottom:0pt"><span style=" font-size:12pt;font-family:Times New Roman">a)
     a Time Code Field (variable length) only;</span></p>
<p style="margin-top:180pt;margin-Bottom:0pt"><span style=" font-size:12pt;font-family:Times New Roman">b)
     an Ancillary Data Field (variable length) only; or</span></p>
<p style="margin-top:180pt;margin-Bottom:0pt"><span style=" font-size:12pt;font-family:Times New Roman">c)
     a Time Code Field followed by an Ancillary Data Field.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">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.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">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.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">Peter</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:12pt;font-family:Calibri"><b>From:
</b>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></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">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:</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">Hi
Jonathan,</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">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.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">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.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">Peter</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"><b>From:
</b>SLS-SLP </span><a href="mailto:sls-slp-bounces@mailman.ccsds.org"><span style=" font-size:11pt;color:blue;font-family:Calibri"><u><sls-slp-bounces@mailman.ccsds.org></u></span></a><span style=" font-size:11pt;font-family:Calibri">
on behalf of Jonathan Wilmot via SLS-SLP </span><a href="mailto:sls-slp@mailman.ccsds.org"><span style=" font-size:11pt;color:blue;font-family:Calibri"><u><sls-slp@mailman.ccsds.org></u></span></a><span style=" font-size:11pt;font-family:Calibri"><b><br>
Reply-To: </b>"Wilmot, Jonathan J. (GSFC-5820)" </span><a href=mailto:Jonathan.J.Wilmot@NASA.gov><span style=" font-size:11pt;color:blue;font-family:Calibri"><u><Jonathan.J.Wilmot@NASA.gov></u></span></a><span style=" font-size:11pt;font-family:Calibri"><b><br>
Date: </b>Thursday, February 28, 2019 at 7:43 AM<b><br>
To: </b>Peter Shames </span><a href=mailto:Peter.M.Shames@jpl.nasa.gov><span style=" font-size:11pt;color:blue;font-family:Calibri"><u><Peter.M.Shames@jpl.nasa.gov></u></span></a><span style=" font-size:11pt;font-family:Calibri">,
Scott Burleigh </span><a href=mailto:Scott.C.Burleigh@jpl.nasa.gov><span style=" font-size:11pt;color:blue;font-family:Calibri"><u><Scott.C.Burleigh@jpl.nasa.gov></u></span></a><span style=" font-size:11pt;font-family:Calibri">,
"Greenberg, Edward" </span><a href=mailto:Edward.Greenberg@jpl.nasa.gov><span style=" font-size:11pt;color:blue;font-family:Calibri"><u><Edward.Greenberg@jpl.nasa.gov></u></span></a><span style=" font-size:11pt;font-family:Calibri">,
</span><a href="mailto:sls-slp@mailman.ccsds.org"><span style=" font-size:11pt;color:blue;font-family:Calibri"><u>"sls-slp@mailman.ccsds.org"</u></span></a><span style=" font-size:11pt;font-family:Calibri">
</span><a href="mailto:sls-slp@mailman.ccsds.org"><span style=" font-size:11pt;color:blue;font-family:Calibri"><u><sls-slp@mailman.ccsds.org></u></span></a><span style=" font-size:11pt;font-family:Calibri"><b><br>
Cc: </b>Lee Pitts </span><a href=mailto:robert.l.pitts@nasa.gov><span style=" font-size:11pt;color:blue;font-family:Calibri"><u><robert.l.pitts@nasa.gov></u></span></a><span style=" font-size:11pt;font-family:Calibri"><b><br>
Subject: </b>Re: [Sls-slp] Call for Use Cases of Space Packet Protocol</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">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:</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">Hi
Jonathan,</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">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.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">I'd
like to encourage something like a two level approach to this:</span></p>
<br><span style=" font-size:11pt;font-family:Calibri">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
</span>
<br><span style=" font-size:11pt;font-family:Calibri">2.    
  An XML schema (or JSON, your choice) that formalizes the secondary
header structure, field names, data types, sizes, and definitions </span>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">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.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">Does
his make sense to you guys?  </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">Thanks,
Peter</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"><b>From:
</b>SLS-SLP </span><a href="mailto:sls-slp-bounces@mailman.ccsds.org"><span style=" font-size:11pt;color:blue;font-family:Calibri"><u><sls-slp-bounces@mailman.ccsds.org></u></span></a><span style=" font-size:11pt;font-family:Calibri">
on behalf of Jonathan Wilmot via SLS-SLP </span><a href="mailto:sls-slp@mailman.ccsds.org"><span style=" font-size:11pt;color:blue;font-family:Calibri"><u><sls-slp@mailman.ccsds.org></u></span></a><span style=" font-size:11pt;font-family:Calibri"><b><br>
Reply-To: </b>"Wilmot, Jonathan J. (GSFC-5820)" </span><a href=mailto:Jonathan.J.Wilmot@NASA.gov><span style=" font-size:11pt;color:blue;font-family:Calibri"><u><Jonathan.J.Wilmot@NASA.gov></u></span></a><span style=" font-size:11pt;font-family:Calibri"><b><br>
Date: </b>Thursday, February 28, 2019 at 7:28 AM<b><br>
To: </b>Peter Shames </span><a href=mailto:Peter.M.Shames@jpl.nasa.gov><span style=" font-size:11pt;color:blue;font-family:Calibri"><u><Peter.M.Shames@jpl.nasa.gov></u></span></a><span style=" font-size:11pt;font-family:Calibri">,
Scott Burleigh </span><a href=mailto:Scott.C.Burleigh@jpl.nasa.gov><span style=" font-size:11pt;color:blue;font-family:Calibri"><u><Scott.C.Burleigh@jpl.nasa.gov></u></span></a><span style=" font-size:11pt;font-family:Calibri">,
"Greenberg, Edward" </span><a href=mailto:Edward.Greenberg@jpl.nasa.gov><span style=" font-size:11pt;color:blue;font-family:Calibri"><u><Edward.Greenberg@jpl.nasa.gov></u></span></a><span style=" font-size:11pt;font-family:Calibri">,
</span><a href="mailto:sls-slp@mailman.ccsds.org"><span style=" font-size:11pt;color:blue;font-family:Calibri"><u>"sls-slp@mailman.ccsds.org"</u></span></a><span style=" font-size:11pt;font-family:Calibri">
</span><a href="mailto:sls-slp@mailman.ccsds.org"><span style=" font-size:11pt;color:blue;font-family:Calibri"><u><sls-slp@mailman.ccsds.org></u></span></a><span style=" font-size:11pt;font-family:Calibri"><b><br>
Cc: </b>Lee Pitts </span><a href=mailto:robert.l.pitts@nasa.gov><span style=" font-size:11pt;color:blue;font-family:Calibri"><u><robert.l.pitts@nasa.gov></u></span></a><span style=" font-size:11pt;font-family:Calibri"><b><br>
Subject: </b>Re: [Sls-slp] Call for Use Cases of Space Packet Protocol</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">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:</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">Folks,</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">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.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">By
the way, the SOIS Dictionary of Terms (DoT) may prove to be useful as a
source of standardized terms.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">Lastly,
as I recall the Constellation DEM did not adhere to the SPP at all.  I
may be mis-remembering.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">Cheers,
Peter</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"><b>From:
</b>SLS-SLP </span><a href="mailto:sls-slp-bounces@mailman.ccsds.org"><span style=" font-size:11pt;color:blue;font-family:Calibri"><u><sls-slp-bounces@mailman.ccsds.org></u></span></a><span style=" font-size:11pt;font-family:Calibri">
on behalf of Jonathan Wilmot via SLS-SLP </span><a href="mailto:sls-slp@mailman.ccsds.org"><span style=" font-size:11pt;color:blue;font-family:Calibri"><u><sls-slp@mailman.ccsds.org></u></span></a><span style=" font-size:11pt;font-family:Calibri"><b><br>
Reply-To: </b>"Wilmot, Jonathan J. (GSFC-5820)" </span><a href=mailto:Jonathan.J.Wilmot@NASA.gov><span style=" font-size:11pt;color:blue;font-family:Calibri"><u><Jonathan.J.Wilmot@NASA.gov></u></span></a><span style=" font-size:11pt;font-family:Calibri"><b><br>
Date: </b>Thursday, February 28, 2019 at 7:03 AM<b><br>
To: </b>Scott Burleigh </span><a href=mailto:Scott.C.Burleigh@jpl.nasa.gov><span style=" font-size:11pt;color:blue;font-family:Calibri"><u><Scott.C.Burleigh@jpl.nasa.gov></u></span></a><span style=" font-size:11pt;font-family:Calibri">,
"Greenberg, Edward" </span><a href=mailto:Edward.Greenberg@jpl.nasa.gov><span style=" font-size:11pt;color:blue;font-family:Calibri"><u><Edward.Greenberg@jpl.nasa.gov></u></span></a><span style=" font-size:11pt;font-family:Calibri">,
</span><a href="mailto:sls-slp@mailman.ccsds.org"><span style=" font-size:11pt;color:blue;font-family:Calibri"><u>"sls-slp@mailman.ccsds.org"</u></span></a><span style=" font-size:11pt;font-family:Calibri">
</span><a href="mailto:sls-slp@mailman.ccsds.org"><span style=" font-size:11pt;color:blue;font-family:Calibri"><u><sls-slp@mailman.ccsds.org></u></span></a><span style=" font-size:11pt;font-family:Calibri"><b><br>
Cc: </b>Peter Shames </span><a href=mailto:Peter.M.Shames@jpl.nasa.gov><span style=" font-size:11pt;color:blue;font-family:Calibri"><u><Peter.M.Shames@jpl.nasa.gov></u></span></a><span style=" font-size:11pt;font-family:Calibri">,
Lee Pitts </span><a href=mailto:robert.l.pitts@nasa.gov><span style=" font-size:11pt;color:blue;font-family:Calibri"><u><robert.l.pitts@nasa.gov></u></span></a><span style=" font-size:11pt;font-family:Calibri"><b><br>
Subject: </b>Re: [Sls-slp] Call for Use Cases of Space Packet Protocol</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">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:</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">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 style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">Scott</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"><b>From:</b>
Greenberg, Edward (312B) <b><br>
Sent:</b> Sunday, April 22, 2018 7:37 AM<b><br>
To:</b> </span><a href="mailto:sls-slp@mailman.ccsds.org"><span style=" font-size:11pt;color:blue;font-family:Calibri"><u>sls-slp@mailman.ccsds.org</u></span></a><span style=" font-size:11pt;font-family:Calibri">;
</span><a href=mailto:Jonathan.J.Wilmot@NASA.gov><span style=" font-size:11pt;color:blue;font-family:Calibri"><u>Jonathan.J.Wilmot@NASA.gov</u></span></a><span style=" font-size:11pt;font-family:Calibri"><b><br>
Cc:</b> Lee Pitts </span><a href=mailto:robert.l.pitts@nasa.gov><span style=" font-size:11pt;color:blue;font-family:Calibri"><u><robert.l.pitts@nasa.gov></u></span></a><span style=" font-size:11pt;font-family:Calibri"><b><br>
Subject:</b> Call for Use Cases of Space Packet Protocol</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri"> </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">There
seems to be lots of new Use Cases for Space Packets then were considered
in the original specification. For example:</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">
        ESA has PUS </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">
        Space Station has its own secondary header
</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">
        Orion is looking for a secondary header </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">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).
</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">It
is possible that the role of the packet might change with the use of DTN
bundles.</span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">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.  </span></p>
<p style="margin-top:0px;margin-Bottom:0px"><span style=" font-size:11pt;font-family:Calibri">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>
<br><span style=" font-size:12pt"> </span>
<br><span style=" font-size:12pt"> </span>
<br><span style=" font-size:12pt"> </span>
<br><span style=" font-size:12pt"> </span>
<br><tt><span style=" font-size:10pt">_______________________________________________<br>
SLS-SLP mailing list<br>
SLS-SLP@mailman.ccsds.org<br>
</span></tt><a href="https://mailman.ccsds.org/cgi-bin/mailman/listinfo/sls-slp"><tt><span style=" font-size:10pt">https://mailman.ccsds.org/cgi-bin/mailman/listinfo/sls-slp</span></tt></a><tt><span style=" font-size:10pt"><br>
</span></tt>
<br>
<br></div><PRE>This message is intended only for the recipient(s) named above. It may contain proprietary information and/or
protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received
this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect
personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (dpo@esa.int).
</PRE>