[Css-csts] Inter-operability test results posted

Ray, Timothy J. (GSFC-5830) timothy.j.ray at nasa.gov
Mon Apr 26 14:15:00 EDT 2010


Dear Martin,

Everything you said makes sense to me.  I agree.

Best regards,
Tim

From: Martin Götzelmann [mailto:martin.goetzelmann at vega.de]
Sent: Monday, April 26, 2010 12:06 PM
To: Ray, Timothy J. (GSFC-5830)
Cc: css-csts at mailman.ccsds.org; Martin Karch; Christian Laroque
Subject: RE: [Css-csts] Inter-operability test results posted

Dear Tim,

One more (minor) comment from me related to test 4e):

The implementation on the provider side is obviously not correct, but I feel the distinction between the two diagnostic codes in the specification framework is rather subtle. I must admit that I recognised it only after reading the definition several times and had already started with the statement that they are not unambiguous. The definitions are:

'invalid time'- the BIND operation was invoked outside the service instance provision period of the service instance identified by the service-instance-identifier parameter;
'service instance ended'-the BIND operation was invoked after the Service User unbound the association with reason 'end' (see 3.5.2.3.2) and as a consequence the Service Provider released all service instance resources.
I understand this to say that the code 'service instance ended' must only be used if the service instance provision period has terminated due to the fact that a previous UNBIND invocation had the parameter unbind reason set to "end" whereas 'invalid time' shall be used when the provision period has expired. An interesting question is what code should be used if the service instance was terminated by UNBIND with 'end' but the original service instance provision period also terminated before the new BIND invocation. I assume 'invalid time' would take precedence in that case.
The code 'service instance ended' was not present in the SLE specifications and I think we should discuss next week whether we want to keep it of simply extent the definition of 'invalid time' by something like "... or the Service User unbound the association with reason 'end'
Regards, Martin
________________________________
From: css-csts-bounces at mailman.ccsds.org [mailto:css-csts-bounces at mailman.ccsds.org] On Behalf Of Ray, Timothy J. (GSFC-5830)
Sent: 23 April 2010 19:36
To: css-csts at mailman.ccsds.org
Subject: [Css-csts] Inter-operability test results posted
Dear WG,

A round of testing was conducted today between the Provider (ESA) and User (NASA) Proto-Framework Service prototypes.  The test results have been posted to the CWE at the following directory:   (CSTS-Private / CSTS Framework and Concept)

http://cwe.ccsds.org/css/docs/Forms/AllItems.aspx?RootFolder=%2Fcss%2Fdocs%2FCSS-CSTS%2FCWE%20Private%2FCSTS%20Framework%20and%20Concept&View={8045374D-F8E0-4356-83CA-993252A38FE8}&SortField=Modified&SortDir=Desc<http://cwe.ccsds.org/css/docs/Forms/AllItems.aspx?RootFolder=%2Fcss%2Fdocs%2FCSS-CSTS%2FCWE%20Private%2FCSTS%20Framework%20and%20Concept&View=%7b8045374D-F8E0-4356-83CA-993252A38FE8%7d&SortField=Modified&SortDir=Desc>

Best regards,
Tim

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ccsds.org/pipermail/css-csts/attachments/20100426/df23491f/attachment.htm


More information about the Css-csts mailing list