From greg.j.kazz at jpl.nasa.gov Mon Jan 11 15:54:53 2016 From: greg.j.kazz at jpl.nasa.gov (Kazz, Greg J (312B)) Date: Mon, 11 Jan 2016 15:54:53 +0000 Subject: [Sls-slp] New Draft USLP White Book Available for Review Message-ID: Dear SLP WG, I hope all of you are doing well and I wish you all the best in 2016 ! Please find the latest version of the Draft USLP White Book on the CWE under: http://tinyurl.com/jf9j6u3 Along with it, is a word file called, Issues, that contain questions and options that I would like the working group to discuss in a series of telecons that I will set up using doodle polling. Please watch for an email soon, asking you for preferences when you can attend the telecons. You are welcome to add to the issues list as well. Best regards, Greg Chairman SLP WG -------------- next part -------------- An HTML attachment was scrubbed... URL: From greg.j.kazz at jpl.nasa.gov Fri Jan 15 17:32:41 2016 From: greg.j.kazz at jpl.nasa.gov (Kazz, Greg J (312B)) Date: Fri, 15 Jan 2016 17:32:41 +0000 Subject: [Sls-slp] Updated USLP Issues List now on CWE Message-ID: All, A few modifications have been made to the USLP White Book Issues list. Please find the updates (text in red) on the CWE with the date of Jan 15 in: http://tinyurl.com/jf9j6u3 Regards, Greg -------------- next part -------------- An HTML attachment was scrubbed... URL: From greg.j.kazz at jpl.nasa.gov Wed Jan 20 23:41:26 2016 From: greg.j.kazz at jpl.nasa.gov (Kazz, Greg J (312B)) Date: Wed, 20 Jan 2016 23:41:26 +0000 Subject: [Sls-slp] Minutes of SLP telecon of Jan 20 2016 on USLP White book Message-ID: Dear SLP WG member, Attached please find the meeting minutes for the telecon held on Jan. 20 to discuss Chapter 4 Frame PDU format for the draft USLP white book. Additional telecons will be announced soon. Please check your email for future announcements. Also if you have any additional USLP issues, please email them to me and I will update the Issues list on the CWE. Best regards, Greg Kazz Chairman CCSDS SLP WG -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: USLP Telecon_WB_1_2016.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 150706 bytes Desc: USLP Telecon_WB_1_2016.docx URL: From greg.j.kazz at jpl.nasa.gov Mon Jan 25 17:27:22 2016 From: greg.j.kazz at jpl.nasa.gov (Kazz, Greg J (312B)) Date: Mon, 25 Jan 2016 17:27:22 +0000 Subject: [Sls-slp] Latest USLP White Book and Issues documents on CWE Message-ID: All, Responding to the comments made at our last telecon on Jan 20, I have posted a slightly updated (based upon the minutes in the file, USLP Telecon_WB_1 _2016) draft USLP white book ( with “post_telecon1” in the filename) on the CWE. http://tinyurl.com/jf9j6u3 The minutes to the meeting are also posted along with and updated issues file. I will soon send another Doodle Poll for a second telecon on the USLP white book to be held next week. Please stay tuned for that. Best regards, Greg Kazz Chairman CCSDS SLP WG -------------- next part -------------- An HTML attachment was scrubbed... URL: From greg.j.kazz at jpl.nasa.gov Tue Jan 26 17:05:32 2016 From: greg.j.kazz at jpl.nasa.gov (Kazz, Greg J (312B)) Date: Tue, 26 Jan 2016 17:05:32 +0000 Subject: [Sls-slp] USLP capability of direct PDU insertion into Frame Data Field Message-ID: Dear SLP members, Just as a reminder, the definition of the Protocol ID field within the USLP Transfer Frame Data Field Header allows for the capability of inserting CCSDS recognized PDUs directly into the data field I.e., data zone in USLP parlance of the frame. See Section 4.1.4.2 TRANSFER FRAME DATA FIELD HEADER Thanks!Regards…Greg G Greg -------------- next part -------------- An HTML attachment was scrubbed... URL: From Tomaso.deCola at dlr.de Tue Jan 26 23:15:09 2016 From: Tomaso.deCola at dlr.de (Tomaso.deCola at dlr.de) Date: Tue, 26 Jan 2016 23:15:09 +0000 Subject: [Sls-slp] USLP capability of direct PDU insertion into Frame Data Field In-Reply-To: References: Message-ID: <1A39DCC13AF3C14B83CD74124D4DCFC3175C064B@DLREXMBX01.intra.dlr.de> Hi Greg, With this do you mean that "higher" layer protocol PDUs can be directly encapsulated into USLP, avoiding the use of the Encaps Service? If this is the case, I guess ( I don't remember right now) that the service primitives exposed to the upper layers (e.g., LTP or BP) will override the primitives currently offered by the Encaps service. On the contrary, if the primitives are different I'd say that the interface between USLP and the higher layer protocols will be different from the case where you have Encaps instead of USLP. Can you develop a bit more on this point? Tomaso ------------------------ Deutsches Zentrum für Luft- und Raumfahrt (DLR) German Aerospace Center Institute of Communications and Navigation | Satellite Networks | Oberpfaffenhofen | 82234 Wessling | Germany Tomaso de Cola, Ph.D. Telefon +49 8153 28-2156 | Telefax +49 8153 28-2844 | tomaso.decola at dlr.de http://www.dlr.de/kn/institut/abteilungen/san From: sls-slp-bounces at mailman.ccsds.org [mailto:sls-slp-bounces at mailman.ccsds.org] On Behalf Of Kazz, Greg J (312B) Sent: Tuesday, January 26, 2016 18:06 To: sls-slp at mailman.ccsds.org Subject: [Sls-slp] USLP capability of direct PDU insertion into Frame Data Field Dear SLP members, Just as a reminder, the definition of the Protocol ID field within the USLP Transfer Frame Data Field Header allows for the capability of inserting CCSDS recognized PDUs directly into the data field I.e., data zone in USLP parlance of the frame. See Section 4.1.4.2 TRANSFER FRAME DATA FIELD HEADER Thanks!Regards...Greg G Greg -------------- next part -------------- An HTML attachment was scrubbed... URL: From greg.j.kazz at jpl.nasa.gov Wed Jan 27 16:55:01 2016 From: greg.j.kazz at jpl.nasa.gov (Kazz, Greg J (312B)) Date: Wed, 27 Jan 2016 16:55:01 +0000 Subject: [Sls-slp] USLP capability of direct PDU insertion into Frame Data Field In-Reply-To: <1A39DCC13AF3C14B83CD74124D4DCFC3175C064B@DLREXMBX01.intra.dlr.de> References: <1A39DCC13AF3C14B83CD74124D4DCFC3175C064B@DLREXMBX01.intra.dlr.de> Message-ID: Tomaso, Our basic service primative for other protocols to use USLP is the packet primative. It is the same one we have been using for TM, AOS, TC except we also added a Protocol ID field to accommodate upper layer protocols. Do you see a problem with this approach ? So yes, the I/F is different from AOS, TC, TM but only very slightly different by one parameter. Regards, Greg From: "Tomaso.deCola at dlr.de" > Date: Tuesday, January 26, 2016 at 3:15 PM To: "Kazz, Greg J (313B)" > Cc: "sls-slp at mailman.ccsds.org" > Subject: RE: [Sls-slp] USLP capability of direct PDU insertion into Frame Data Field Hi Greg, With this do you mean that “higher” layer protocol PDUs can be directly encapsulated into USLP, avoiding the use of the Encaps Service? If this is the case, I guess ( I don’t remember right now) that the service primitives exposed to the upper layers (e.g., LTP or BP) will override the primitives currently offered by the Encaps service. On the contrary, if the primitives are different I’d say that the interface between USLP and the higher layer protocols will be different from the case where you have Encaps instead of USLP. Can you develop a bit more on this point? Tomaso ———————————————————————— Deutsches Zentrum für Luft- und Raumfahrt (DLR) German Aerospace Center Institute of Communications and Navigation | Satellite Networks | Oberpfaffenhofen | 82234 Wessling | Germany Tomaso de Cola, Ph.D. Telefon +49 8153 28-2156 | Telefax +49 8153 28-2844 |tomaso.decola at dlr.de http://www.dlr.de/kn/institut/abteilungen/san From: sls-slp-bounces at mailman.ccsds.org [mailto:sls-slp-bounces at mailman.ccsds.org] On Behalf Of Kazz, Greg J (312B) Sent: Tuesday, January 26, 2016 18:06 To: sls-slp at mailman.ccsds.org Subject: [Sls-slp] USLP capability of direct PDU insertion into Frame Data Field Dear SLP members, Just as a reminder, the definition of the Protocol ID field within the USLP Transfer Frame Data Field Header allows for the capability of inserting CCSDS recognized PDUs directly into the data field I.e., data zone in USLP parlance of the frame. See Section 4.1.4.2 TRANSFER FRAME DATA FIELD HEADER Thanks!Regards…Greg G Greg -------------- next part -------------- An HTML attachment was scrubbed... URL: From Tomaso.deCola at dlr.de Wed Jan 27 17:44:28 2016 From: Tomaso.deCola at dlr.de (Tomaso.deCola at dlr.de) Date: Wed, 27 Jan 2016 17:44:28 +0000 Subject: [Sls-slp] USLP capability of direct PDU insertion into Frame Data Field In-Reply-To: References: <1A39DCC13AF3C14B83CD74124D4DCFC3175C064B@DLREXMBX01.intra.dlr.de> Message-ID: <1A39DCC13AF3C14B83CD74124D4DCFC3175C0987@DLREXMBX01.intra.dlr.de> Greg, What I meant is the possible difference between the interfaces USLP - Higher layer protocol and Encaps - Higher layer protocol. In any case, I checked the encaps blue book and the current version of the USLP and there is no difference (if I'm not wrong) in the parameters passed with encaps.request and packet.request, respectively. Therefore, I guess that the higher layer protocols that required encaps can now (almost) seamlessly go over USLP. Tomaso ------------------------ Deutsches Zentrum für Luft- und Raumfahrt (DLR) German Aerospace Center Institute of Communications and Navigation | Satellite Networks | Oberpfaffenhofen | 82234 Wessling | Germany Tomaso de Cola, Ph.D. Telefon +49 8153 28-2156 | Telefax +49 8153 28-2844 | tomaso.decola at dlr.de http://www.dlr.de/kn/institut/abteilungen/san From: Kazz, Greg J (312B) [mailto:greg.j.kazz at jpl.nasa.gov] Sent: Wednesday, January 27, 2016 17:55 To: Cola, Tomaso de Cc: sls-slp at mailman.ccsds.org Subject: Re: [Sls-slp] USLP capability of direct PDU insertion into Frame Data Field Tomaso, Our basic service primative for other protocols to use USLP is the packet primative. It is the same one we have been using for TM, AOS, TC except we also added a Protocol ID field to accommodate upper layer protocols. Do you see a problem with this approach ? So yes, the I/F is different from AOS, TC, TM but only very slightly different by one parameter. Regards, Greg From: "Tomaso.deCola at dlr.de" > Date: Tuesday, January 26, 2016 at 3:15 PM To: "Kazz, Greg J (313B)" > Cc: "sls-slp at mailman.ccsds.org" > Subject: RE: [Sls-slp] USLP capability of direct PDU insertion into Frame Data Field Hi Greg, With this do you mean that "higher" layer protocol PDUs can be directly encapsulated into USLP, avoiding the use of the Encaps Service? If this is the case, I guess ( I don't remember right now) that the service primitives exposed to the upper layers (e.g., LTP or BP) will override the primitives currently offered by the Encaps service. On the contrary, if the primitives are different I'd say that the interface between USLP and the higher layer protocols will be different from the case where you have Encaps instead of USLP. Can you develop a bit more on this point? Tomaso ------------------------ Deutsches Zentrum für Luft- und Raumfahrt (DLR) German Aerospace Center Institute of Communications and Navigation | Satellite Networks | Oberpfaffenhofen | 82234 Wessling | Germany Tomaso de Cola, Ph.D. Telefon +49 8153 28-2156 | Telefax +49 8153 28-2844 |tomaso.decola at dlr.de http://www.dlr.de/kn/institut/abteilungen/san From: sls-slp-bounces at mailman.ccsds.org [mailto:sls-slp-bounces at mailman.ccsds.org] On Behalf Of Kazz, Greg J (312B) Sent: Tuesday, January 26, 2016 18:06 To: sls-slp at mailman.ccsds.org Subject: [Sls-slp] USLP capability of direct PDU insertion into Frame Data Field Dear SLP members, Just as a reminder, the definition of the Protocol ID field within the USLP Transfer Frame Data Field Header allows for the capability of inserting CCSDS recognized PDUs directly into the data field I.e., data zone in USLP parlance of the frame. See Section 4.1.4.2 TRANSFER FRAME DATA FIELD HEADER Thanks!Regards...Greg G Greg -------------- next part -------------- An HTML attachment was scrubbed... URL: From kscott at mitre.org Fri Jan 29 13:28:13 2016 From: kscott at mitre.org (Scott, Keith L.) Date: Fri, 29 Jan 2016 13:28:13 +0000 Subject: [Sls-slp] USLP capability of direct PDU insertion into Frame Data Field In-Reply-To: References: <1A39DCC13AF3C14B83CD74124D4DCFC3175C064B@DLREXMBX01.intra.dlr.de> Message-ID: <81B93A31-88DA-48C2-AC84-F06DD69A3487@mitre.org> This is analogous to the ‘Protocol' field in IPv4, with definitions for specific CCSDS data formats? So long as the included protocols are really higher-layer I think this should be fine. —keith From: > on behalf of Greg Kazz > Date: Wednesday, January 27, 2016 at 11:55 AM To: "Tomaso.deCola at dlr.de" > Cc: "sls-slp at mailman.ccsds.org" > Subject: Re: [Sls-slp] USLP capability of direct PDU insertion into Frame Data Field Tomaso, Our basic service primative for other protocols to use USLP is the packet primative. It is the same one we have been using for TM, AOS, TC except we also added a Protocol ID field to accommodate upper layer protocols. Do you see a problem with this approach ? So yes, the I/F is different from AOS, TC, TM but only very slightly different by one parameter. Regards, Greg From: "Tomaso.deCola at dlr.de" > Date: Tuesday, January 26, 2016 at 3:15 PM To: "Kazz, Greg J (313B)" > Cc: "sls-slp at mailman.ccsds.org" > Subject: RE: [Sls-slp] USLP capability of direct PDU insertion into Frame Data Field Hi Greg, With this do you mean that “higher” layer protocol PDUs can be directly encapsulated into USLP, avoiding the use of the Encaps Service? If this is the case, I guess ( I don’t remember right now) that the service primitives exposed to the upper layers (e.g., LTP or BP) will override the primitives currently offered by the Encaps service. On the contrary, if the primitives are different I’d say that the interface between USLP and the higher layer protocols will be different from the case where you have Encaps instead of USLP. Can you develop a bit more on this point? Tomaso ———————————————————————— Deutsches Zentrum für Luft- und Raumfahrt (DLR) German Aerospace Center Institute of Communications and Navigation | Satellite Networks | Oberpfaffenhofen | 82234 Wessling | Germany Tomaso de Cola, Ph.D. Telefon +49 8153 28-2156 | Telefax +49 8153 28-2844 |tomaso.decola at dlr.de http://www.dlr.de/kn/institut/abteilungen/san From:sls-slp-bounces at mailman.ccsds.org [mailto:sls-slp-bounces at mailman.ccsds.org] On Behalf Of Kazz, Greg J (312B) Sent: Tuesday, January 26, 2016 18:06 To: sls-slp at mailman.ccsds.org Subject: [Sls-slp] USLP capability of direct PDU insertion into Frame Data Field Dear SLP members, Just as a reminder, the definition of the Protocol ID field within the USLP Transfer Frame Data Field Header allows for the capability of inserting CCSDS recognized PDUs directly into the data field I.e., data zone in USLP parlance of the frame. See Section 4.1.4.2 TRANSFER FRAME DATA FIELD HEADER Thanks!Regards…Greg G Greg -------------- next part -------------- An HTML attachment was scrubbed... URL: