From greg.j.kazz at jpl.nasa.gov Fri Apr 13 00:39:50 2018 From: greg.j.kazz at jpl.nasa.gov (Kazz, Greg J (312B)) Date: Fri, 13 Apr 2018 00:39:50 +0000 Subject: [Sls-slp] NASA Presentation on SPP APID Extension Message-ID: Dear SLP WG, Jonathan Wilmot’s presentation on the Space Packet Protocol (SPP) APID Extension proposal for tomorrow’s SLP WG meeting is in the CWE under this URL: https://tinyurl.com/yaj8cu7d best regards, Greg Greg Kazz Principal Engineer Technical Group Supervisor, Project Software and End-to-End Information Systems Engineering (312B) Jet Propulsion Laboratory 4800 Oak Grove Dr., M/S 301-490 Pasadena, CA 91109 1+(818)393 6529(voice) 1+(818)393 6871(fax) email: greg.j.kazz at jpl.nasa.gov -------------- next part -------------- An HTML attachment was scrubbed... URL: From greg.j.kazz at jpl.nasa.gov Fri Apr 13 14:54:48 2018 From: greg.j.kazz at jpl.nasa.gov (Kazz, Greg J (312B)) Date: Fri, 13 Apr 2018 14:54:48 +0000 Subject: [Sls-slp] Updated notes to SPP Revisions Presentation from Gian Paolo and Greg Message-ID: <65222732-74F4-4A29-A7DA-C115ED9F4359@jpl.nasa.gov> All, Attached are the comments made in today’s AM SLP WG session on SPP Revision. Regards, Greg Greg Kazz Principal Engineer Technical Group Supervisor, Project Software and End-to-End Information Systems Engineering (312B) Jet Propulsion Laboratory 4800 Oak Grove Dr., M/S 301-490 Pasadena, CA 91109 1+(818)393 6529(voice) 1+(818)393 6871(fax) email: greg.j.kazz at jpl.nasa.gov -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Way_forward_on_SPP+gpc20180313+gk_NIST.pptx Type: application/vnd.openxmlformats-officedocument.presentationml.presentation Size: 1696513 bytes Desc: Way_forward_on_SPP+gpc20180313+gk_NIST.pptx URL: From greg.j.kazz at jpl.nasa.gov Tue Apr 17 23:47:32 2018 From: greg.j.kazz at jpl.nasa.gov (Kazz, Greg J (312B)) Date: Tue, 17 Apr 2018 23:47:32 +0000 Subject: [Sls-slp] Draft SLP WG meeting minutes Spring 2018 NIST Message-ID: Dear All, Please let me know your comments and any updates you may have on the attached SLP WG meeting minutes from our recent meeting at NIST. I would like to get them finalized by April 25 so please send me your comments beforehand. Thanks! Greg Greg Kazz Principal Engineer Technical Group Supervisor, Project Software and End-to-End Information Systems Engineering (312B) Jet Propulsion Laboratory 4800 Oak Grove Dr., M/S 301-490 Pasadena, CA 91109 1+(818)393 6529(voice) 1+(818)393 6871(fax) email: greg.j.kazz at jpl.nasa.gov -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: CCSDS Spring 2018 SLP WG Meeting Minutes_NIST_V1.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 1506644 bytes Desc: CCSDS Spring 2018 SLP WG Meeting Minutes_NIST_V1.docx URL: From edward.greenberg at jpl.nasa.gov Sun Apr 22 14:37:01 2018 From: edward.greenberg at jpl.nasa.gov (Greenberg, Edward (312B)) Date: Sun, 22 Apr 2018 14:37:01 +0000 Subject: [Sls-slp] Call for Use Cases of Space Packet Protocol Message-ID: There seems to be lots of new Use Cases for Space Packets then were considered in the original specification. For example: * ESA has PUS * Space Station has its own secondary header * Orion is looking for a secondary header 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). It is possible that the role of the packet might change with the use of DTN bundles. 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. 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From edward.greenberg at jpl.nasa.gov Mon Apr 23 00:42:14 2018 From: edward.greenberg at jpl.nasa.gov (Greenberg, Edward (312B)) Date: Mon, 23 Apr 2018 00:42:14 +0000 Subject: [Sls-slp] Call for Use Cases of Space Packet Protocol In-Reply-To: <8f46b707d7074aa5b1fa0912ab9612f1@jpl.nasa.gov> References: <8f46b707d7074aa5b1fa0912ab9612f1@jpl.nasa.gov> Message-ID: <98375e11c2ac432d83927b2dc04de222@jpl.nasa.gov> I'm sure it can but everyone has their own unidentified secondary header. From: Burleigh, Scott C (312B) Sent: Sunday, April 22, 2018 9:16 AM To: Greenberg, Edward (312B) ; sls-slp at mailman.ccsds.org; Jonathan.J.Wilmot at NASA.gov Cc: Lee Pitts Subject: RE: Call for Use Cases of Space Packet Protocol 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. Scott From: Greenberg, Edward (312B) Sent: Sunday, April 22, 2018 7:37 AM To: sls-slp at mailman.ccsds.org; Jonathan.J.Wilmot at NASA.gov Cc: Lee Pitts > Subject: Call for Use Cases of Space Packet Protocol There seems to be lots of new Use Cases for Space Packets then were considered in the original specification. For example: * ESA has PUS * Space Station has its own secondary header * Orion is looking for a secondary header 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). It is possible that the role of the packet might change with the use of DTN bundles. 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. 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.c.burleigh at jpl.nasa.gov Sun Apr 22 16:16:23 2018 From: scott.c.burleigh at jpl.nasa.gov (Burleigh, Scott C (312B)) Date: Sun, 22 Apr 2018 16:16:23 +0000 Subject: [Sls-slp] Call for Use Cases of Space Packet Protocol In-Reply-To: References: Message-ID: <8f46b707d7074aa5b1fa0912ab9612f1@jpl.nasa.gov> 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. Scott From: Greenberg, Edward (312B) Sent: Sunday, April 22, 2018 7:37 AM To: sls-slp at mailman.ccsds.org; Jonathan.J.Wilmot at NASA.gov Cc: Lee Pitts Subject: Call for Use Cases of Space Packet Protocol There seems to be lots of new Use Cases for Space Packets then were considered in the original specification. For example: * ESA has PUS * Space Station has its own secondary header * Orion is looking for a secondary header 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). It is possible that the role of the packet might change with the use of DTN bundles. 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. 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From peter.m.shames at jpl.nasa.gov Mon Apr 23 22:49:17 2018 From: peter.m.shames at jpl.nasa.gov (Shames, Peter M (312B)) Date: Mon, 23 Apr 2018 22:49:17 +0000 Subject: [Sls-slp] Call for Use Cases of Space Packet Protocol Message-ID: <77134E1F-3004-49BC-9296-2DEA341B5FF4@jpl.nasa.gov> 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. 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. Let's not get them confused any more than they already are. Peter From: SLS-SLP on behalf of Scott Burleigh Date: Monday, April 23, 2018 at 9:08 AM To: "Greenberg, Edward" , "sls-slp at mailman.ccsds.org" , "Wilmot, Jonathan J. (GSFC-5820)" Cc: Lee Pitts Subject: Re: [Sls-slp] Call for Use Cases of Space Packet Protocol 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. Scott From: Greenberg, Edward (312B) Sent: Sunday, April 22, 2018 7:37 AM To: sls-slp at mailman.ccsds.org; Jonathan.J.Wilmot at NASA.gov Cc: Lee Pitts Subject: Call for Use Cases of Space Packet Protocol There seems to be lots of new Use Cases for Space Packets then were considered in the original specification. For example: · ESA has PUS · Space Station has its own secondary header · Orion is looking for a secondary header 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). It is possible that the role of the packet might change with the use of DTN bundles. 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. 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From edward.greenberg at jpl.nasa.gov Mon Apr 23 22:56:02 2018 From: edward.greenberg at jpl.nasa.gov (Greenberg, Edward (312B)) Date: Mon, 23 Apr 2018 22:56:02 +0000 Subject: [Sls-slp] Call for Use Cases of Space Packet Protocol In-Reply-To: <77134E1F-3004-49BC-9296-2DEA341B5FF4@jpl.nasa.gov> References: <77134E1F-3004-49BC-9296-2DEA341B5FF4@jpl.nasa.gov> Message-ID: <794a5017dacb4cf48cecadc71e21239d@jpl.nasa.gov> 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. From: Shames, Peter M (312B) Sent: Monday, April 23, 2018 3:49 PM To: Burleigh, Scott C (312B) ; Greenberg, Edward (312B) ; sls-slp at mailman.ccsds.org; Jonathan.J.Wilmot at NASA.gov Cc: Lee Pitts Subject: Re: [Sls-slp] Call for Use Cases of Space Packet Protocol 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. 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. Let's not get them confused any more than they already are. Peter From: SLS-SLP > on behalf of Scott Burleigh > Date: Monday, April 23, 2018 at 9:08 AM To: "Greenberg, Edward" >, "sls-slp at mailman.ccsds.org" >, "Wilmot, Jonathan J. (GSFC-5820)" > Cc: Lee Pitts > Subject: Re: [Sls-slp] Call for Use Cases of Space Packet Protocol 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. Scott From: Greenberg, Edward (312B) Sent: Sunday, April 22, 2018 7:37 AM To: sls-slp at mailman.ccsds.org; Jonathan.J.Wilmot at NASA.gov Cc: Lee Pitts > Subject: Call for Use Cases of Space Packet Protocol There seems to be lots of new Use Cases for Space Packets then were considered in the original specification. For example: · ESA has PUS · Space Station has its own secondary header · Orion is looking for a secondary header 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). It is possible that the role of the packet might change with the use of DTN bundles. 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. 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.c.burleigh at jpl.nasa.gov Mon Apr 23 23:01:11 2018 From: scott.c.burleigh at jpl.nasa.gov (Burleigh, Scott C (312B)) Date: Mon, 23 Apr 2018 23:01:11 +0000 Subject: [Sls-slp] Call for Use Cases of Space Packet Protocol In-Reply-To: <77134E1F-3004-49BC-9296-2DEA341B5FF4@jpl.nasa.gov> References: <77134E1F-3004-49BC-9296-2DEA341B5FF4@jpl.nasa.gov> Message-ID: <3580c73708264a67964aa56620c1cfe3@jpl.nasa.gov> Hi, Peter. Actually, what you say about the DEM being used on top of the network and transport layers is exactly what I was thinking of: Space Packets seem like a great way to package application (e.g., instrument, vehicle health, etc.) data that would be carried by underlying DTN. I definitely agree that we must not overload the Space Packet with features that belong at other layers of the stack, such as routing and network functions. Scott From: Shames, Peter M (312B) Sent: Monday, April 23, 2018 3:49 PM To: Burleigh, Scott C (312B) ; Greenberg, Edward (312B) ; sls-slp at mailman.ccsds.org; Jonathan.J.Wilmot at NASA.gov Cc: Lee Pitts Subject: Re: [Sls-slp] Call for Use Cases of Space Packet Protocol 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. 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. Let's not get them confused any more than they already are. Peter From: SLS-SLP > on behalf of Scott Burleigh > Date: Monday, April 23, 2018 at 9:08 AM To: "Greenberg, Edward" >, "sls-slp at mailman.ccsds.org" >, "Wilmot, Jonathan J. (GSFC-5820)" > Cc: Lee Pitts > Subject: Re: [Sls-slp] Call for Use Cases of Space Packet Protocol 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. Scott From: Greenberg, Edward (312B) Sent: Sunday, April 22, 2018 7:37 AM To: sls-slp at mailman.ccsds.org; Jonathan.J.Wilmot at NASA.gov Cc: Lee Pitts > Subject: Call for Use Cases of Space Packet Protocol There seems to be lots of new Use Cases for Space Packets then were considered in the original specification. For example: · ESA has PUS · Space Station has its own secondary header · Orion is looking for a secondary header 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). It is possible that the role of the packet might change with the use of DTN bundles. 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. 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From greg.j.kazz at jpl.nasa.gov Wed Apr 25 22:16:12 2018 From: greg.j.kazz at jpl.nasa.gov (Kazz, Greg J (312B)) Date: Wed, 25 Apr 2018 22:16:12 +0000 Subject: [Sls-slp] Final Meeting Minutes from SLS-SLP WG Spring 2018 at NIST Message-ID: Dear SLP WG members, Attached and in the CWE under the following URL, please find the final SLP WG meeting minutes for the Spring 2018 meeting. https://tinyurl.com/y6ur272p Best regards, Greg Greg Kazz Principal Engineer Technical Group Supervisor, Project Software and End-to-End Information Systems Engineering (312B) Jet Propulsion Laboratory 4800 Oak Grove Dr., M/S 301-490 Pasadena, CA 91109 1+(818)393 6529(voice) 1+(818)393 6871(fax) email: greg.j.kazz at jpl.nasa.gov -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: CCSDS Spring 2018 SLP WG Meeting Minutes_NIST_V2.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 1508626 bytes Desc: CCSDS Spring 2018 SLP WG Meeting Minutes_NIST_V2.docx URL: