<font size=2 face="sans-serif">Dear all</font>
<br>
<br><font size=2 face="sans-serif">Rick is the only one who commented Peter's
updates.</font>
<br>
<br><font size=2 face="sans-serif">Please send comments to Peter at the
latest by end June 2015</font>
<br>
<br><font size=2 face="sans-serif">From 1st July 2015, the ADs, who own
the docs, need to issue resolutions for the CESG reviews.</font>
<br>
<br><font size=2 face="sans-serif">ciao</font>
<br><font size=2 face="sans-serif">nestor</font>
<br>
<br>
<br><font size=1 color=#800080 face="sans-serif">----- Forwarded by Nestor
Peccia/esoc/ESA on 10/06/2015 15:00 -----</font>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">"Shames, Peter
M (312B)" <peter.m.shames@jpl.nasa.gov></font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">CCSDS Engineering Steering
Group - CESG Exec <cesg@mailman.ccsds.org>, </font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">03/06/2015 21:58</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">[CESG] Follow
up on CESG discussion of SANA and registry changes</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Sent by:
</font><font size=1 face="sans-serif">cesg-bounces@mailman.ccsds.org</font>
<br>
<hr noshade>
<br>
<br>
<br><font size=2 face="Calibri">Dear CESG colleagues,</font>
<br>
<br><font size=2 face="Calibri">Attached please find three <b><i>draft</i></b>
sets of document edits to the following:</font>
<br><font size=2 face="sans-serif">1. </font><font size=2 face="Calibri">The
SANA Yellow Book, CCSDS 313xoy1 SEA edits</font>
<br><font size=2 face="sans-serif">2. </font><font size=2 face="Calibri">The
SCID Blue Book, CCSDS 320x0b6c1_mods</font>
<br><font size=2 face="sans-serif">3. </font><font size=2 face="Calibri">The
MACAO Blue Book, CCSDS 630x0b1_mods</font>
<br><font size=2 face="Calibri">As I pointed out during the CESG telecon,
we do already have a set of agency and point of contact registries defined
in a couple of CCSDS documents, dating back to 1993. These registries
were designed to serve a specific purpose, I.e. registering spacecraft
IDs, and registering SFDU identifiers. And they were defined prior
to the existence of the SANA, so they make no reference to the SANA nor
even to each other. But they do, taken together, a pretty credible
job of defining the needed structures, rules, and info models for the key
CCSDS "organization" and "contact" registries.</font>
<br>
<br><font size=2 face="Calibri">Here is what they currently have defined:</font>
<br>
<br><font size=2 face="Calibri"><b>SCID Blue Book, CCSDS 320x0b6c1, currently
contains:</b></font>
<br><font size=2 face="sans-serif">1. </font><font size=2 face="Calibri">A
SCID registration process</font>
<br><font size=2 face="sans-serif">2. </font><font size=2 face="Calibri">A
set of rules for who can request SCID changes, which references: </font>
<br><font size=2 face="sans-serif">1. </font><font size=2 face="Calibri">A
"CCSDS agency" may be a member or observer agency</font>
<br><font size=2 face="sans-serif">2. </font><font size=2 face="Calibri">An
Agency Head of Delegation</font>
<br><font size=2 face="sans-serif">3. </font><font size=2 face="Calibri">An
Agency Representative who can make changes, appointed by the Agency HoD</font>
<br><font size=2 face="sans-serif">4. </font><font size=2 face="Calibri">The
Secretariat which does issue resolution and handles requests for agencies
not affiliated with CCSDS</font>
<br><font size=2 face="sans-serif">3. </font><font size=2 face="Calibri">None
of these registries were specified, nor were references to other sources
provided</font>
<br><font size=2 face="sans-serif">4. </font><font size=2 face="Calibri">There
is not even a spec for what the structure of the SCID registry should be</font>
<br><font size=2 face="sans-serif">5. </font><font size=2 face="Calibri">A
form for submitting requests / return of SCIDs</font>
<br><font size=2 face="Calibri">What is in the proposed revisions:</font>
<br><font size=2 face="sans-serif">1. </font><font size=2 face="Calibri">A
SANA registry considerations section formally defining the SCID registry,
structure, and contents</font>
<br><font size=2 face="sans-serif">2. </font><font size=2 face="Calibri">SANA
rules and registration authority for this registry, as requested in the
SANA YB</font>
<br><font size=2 face="sans-serif">3. </font><font size=2 face="Calibri">Addition
of a unique OID assignment along with the SCID which must be "re-cycled"
when no longer needed</font>
<br><font size=2 face="sans-serif">4. </font><font size=2 face="Calibri">A
few new fields in the SCID registry, for S/C names, aliases, and the OID</font>
<br><font size=2 face="sans-serif">5. </font><font size=2 face="Calibri">References
to the agency, agency HoD, and agency representative registries that the
MACAO describes</font>
<br><font size=2 face="sans-serif">6. </font><font size=2 face="Calibri">Extensiosn
to the SCID form to add OID and optional S/C name & aliases</font>
<br><font size=2 face="Calibri"><b>MACAO Blue Book, CCSDS 630x0b1, currently
contains:</b></font>
<br><font size=2 face="sans-serif">1. </font><font size=2 face="Calibri">MACAO
creation and extension procedures</font>
<br><font size=2 face="sans-serif">2. </font><font size=2 face="Calibri">A
set of rules for creating and operating the MACAO, including the CA Agent
as the top level</font>
<br><font size=2 face="sans-serif">3. </font><font size=2 face="Calibri">Definitions
for: </font>
<br><font size=2 face="sans-serif">1. </font><font size=2 face="Calibri">CA
RP originator info model (assigned agent to make registrations)</font>
<br><font size=2 face="sans-serif">2. </font><font size=2 face="Calibri">CA
Reviser info model (assigned agent to change registrations)</font>
<br><font size=2 face="sans-serif">3. </font><font size=2 face="Calibri">References
to the Agency, Agency Representaive, and Agency Head of Delegation</font>
<br><font size=2 face="sans-serif">4. </font><font size=2 face="Calibri">Definition
for MACAO creation request info model, including agency & AR references
and MACAO info model</font>
<br><font size=2 face="sans-serif">5. </font><font size=2 face="Calibri">Agency
and MACAO info model</font>
<br><font size=2 face="sans-serif">4. </font><font size=2 face="Calibri">Several
of these info model structures are quite well specified, but there is no
specificaiton of registries</font>
<br><font size=2 face="sans-serif">5. </font><font size=2 face="Calibri">There
is no full agency specification, nor a full agency HoD or AR specification,
and none of the info models include accurate field specifications </font>
<br><font size=2 face="Calibri">What is in the proposed revisions:</font>
<br><font size=2 face="sans-serif">1. </font><font size=2 face="Calibri">A
SANA Registry considerations section formally defining the MACAO agency
registry, a CCSDS Contacts registry (for all persons, HoD, AR, MACAO originator
& reviser, with full info model & extensible role set), and a CCSDS
Organization registry (agency, observer, affiliate, with full info model
(MACAO, etc) and extensible role set)</font>
<br><font size=2 face="sans-serif">2. </font><font size=2 face="Calibri">SANA
rules and registration authorities for each registry, as requested in the
SANA YB</font>
<br><font size=2 face="sans-serif">3. </font><font size=2 face="Calibri">Complete
specification of the relationships among Secretariat, agency, HoD, AR,
and MACAO structures</font>
<br><font size=2 face="sans-serif">4. </font><font size=2 face="Calibri">Clarification
of the SANA role as the CA Agent to replace the defunct WDC-A</font>
<br><font size=2 face="sans-serif">5. </font><font size=2 face="Calibri">A
few new fields in the Orgnization and Contacts registries, for the OIDs</font>
<br><font size=2 face="sans-serif">6. </font><font size=2 face="Calibri">Roles
fields for both Organization and Contacts registries that support assignment
of roles like AR, MACAO originator, member / observer agency, service provider
and that define a process for extension by other standards as needed (SCCM,
etc).</font>
<br><font size=2 face="Calibri"><b>SANA Yellow Book, CCSDS 313xoy1, currently
contains:</b></font>
<br><font size=2 face="sans-serif">1. </font><font size=2 face="Calibri">SANA
Role, responsibilities and policies, speifically focused on what the SANA
and the operator must do, less about the users of SANA</font>
<br><font size=2 face="sans-serif">2. </font><font size=2 face="Calibri">SANA
/ WG relationship (which has some inaccuracies that need fixing)</font>
<br><font size=2 face="sans-serif">3. </font><font size=2 face="Calibri">Simple
rules for creating new registries and changing existing ones</font>
<br><font size=2 face="Calibri">What is in the proposed revisions:</font>
<br><font size=2 face="sans-serif">1. </font><font size=2 face="Calibri">Clarification
of SANA role in providing on-line, web accessible, registries</font>
<br><font size=2 face="sans-serif">2. </font><font size=2 face="Calibri">Clarification
of SANA / WG relationship</font>
<br><font size=2 face="sans-serif">3. </font><font size=2 face="Calibri">References
to the organization, person, OID, and other registries that are intended
for adoption and re-use</font>
<br><font size=2 face="sans-serif">4. </font><font size=2 face="Calibri">A
WG procedure for creating new reqistries and modifying existing ones that
requires use (or extension) of existing registries, such as agency, org,
persons, etc.</font>
<br><font size=2 face="sans-serif">5. </font><font size=2 face="Calibri">Definition
of the Expert Group and policy </font>
<br><font size=2 face="Calibri"><b>Some further comments for consideration</b></font>
<br>
<br><font size=2 face="Calibri">The adoption and extension of the existing
SCID and MACAO registires was proposed because these already exist. In
spite of their not being fully specified, these two documents, taken together,
do describe a quite commplete set of registires for agency, HoD, PoC, AR,
and related structures. Taken together with how these have actually
been implemented by the SANA Operator, using a real database to manage
the data and with web accessible interfaces, we already have a very good
start in the right direction. What is missing is a set of policies
for re-using and extending these registries, and others, as the need arises
instead of just creating new, overlapping, partially (or weakly) specified
registries and policies. </font>
<br>
<br><font size=2 face="Calibri">But what this approach does is it requires
anyone who tries to understand these registries and how we intend
them to be used and extended to read all three of these documents. The
SANA has to point to the SCID and the MACAO docs, and the SCID and MACAO
each must point to each other, because one defines some of the info model
and the other defines the rest. It is workable, but awkward at best.
These mods accomplish this.</font>
<br>
<br><font size=2 face="Calibri">I have the belief that we could substantially
improve this by creating one new "CCSDS registry Management Polciy"
document that puts all of these core infrastructure, and the related policies
and info models, into one coherent document. If we take that approach
then the changes to these two documents would just have to say "Use
the procedures and information defined over there." and add the one
or two unique pieces for their own specificly defined roles or fields.</font>
<br>
<br><font size=2 face="Calibri">Either approach can be made to work, let's
first try to get agreement on the overall concept of a single, unified,
set of organization and contacts registries, and a set of rules for extending
them.</font>
<br>
<br><font size=2 face="Calibri">I will be meeting with the Secretariat
and SANA operator to discuss these changes as well. Out of that discussion
should come some understanding of whether they agree that these changes
are feasible and what the impact is likely to be. I have the belief
that going from 10 "organization" registries and 4 "people"
registries down to one of each has to be a net benefit in on-going effort,
but it will take some effort to get there.</font>
<br>
<br><font size=2 face="Calibri">Thanks, Peter</font>
<br>
<br>
<br>
<br>
<br>
<br>
<br><tt><font size=2>_______________________________________________<br>
CESG mailing list<br>
CESG@mailman.ccsds.org<br>
</font></tt><a href=http://mailman.ccsds.org/mailman/listinfo/cesg><tt><font size=2>http://mailman.ccsds.org/mailman/listinfo/cesg</font></tt></a><tt><font size=2><br>
</font></tt><PRE>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.
</PRE>