Fw: [Css-csts] RE: User state table for "startable" procedures

Tue Nov 1 06:59:02 EST 2011

Dear Martin,

As discussed during the meeting the peer-abort from the procedures to the
Assoc.Ctrl procedure will be rephrased to "procedure to association abort".
I updated the entire document accordingly.

Best regards
Yves

----- Forwarded by Yves Doat/esoc/ESA on 31/10/2011 22:25 -----

  From:       "Ray, Timothy J. (GSFC-5830)" <timothy.j.ray at nasa.gov>                                                               

  To:         "css-csts at mailman.ccsds.org" <css-csts at mailman.ccsds.org>                                                            

  Date:       24/10/2011 20:18                                                                                                     

  Subject:    [Css-csts] RE: User state table for "startable" procedures                                                           

  Sent by:    css-csts-bounces at mailman.ccsds.org                                                                                   

By the way, a related technical detail to take care of in Boulder:

The linkage for communicating a peer-abort from one Provider state table to
another appears to be incorrect in the current Framework spec.

For example, the Buffered Data Delivery procedure communicates a peer-abort
by raising the ‘Peer-abort invocation’ to the Association Control procedure.
But a ‘Peer-abort invocation’ event is associated with an incoming peer-abort
invocation from the CSTS *partner*.  The correct linkage for *internal*
propagation of a peer-abort is by raising the ‘Peer-abort xxx’ event in the
Association Control procedure.

Best regards,
Tim

From: Ray, Timothy J. (GSFC-5830)
Sent: Monday, October 24, 2011 2:09 PM
To: css-csts at mailman.ccsds.org
Subject: User state table for "startable" procedures

Hi,

I’ve uploaded state table logic for the User side of “startable” Framework
procedures:

http://cwe.ccsds.org/css/docs/CSS-CSTS/CWE%20Private/CSTS%20Framework%20and%20Concept/2011_24_October%20Stateful%20Procedure%20User%20State%20Table.doc
The bigger picture:
The Framework spec has state tables for the *Provider* side of all Framework
procedures.  A state table for the *User* side of the Association Control
procedure was uploaded months ago:

http://cwe.ccsds.org/css/docs/CSS-CSTS/CWE%20Private/CSTS%20Framework%20and%20Concept/2011_25_May%20Assoc%20Control%20User%20State%20Table.doc
The Association Control state table covers the Bind/Unbind logic.  Today’s
upload covers the Start/Stop logic that is the heart of most of the other
procedures.  If there is a consensus that it would be better to publish a
separate User state table for each Framework procedure (i.e. 8 User state
tables instead of 2),  I would be willing to put that together.

The User-side logic for the Data Processing is a superset of today’s upload,
so it makes sense to add one more User state table to cover this procedure.
Because the Data Processing procedure is still in flux, I would like to hold
off on developing this state table.  However, if anyone responds saying
“please provide a ‘Data Processing’ User state table for discussion in
Boulder”, I will attempt to do so.

Best regards,
Tim_______________________________________________
Css-csts mailing list
Css-csts at mailman.ccsds.org
http://mailman.ccsds.org/cgi-bin/mailman/listinfo/css-csts