From greg.j.kazz at jpl.nasa.gov Tue May 3 16:50:01 2011 From: greg.j.kazz at jpl.nasa.gov (Kazz, Greg J (313B)) Date: Tue, 3 May 2011 09:50:01 -0700 Subject: [Sls-slp] FW: Proximity-1 Timing Services comments from Gian Paolo Calzolari In-Reply-To: Message-ID: Dear SLS-SLP WG, Below please find comments from Gian Paolo on Prox-1 Data Link Section 5 Timing Services. We will be reviewing the entire Prox-1 Data Link Layer book during our Berlin meeting including this section as well. Please let me know if you have any responses to these comments below Thanks and best regards, Greg Kazz Chairman SLS-SLP WG From: "Gian.Paolo.Calzolari at esa.int" > Date: Tue, 3 May 2011 07:57:20 -0700 To: "Kazz, Greg J (313B)" > Cc: Marjorie de Lande Long > Subject: Proximity-1 Timing Services Greg, As you know the current CCSDS 211.0-B-4 July 2006 Proximity-1 DLL Blue Book contains a Section 5 titled PROXIMITY-1 TIMING SERVICES containing two subsections: 5.1 COUPLED NON-COHERENT PROXIMITY TIMING SERVICE and 5.2 PROXIMITY TIME CORRELATION. Comparing the blue book in force with your latest file “CCSDS_211.0-B-4_Apr20_2011_GJK.doc” there are no changes apart from a typo (course --> coarse). I think this section deserves some clarification despite we are doing a good work with the clarifications that will go into the Proximity-1 C&S Book. See the items below. Regards Gian Paolo --------------------------- #1 I think that clause 5.1.1 is not really a normative clause (it says: Timing Services are required for Proximity operations in order to provide the following three capabilities........) but just an informative preamble. There is no "shall formulation" and no one of the 3 listed capabilities is "fully" specified in the document. The same could be said for clause 5.1.2 (it says: All three of these capabilities require that MODEis active and.....) as I think that requirements on the MODE setting are elsewhere. Recommendation: transform section 5.1 into a non normative section titled e.g. OVERVIEW. --------------------------- #2 Following the suggestion #1 above, the current section 5.2.1 OVERVIEW could be embedded into 5.1 as it continues the description. --------------------------- #3 The first sentence of 5.2.1 OVERVIEW (i.e.: "The method requires that both the initiating and recipient transceiver shall have the capability of time tagging the trailing edge of the last bit of the Attached Synchronization Marker of every incoming and every outgoing Proximity frame.") should be modified removing "shall" (i.e. From " transceiver shall have" To " transceiver have". In fact shall can only be in normative sections. --------------------------- #4 Steps a) to c) in in 5.2.2 TIME TAG CAPTURE METHOD are fine with me. Step d) is unverifiable and not fully specified in this document. The "Proximity time correlation packet" is undefined in this document (despite it deserves also an acronym TCP). The processing of "Proximity time correlation packet" is undefined in this document. Recommendation: convert step d) into descriptive statements specifying that the further processing is not defined in this document. --------------------------- #5 Remove from Annex E the acronym TCP = Time Correlation Packet It is never used. It is likely to create confusion with e.g. TCP/IP if used. --------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: From MCOSBY at qinetiq.com Thu May 5 08:45:43 2011 From: MCOSBY at qinetiq.com (Cosby Matthew) Date: Thu, 5 May 2011 09:45:43 +0100 Subject: [Sls-slp] Presentation Hail Issues for Prox-1 Message-ID: <130458515579513712@towy> All, During the last few months we have been developing the ExoMars transceiver with the requirement that it has to support multiple Orbiters (ExoMars Orbiter, MRO, Maven, and MEx). As a result of this work we believe that we have identified an issue with sequence control numbers between passes of the different Orbiters. I have put this is a presentation and uploaded this on CWE (here - http://tinyurl.com/5sztudv ). The proposed changes to the Prox-1 standard are also on the CWE (here - http://tinyurl.com/6len34j). I will present this during the 5-year review of Prox-1 Data Link Layer Protocol in the Space Link Working group meeting. I welcome any comments before the meeting - I am on leave next week, so I should pick them up the day before I leave for Berlin. Cheers, Matt. Matthew Cosby Communications Engineering, Space Manpower Tel: 01252 396313 email: mcosby at QinetiQ.com www.QinetiQ.com QinetiQ - Delivering customer-focused solutions Please consider the environment before printing this email. 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 Thu May 5 16:47:57 2011 From: greg.j.kazz at jpl.nasa.gov (Kazz, Greg J (313B)) Date: Thu, 5 May 2011 09:47:57 -0700 Subject: [Sls-slp] FW: [Sls-ngu] SDLS presentation on link layer protocol compatibility In-Reply-To: Message-ID: Dear SLP WG, Please note that the following presentation – will be given in the NGU WG meeting – it is relevant to the task of the SLP WG – please see below. Best regards, Greg Kazz Chairman SLP WG From: "Kazz, Greg J (313B)" > Date: Thu, 5 May 2011 09:00:55 -0700 To: "sls-ngu at mailman.ccsds.org" > Subject: [Sls-ngu] SDLS presentation on link layer protocol compatibility Dear NGU, Gilles Moury's presentation on the Compatibility of Space Data Lin Security protocol with TC, TM, AOS Space Data Link Protocols is now in the NGU CWE under the URL: http://tinyurl.com/4k9ryfw Gilles will give his presentation in the NGU WG meeting during the Monday May 16 AM session. Please review it beforehand! Best regards, Greg Kazz Chairman SLS-NGU WG Space Data Link Security Protocol Compatibility of Space Data Link Security protocol with TC, TM, AOSSpace Data Link Protocols -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: From greg.j.kazz at jpl.nasa.gov Thu May 5 22:27:13 2011 From: greg.j.kazz at jpl.nasa.gov (Kazz, Greg J (313B)) Date: Thu, 5 May 2011 15:27:13 -0700 Subject: [Sls-slp] Reformulation of Section 5 Prox-1 Timing Services Message-ID: All, Please review the following NASA proposal to reformulate Sec 5: Prox-1 Timing Services in the Prox-1 Data Link Layer Specification as part of the 5-year review effort. This will also be uploaded to the SLP CWE. Your comments are welcome. Best regards, Greg Kazz Chairman SLS-SLP WG -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: New_Prox1_Timing_Service_Section-NASA.docx Type: application/x-msword Size: 130805 bytes Desc: New_Prox1_Timing_Service_Section-NASA.docx URL: From greg.j.kazz at jpl.nasa.gov Mon May 16 19:48:29 2011 From: greg.j.kazz at jpl.nasa.gov (Kazz, Greg J (313B)) Date: Mon, 16 May 2011 12:48:29 -0700 Subject: [Sls-slp] Prox-2 Viewgraphs Message-ID: Dear SLPers, Please see the attached viewgraphs for discussion tomorrow in SLS-SLP WG on Proximity-2 proposed capabilities. Also now loaded onto the CWE. Best regards, Greg -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Proximity-2a.ppt Type: application/x-mspowerpoint Size: 112640 bytes Desc: Proximity-2a.ppt URL: