[Css-csts] SLE Issues: open questions

Alan Jeffries alan at jetsi.com
Wed Mar 13 16:28:42 EST 2013


Wolfgang,

Good to hear from you and all the CSTS folks.

I can indeed provide some insight. It was not due to security in the end.

We are deploying SLE for our high rate Stored Mission Data (SMD) links.
This data is dumped once per orbit at polar sites. Currently we are flying
the recently launched Soumi-NPP satellite, but we are updating the ground
system to support the JPSS-1 satellite and GCOMW-1 in the near future.

We transport the SMD data back to CONUS via SLE, where it is processed into
a myriad of weather/climate data products. The collection point for all of
our polar sites is responsible for data auditing (making sure we get all the
data off the recorders, even if we loose some or all of a pass). There will
be 2 northern and 2 southern plus a TDRS K-band option in the future. So we
have a central collection hub from which we can process the weather products
collected from all these sites and account for data from the recorders,
across multiple platforms.

Instead of scheduling this collection hub, it was decided it would be better
to have that node data driven and always listening for the Provider binds
from all over the globe.

Thus, we still schedule the passes at the provider sites by mission, but
don't need to 'schedule' the central SMD collection hub.  It was deemed an
operational simplification.

Kind regards, Alan


On 3/13/13 10:34 AM, "Wolfgang.Hell at esa.int" <Wolfgang.Hell at esa.int> wrote:

> Dear Alan,
> 
> Given your input, I stand corrected. There is at least one case where the
> provider-initiated BIND option will be used. It is certainly not a problem to
> retain that option - we just tried not to invest effort into improving the
> specification of a feature that is not used by anybody.
> 
> Given that so far this feature had not been used, I'm sure that the WG would
> be very interested in learning why the JPSS program has chosen this option.
> Could you perhaps provide information on the the rational for this design
> decision?
> 
> Best regards,
> 
> Wolfgang Hell
> 
> 
> |------------>
> | From:      |
> |------------>
>> -----------------------------------------------------------------------------
>> -------------------------------------------------------------------------|
>   |Alan Jeffries <alan at jetsi.com>
> |
>> -----------------------------------------------------------------------------
>> -------------------------------------------------------------------------|
> |------------>
> | To:        |
> |------------>
>> -----------------------------------------------------------------------------
>> -------------------------------------------------------------------------|
>   |Martin Karch <martin.karch at telespazio-vega.de>,
> "css-csts at mailman.ccsds.org" <css-csts at mailman.ccsds.org>
> |
>> -----------------------------------------------------------------------------
>> -------------------------------------------------------------------------|
> |------------>
> | Date:      |
> |------------>
>> -----------------------------------------------------------------------------
>> -------------------------------------------------------------------------|
>   |11/03/2013 14:20
> |
>> -----------------------------------------------------------------------------
>> -------------------------------------------------------------------------|
> |------------>
> | Subject:   |
> |------------>
>> -----------------------------------------------------------------------------
>> -------------------------------------------------------------------------|
>   |Re: [Css-csts] SLE Issues: open questions
> |
>> -----------------------------------------------------------------------------
>> -------------------------------------------------------------------------|
> |------------>
> | Sent by:   |
> |------------>
>> -----------------------------------------------------------------------------
>> -------------------------------------------------------------------------|
>   |css-csts-bounces at mailman.ccsds.org
> |
>> -----------------------------------------------------------------------------
>> -------------------------------------------------------------------------|
> 
> 
> 
> 
> 
> Dear CSTS Group,
> 
> I normally do not chime in, but I am working on the JPSS weather satellite
> program and we are migrating our T&C and high rate science links to SLE. As
> part of this we are moving to provider initiated binds, so we would be
> interested in keeping the concept as an option.
> 
> May I inquire as to why these were considered for removal.
> 
> Best regards, Alan Jeffries
> 
> 
> On 3/11/13 3:38 AM, "Martin Karch" <martin.karch at telespazio-vega.de> wrote:
> 
> 
>       Dear Working Group members,
> 
>       We have started to prepare the Pink Sheets for the SLE Books based on
>       the problems reported by Wolfgang in his presentation on SLE issues
>       during our meeting in Cleveland (see
>       
> http://cwe.ccsds.org/css/docs/CSS-CSTS/CWE%20Private/SLE%20Services/SLE%20Issu
> es.ppt
>        <
>       
> http://cwe.ccsds.org/css/docs/CSS-CSTS/CWE%20Private/SLE%20Services/SLE%20Issu
> es.ppt
>>  in the CWE).
> 
>       There are the following 2 open points for clarification:
> 
>       - removal of the provider initiated BIND from the return services:
>         Do we remove provider initiated BIND or do we keep it?
> 
>       - how to deal with not yet 'initialised' gettable parameters when the
>       ASN.1 as is does not allow the parameter to be set to NULL. (See page
>       26 on SLE Issues presentation).
>       We think the cleanest solution would be to implement an ASN.1 change
>       introducing a value qualifier. The more pragmatic (less invasive)
>       approach would be the use of specific values to flag not yet
>       initialized parameters. The decision on this shall be made by the WG.
> 
>       May I ask you to send me your opinions/decisions on these 2 points
>       above not later than 15.03.2013.
> 
>       Many thanks in advance!
> 
>       Best regards,
>       Martin
> 
>       ----------------------------
>       Martin Karch
>       Telespazio VEGA Deutschland GmbH
>       Europaplatz 5
>       D-64293 Darmstadt
>       Germany
>       Tel : +49 (0)6151 8257-135
>       Fax : +49 (0)6151 8257-799
>       Email : Martin.Karch at vega.de <mailto:Martin.Karch at vega.de>
>       Web : www.telespazio-vega.de <http://www.telespazio-vega.de>
>       Registered office/Sitz: Darmstadt, Register court/Registergericht:
>       Darmstadt, HRB 89231; Managing Directors/Geschäftsführer: Sigmar
>       Keller, John Lewis, Yves Constantin
>       Notice of Confidentiality
>       This transmission is intended for the named addressee only. It contains
>       information which may be confidential and which may also be privileged.
>       Unless you are the named addressee (or authorised to receive it for the
>       addressee) you may not copy or use it, or disclose it to anyone else.
>       If you have received this transmission in error please notify the
>       sender immediately.
> 
> 
> 
> 
>       _______________________________________________
>       Css-csts mailing list
>       Css-csts at mailman.ccsds.org
>       http://mailman.ccsds.org/cgi-bin/mailman/listinfo/css-csts
> 
> 
> 
> ------------------------------------------
> Alan Jeffries
> Jeffries Technology Solutions, Inc
> VA Office: +1 703 471 7588
> JPSS Office: +1 240 684 0982
> Cell: +1 703 582 0228
> E-Mail: alan at jetsi.com
> _______________________________________________
> Css-csts mailing list
> Css-csts at mailman.ccsds.org
> http://mailman.ccsds.org/cgi-bin/mailman/listinfo/css-csts
> 
> 
> 
> 
> 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.
> 



------------------------------------------
Alan Jeffries
Jeffries Technology Solutions, Inc
VA Office: +1 703 471 7588
JPSS Office: +1 240 684 0982
Cell: +1 703 582 0228
E-Mail: alan at jetsi.com






More information about the Css-csts mailing list