[CESG] Re: [SSG] SSG request re SANA SCID registry policies in CCSDS 320.0-B-6

[Marc Blanchet]

Le 2013-11-01 à 20:13, "Kearney, Mike W. (MSFC-EO01)" <mike.kearney at nasa.gov> a écrit :

> Peter, in the near term, given the uncertainty about exactly which codes are available, I think we should take the public list off-line. 

I'm at your service, but taking the spacecraft id offline would be a big change since ... the beginning?  It would most likely create a backfire. Not sure we want that. But that is my take. SANA will implement whatever you want us to do.

> We can make it public later, once we have confidence in it, but in the near term it should be off-line.  And we don’t want to publish procedures telling people to refer to the online list until we can make it available again. 
>  
> And why do we need to be so accommodating as to even solicit requests for specific numbers “in exceptional circumstances”?  I’m sure that if the circumstances are exceptional, the customer will explain them unsolicited, and then we can consider an off-nominal response.  In the meantime, why not let our procedures and our forms reflect only the nominal process? 

I'm sympathic to this idea!

But again, you guys to decide, we will implement.

Marc.

>  
>    -=- Mike
>  
> Mike Kearney
> Lead Technology Manager
> Mission Operations Laboratory
> NASA MSFC EO-01
> +1-256-544-2029
>  
> From: ssg-bounces at mailman.ccsds.org [mailto:ssg-bounces at mailman.ccsds.org] On Behalf Of Shames, Peter M (312G)
> Sent: Friday, November 01, 2013 6:57 PM
> To: Tom Gannett
> Cc: SANA Steering Group (SSG); CCSDS Engineering Steering Group - CESG Exec
> Subject: [SSG] SSG request re SANA SCID registry policies in CCSDS 320.0-B-6
>  
> Tom,
>  
> I am not certain of how we should handle this update, but it is formulated as a CESG resolution.   As a result of the SSG meeting and CESG discussion the SSG wishes to request the following change, to be applied to the CCSDS  GLOBAL SPACECRAFT IDENTIFIER FIELD: CODE ASSIGNMENT CONTROL PROCEDUREs, CCSDS 320.0-B-6.
> Regards, Peter   
>  
> ******************************************************************* 
> 
> SEA-R-2013-11-001, Resolution concerning the SANA SCID Policy in CCSDS 320.0-B-6
> 
> The CCSDS System Engineering Area: 
> 
> CONSIDERING that the SANA Steering Group has reviewed the current SANA SCID Registry Policy;
> 
> and RECOGNIZING that the present policy is subject tto misinterpretation; 
>  
> and RECOGNIZING that existing practices of users of the SCID registry are out of sync with the desired procedures;
> 
> RECOMMENDS that the SANA SCID policy in CCSDS 320.0-B-6 be changed as follows:
> A new Section 3.4.2 shall be instered stating:   The SANA shall assign the speciic SCIDs based on availability.  Only in exceptional circumstances will user requests for specific numerical code assignments be honored.
> Section 3.4.5 shall be modified as follows:  User requests for assignment of specific numerical codes may be accepted in exceptional circumstances and only if those numerical codes are available. The user should refer to the catalog of existing SCID assignments (reference [6]) to avoid requesting assignments that could result in duplication, and, therefore, denial of a request.  If a request for a specific numerical code cannot be honored the SANA shall assign a SCID based on availability. 
> and REQUESTS that the CCSDS Engineering Steering Group Chair initiate the required CESG poll for approval.
> 
>  
> _______________________________________________
> SSG mailing list
> SSG at mailman.ccsds.org
> http://mailman.ccsds.org/cgi-bin/mailman/listinfo/ssg

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ccsds.org/pipermail/cesg/attachments/20131101/7578055c/attachment.html