From greg.j.kazz at jpl.nasa.gov Wed Mar 2 16:27:16 2016 From: greg.j.kazz at jpl.nasa.gov (Kazz, Greg J (312B)) Date: Wed, 2 Mar 2016 16:27:16 +0000 Subject: [Sls-slp] USLP White Book Telecon #4 - Tue. March 9 at 7 AM Pacific Time Message-ID: Dear SLP WG, I’ve set up a Webex telecon to discuss Section 3: Services of the Draft USLP White Book for this coming Tuesday March 8 at 7 AM Pacific Time. The USLP white book we will be reviewing is in the CWE under the following URL. It is dated Feb 26 on the filename, cover sheet, as well as the footer of the file itself. I hope you can join us. http://tinyurl.com/jf9j6u3 Best regards, Greg Kazz CCSDS SLS-SLP WG chairman -------------- next part -------------- An HTML attachment was scrubbed... URL: From Gilles.Moury at cnes.fr Thu Mar 3 15:13:37 2016 From: Gilles.Moury at cnes.fr (Moury Gilles) Date: Thu, 3 Mar 2016 15:13:37 +0000 Subject: [Sls-slp] proposal for a Technical Corrigendum to 732x0b3 and 132x0b2 Message-ID: <442F062EBF46F247A96B8A50EF3EB6F42A1B0D83@TW-MBX-P04.cnesnet.ad.cnes.fr> Dear Greg, During our last SDLS WG meeting, while reviewing the content of the SDLS green book, we discovered that there were missing requirements in the new editions of AOS Space Data Link Protocol (732.0-B-3) and TM space data link protocol (132.0-B2) regarding the non-protection by SDLS of the VC carrying OID frames. Those requirements are needed because protecting VC carrying OID frames could actually ease cryptanalysis and therefore introduce a vulnerability. Those requirements are partially missing in 132.0 and completely missing in 732.0. I have drafted a proposal for a Technical Corrigendum to both documents to correct this flaw. The added requirements are the following: - In 732.0 : 6.4.5.3 & 6.4.6.2 - In 132.0 : 6.4.4.3 I attach the two documents with the additional requirements inserted: I propose to discuss those TC at our upcoming spring meetings (either SLP or SDLS). Best regards, Gilles Gilles MOURY SDLS WG Co-Chair Gilles MOURY CNES Toulouse Expert senior "Plateforme Satellite" Sous-Direction "Techniques Véhicule, Architecture & Intégration" DCT/TV-RA - Bpi 1416 18, avenue Edouard Belin F-31401 TOULOUSE Cedex 9 http://www.cnes.fr tel : +33 (0)5 61 27 3790 fax : +33 (0)5 61 27 4099 sec : +33 (0)5 61 27 3882 mob : +33 (0)6 83 56 0485 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 732x0b3_final with add req for OID VC.doc Type: application/msword Size: 596992 bytes Desc: 732x0b3_final with add req for OID VC.doc URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 132x0b2_final with add req for OID VC.doc Type: application/msword Size: 624128 bytes Desc: 132x0b2_final with add req for OID VC.doc URL: From greg.j.kazz at jpl.nasa.gov Thu Mar 3 19:00:20 2016 From: greg.j.kazz at jpl.nasa.gov (Kazz, Greg J (312B)) Date: Thu, 3 Mar 2016 19:00:20 +0000 Subject: [Sls-slp] Draft SLP WG Agenda for Cleveland Meetings Apr 2016 Message-ID: All, Please find attached and in-line in this email a draft agenda for the SLP WG meegings in Cleveland, OH during the week of April 4, 2016 Please let me know if you have any questions or comments. Best regards, Greg Kazz CCSDS Chairman SLS-SLP WG SLP Agenda Spring 2016 CCSDS Meeting in Cleveland – April 4 -8 2016 Monday AM & PM 1) Reconfirmation (5-year) review of CCSDS 232.1-B-2 COP-1 protocol 2) Review the updated USLP White Book and associated Issues File · Chap 1 - Introduction · Chap 2 – Overview · Chap 3 - Services · Chap 4 – PDU Format · Chap 5 - Managed Parameters · Chap 6 – PDU format with SDLS · Annexes Tuesday AM 1) Concept paper on modification to Prox-1 C&S CCSDS 211.2-B-2 to accommodate Version-4 USLP transfer frame together with C&S WG 2) Editorial or Technical Corrigendum for TM/AOS SDLP’s OID Frame Exception (132.0-B & 732.0-B) – Gilles Moury CNES 3) USLP Green Book Review Friday AM Joint Session with RFM, C&S, and OPT WG's - TBD See separate Joint Meeting Agenda for all of the detailed topics -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: SLP Agenda_Apr4_2016.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 68943 bytes Desc: SLP Agenda_Apr4_2016.docx URL: From MCOSBY at qinetiq.com Fri Mar 4 10:23:49 2016 From: MCOSBY at qinetiq.com (Cosby Matthew) Date: Fri, 4 Mar 2016 10:23:49 +0000 Subject: [Sls-slp] RE: UC Draft SLP WG Agenda for Cleveland Meetings Apr 2016 Message-ID: Greg, I would like to request 10-15mins to discuss an error in the P1 green book. The error is minor, but I would like to establish the method and timing to correct it (if agreed by the WG). Matt. Matthew Cosby Chief Engineer, QinetiQ Space UK Tel: +44 (0)1252 396313 email: mcosby at QinetiQ.com www.QinetiQ.com QinetiQ - Delivering customer-focused solutions Please consider the environment before printing this email. From: sls-slp-bounces at mailman.ccsds.org [mailto:sls-slp-bounces at mailman.ccsds.org] On Behalf Of Kazz, Greg J (312B) Sent: 03 March 2016 19:00 To: sls-slp at mailman.ccsds.org Subject: [Sls-slp] Draft SLP WG Agenda for Cleveland Meetings Apr 2016 All, Please find attached and in-line in this email a draft agenda for the SLP WG meegings in Cleveland, OH during the week of April 4, 2016 Please let me know if you have any questions or comments. Best regards, Greg Kazz CCSDS Chairman SLS-SLP WG SLP Agenda Spring 2016 CCSDS Meeting in Cleveland - April 4 -8 2016 Monday AM & PM 1) Reconfirmation (5-year) review of CCSDS 232.1-B-2 COP-1 protocol 2) Review the updated USLP White Book and associated Issues File ? Chap 1 - Introduction ? Chap 2 - Overview ? Chap 3 - Services ? Chap 4 - PDU Format ? Chap 5 - Managed Parameters ? Chap 6 - PDU format with SDLS ? Annexes Tuesday AM 1) Concept paper on modification to Prox-1 C&S CCSDS 211.2-B-2 to accommodate Version-4 USLP transfer frame together with C&S WG 2) Editorial or Technical Corrigendum for TM/AOS SDLP's OID Frame Exception (132.0-B & 732.0-B) - Gilles Moury CNES 3) USLP Green Book Review Friday AM Joint Session with RFM, C&S, and OPT WG's - TBD See separate Joint Meeting Agenda for all of the detailed topics This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone. Please contact the sender if you believe you have received this email in error. QinetiQ may monitor email traffic data and also the content of email for the purposes of security. QinetiQ Limited (Registered in England & Wales: Company Number: 3796233) Registered office: Cody Technology Park, Ively Road, Farnborough, Hampshire, GU14 0LX http://www.qinetiq.com. -------------- next part -------------- An HTML attachment was scrubbed... URL: From greg.j.kazz at jpl.nasa.gov Tue Mar 8 17:13:38 2016 From: greg.j.kazz at jpl.nasa.gov (Kazz, Greg J (312B)) Date: Tue, 8 Mar 2016 17:13:38 +0000 Subject: [Sls-slp] New USLP Documents on SLP CWE Now Message-ID: Dear SLP WG members, Please find the version of the Issues file and the draft USLP White book which we will use at the Cleveland Meeting to discuss USLP in the following URL: http://tinyurl.com/jf9j6u3 Note that both files have today’s date in them: For the draft white book – March 8 Post Telecon 4 For the Issues file – 2016 _3 _08 I plan on issuing a set of meeting minutes for Telecon #4 of the USLP White Book later this week. For Kevan Moore – I have sent you a subscription notice to SLP WG. Please look for it in your email folder. Best regards, Greg Kazz Chairman CCSDS SLP WG -------------- next part -------------- An HTML attachment was scrubbed... URL: From kevan.l.moore at nasa.gov Tue Mar 8 17:14:20 2016 From: kevan.l.moore at nasa.gov (Moore, Kevan L. (MSFC-EO50)[HOSC SERVICES CONTRACT]) Date: Tue, 8 Mar 2016 17:14:20 +0000 Subject: [Sls-slp] RE: New USLP Documents on SLP CWE Now In-Reply-To: References: Message-ID: <86A82FEFF63F844391C5A7290E9F8FE71536400E@NDMSMBX304.ndc.nasa.gov> AH! thank you, greg. it looked like spam and went to my junk folder. i'll happily subscribe now that i know what it was. klm From: Kazz, Greg J (312B) [mailto:greg.j.kazz at jpl.nasa.gov] Sent: Tuesday, March 08, 2016 11:14 AM To: sls-slp at mailman.ccsds.org Cc: Moore, Kevan L. (MSFC-EO50)[HOSC SERVICES CONTRACT] Subject: New USLP Documents on SLP CWE Now Dear SLP WG members, Please find the version of the Issues file and the draft USLP White book which we will use at the Cleveland Meeting to discuss USLP in the following URL: http://tinyurl.com/jf9j6u3 Note that both files have today's date in them: For the draft white book - March 8 Post Telecon 4 For the Issues file - 2016 _3 _08 I plan on issuing a set of meeting minutes for Telecon #4 of the USLP White Book later this week. For Kevan Moore - I have sent you a subscription notice to SLP WG. Please look for it in your email folder. 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 Mar 8 18:06:05 2016 From: greg.j.kazz at jpl.nasa.gov (Kazz, Greg J (312B)) Date: Tue, 8 Mar 2016 18:06:05 +0000 Subject: [Sls-slp] March 8 Telecon #4 Meeting Minutes now on CWE Message-ID: Dear SLP WG, Please find the minutes of USLP Draft White Book Telecon #4 on the CWE under the following URL: http://tinyurl.com/jf9j6u3 The filename is: USLP Telecon 4 minutes March 08_2016 Best regards, Greg -------------- next part -------------- An HTML attachment was scrubbed... URL: From Gian.Paolo.Calzolari at esa.int Wed Mar 9 10:54:28 2016 From: Gian.Paolo.Calzolari at esa.int (Gian.Paolo.Calzolari at esa.int) Date: Wed, 9 Mar 2016 11:54:28 +0100 Subject: [Sls-slp] March 8 Telecon #4 Meeting Minutes now on CWE In-Reply-To: References: Message-ID: <31449_1457520871_56E000E7_31449_236_1_OF7925CBF0.501DDD2F-ONC1257F71.003B55A6-C1257F71.003BEAF7@esa.int> Greg, here attached a copy of the MoMs with a number of remark addressing two purposes: 1) possible improvements to the text of the MoMs 2) open questions or suggestions to be eventually incorporated in the draft USLP book. Sorry for mixing the topics. Regards Gian Paolo From: "Kazz, Greg J (312B)" To: "sls-slp at mailman.ccsds.org" Date: 08/03/2016 19:06 Subject: [Sls-slp] March 8 Telecon #4 Meeting Minutes now on CWE Sent by: sls-slp-bounces at mailman.ccsds.org Dear SLP WG, Please find the minutes of USLP Draft White Book Telecon #4 on the CWE under the following URL: http://tinyurl.com/jf9j6u3 The filename is: USLP Telecon 4 minutes March 08_2016 Best regards, Greg_______________________________________________ Sls-slp mailing list Sls-slp at mailman.ccsds.org http://mailman.ccsds.org/mailman/listinfo/sls-slp This message and any attachments are intended for the use of the addressee or addressees only. The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its content is not permitted. If you received this message in error, please notify the sender and delete it from your system. Emails can be altered and their integrity cannot be guaranteed by the sender. Please consider the environment before printing this email. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: USLP Telecon4_minutes_March08_2016+gpc.pdf Type: application/octet-stream Size: 92309 bytes Desc: not available URL: From Tomaso.deCola at dlr.de Wed Mar 9 13:02:21 2016 From: Tomaso.deCola at dlr.de (Tomaso.deCola at dlr.de) Date: Wed, 9 Mar 2016 13:02:21 +0000 Subject: [Sls-slp] RE: March 8 Telecon #4 Meeting Minutes now on CWE In-Reply-To: References: Message-ID: <1A39DCC13AF3C14B83CD74124D4DCFC3175EDCB3@DLREXMBX01.intra.dlr.de> Greg, Just a clarification about the field transporting the protocol identifiers. In the past weeks, we discussed with Ed, Gian Paolo and Keith about the large space allocated so far (8+5 bits) and somehow agreed that we can simply have 8 bits (256 combinations are enough to account all different protocol and extensions where applicable) and leave the remaining 5 (which help for 32-bits alignment) as reserved. However, I cannot see this point reflected in the current version of the book. If this solution could be implemented in the book, then we could use any of the 5-reseved bits to bring information about the COP stuff, without mixing together COP and proto identifiers in the 8 bits field. Best Regards, 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, March 08, 2016 19:06 To: sls-slp at mailman.ccsds.org Subject: [Sls-slp] March 8 Telecon #4 Meeting Minutes now on CWE Dear SLP WG, Please find the minutes of USLP Draft White Book Telecon #4 on the CWE under the following URL: http://tinyurl.com/jf9j6u3 The filename is: USLP Telecon 4 minutes March 08_2016 Best regards, Greg -------------- next part -------------- An HTML attachment was scrubbed... URL: From greg.j.kazz at jpl.nasa.gov Wed Mar 9 16:18:11 2016 From: greg.j.kazz at jpl.nasa.gov (Kazz, Greg J (312B)) Date: Wed, 9 Mar 2016 16:18:11 +0000 Subject: [Sls-slp] Re: March 8 Telecon #4 Meeting Minutes now on CWE In-Reply-To: <1A39DCC13AF3C14B83CD74124D4DCFC3175EDCB3@DLREXMBX01.intra.dlr.de> References: <1A39DCC13AF3C14B83CD74124D4DCFC3175EDCB3@DLREXMBX01.intra.dlr.de> Message-ID: Tomaso, We heard your suggestions and considered them but we believe that the original suggested 5 bit (32 protocols) was adequate but provided for unexpected growth by providing the signaled inclusion of an additional 255 IDs. Why add a byte when we don’t need it? Of course, this can be discussed further in CLE. Best regards, Greg From: "Tomaso.deCola at dlr.de" > Date: Wednesday, March 9, 2016 at 5:02 AM To: "Kazz, Greg J (313B)" > Cc: "sls-slp at mailman.ccsds.org" > Subject: RE: March 8 Telecon #4 Meeting Minutes now on CWE Greg, Just a clarification about the field transporting the protocol identifiers. In the past weeks, we discussed with Ed, Gian Paolo and Keith about the large space allocated so far (8+5 bits) and somehow agreed that we can simply have 8 bits (256 combinations are enough to account all different protocol and extensions where applicable) and leave the remaining 5 (which help for 32-bits alignment) as reserved. However, I cannot see this point reflected in the current version of the book. If this solution could be implemented in the book, then we could use any of the 5-reseved bits to bring information about the COP stuff, without mixing together COP and proto identifiers in the 8 bits field. Best Regards, 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, March 08, 2016 19:06 To: sls-slp at mailman.ccsds.org Subject: [Sls-slp] March 8 Telecon #4 Meeting Minutes now on CWE Dear SLP WG, Please find the minutes of USLP Draft White Book Telecon #4 on the CWE under the following URL: http://tinyurl.com/jf9j6u3 The filename is: USLP Telecon 4 minutes March 08_2016 Best regards, Greg -------------- next part -------------- An HTML attachment was scrubbed... URL: From greg.j.kazz at jpl.nasa.gov Wed Mar 9 22:02:17 2016 From: greg.j.kazz at jpl.nasa.gov (Kazz, Greg J (312B)) Date: Wed, 9 Mar 2016 22:02:17 +0000 Subject: [Sls-slp] Updated Meeting Minutes to Telecon 4 USLP White Book Message-ID: Dear SLP WG, I updated our meeting minutes. Please find the update attached. Later today, I will load this update to the CWE SLP Area. Best regards, Greg CCSDS Chairman SLP WG -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: USLP Telecon4_minutes_March09_2016_update.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 30199 bytes Desc: USLP Telecon4_minutes_March09_2016_update.docx URL: From greg.j.kazz at jpl.nasa.gov Wed Mar 9 23:34:40 2016 From: greg.j.kazz at jpl.nasa.gov (Kazz, Greg J (312B)) Date: Wed, 9 Mar 2016 23:34:40 +0000 Subject: [Sls-slp] A finer clarification about point 1 in the minutes of Telecon 4 in RED Message-ID: We discussed the new MAP_PDU Service. Perhaps a better name for this service would be MAP_UPDU for upper layer PDU. It allows for the transfer of CCSDS recognized PDUs to be transferred across the USLP Space Data Link. These PDUs are defined in SANA already. Should USLP allow only PDUs that contain a defined length field or should USLP also allow PDUs that do not have a defined length field such as DTN Bundles and LTP Segments (within the spanning rules “000”)?. This capability can be transmitted using rule “001” or MAP-ACCESS Service. After this meeting, I have asked Keith Scott, the SIS Area Director for guidance. He will meet with SLP in Cleveland to discuss options for this. For these types of PDUs the user must chain from one field to the next to sum up the length in order to delimit that kind of PDU. GPC questioned the usefulness of allowing these types of PDUs needing extensive operations for data extraction that could impact performance. For these types of PDUs the encapsulation service remains a user option . Therefore USLP requires that PDUs transferred by this service using rule “000” must be self-delimiting, and have a USLP Protocol ID (UPID) registered by SANA. How the length of the PDU is passed to the USLP API is the subject of Keith Scott’s future discussion at the Cleveland meeting. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: USLP Telecon4_minutes_March09_2016_update.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 30500 bytes Desc: USLP Telecon4_minutes_March09_2016_update.docx URL: From greg.j.kazz at jpl.nasa.gov Thu Mar 10 03:28:50 2016 From: greg.j.kazz at jpl.nasa.gov (Kazz, Greg J (312B)) Date: Thu, 10 Mar 2016 03:28:50 +0000 Subject: [Sls-slp] New update to USLP White Book dated March 9 Message-ID: Dear SLP WG, A slightly new version of the USLP white book based upon the updated comments on Telecon #4 is now in the CWE under the following URL: http://tinyurl.com/jf9j6u3 Look for the file with the date March 9 in the file name: USLP Space Data Link Protocol March 9 Post Telecon 4 Best regards, Greg Kazz CCSDS SLP WG Chairman -------------- next part -------------- An HTML attachment was scrubbed... URL: From Tomaso.deCola at dlr.de Thu Mar 10 08:10:29 2016 From: Tomaso.deCola at dlr.de (Tomaso.deCola at dlr.de) Date: Thu, 10 Mar 2016 08:10:29 +0000 Subject: [Sls-slp] RE: March 8 Telecon #4 Meeting Minutes now on CWE In-Reply-To: References: <1A39DCC13AF3C14B83CD74124D4DCFC3175EDCB3@DLREXMBX01.intra.dlr.de> Message-ID: <1A39DCC13AF3C14B83CD74124D4DCFC3175F0FCE@DLREXMBX01.intra.dlr.de> Greg, Actually I don't ask to add 1 byte but to make a more efficient use of the 5+8 bits, which are defined at the moment to protocol information and possible extensions. What I personally don't like much is the fact that we'll have a field where we'll be mixing together protocol identifier and COP signaling indication (as also pointed out by Gian Paolo), which should instead go separated in my view. I'd indeed appreciate if you could add these points in the Cleveland agenda, so that we can reach an easy and quick agreement on how to proceed with this. Best Regards, 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, March 09, 2016 17:18 To: Cola, Tomaso de Cc: sls-slp at mailman.ccsds.org Subject: Re: March 8 Telecon #4 Meeting Minutes now on CWE Tomaso, We heard your suggestions and considered them but we believe that the original suggested 5 bit (32 protocols) was adequate but provided for unexpected growth by providing the signaled inclusion of an additional 255 IDs. Why add a byte when we don't need it? Of course, this can be discussed further in CLE. Best regards, Greg From: "Tomaso.deCola at dlr.de" > Date: Wednesday, March 9, 2016 at 5:02 AM To: "Kazz, Greg J (313B)" > Cc: "sls-slp at mailman.ccsds.org" > Subject: RE: March 8 Telecon #4 Meeting Minutes now on CWE Greg, Just a clarification about the field transporting the protocol identifiers. In the past weeks, we discussed with Ed, Gian Paolo and Keith about the large space allocated so far (8+5 bits) and somehow agreed that we can simply have 8 bits (256 combinations are enough to account all different protocol and extensions where applicable) and leave the remaining 5 (which help for 32-bits alignment) as reserved. However, I cannot see this point reflected in the current version of the book. If this solution could be implemented in the book, then we could use any of the 5-reseved bits to bring information about the COP stuff, without mixing together COP and proto identifiers in the 8 bits field. Best Regards, 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, March 08, 2016 19:06 To: sls-slp at mailman.ccsds.org Subject: [Sls-slp] March 8 Telecon #4 Meeting Minutes now on CWE Dear SLP WG, Please find the minutes of USLP Draft White Book Telecon #4 on the CWE under the following URL: http://tinyurl.com/jf9j6u3 The filename is: USLP Telecon 4 minutes March 08_2016 Best regards, Greg -------------- next part -------------- An HTML attachment was scrubbed... URL: From Gian.Paolo.Calzolari at esa.int Thu Mar 10 08:36:45 2016 From: Gian.Paolo.Calzolari at esa.int (Gian.Paolo.Calzolari at esa.int) Date: Thu, 10 Mar 2016 09:36:45 +0100 Subject: [Sls-slp] COP-1 with mixed protocols - RE: March 8 Telecon #4 Meeting Minutes now on CWE In-Reply-To: <1A39DCC13AF3C14B83CD74124D4DCFC3175F0FCE@DLREXMBX01.intra.dlr.de> References: <1A39DCC13AF3C14B83CD74124D4DCFC3175EDCB3@DLREXMBX01.intra.dlr.de> <1A39DCC13AF3C14B83CD74124D4DCFC3175F0FCE@DLREXMBX01.intra.dlr.de> Message-ID: <28167_1457599008_56E13220_28167_985_1_OF0A7D0890.C0FB39B4-ONC1257F72.002DAB04-C1257F72.002F4F69@esa.int> Greg, with respect to the COPs I think we need some discussion in Cleveland at least to fix some ideas/decisions. In addition to what Tomaso asks, we may want to point out about COP-1 usage vs. protocols. Clearly the CLCW has a 6 bits VC identifier to it can report about data received either within a TC frame or via a USLP Frame as both of them have the same size VC identifier. In other words it is possible to have a link with TC Frames in Uplink and USLP Frames in downlink as well as having a link with USLP Frames in both directions. This may need to be verified, agreed and spelled out in the document. Another point is that it looks as USLP Managed Parametrs have nothing about usage with Proximity-1 and COP-P. This is clearly an inheratanche from the fact that Proximity-1 unfortunately has no (formal) section for Managed Parameters. STill there is the need of importing/defining some USLP managed parameter for usage with Proximity-1 and COP-P (e.g. PLCW_Repeat_Interval, PLCW Timer, etc.). I fear this task may be a little more complex to the "catch all" nature of Proximity-1 SDLP book and an action may need to be assigned and, at the very extreme, the need for a Magenta may be investigated. In general USLP docs just says: The use of either the COP-1, or COP-P procedures are optional and both are compatible with the USLP. The Protocol Data Units (CLCW for COP-1 and PLCW for COP-P) and operational procedures for both COP-1 and COP-P are not identical but similar and are transparent to USLP. It may be an Annex could clarify how they are supposed to work with USLP. It may a dedicated agenda (sub)point about USLP vs. COPs should be added. Regards Gian Paolo From: To: Cc: sls-slp at mailman.ccsds.org Date: 10/03/2016 09:11 Subject: [Sls-slp] RE: March 8 Telecon #4 Meeting Minutes now on CWE Sent by: sls-slp-bounces at mailman.ccsds.org Greg, Actually I don?t ask to add 1 byte but to make a more efficient use of the 5+8 bits, which are defined at the moment to protocol information and possible extensions. What I personally don?t like much is the fact that we?ll have a field where we?ll be mixing together protocol identifier and COP signaling indication (as also pointed out by Gian Paolo), which should instead go separated in my view. I?d indeed appreciate if you could add these points in the Cleveland agenda, so that we can reach an easy and quick agreement on how to proceed with this. Best Regards, 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, March 09, 2016 17:18 To: Cola, Tomaso de Cc: sls-slp at mailman.ccsds.org Subject: Re: March 8 Telecon #4 Meeting Minutes now on CWE Tomaso, We heard your suggestions and considered them but we believe that the original suggested 5 bit (32 protocols) was adequate but provided for unexpected growth by providing the signaled inclusion of an additional 255 IDs. Why add a byte when we don?t need it? Of course, this can be discussed further in CLE. Best regards, Greg From: "Tomaso.deCola at dlr.de" Date: Wednesday, March 9, 2016 at 5:02 AM To: "Kazz, Greg J (313B)" Cc: "sls-slp at mailman.ccsds.org" Subject: RE: March 8 Telecon #4 Meeting Minutes now on CWE Greg, Just a clarification about the field transporting the protocol identifiers. In the past weeks, we discussed with Ed, Gian Paolo and Keith about the large space allocated so far (8+5 bits) and somehow agreed that we can simply have 8 bits (256 combinations are enough to account all different protocol and extensions where applicable) and leave the remaining 5 (which help for 32-bits alignment) as reserved. However, I cannot see this point reflected in the current version of the book. If this solution could be implemented in the book, then we could use any of the 5-reseved bits to bring information about the COP stuff, without mixing together COP and proto identifiers in the 8 bits field. Best Regards, 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, March 08, 2016 19:06 To: sls-slp at mailman.ccsds.org Subject: [Sls-slp] March 8 Telecon #4 Meeting Minutes now on CWE Dear SLP WG, Please find the minutes of USLP Draft White Book Telecon #4 on the CWE under the following URL: http://tinyurl.com/jf9j6u3 The filename is: USLP Telecon 4 minutes March 08_2016 Best regards, Greg_______________________________________________ Sls-slp mailing list Sls-slp at mailman.ccsds.org http://mailman.ccsds.org/mailman/listinfo/sls-slp This message and any attachments are intended for the use of the addressee or addressees only. The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its content is not permitted. If you received this message in error, please notify the sender and delete it from your system. Emails can be altered and their integrity cannot be guaranteed by the sender. Please consider the environment before printing this email. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Gian.Paolo.Calzolari at esa.int Thu Mar 10 13:16:16 2016 From: Gian.Paolo.Calzolari at esa.int (Gian.Paolo.Calzolari at esa.int) Date: Thu, 10 Mar 2016 14:16:16 +0100 Subject: [Sls-slp] USLP Issue 8 - COP Management Message-ID: <25674_1457615780_56E173A4_25674_59_1_OF50275891.B165F0DB-ONC1257F72.0034007D-C1257F72.0048E66A@esa.int> Greg, I would like to come back on a minor point about USLP Issue 8 - COP Management as reported in the snapshot. I still agree that the details of COP Management are defined outside USLP (i.e. COP-1, SLE, Proximity-1), however the USLP capability of interfacing to COPs Management (for COP-1 and for COP-P) has to be in the USLP book as CCSDS 232.0-B-3 TC SDLP includes the capabilities for interfacing to COP-1. Note that the plura is used in "COPs Management" as the interfacing shall be available for both COP-1 and COP-P. Some investigation is likley o be required to check about any possible difference in USLP interfacing to COP-1 or COP-P. With reference to the attached file this means that USLP book (also for consistency with e.g. the TC approach) should at least: 1) similarly to Table 2-1 of TC SDLP, include a row for "COPs Management" in Table 2 1: Summary of Services Provided by USLP Space Data Link Protocol 2) similarly to section 2.2.3.8 of TC SDLP, include a section 2.2.3.x for COPs Management Service. Most likely the text from 2.2.3.8 of TC SDLP may be sufficient with minor additions. 3) similarly to Figure 2-3 of TC SDLP, show the COPs Management Service towards Virtual Channel generation box in USLP Figure 2 5: Internal Organization of Protocol Entity (Sending End) 4) similarly to section 3.9 of TC SDLP, include a section 3.x for COPs Management Service. Most likely this section should be structured as follows (unless the parameters for COP-1 and COP-P are the same) 3.x COPs Management Service 3.x.1 Overview 3.x.2 COP-1 Management Service Parameters 3.x.3 COP-1 Management Service Primitives 3.x.4 COP-P Management Service Parameters 3.x.5 COP-P Management Service Primitives 5) similarly to section 4.3.5 of TC SDLP, include in section 4.2.5 VIRTUAL CHANNEL GENERATION FUNCTION the FOP-(1/P) capability to accept Directives from a COPs Management Service User and update accordingly Figure 4 15: Abstract Model of Virtual Channel Generation Function. 6) similarly to section 4.4.5 of TC SDLP, include in USLP section 4.3.5 VIRTUAL CHANNEL RECEPTION FUNCTION references to COPs/FARMs as appropriate. So it looks as a dedicated (sub)point about USLP vs. COPs and the interfacing to their management service(s) should be added to the SLP agenda for Cleveland. That's all for now. Best regards Gian Paolo This message and any attachments are intended for the use of the addressee or addressees only. The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its content is not permitted. If you received this message in error, please notify the sender and delete it from your system. Emails can be altered and their integrity cannot be guaranteed by the sender. Please consider the environment before printing this email. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 35067 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: COPsManagement.20160310.docx Type: application/octet-stream Size: 474140 bytes Desc: not available URL: From greg.j.kazz at jpl.nasa.gov Mon Mar 14 20:44:23 2016 From: greg.j.kazz at jpl.nasa.gov (Kazz, Greg J (312B)) Date: Mon, 14 Mar 2016 20:44:23 +0000 Subject: [Sls-slp] Re: March 8 Telecon #4 Meeting Minutes now on CWE In-Reply-To: <1A39DCC13AF3C14B83CD74124D4DCFC3175F0FCE@DLREXMBX01.intra.dlr.de> References: <1A39DCC13AF3C14B83CD74124D4DCFC3175EDCB3@DLREXMBX01.intra.dlr.de> <1A39DCC13AF3C14B83CD74124D4DCFC3175F0FCE@DLREXMBX01.intra.dlr.de> Message-ID: Tomaso and All, Yes we need to have futher discussion on this item at the Cleveland meetings. I have asked Keith Scott to attend the SLP meeting and he said he will find some time to do so on Tuesday. In the mean time, take a look at all the applicable USLP PIDs I have found to date in the attached word file. I will also upload this file to the CWE. Best regards, Greg Chairman CCSDS SLP WG From: "Tomaso.deCola at dlr.de" > Date: Thursday, March 10, 2016 at 1:10 AM To: "Kazz, Greg J (313B)" > Cc: "sls-slp at mailman.ccsds.org" > Subject: RE: March 8 Telecon #4 Meeting Minutes now on CWE Greg, Actually I don’t ask to add 1 byte but to make a more efficient use of the 5+8 bits, which are defined at the moment to protocol information and possible extensions. What I personally don’t like much is the fact that we’ll have a field where we’ll be mixing together protocol identifier and COP signaling indication (as also pointed out by Gian Paolo), which should instead go separated in my view. I’d indeed appreciate if you could add these points in the Cleveland agenda, so that we can reach an easy and quick agreement on how to proceed with this. Best Regards, 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, March 09, 2016 17:18 To: Cola, Tomaso de Cc: sls-slp at mailman.ccsds.org Subject: Re: March 8 Telecon #4 Meeting Minutes now on CWE Tomaso, We heard your suggestions and considered them but we believe that the original suggested 5 bit (32 protocols) was adequate but provided for unexpected growth by providing the signaled inclusion of an additional 255 IDs. Why add a byte when we don’t need it? Of course, this can be discussed further in CLE. Best regards, Greg From: "Tomaso.deCola at dlr.de" > Date: Wednesday, March 9, 2016 at 5:02 AM To: "Kazz, Greg J (313B)" > Cc: "sls-slp at mailman.ccsds.org" > Subject: RE: March 8 Telecon #4 Meeting Minutes now on CWE Greg, Just a clarification about the field transporting the protocol identifiers. In the past weeks, we discussed with Ed, Gian Paolo and Keith about the large space allocated so far (8+5 bits) and somehow agreed that we can simply have 8 bits (256 combinations are enough to account all different protocol and extensions where applicable) and leave the remaining 5 (which help for 32-bits alignment) as reserved. However, I cannot see this point reflected in the current version of the book. If this solution could be implemented in the book, then we could use any of the 5-reseved bits to bring information about the COP stuff, without mixing together COP and proto identifiers in the 8 bits field. Best Regards, 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, March 08, 2016 19:06 To: sls-slp at mailman.ccsds.org Subject: [Sls-slp] March 8 Telecon #4 Meeting Minutes now on CWE Dear SLP WG, Please find the minutes of USLP Draft White Book Telecon #4 on the CWE under the following URL: http://tinyurl.com/jf9j6u3 The filename is: USLP Telecon 4 minutes March 08_2016 Best regards, Greg -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: UPIDS2.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 126552 bytes Desc: UPIDS2.docx URL: From greg.j.kazz at jpl.nasa.gov Mon Mar 14 23:15:45 2016 From: greg.j.kazz at jpl.nasa.gov (Kazz, Greg J (312B)) Date: Mon, 14 Mar 2016 23:15:45 +0000 Subject: [Sls-slp] Latest Draft USLP White Book on CWE Message-ID: Dear SLP WG, The latest draft USLP white book is now on the CWE under: http://tinyurl.com/jf9j6u3 The new file name is: USLP Space Data LInk Protocol March 9 post telecon4 Hint: Look for the new file around the middle of the page. Changes made since the last version are: 1. Needed correction for USLP section 4.2.8 ALL FRAMES GENERATION FUNCTION (no multiple frames). 2. Added COPs Management back into the book. 3. Needed correction for USLP section 4.2.8 ALL FRAMES RECEPTION FUNCTION (no multiple frames). 4. Explicitly name the Octet Stream Service consistently VC Octet Stream Service 5. Some minor clean up post telecon 4 Best regards, Greg -------------- next part -------------- An HTML attachment was scrubbed... URL: From greg.j.kazz at jpl.nasa.gov Tue Mar 22 16:29:18 2016 From: greg.j.kazz at jpl.nasa.gov (Kazz, Greg J (312B)) Date: Tue, 22 Mar 2016 16:29:18 +0000 Subject: [Sls-slp] FW: [SLS] FINAL CALL FOR PAPERS - 7th ESA International Workshop on Tracking, Telemetry and Command Systems for Space Applications (TTC) / 13-16 September 2016, ESA/ESTEC In-Reply-To: <1167_1458652757_56F14655_1167_2453_1_OFC6B66ECE.01C3FCDC-ONC1257F7E.00491AE8-C1257F7E.00492C23@esa.int> References: <1167_1458652757_56F14655_1167_2453_1_OFC6B66ECE.01C3FCDC-ONC1257F7E.00491AE8-C1257F7E.00492C23@esa.int> Message-ID: Dear SLP WG, Please consider the workshop below. Best regards, Greg Kazz Chairman CCSDS SLS-SLP WG From: > on behalf of "Gian.Paolo.Calzolari at esa.int" > Date: Tuesday, March 22, 2016 at 6:19 AM To: SLS - Space Link Services Area > Subject: [SLS] FINAL CALL FOR PAPERS - 7th ESA International Workshop on Tracking, Telemetry and Command Systems for Space Applications (TTC) / 13-16 September 2016, ESA/ESTEC In case you want to forward it to your WG. Regards Gian Paolo ----- Forwarded by Gian Paolo Calzolari/esoc/ESA on 22/03/2016 14:18 ----- From: ESA Conference Bureau/estec/ESA To: Date: 22/03/2016 10:12 Subject: FINAL CALL FOR PAPERS - 7th ESA International Workshop on Tracking, Telemetry and Command Systems for Space Applications (TTC) / 13-16 September 2016, ESA/ESTEC Sent by: Eveline van Beekhuizen ________________________________ Dear Colleague, We herewith would like to remind you that the abstract submission deadline for the 7th ESA International Workshop on Tracking, Telemetry and Command Systems for Space Applications (TTC), has been extended to Friday April 1st. Authors are kindly invited to submit their abstracts by using the on-line abstract submission form on the workshop website: http://www.congrexprojects.com/2016-events/16a05/call-for-papers Authors will be notified on the acceptance of their submission by Friday May 6th. For additional information and registration, please also visit the other pages of the workshop website. Should you have any questions, please do not hesitate to contact us. With kind regards, On behalf of the organisers, ESA Conference Bureau T: +31 715658602 E: esa.conference.bureau at esa.int W : http://www.congrexprojects.com/2016-events/16a05/home This message and any attachments are intended for the use of the addressee or addressees only. The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its content is not permitted. If you received this message in error, please notify the sender and delete it from your system. Emails can be altered and their integrity cannot be guaranteed by the sender. Please consider the environment before printing this email. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00002.txt URL: From greg.j.kazz at jpl.nasa.gov Tue Mar 22 17:21:54 2016 From: greg.j.kazz at jpl.nasa.gov (Kazz, Greg J (312B)) Date: Tue, 22 Mar 2016 17:21:54 +0000 Subject: [Sls-slp] Review Copy of USLP Draft White Book for Cleveland Meeting placed on CWE - Please use this version Message-ID: Dear SLP WG, I’ve placed the final review copy for the CCSDS Spring 2016 meeting that we will use in Cleveland now on the CWE. The filename is: USLP Space Data Link Protocol_March21_post_telecon4 The recent changes made from the last version (with the exception of a few clean up comments) can be found in the file called: review of USLP_rationale for_changes_March21_copy The URL is: http://tinyurl.com/jf9j6u3 No more changes will be made to this document until we meet in Cleveland on April 4 and 5. I wish you all a very safe journey and Happy Easter/Happy Purim ! Greg Kazz Chairman SLS-SLP -------------- next part -------------- An HTML attachment was scrubbed... URL: From Gian.Paolo.Calzolari at esa.int Wed Mar 23 07:32:51 2016 From: Gian.Paolo.Calzolari at esa.int (Gian.Paolo.Calzolari at esa.int) Date: Wed, 23 Mar 2016 08:32:51 +0100 Subject: Capability to transfer data either in an asynchronous, synchronous, or periodic fashion: [Sls-slp] Review Copy of USLP Draft White Book for Cleveland Meeting placed on CWE - Please use this version In-Reply-To: References: Message-ID: <27468_1458718373_56F246A5_27468_877_1_OF98211AB3.81B001DA-ONC1257F7F.0027EDBB-C1257F7F.002975DB@esa.int> Greg, I would like to refer to the change in the snapshot. Section 2.2 describes the data transfer services that the USLP Space Data Link Protocol provides to users. In this sense the data are not frames (generated by the protocol sublayer towards the coding sublayer, at sending end) but are the data (packets, etc received .by the protocol sublayer from the upper layer). In fact those services are summarised in Table 2-1. Therefore the reference to frame and codeblock alignment is not appropriate there. In other words if a users decide to use the Virtual Channel Octet Stream Service generating data in Asynchronous [Periodic] mode, that service will remain Asynchronous [Periodic] independently from frame and codeblock alignment. In general I think USLP has no need to mention frame and codeblock alignment anywhere in this document. Best regards and Happy Easter/Happy Purim to everybody. Gian Paolo From: "Kazz, Greg J (312B)" To: "sls-slp at mailman.ccsds.org" Date: 22/03/2016 18:22 Subject: [Sls-slp] Review Copy of USLP Draft White Book for Cleveland Meeting placed on CWE - Please use this version Sent by: sls-slp-bounces at mailman.ccsds.org Dear SLP WG, I?ve placed the final review copy for the CCSDS Spring 2016 meeting that we will use in Cleveland now on the CWE. The filename is: USLP Space Data Link Protocol_March21_post_telecon4 The recent changes made from the last version (with the exception of a few clean up comments) can be found in the file called: review of USLP_rationale for_changes_March21_copy The URL is: http://tinyurl.com/jf9j6u3 No more changes will be made to this document until we meet in Cleveland on April 4 and 5. I wish you all a very safe journey and Happy Easter/Happy Purim ! Greg Kazz Chairman SLS-SLP_______________________________________________ Sls-slp mailing list Sls-slp at mailman.ccsds.org http://mailman.ccsds.org/mailman/listinfo/sls-slp This message and any attachments are intended for the use of the addressee or addressees only. The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its content is not permitted. If you received this message in error, please notify the sender and delete it from your system. Emails can be altered and their integrity cannot be guaranteed by the sender. Please consider the environment before printing this email. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 6625 bytes Desc: not available URL: From edward.greenberg at jpl.nasa.gov Wed Mar 23 14:22:48 2016 From: edward.greenberg at jpl.nasa.gov (Greenberg, Edward (312B)) Date: Wed, 23 Mar 2016 14:22:48 +0000 Subject: Capability to transfer data either in an asynchronous, synchronous, or periodic fashion: [Sls-slp] Review Copy of USLP Draft White Book for Cleveland Meeting placed on CWE - Please use this version In-Reply-To: <27468_1458718373_56F246A5_27468_877_1_OF98211AB3.81B001DA-ONC1257F7F.0027EDBB-C1257F7F.002975DB@esa.int> References: <27468_1458718373_56F246A5_27468_877_1_OF98211AB3.81B001DA-ONC1257F7F.0027EDBB-C1257F7F.002975DB@esa.int> Message-ID: <4EF9F303214ADB458948F9AD7A608EB31BE6E521@ap-embx-sp30.RES.AD.JPL> It relies on frame delivery From: sls-slp-bounces at mailman.ccsds.org [mailto:sls-slp-bounces at mailman.ccsds.org] On Behalf Of Gian.Paolo.Calzolari at esa.int Sent: Wednesday, March 23, 2016 12:33 AM To: Kazz, Greg J (312B) Cc: sls-slp at mailman.ccsds.org Subject: Capability to transfer data either in an asynchronous, synchronous, or periodic fashion: [Sls-slp] Review Copy of USLP Draft White Book for Cleveland Meeting placed on CWE - Please use this version Greg, I would like to refer to the change in the snapshot. [cid:image001.gif at 01D184D4.CB7FAB50] Section 2.2 describes the data transfer services that the USLP Space Data Link Protocol provides to users. In this sense the data are not frames (generated by the protocol sublayer towards the coding sublayer, at sending end) but are the data (packets, etc received .by the protocol sublayer from the upper layer). In fact those services are summarised in Table 2-1. Therefore the reference to frame and codeblock alignment is not appropriate there. In other words if a users decide to use the Virtual Channel Octet Stream Service generating data in Asynchronous [Periodic] mode, that service will remain Asynchronous [Periodic] independently from frame and codeblock alignment. In general I think USLP has no need to mention frame and codeblock alignment anywhere in this document. Best regards and Happy Easter/Happy Purim to everybody. Gian Paolo From: "Kazz, Greg J (312B)" > To: "sls-slp at mailman.ccsds.org" > Date: 22/03/2016 18:22 Subject: [Sls-slp] Review Copy of USLP Draft White Book for Cleveland Meeting placed on CWE - Please use this version Sent by: sls-slp-bounces at mailman.ccsds.org ________________________________ Dear SLP WG, I've placed the final review copy for the CCSDS Spring 2016 meeting that we will use in Cleveland now on the CWE. The filename is: USLP Space Data Link Protocol_March21_post_telecon4 The recent changes made from the last version (with the exception of a few clean up comments) can be found in the file called: review of USLP_rationale for_changes_March21_copy The URL is: http://tinyurl.com/jf9j6u3 No more changes will be made to this document until we meet in Cleveland on April 4 and 5. I wish you all a very safe journey and Happy Easter/Happy Purim ! Greg Kazz Chairman SLS-SLP_______________________________________________ Sls-slp mailing list Sls-slp at mailman.ccsds.org http://mailman.ccsds.org/mailman/listinfo/sls-slp This message and any attachments are intended for the use of the addressee or addressees only. The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its content is not permitted. If you received this message in error, please notify the sender and delete it from your system. Emails can be altered and their integrity cannot be guaranteed by the sender. Please consider the environment before printing this email. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 6625 bytes Desc: image001.gif URL: