[CESG] UPDATE: SEA Resolution SEA-R-2016-07-001: Request publication of revised CCSDS SCID Code Assignment Control Procedures

Tue Jul 12 12:30:18 UTC 2016

The historical perspective:

The GSCID Assignment Control Procedures book was created by the Management
Council and published by fiat as a Blue Book in the early days of the CCSDS.
It has since then been maintained by the Secretariat. It has never been to
Agency review, and it has never before been presented to the CESG for
approval.

SEA has taken over the document, so it will now have to suffer the slings
and arrows of CESG political technical discussion. But everyone should keep
in mind that the book is 1) just a very simply procedural instruction and 2)
nevertheless actually very important to assure that GSCIDs are assigned (and
relinquished) in an orderly manner.

Sending the book to Agency review could be seen as a needless waste of
resources as well as time. Probably it should simply be made a Yellow Book
at this point, but the original intent of the Management Council was to have
a normative procedure that applied outside the CCSDS, even though the
primary users are the Agency Heads of Delegation.

Thomas Gannett

thomas.gannett at tgannett.net

+1 443 472 0805

From: Nestor.Peccia at esa.int [mailto:Nestor.Peccia at esa.int] 
Sent: Tuesday, July 12, 2016 5:57 AM
To: Shames, Peter M (312B)
Cc: CCSDS Engineering Steering Group - CESG Exec; CESG; CCSDS Secretariat;
SANA Steering Group(SSG); Tom Gannett
Subject: UPDATE: [CESG] SEA Resolution SEA-R-2016-07-001: Request
publication of revised CCSDS SCID Code Assignment Control Procedures

Peter, 

Apologies for a 2nd mail, but I had to retrieve some paragraph from the
"Bible" 

============================================================================
=== 

Peter 

I believe that you can not issue a resolution for publication of a Magenta
Book without having gone through an Agency Review, even if CESG and CMC have
reviewed it. 

I suggest that you change your resolution according to these terms. 

Otherwise we will introduce a precedence on the "per saltum", i.e. if CESG /
CMC have reviewed a MB, we do not need an Agency Review. 

I, as CESG Chair, am not in favour of such an approach. 

ciao 
nestor 

From:        "Shames, Peter M (312B)" <peter.m.shames at jpl.nasa.gov> 
To:        "CCSDS Secretariat" <secretariat at mailman.ccsds.org>, "Tom
Gannett" <thomas.gannett at tgannett.net> 
Cc:        "SANA Steering Group\(SSG\)" <ssg at mailman.ccsds.org>, "CCSDS
Engineering Steering Group - CESG Exec" <cesg at mailman.ccsds.org> 
Date:        11/07/2016 22:42 
Subject:        [CESG] SEA Resolution SEA-R-2016-07-001: Request publication
of revised CCSDS SCID Code Assignment Control Procedures 
Sent by:        "CESG" <cesg-bounces at mailman.ccsds.org> 

  _____  

[attachment "320x0b6c1_mods_7-12July16.docx" deleted by Nestor
Peccia/esoc/ESA] 
Dear CCSDS Secretariat, 

Please find attached the SEA resolution concerning the request for
publication of the revised CCSDS SCID Code Assignment Control Procedures
Magenta Book.  The major changes are the inclusion of frequency band bins
for allocation of GSCIDs, references to the new registries defined in the
RMP, and re-classifying the document as a Magenta Book based upon its type. 

Thanks, Peter 

========================================================================== 

SEA-R-2016-07-001  Request publication of revised CCSDS SCID Code Assignment
Control Procedures 
----------------------------------------------------------------------------
---- 

The System Engineering Area, 

CONSIDERING that: 

The SEA SANA Steering Group (SSG) has produced a revision of the existing
Blue Book called the CCSDS GLOBAL SPACECRAFT IDENTIFIER FIELD: 
CODE ASSIGNMENT CONTROL PROCEDURES (CCSDS 320.0-B-6), and that 
The source document, CCSDS 320.0-B-1, was originally directly published as a
CMC document, and that 
The specific major changes to the document have already been reviewed and
agreed to by the CESG and CMC, and that 
The SSG Members concur that this draft is ready for publication. 

And RECOGNIZING that: 

A CCSDS Area Director is responsible for requesting CESG concurrence prior
to publication, and that 
The CCSDS Organization and Processes (A02.1-Y-4 cor 2) in Section 6.2.2.2
requests that the AD forward the draft documents to the CESG, and 
notify the Chief Technical Editor. 

And RECOGNIZING that: 

The CCSDS Organization and Processes (A02.1-Y-4 cor 2) in Section 6.1.4.3
now defines this type of book (a process or procedure description) as a
Magenta Book, and that 
Sec 6.2.7 requires periodic review and re-confirmation of Normative Track
documents. 

RESOLVES to request: 

That the Chief Technical Editor ready the document for review, and that 
The document be re-classified as a Magenta Book, to properly characterize it
based on its contents, and that 
The Secretariat create the necessary CESG poll to request the CESG review
and approval of this document, and that 
Once the CESG poll succeeds that the CMC be polled to approve the document
for direct publication, as it was in its original form. 

 _______________________________________________
CESG mailing list
CESG at mailman.ccsds.org
 <https://mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg>
https://mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg

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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/cesg/attachments/20160712/fa83cf6a/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 12587 bytes
Desc: not available
URL: <http://mailman.ccsds.org/pipermail/cesg/attachments/20160712/fa83cf6a/attachment.gif>