From greg.j.kazz at jpl.nasa.gov Mon Aug 1 15:56:07 2005 From: greg.j.kazz at jpl.nasa.gov (Greg Kazz) Date: Mon, 01 Aug 2005 08:56:07 -0700 Subject: [Sls-slp] Fwd: [SLS-CC] CCSDS Fall 2005 Meeting Registration is Now Open Message-ID: <6.2.0.14.2.20050801085542.02d26e78@mail.jpl.nasa.gov> >Dear SLS-SLPers, > Registration for the CCSDS Fall 2005 Meetings is now open! > >In cooperation with the Object Management Group (OMG), the CCSDS Fall 2005 >Meetings will take place from September 12 – 16, in Atlanta, Georgiaat the >following meeting location: > > >Sheraton Atlanta Hotel >1165 Courtland Street >AtlantaGeorgia30303 >Tel: + 1 800 833 8624 >Fax: +1 404 681 5306 > > >Please note that hotel room registration at the Sheraton ends on Monday, >August 22, 2005. Reservations made after this date will be made subject >to availability. Please visit >http://public.ccsds.org/meetings/2005Fall/2005FallLogistics.aspx >for more information. > >CCSDS Meeting Registration > >To register for CCSDS Meetings, please visit the main meeting registration >page located on the CCSDS web site at >http://public.ccsds.org/meetings/2005Fall/default.aspx . Also visit this >page to access the latest scheduled meetings information for each day, >agendas for individual meetings (when available), logistics information, >and a list of registered participants (requires log in). > >Tech Support > >The registration system is optimized for following browsers: > >IBM/PC >- Microsoft Internet Explorer 5.01 or later, plus the latest service packs >- Netscape Navigator 6.2 or later > >MAC >- Internet Explorer 5.2 for Mac OS X, plus the latest service pack >- Netscape Navigator 6.2 for Mac or later > >- Firefox 1.0 or greater > >- Mozilla 1.7 for Mac or later > > > >UNIX >- Netscape Navigator 6.2 for UNIX or later > >If you experience technical difficulty completing your registration, >please contact Brian Oliver at >brian.oliver at btas.com . If you need to make >changes to your registration information once you have registered through >the system, please contact Marco Bovo at marco.bovo at btas.com for >assistance. If you have general questions or would like to request >access to the CCSDS logo suite, please contact Penelope Walz at >penelope.walz at btas.com . > >Please note that the CESG is scheduled to meet in Atlanta, from September >19 – 20, 2005. The CCSDS Management Council and ISO TC20 / SC 13 are >currently scheduled to meet in Washington, D.C., from October 25 – 28, 2005. > > > >Thank you for your participation. > > > >Best regards, > >The CCSDS Secretariat Support Team From greg.j.kazz at jpl.nasa.gov Thu Aug 18 16:37:08 2005 From: greg.j.kazz at jpl.nasa.gov (Greg Kazz) Date: Thu, 18 Aug 2005 09:37:08 -0700 Subject: [Sls-slp] SLS-SLP files moved from CCSDS Docushare to CCSDS CWE Message-ID: <6.2.0.14.2.20050818093440.02d521b0@mail.jpl.nasa.gov> All, As Gian-Paolo points out below, all CCSDS docushare files have been moved to the CWE area. This includes the files concerning SLS-SLP as well. best regards, Greg Kazz Chairman CCSDS SLS-SLP, Prox-1-Build-2 WG High Rate Uplink BOF, IP over CCSDS Links BOF >Date: Thu, 18 Aug 2005 16:50:28 +0200 >From: Gian.Paolo.Calzolari at esa.int >Subject: [SLS-CC] Our stuff moved from CCSDS Docushare to CCSDS CWE >To: SLS Channel Coding Working Groups >Cc: Brian Oliver , > "Walz Penelope (BTAS)" , > "Bovo Marco (BTAS)" , Jean-Luc.Gerner at esa.int, > Gilles Moury , Pen-Shu Yeh > , > "Greg J. Kazz" , Enrico.Vassallo at esa.int >X-Mailer: Lotus Notes Release 5.0.10 March 22, 2002 >X-MIMETrack: Serialize by Router on esocmta1/esoc/ESA at 08/18/2005 16:50:15, > Serialize complete at 08/18/2005 16:50:15 >X-Source-IP: esacom89-ext.esoc.esa.int [131.176.86.4] >X-Source-Sender: Gian.Paolo.Calzolari at esa.int >X-JPL-spam-score: 0.00% >Original-recipient: rfc822;gkazz at mail.jpl.nasa.gov > > >Dear All, > please be informed that CCSDS Secretariat has moved all of the > files from the Space Link Coding and Synchronization WG in DocuShare to > the Space Link Coding and Synchronization WG CWE Website. The files can > be found in the Private and Public Document Libraries. > >This is happening as per CMC Action Item: CMC-A-0504-011 / CMC-R-0504-008 >The Secretariat will migrate all documents currently stored on DocuShare >into a corresponding storage and retrieval structure within the >Collaborative Work Environment and alert the CESG of the CMC's intention >to decommit the Docushare capability. Assignee: CCSDS Secretariat > > Note that CWE requires your login. >If you do not have an allowed user name, please send me a note with copy >to ccsdstechsupport at ccsds.org and Brian Oliver . > >Best regards > >Gian Paolo Calzolari >SLS-CC Chair > >PS The following CWE areas are availe for the WG's/BOF's under SLS-CC: > >Space Link Coding and Synchronization >WG >http://public.ccsds.org/sites/cwe/sls-slcs/Private.aspx > >Telecommand Channel Coding >WG >http://public.ccsds.org/sites/cwe/sls-tcc/Private.aspx > >Long Erasure Codes >BOF >http://public.ccsds.org/sites/cwe/sls-lec/Private.aspx > >New Codes >BOF >http://public.ccsds.org/sites/cwe/sls-nc/Private.aspx > From greg.j.kazz at jpl.nasa.gov Tue Aug 23 19:42:25 2005 From: greg.j.kazz at jpl.nasa.gov (Greg Kazz) Date: Tue, 23 Aug 2005 12:42:25 -0700 Subject: [Sls-slp] Fwd: Re: RIDs to Encapsulation Service Red Book Message-ID: <6.2.0.14.2.20050823122745.02e56c28@mail.jpl.nasa.gov> Marjorie & SLS-SLP members, Thank you for your expanded comments. I forgot about the existing definitions in the soon to be converted to Silver:Historical Status books which include: TM, TC, and AOS (Annex C). Thanks for pointing this out. I am not aware of any space agencies including NASA that use the Encapsulation Packet. Nevertheless, I agree that it makes sense to add the comments you suggested to both the Encapsulation Service Red Book pink sheets as well as table 7-6 in the Space Link Identifiers book - making the user aware of the differences between the old encapsulation packet header format and the new format (if approved). best regards, Greg >Date: Tue, 23 Aug 2005 14:59:45 +0200 >From: Marjorie de Lande Long >Subject: Re: RIDs to Encapsulation Service Red Book >To: Greg Kazz >Cc: Gian.Paolo.Calzolari at esa.int, Enrico.Vassallo at esa.int, > Gilles.Moury at cnes.fr, Jean-Luc.Gerner at esa.int, pen-shu.yeh at gsfc.nasa.gov >Reply-to: marjorie at delandelong.com >User-Agent: KMail/1.6.1 >X-Source-IP: plus44.host4u.net [69.94.105.172] (may be forged) >X-Source-Sender: marjorie at delandelong.com >X-JPL-spam-score: 0.00% >Original-recipient: rfc822;gkazz at mail.jpl.nasa.gov > >Greg, > >With reference to the RID for 133.1-R-3 (Encapsulation Service), here is an >explanation of what I meant by "incompatible". > >Consider the receiving end of the Packet Service of the TM Space Data Link >Protocol (132.0-B-1): >- the First Header Pointer indicates the start of a Packet >- the first 3 bits are the PVN >- if the PVN contains '111', this is an Encapsulation Packet >- look at the 2 bits of the Length of Length field >- if the Length of Length contains the value '10', then > * by the definition in 102.0-B-5, the length field for the packet > is in >octets 1 and 2 of the packet > * by the definition in 133.1-R-3, the length field for the packet > is in >octets 2 and 3 of the packet >- if the Length of Length contains the value '11', then > * by the definition in 102.0-B-5, the length field for the packet > is in >octets 1 to 5 of the packet > * by the definition in 133.1-R-3, the length field for the packet > is in >octets 4 to 7 of the packet > >The receiving end of the Packet Service needs the length field of a packet in >order to determine how much data belongs to the packet, and in order to find >the start of the packet header for the next packet. When the Packet Service >at the receiving end finds a packet with PVN of '111', the position of the >length field is uncertain. Thus the definitions in 102.0-B-5 and 133.1-R-3 >are incompatible. > >(Note that the problem is not confined to the Packet Service of the TM Space >Data Link Protocol. The TC Space Data Link Protocol is affected too, if >blocking is in use. Also, an implementation of a protocol service in a higher >layer, which extracts the Encapsulated Data Unit from an Encapsulation >Packet, is likely to have similar difficulty with finding the length field >and the start of the Encapsulated Data Unit.) > >As a result of the incompatible definitions, an implementation of the Packet >Service at the receiving end needs to "know" which definition applies for a >particular virtual channel. So a solution to the problem exists, as long as >people are aware that the problem exists. But it is not difficult to imagine >a cross-support situation where both parties correctly claim to support >packets with PVN '111', but they are unaware that there are using the >different definitions. > >The definition in 102.0-B-5 has the status which comes from being part of a >CCSDS Blue Book since 2000, and it is (was?) also an ISO standard (ISO >13419). Even if the Blue Book is withdrawn by being converted to historical >status, there may be existing systems, implementations, designs, etc. which >follow the definition. (On the CCSDS website today (23. August) 102.0-B-5 is >still listed as a Blue Book. There is also an Encapsulation Packet >definition in 203.0-B-2 (ISO 12174) which is still listed as a Blue Book - it >is the same as the definition in 102.0-B-5.) > >Clearly, CCSDS can change the definition of the Encapsulation Packet to the >new format in 133.1-R-3, but people need to have the change drawn to their >attention. This is what I am suggesting in the RID. I think it would be >helpful for the new Encapsulation Service book to contain statements that: > 1) there is a difference in the definition which is, from the point of view >of implementations, incompatible with the earlier definition, and >2) the new definition replaces the old definition, making the old definition >obsolete. > >It would also be helpful if: >- a note could be added to table 7-6 of 135.0-B-1 (Space Link >Identifiers), to >explain that the packets with PVN '111' exclude the old definition in >102.0-B-5 and 203.0-B-2. >- when 102.0-B-5 and 203.0-B-2 are moved to Silver status on the CCSDS >website, a mention of the different definition could be added to their >website entries. > >Best regards, >Marjorie From greg.j.kazz at jpl.nasa.gov Tue Aug 23 20:04:05 2005 From: greg.j.kazz at jpl.nasa.gov (Greg Kazz) Date: Tue, 23 Aug 2005 13:04:05 -0700 Subject: [Sls-slp] Encapsulation Packet Message-ID: <6.2.0.14.2.20050823130219.02ea3d48@mail.jpl.nasa.gov> Dear SLS-SLPer, Does your space agency currently or plans to use the CCSDS Encapsulation Packet on its missions? Please respond back to me via email. We will discuss changes to the encapsulation packet header at the Fall CCSDS SLS-SLP meeting in Atlanta. thanks, Greg Kazz From greg.j.kazz at jpl.nasa.gov Sat Aug 27 20:53:58 2005 From: greg.j.kazz at jpl.nasa.gov (Greg Kazz) Date: Sat, 27 Aug 2005 13:53:58 -0700 Subject: [Sls-slp] Updated Prox-1 GB available Message-ID: <6.2.0.14.2.20050827134626.02bbc050@mail.jpl.nasa.gov> Dear SLS-SLPers, Please go to http://public.ccsds.org/sites/cwe/sls-slp/default.aspx which is the Public site for the CCSDS SLS-SLP WG on CWE and review the updated Proximity-1 Green Book. In reference [15], this greenbook references the pdf file which evaluates the CCITT-32 and the Proximity-1 32 bit CRC, which also has been uploaded to this directory for reference. Please be ready to discuss the Prox-1 GB at the SLS-SLP WG meeting in Atlanta on Tue. Sept. 13 best regards, Greg Kazz Chairman SLS-SLP WG From greg.j.kazz at jpl.nasa.gov Tue Aug 30 16:03:16 2005 From: greg.j.kazz at jpl.nasa.gov (Greg Kazz) Date: Tue, 30 Aug 2005 09:03:16 -0700 Subject: [Sls-slp] JAXA Response to AOS Pink Sheets Message-ID: <6.2.0.14.2.20050830090118.02b51d38@mail.jpl.nasa.gov> Dear SLS-SLPers, Please review the following response from JAXA regarding the proposed change to the AOS Space Data Link protocol in terms of extending the frame count. Please let me know if you have any comments. thanks, Greg >Date: Tue, 30 Aug 2005 15:52:13 +0900 >From: JAXA CCSDS Secretariat >Subject: [CCSDS] Re: More on AOS Pink Sheets >To: Greg Kazz >Cc: =?ISO-2022-JP?B?GyRCRURPJDRdGyhCIBskQk1NIUobKEI=?= > =?ISO-2022-JP?B?GyRCO3ZMMzZJIUsbKEIg?= , > JAXA CCSDS >User-Agent: Microsoft-Entourage/11.1.0.040913 >X-Source-IP: stone.tksc.jaxa.jp [133.56.11.12] >X-Source-Sender: jaxa.ccsds at jaxa.jp >X-JPL-spam-score: 0.00% >Original-recipient: rfc822;gkazz at mail.jpl.nasa.gov > >Dear Mr. Kazz, > >This is a conclusion from discussions with associates. > >Concerning your response, JAXA cannot agree with your comments, since >many of JAXA LSIs handle M_PDU production process and AOS transfer frame >generation process independently. > >Rationale of the proposed change in WG meeting minutes said that the reason >for this change is due to frame accountability and frame retransmission >especially for high rate telemetry missions utilizing SLE RCF service. >JAXA understands that this proposed change is beneficial to frame >accountability of some high rate telemetry missions. >But JAXA recognizes that the frame accountability in SLE RCF service is >achieved by not just "data-link-continuity" parameter (equivalent to VC >frame count) but also "earth-receive-time" parameter in RCF-TRANSFER-DATA. >If VC Frame Count remains to provide only 16777216 counts, those information >seems enough to eliminate ambiguity of frame count during the pass and to >support frame retransmission needs. > >If those information is not enough for data link frame accountability and VC >frame count should be augmented for high rate telemetry missions, rather >than the proposed change, JAXA would prefer the following alternatives; > >1) To define VC Frame Count Extension on spare bits of signaling field in >AOS Transfer Frame Header as OPTIONAL with an use flag, >or >2) To define augmented VC Frame Count in "High Rate AOS Transfer Frame" >Header having new transfer frame version number (i.e., Version 4). > > >Please take this message into your consideration. > > >Thank you and best regards, > >I. Nohara > >-- >************************************* >*** JAXA CCSDS Secretariat *** >*** +81 29 868 2613 *** >*** +81 29 868 2990 *** >*** JAXA.CCSDS at jaxa.jp *** >************************************* From greg.j.kazz at jpl.nasa.gov Wed Aug 31 16:10:59 2005 From: greg.j.kazz at jpl.nasa.gov (Greg Kazz) Date: Wed, 31 Aug 2005 09:10:59 -0700 Subject: [Sls-slp] Fwd: [CESG] NEW CESG POLL CESG-R0805-003 (SLS-0508-003) Space Packet Protocol Green Book Message-ID: <6.2.0.14.2.20050831090843.027b69d0@mail.jpl.nasa.gov> Dear WG, Please review the comments from ESA on the three Green Books and email me your opinion and comments, if at all possible before the Atlanta meeting. We will discuss this at the SLS-SLP WG meeting in Atlanta. thanks, Greg Kazz Chairman CCSDS SLS-SLP WG >Date: Wed, 31 Aug 2005 15:59:44 +0200 >From: Jean-Luc.Gerner at esa.int >Subject: [CESG] NEW CESG POLL CESG-R0805-003 (SLS-0508-003) Space Packet > Protocol Green Book >To: greg.kazz%jpl.nasa.gov%ESA at estec.esa.int >Cc: Enrico.Vassallo at esa.int, Gian.Paolo.Calzolari at esa.int, > greg.kazz%jpl.nasa.gov%ESA at estec.esa.int, > pen-shu.yeh%gsfc.nasa.gov%ESA at estec.esa.int, > Gilles.Moury%cnes.fr%ESA at estec.esa.int, Jean-Francois.Kaufeler at esa.int, > Nestor.Peccia at esa.int >X-Mailer: Lotus Notes Release 5.0.10 March 22, 2002 >X-MIMETrack: Serialize by Router on estecmta1/estec/ESA(Release 5.0.11 |July > 24, 2002) at 31/08/2005 03:59:47 PM >X-Source-IP: esacom57-ext.estec.esa.int [131.176.107.4] >X-Source-Sender: Jean-Luc.Gerner at esa.int >X-JPL-spam-score: 0.00% >Original-recipient: rfc822;gkazz at mail.jpl.nasa.gov > >Greg, > >Here attached are the comments which were produced (together with the >disapproval) on these three GBs currently under CESG poll for approval prior >to publication. >(See attached file: Comments to Space Link Protocols GBs.doc) >When reviewed by networking specialists, it appeared that they deserve >improvements to render them more clear. Also some concepts are not defined as >in ISO and are ambiguous.Most important is that independence between layers >does not seem to be ensured. >The comments I am sending are only a subset of all the comments which were >made and I suggest that an exhaustive review of these documents be made. > >I understand that some of these remarks do affect the corresponding BBs. So, >the purpose of rejecting their publication is to raise awareness on the issue >and decide within the area on the best way to proceed. First thing is >obviously to measure how far, when and how should the change process go given >the need for some backward compatibility. > >Let me know of your opinion. > >Jean-Luc Gerner >TEC-ETT >Tel: +31 71 565 4473 >----- Forwarded by Jean-Luc Gerner/estec/ESA on 31/08/2005 15:38 ----- > > > "Adrian J. > Hooke" > > Engineering Steering Group - ADs > .nasa.gov> cc: > > Sent by: Subject: [CESG] NEW > CESG POLL CESG-R0805-003 (SLS-0508-003) Space Packet Protocol > cesg-bounces at mailma Green > Book > n.ccsds.org > > > > > > 26/08/2005 > 16:00 > > > > > > > > > >RESOLUTION CESG-R0805-003 (SLS-0508-003) Approval of Space Packet Protocol >Green Book > >The Space Link Services Area, > >CONSIDERING that the Space Link Protocols Working Group has reviewed and >approved the technical contents of the draft Green Book concerning Space >Packet Protocol, > >RECOMMENDS that the document be approved for publication as an issue-1 >Informational Report, CCSDS 130.3-G-1. > >Attachment: 130x3g04[Approval].pdf > >- - - - - - - - > >Accordingly, a poll has been set up for CESG voting as follows: > >Shall the document Space Packet Protocol be approved for publication as an >issue-1 Informational Report, CCSDS 130.3-G-1. >Attachment: 130x3g04[Approval].pdf > >Responses: >ABSTAIN (does not affect my Area) >APPROVE UNCONDITIONALLY >APPROVE WITH CONDITIONS (state conditions that must be satisfied) >DISAPPROVE WITH COMMENT (state detailed reasons for disapproval) >NO VOTE CAST (automatic approval by my Area) > >Open: 26 August2005 >Close: 09 September 2005 >- - - - - - - - > >PLEASE CAST YOUR VOTE AS FOLLOWS. > >CESG Approval Poll: > >http://public.ccsds.org/sites/cwe/cesg/polls/default.aspx > >Poll: > >RESOLUTION CESG-R0805-003 (SLS-0508-003) Approval of Space Packet Protocol >Green Book - (Series Items) > >You will need to click the CWE "Sign In" button located at the top right of >the page and provide your log-in information. Should you require log-in >assistance, please click on "Help" located at the top left of the page. > >Best regards >Adrian > >Adrian J. Hooke >Chairman, CCSDS Engineering Steering Group (CESG) >_______________________________________________ >CESG mailing list >CESG at mailman.ccsds.org >http://mailman.ccsds.org/mailman/listinfo/cesg > >----- Forwarded by Jean-Luc Gerner/estec/ESA on 31/08/2005 15:38 ----- > > > "Adrian J. > Hooke" > > Engineering Steering Group - ADs > .nasa.gov> cc: > > Sent by: Subject: [CESG] NEW > CESG POLL CESG-R0805-001 (SLS-0508-001): Overview, Space Link > cesg-bounces at mailma Protocols > > n.ccsds.org > > > > > > 26/08/2005 > 16:00 > > > > > > > > > >RESOLUTION CESG-R0805-001 (SLS-0508-001) Approval of updated Overview of >Space Link Protocols Green Book > >The Space Link Services Area Director, > >CONSIDERING that the Space Link Protocols Working Group has reviewed and >approved the technical contents of the draft update to Overview of Space Link >Protocols, > >RECOMMENDS that the document be approved for publication as an issue-2 >Informational Report, CCSDS 130.0-G-2. > >Attachment: 130x0g13[Approval].pdf > >- - - - - - - - > >Accordingly, a poll has been set up for CESG voting as follows: > >Shall the document Overview of Space Link Protocols, be approved for >publication as an issue-2 Informational Report, CCSDS 130.0-G-2. >Responses: >ABSTAIN (does not affect my Area) >APPROVE UNCONDITIONALLY >APPROVE WITH CONDITIONS (state conditions that must be satisfied) >DISAPPROVE WITH COMMENT (state detailed reasons for disapproval) >NO VOTE CAST (automatic approval by my Area) > >Open: 26 August 2005 >Close: 09 September 2005 >- - - - - - - - > >PLEASE CAST YOUR VOTE AS FOLLOWS. > >CESG Approval Poll: > >http://public.ccsds.org/sites/cwe/cesg/polls/default.aspx > >Poll: > >RESOLUTION CESG-R0805-001(SLS-0508-001) Approval of updated Overview of Space >Link Protocols Green Book - (Series Items) > >You will need to click the CWE "Sign In" button located at the top right of >the page and provide your log-in information. Should you require log-in >assistance, please click on "Help" located at the top left of the page. > >Best regards >Adrian > >Adrian J. Hooke >Chairman, CCSDS Engineering Steering Group (CESG) >_______________________________________________ >CESG mailing list >CESG at mailman.ccsds.org >http://mailman.ccsds.org/mailman/listinfo/cesg > >----- Forwarded by Jean-Luc Gerner/estec/ESA on 31/08/2005 15:38 ----- > > > "Adrian J. > Hooke" > > Engineering Steering Group - ADs > .nasa.gov> cc: > > Sent by: Subject: [CESG] NEW > CESG POLL CESG-R0805-002 (SLS-0508-002): Space Data Link > cesg-bounces at mailma Protocols > > n.ccsds.org > > > > > > 26/08/2005 > 15:59 > > > > > > > > > >RESOLUTION CESG-R0805-002 (SLS-0508-002) Approval of Space Data Link >Protocols Green Book > >The Space Link Services Area, > >CONSIDERING that the Space Link Protocols Working Group has reviewed and >approved the technical contents of the draft Green Book concerning Space Data >Link Protocols, > >RECOMMENDS that the document be approved for publication as an issue-1 >Informational Report, CCSDS 130.2-G-1. > >Attachment: 130x2g03[Approval].pdf > >- - - - - - - - > >Accordingly, a poll has been set up for CESG voting as follows: > >Shall the document Space Data Link Protocols be approved for publication as >an issue-1 Informational Report, CCSDS 130.2-G-1. > >Responses: >ABSTAIN (does not affect my Area) >APPROVE UNCONDITIONALLY >APPROVE WITH CONDITIONS (state conditions that must be satisfied) >DISAPPROVE WITH COMMENT (state detailed reasons for disapproval) >NO VOTE CAST (automatic approval by my Area) > >Open: 26 August2005 >Close: 09 September 2005 > >- - - - - - - - > >PLEASE CAST YOUR VOTE AS FOLLOWS. > >CESG Approval Poll: > >http://public.ccsds.org/sites/cwe/cesg/polls/default.aspx > >Poll: > >RESOLUTION CESG-R0805-002 (SLS-0508-002) Approval of Space Data Link >Protocols Green Book - (Series Items) > >You will need to click the CWE "Sign In" button located at the top right of >the page and provide your log-in information. Should you require log-in >assistance, please click on "Help" located at the top left of the page. > >Best regards >Adrian > >Adrian J. Hooke >Chairman, CCSDS Engineering Steering Group (CESG) > > > > > > >_______________________________________________ >CESG mailing list >CESG at mailman.ccsds.org >http://mailman.ccsds.org/mailman/listinfo/cesg > > -------------- next part -------------- A non-text attachment was scrubbed... Name: Comments to Space Link Protocols GBs.doc Type: application/msword Size: 27136 bytes Desc: not available URL: From greg.j.kazz at jpl.nasa.gov Wed Aug 31 23:10:13 2005 From: greg.j.kazz at jpl.nasa.gov (Greg Kazz) Date: Wed, 31 Aug 2005 16:10:13 -0700 Subject: [Sls-slp] Fwd: Re: Pink Sheet Request for Prox-1 Data Link Message-ID: <6.2.0.14.2.20050831155224.030e7300@mail.jpl.nasa.gov> SLS-SLPers, Attached are the proposed pink sheets in response to RIDs received against 1) Space Link Identifiers Blue Book and 2) Proximity-1 Space Data Link Protocol Blue book. The response to these RIDs are as follows: 1) Space Link Identifiers Additional Note 3 added to p 7-5. If the Encapsulation Packet header is changed as proposed in the Encapsulation Service Pink Sheets, then this note points out not to use the original definition of the encapsulation packet as defined in the soon to become historical link layer specifications. 2) Proximity-1 Data Link Layer a) Update to the ordering of frames in the frame sublayer. NASA/JPL MRO spacecraft in test discovered that the forward link can be starved when there is a large asymmetry in data rates (128:1 and beyond) between the forward and return link. To prevent this, frame ordering now includes a check to see if any data frames need to be transmitted. If so , those frames are shared with PLCW traffic, thus preventing data frame starvation. b) Minor change: PLCW_Repeat MIB parameter is now, PLCW_Repeat_Interval. Which clarifies the functionality c) Event E8 in full duplex session establishment now includes a note that if Carrier_only was received but no data was sent then this event shall be a required notification in the protocol and reported to the vehicle controller subsystem. Same is true for Event E36 in Half-duplex. This situation was discovered in NASA/JPL MRO system test. Please let me know if you have any questions or comments. We will discuss these proposals at the SLS-SLP meeting in Atlanta. best regards, Greg Kazz Chairman CCSDS SLS-SLP WG >Date: Wed, 31 Aug 2005 18:46:41 -0400 >From: Thomas Gannett >Subject: Re: Pink Sheet Request for Prox-1 Data Link >X-Sender: tgannett at mail.us.net >To: Greg Kazz >Cc: ed Greenberg >X-Mailer: QUALCOMM Windows Eudora Version 5.1.1 >X-Source-IP: rwcrmhc13.comcast.net [204.127.198.39] >X-Source-Sender: tgannett at us.net >X-JPL-spam-score: 0.00% > >Greg: > >Attached are proposed change pages for both Space Link Identifiers and >Proximity-1. Since the covers of both books will be changed with the next >issue, I have replaced the covers with a status cover sheet. > >TG > > > -------------- next part -------------- A non-text attachment was scrubbed... Name: 135x0p11a.pdf Type: application/pdf Size: 340344 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 211x0p31a[PROPOSED].pdf Type: application/pdf Size: 334043 bytes Desc: not available URL: From penelope.walz at btas.com Mon Aug 8 21:03:42 2005 From: penelope.walz at btas.com (Walz Penelope (BTAS)) Date: Mon, 08 Aug 2005 21:03:42 -0000 Subject: [Sls-slp] [Ccsds-all] CCSDS Fall 2005 Meeting Registration is Now Open Message-ID: <389C1A32820B4C4A8F3994B435BB98371B9DC8@btas14.BTAS.local> CCSDS FALL 2005 MEETINGS – ATLANTA ► Registration for the CCSDS Fall 2005 Meetings is now open! In cooperation with the Object Management Group (OMG), the CCSDS Fall 2005 Meetings will take place from September 12 – 16, in Atlanta, Georgia at the following meeting location: Sheraton Atlanta Hotel 165 Courtland Street Atlanta Georgia 30303 Tel: + 1 800 833 8624 Fax: +1 404 681 5306 Hotel room registration at the Sheraton closes for this event on Monday, August 22, 2005. Reservations made after this date will be made subject to availability. Please visit http://public.ccsds.org/meetings/2005Fall/2005FallLogistics.aspx for more information. CCSDS Meeting Registration To register for CCSDS Meetings, please visit the main meeting registration page located on the CCSDS web site at http://public.ccsds.org/meetings/2005Fall/default.aspx . Also visit this page to access the latest scheduled meetings information for each day, agendas for individual meetings (when available), logistics information, and a list of registered participants (requires log in). Tech Support The registration system is optimized for following browsers: IBM/PC - Microsoft Internet Explorer 5.01 or later, plus the latest service packs - Netscape Navigator 6.2 or later MAC - Internet Explorer 5.2 for Mac OS X, plus the latest service pack - Netscape Navigator 6.2 for Mac or later - Firefox 1.0 or greater - Mozilla 1.7 for Mac or later UNIX - Netscape Navigator 6.2 for UNIX or later If you experience technical difficulty completing your registration, please contact Brian Oliver at brian.oliver at btas.com . If you need to make changes to your registration information once you have registered through the system, please contact Marco Bovo at marco.bovo at btas.com for assistance. If you have general questions or would like to request access to the CCSDS logo suite, please contact Penelope Walz at penelope.walz at btas.com . Please note that the CESG is scheduled to meet in Atlanta, from September 19 – 20, 2005. The CCSDS Management Council and ISO TC20 / SC 13 are currently scheduled to meet in Washington, D.C., from October 25 – 28, 2005. Thank you for your participation. Best regards, The CCSDS Secretariat Support Team Penelope Wrenn Walz The Consultative Committee for Space Data Systems (CCSDS) CCSDS Secretariat – Public Affairs 6301 Ivy Lane, Ste 720 Greenbelt, MD 20770 USA Tel - +1 301 474 5424 Fax - +1 301 474 5427 Mobile - +1 571 235 1625 (best contact / voicemail) E-mail - penelope.walz at btas.com -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- _______________________________________________ CCSDS-All mailing list CCSDS-All at mailman.ccsds.org http://mailman.ccsds.org/cgi-bin/mailman/listinfo/ccsds-all From pen-shu.yeh-1 at nasa.gov Thu Aug 11 17:44:01 2005 From: pen-shu.yeh-1 at nasa.gov (Pen-Shu Yeh) Date: Thu, 11 Aug 2005 17:44:01 -0000 Subject: [Sls-slp] Re: [Cesg-all] [Ccsds-all] CCSDS PR - Special Delivery: NASA's MESSENGER Sends Flyby Data to Earth Using CFDP In-Reply-To: <389C1A32820B4C4A8F3994B435BB98371B9DD1@btas14.BTAS.local> References: <389C1A32820B4C4A8F3994B435BB98371B9DD1@btas14.BTAS.local> Message-ID: <6.1.2.0.2.20050811130355.01c75d88@pop500.gsfc.nasa.gov> Please also note that the CCSDS.121.0-B-1 (Lossless Data Compression) was implemented on the MLA (Messenger Laser Altimeter) data in S/W by NASA's GSFC. Pen-Shu Yeh Data Compression WG Chair At 02:04 PM 8/9/2005, Walz Penelope \(BTAS\) wrote: >Dear CCSDS Community: > >Today CCSDS Public Affairs began dissemination of a press release entitled >“Special Delivery: NASA’s MESSENGER Sends Flyby Data to Earth Using CCSDS >File Delivery Protocol Developed for Deep Space by International Team” >through international newswire and to targeted media contacts >worldwide. The release should be available to the general public >tomorrow, Aug. 10, but for your convenience, it is attached in .pdf format >and also appears below. > > >Thanks to the following individuals for their input on this release: > > > >- Scott Burleigh, NASA JPL > >- Christopher Krupiarz, JHU APL > >- Kathy Rockwell, NASA JPL > > >If you have any future CCSDS public affairs ideas, please feel free to >send them to me at penelope.walz at btas.com . > >Thank you for your participation and support. > >Best regards, >Penelope W. Walz >The Consultative Committee for Space Data Systems >CCSDS Secretariat Support – Public Affairs >6301 Ivy Lane, Ste 720 >Greenbelt, MD 20770 USA >Tel - +1 301 474 5424 >Fax - +1 301 474 5427 >Mobile (best contact) - +1 571 235 1625 >E-mail - penelope.walz at btas.com > > > >CCSDS Press Release > >Please hold until WED, August 10. > > > >Special Delivery: NASA’s MESSENGER Sends Flyby Data to Earth Using CCSDS >File Delivery Protocol Developed for Deep Space by International Team > > > >WASHINGTON, Aug. 10 (CCSDS) – NASA’s MESSENGER team is using the CCSDS >File Delivery Protocol (CFDP), a highly specialized protocol designed to >overcome space operations communications challenges, to download data >captured during a successful flyby of Earth last week. > >A team of international space data communications experts, collaborating >through the Consultative Committee for Space Data Systems (CCSDS), >developed CFDP to reliably and efficiently downlink files from a >spacecraft even in the strenuous environment of deep space. Since the >MESSENGER spacecraft’s launch a year ago, it has successfully used CFDP to >enable mission communications and will use it throughout its 7.9-billion >kilometer journey to Mercury. > >In using CFDP, MESSENGER communications represents a change in the >standard method of storing science and housekeeping data on spacecraft >built by the Johns Hopkins University Applied Physics Laboratory >(JHU/APL). MESSENGER is also the first U.S. space flight mission to use >CFDP in mission operations. >Prior to MESSENGER, JHU/APL missions used a raw storage model of storing >data, but new mission and operational requirements meant that MESSENGER >would have to incorporate a file system of data storage into its >spacecraft software architecture. A reliable method of downlinking files >to the ground had to be found and CFDP was chosen by mission planners to >do the job. >CFDP is included in the MESSENGER software architecture through a reuse of >a NASA Jet Propulsion Lab (NASA JPL) implementation on the ground and a >JHU/APL “CFDP-lite” implementation on the flight side. The NASA JPL >implementation is also used on NASA’s highly successful Deep Impact mission. >“JHU/APL engineers integrated CFDP software developed by NASA JPL into the >MESSENGER mission's ground system, which communicates with a CFDP flight >software implementation developed by JHU/APL on the spacecraft,” said >Christopher Krupiarz, senior professional staff member, JHU/APL Space >Department Embedded Systems Group in Laurel, Maryland (USA). “Being able >to use an international standard like CFDP was a key factor in getting two >systems developed by two different organizations to work for one Mercury >bound spacecraft.” >CFDP is designed to function reliably despite the long data propagation >delays and frequent, lengthy interruptions in connectivity found in deep >space. It uses powerful forward error correction coding that minimizes >data loss in communication across deep space, and also supports optional >“acknowledged” modes of operation in which data loss is automatically >detected and a retransmission of the lost data is automatically requested. >Some of the world’s leading space communications experts working within >CCSDS collaborated at bi-annual working group sessions (similar to those >scheduled to take place next month in Atlanta, Georgia) to first >standardize CFDP. They defined the protocol according to space file >transfer requirements articulated by CCSDS participating space agencies, >including NASA, the European Space Agency (ESA), the British National >Space Centre (BNSC), the Centre National d'Etudes Spatiales (CNES) and the >Japan Aerospace Exploration Agency (JAXA). The protocol’s ability to >maintain a high level of data transfer reliability even across >interplanetary distances makes it critical to successful communications on >deep space missions like the MESSENGER mission to Mercury and is expected >to have a high level of applicability to future Lunar exploration missions. >CFDP also benefits space flight missions in another important way: cost >savings. >CFDP allows an instrument to record an observation in a file and transmit >the file to Earth without having to consider whether or not physical >transmission is possible at that time. Sequestering outbound data >management and transmission planning functions within CFDP can simplify >flight and ground software, which reduces mission costs - an important >benefit to lower cost missions like MESSENGER. >CCSDS will continue to foster global scale technical cooperation to >develop recommendations for space communication like CFDP that increase >interoperability, as well as reduce risk and mission operation >costs. Currently, the organization is investigating extending the use of >CFDP in emerging delay-tolerant networking technology to Interplanetary >Internet operations, and specifically to the use of CFDP in complex >mission configurations, which should further enhance the usefulness and >value of CFDP to space exploration missions in the future. >Scott Burleigh, CCSDS working group chair and lead CFDP system engineer at >NASA JPL in Pasadena, Calif. commented, “The successes of CFDP on >MESSENGER and the Deep Impact mission bring us closer to having an >automatic interplanetary communication fabric that can support deep space >science and exploration the way the Internet supports science on Earth." > ># # # > >About CCSDS >Established in 1982 by the world’s most influential space agencies, the >Consultative Committee for Space Data Systems (CCSDS) provides >well-engineered international space data handling standards that enhance >government and commercial interoperability and cross-support, while also >reducing risk, project cost and development time. > A pioneer in international cooperation in space, the CCSDS is > made up of leading space communications experts representing 28 > countries, its founding member space agencies, 22 observer space agencies > and over 100 private companies. CCSDS national member space agencies > include Japan, the United Kingdom, France, Germany, Italy, Brazil, > Russia, Canada and the United States, as well as the multi-national > European Space Agency. > To date, more than 300 missions to space have chosen to fly > with CCSDS protocols and the number continues to grow. For more > information on participation or to access CCSDS standards and protocols > free of charge, please visit http://www.CCSDS.org. > > >Contact for the Press: >Penelope W. Walz >CCSDS Public Affairs >Tel 1 - +1 301 474 5424 >Tel 2 - +1 571 235 1625 >E-mail (best contact) – penelope.walz at btas.com > > > > > > > >_______________________________________________ >CCSDS-All mailing list >CCSDS-All at mailman.ccsds.org >http://mailman.ccsds.org/cgi-bin/mailman/listinfo/ccsds-all >_______________________________________________ >CESG-all mailing list >CESG-all at mailman.ccsds.org >http://mailman.ccsds.org/mailman/listinfo/cesg-all -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- _______________________________________________ CCSDS-All mailing list CCSDS-All at mailman.ccsds.org http://mailman.ccsds.org/cgi-bin/mailman/listinfo/ccsds-all From penelope.walz at btas.com Tue Aug 9 18:26:18 2005 From: penelope.walz at btas.com (Walz Penelope (BTAS)) Date: Tue, 09 Aug 2005 18:26:18 -0000 Subject: [Sls-slp] [Ccsds-all] CCSDS PR - Special Delivery: NASA's MESSENGER Sends Flyby Data to Earth Using CFDP Message-ID: <389C1A32820B4C4A8F3994B435BB98371B9DD1@btas14.BTAS.local> Dear CCSDS Community: Today CCSDS Public Affairs began dissemination of a press release entitled "Special Delivery: NASA's MESSENGER Sends Flyby Data to Earth Using CCSDS File Delivery Protocol Developed for Deep Space by International Team" through international newswire and to targeted media contacts worldwide. The release should be available to the general public tomorrow, Aug. 10, but for your convenience, it is attached in .pdf format and also appears below. Thanks to the following individuals for their input on this release: - Scott Burleigh, NASA JPL - Christopher Krupiarz, JHU APL - Kathy Rockwell, NASA JPL If you have any future CCSDS public affairs ideas, please feel free to send them to me at penelope.walz at btas.com . Thank you for your participation and support. Best regards, Penelope W. Walz The Consultative Committee for Space Data Systems CCSDS Secretariat Support - Public Affairs 6301 Ivy Lane, Ste 720 Greenbelt, MD 20770 USA Tel - +1 301 474 5424 Fax - +1 301 474 5427 Mobile (best contact) - +1 571 235 1625 E-mail - penelope.walz at btas.com CCSDS Press Release Please hold until WED, August 10. Special Delivery: NASA's MESSENGER Sends Flyby Data to Earth Using CCSDS File Delivery Protocol Developed for Deep Space by International Team WASHINGTON, Aug. 10 (CCSDS) - NASA's MESSENGER team is using the CCSDS File Delivery Protocol (CFDP), a highly specialized protocol designed to overcome space operations communications challenges, to download data captured during a successful flyby of Earth last week. A team of international space data communications experts, collaborating through the Consultative Committee for Space Data Systems (CCSDS), developed CFDP to reliably and efficiently downlink files from a spacecraft even in the strenuous environment of deep space. Since the MESSENGER spacecraft's launch a year ago, it has successfully used CFDP to enable mission communications and will use it throughout its 7.9-billion kilometer journey to Mercury. In using CFDP, MESSENGER communications represents a change in the standard method of storing science and housekeeping data on spacecraft built by the Johns Hopkins University Applied Physics Laboratory (JHU/APL). MESSENGER is also the first U.S. space flight mission to use CFDP in mission operations. Prior to MESSENGER, JHU/APL missions used a raw storage model of storing data, but new mission and operational requirements meant that MESSENGER would have to incorporate a file system of data storage into its spacecraft software architecture. A reliable method of downlinking files to the ground had to be found and CFDP was chosen by mission planners to do the job. CFDP is included in the MESSENGER software architecture through a reuse of a NASA Jet Propulsion Lab (NASA JPL) implementation on the ground and a JHU/APL "CFDP-lite" implementation on the flight side. The NASA JPL implementation is also used on NASA's highly successful Deep Impact mission. "JHU/APL engineers integrated CFDP software developed by NASA JPL into the MESSENGER mission's ground system, which communicates with a CFDP flight software implementation developed by JHU/APL on the spacecraft," said Christopher Krupiarz, senior professional staff member, JHU/APL Space Department Embedded Systems Group in Laurel, Maryland (USA). "Being able to use an international standard like CFDP was a key factor in getting two systems developed by two different organizations to work for one Mercury bound spacecraft." CFDP is designed to function reliably despite the long data propagation delays and frequent, lengthy interruptions in connectivity found in deep space. It uses powerful forward error correction coding that minimizes data loss in communication across deep space, and also supports optional "acknowledged" modes of operation in which data loss is automatically detected and a retransmission of the lost data is automatically requested. Some of the world's leading space communications experts working within CCSDS collaborated at bi-annual working group sessions (similar to those scheduled to take place next month in Atlanta, Georgia) to first standardize CFDP. They defined the protocol according to space file transfer requirements articulated by CCSDS participating space agencies, including NASA, the European Space Agency (ESA), the British National Space Centre (BNSC), the Centre National d'Etudes Spatiales (CNES) and the Japan Aerospace Exploration Agency (JAXA). The protocol's ability to maintain a high level of data transfer reliability even across interplanetary distances makes it critical to successful communications on deep space missions like the MESSENGER mission to Mercury and is expected to have a high level of applicability to future Lunar exploration missions. CFDP also benefits space flight missions in another important way: cost savings. CFDP allows an instrument to record an observation in a file and transmit the file to Earth without having to consider whether or not physical transmission is possible at that time. Sequestering outbound data management and transmission planning functions within CFDP can simplify flight and ground software, which reduces mission costs - an important benefit to lower cost missions like MESSENGER. CCSDS will continue to foster global scale technical cooperation to develop recommendations for space communication like CFDP that increase interoperability, as well as reduce risk and mission operation costs. Currently, the organization is investigating extending the use of CFDP in emerging delay-tolerant networking technology to Interplanetary Internet operations, and specifically to the use of CFDP in complex mission configurations, which should further enhance the usefulness and value of CFDP to space exploration missions in the future. Scott Burleigh, CCSDS working group chair and lead CFDP system engineer at NASA JPL in Pasadena, Calif. commented, "The successes of CFDP on MESSENGER and the Deep Impact mission bring us closer to having an automatic interplanetary communication fabric that can support deep space science and exploration the way the Internet supports science on Earth." # # # About CCSDS Established in 1982 by the world's most influential space agencies, the Consultative Committee for Space Data Systems (CCSDS) provides well-engineered international space data handling standards that enhance government and commercial interoperability and cross-support, while also reducing risk, project cost and development time. A pioneer in international cooperation in space, the CCSDS is made up of leading space communications experts representing 28 countries, its founding member space agencies, 22 observer space agencies and over 100 private companies. CCSDS national member space agencies include Japan, the United Kingdom, France, Germany, Italy, Brazil, Russia, Canada and the United States, as well as the multi-national European Space Agency. To date, more than 300 missions to space have chosen to fly with CCSDS protocols and the number continues to grow. For more information on participation or to access CCSDS standards and protocols free of charge, please visit http://www.CCSDS.org. Contact for the Press: Penelope W. Walz CCSDS Public Affairs Tel 1 - +1 301 474 5424 Tel 2 - +1 571 235 1625 E-mail (best contact) - penelope.walz at btas.com -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: CSSDS PR 10AUG05.pdf Type: application/octet-stream Size: 21744 bytes Desc: CSSDS PR 10AUG05.pdf URL: -------------- next part -------------- _______________________________________________ CCSDS-All mailing list CCSDS-All at mailman.ccsds.org http://mailman.ccsds.org/cgi-bin/mailman/listinfo/ccsds-all