[Css-csts] Procedure instance number of Association Control procedure?

[John Pietras]

Yves,
I agree with assigning "1" to the procedure instance identifier for the
Association Control (AC) procedure. However, I don't think that it is
necessary to declare the AC procedure to be secondary, and in fact it
seems strange to me to consider the Association Control procedure -
which MUST exist and be executing before and after even the prime
procedure - to be a "secondary" procedure. 

Saying that secondary procedures must be numbered beginning with "1"
does not imply that a procedure with instance number 1 must be a
secondary procedure. I think that we can just state that the instance
number must be "1", but not declare the AC procedure to be a secondary
procedure. I think the text that already exists in the Framework does a
good job of distinguishing the AC procedure from the prime and secondary
procedures.

Best regards,
John


-----Original Message-----
From: Yves.Doat at esa.int [mailto:Yves.Doat at esa.int] 
Sent: Wednesday, September 23, 2009 4:17 AM
To: John Pietras
Cc: css-csts at mailman.ccsds.org; css-csts-bounces at mailman.ccsds.org
Subject: Re: [Css-csts] Procedure instance number of Association Control
procedure?

Dear John,
In my view the section 2.5.3 should address the issue. This section
states:



Every  service  includes  the Association Control procedure (see 4.3).
Only a
single  instance  of  the Association Control procedure exists
throughout the
lifetime of a transfer service instance.


In  addition  to the Association Control procedure a service may
comprise any
number  of  further procedure types and may use one or more instances of
each
procedure  type.   However,  one  single procedure instance is
designated the
prime  procedure  of the service.  All other procedure instances are
referred
to as secondary procedures.


NOTE    -  The  prime  procedure (instance) can be of the same type as
one or
         more secondary procedure instances.


The  prime  procedure  (instance)  of  a  service  should reflect the
primary
purpose  of  the  service.  In practical terms it determines the state
of the
service and as such determines the orderly association release as
detailed in
2.6

>From the text I understand that the association control procedure cannot
be a
prime procedure (last paragraph) and therefore must be of secondary
procedure
type. Its number should therefore be "1".
A clear statement could be added, e.g. the following sentence at the end
of
the 2nd paragraph:
"The association control procedure is a secondary procedure."

Please let me know your opinion.
I would also appreciate an answer of the prototype developers: what
value did
you use?

Best regards
Yves




 

             "John Pietras"

             <john.pietras at gst.

             com>
To 
             Sent by:                   <css-csts at mailman.ccsds.org>

             css-csts-bounces at m
cc 
             ailman.ccsds.org

 
Subject 
                                        [Css-csts] Procedure instance
number 
             22/09/2009 21:59           of Association Control
procedure?   
 

 

 

 

 

 





CSTSWG colleagues -
We have stated that the prime procedure instance get procedure instance
number 0, and that secondary procedure instances are numbered
1 .. <number of secondary instances>. What should be the procedure
instance
number for the Association Control procedure instance, which is neither
prime
nor secondary?

John

John Pietras
GST, Inc.
7855 Walker Drive, Suite 200
Greenbelt, MD 20770
240-542-1155
 _______________________________________________
Css-csts mailing list
Css-csts at mailman.ccsds.org
http://mailman.ccsds.org/cgi-bin/mailman/listinfo/css-csts