<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>Thanks Nestor.</div>
<div><br>
</div>
<div>The relevant file for the MOIMS DAI WG is attached. It is the draft mods for the SFDU CA procdures.</div>
<div><br>
</div>
<div>Regards, Peter</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span><<a href="mailto:cesg-bounces@mailman.ccsds.org">cesg-bounces@mailman.ccsds.org</a>> on behalf of Nestor Peccia <<a href="mailto:Nestor.Peccia@esa.int">Nestor.Peccia@esa.int</a>><br>
<span style="font-weight:bold">Date: </span>Monday, July 27, 2015 at 1:04 AM<br>
<span style="font-weight:bold">To: </span>"<a href="mailto:moims-dai@mailman.ccsds.org">moims-dai@mailman.ccsds.org</a>" <<a href="mailto:moims-dai@mailman.ccsds.org">moims-dai@mailman.ccsds.org</a>><br>
<span style="font-weight:bold">Cc: </span>CCSDS Engineering Steering Group - CESG Exec <<a href="mailto:cesg@mailman.ccsds.org">cesg@mailman.ccsds.org</a>><br>
<span style="font-weight:bold">Subject: </span>[CESG] [Moims-dai] Proposed edits to the MACAO Blue Book<br>
</div>
<div><br>
</div>
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div>
<div><font size="2" face="sans-serif">Daniele, DAI WG members and MOIMS ADs</font>
<br>
<br>
<font size="2" face="sans-serif">Please discuss Peter's mail in your WG and with your AD/DAD</font><br>
<br>
<font size="2" face="sans-serif">The update of the SFDU CA Procedures (630-0-B-1) does not exist as a Project in the CWE Framework. No resources have been committed by the Agencies to handle it. The next 5 year review is due in May 2018. It is clear that if
the WG decides to work on it, a Project has to be created and resources have to be committed by the Agencies via a CMC poll.</font><br>
<br>
<font size="2" face="sans-serif">In addition, the WG has to deal with three other potential 5 year review Projects (in case the WG decides to review it instead of Reconfirm them)</font><br>
<ol>
<li value="1"><font size="2" face="sans-serif">XFDU BB 5 year review is due since Sept 2013</font></li><li value="2"><font size="2" face="sans-serif">EAST BB 5 year review is due in June 2015</font></li><li value="3"><font size="2" face="sans-serif">PAIMS MB 5 year review due in June 2015</font></li></ol>
<br>
<font size="2" face="sans-serif">ciao</font> <br>
<font size="2" face="sans-serif">nestor</font> <br>
<br>
<font size="1" color="#800080" face="sans-serif">----- Forwarded by Nestor Peccia/esoc/ESA on 27/07/2015 09:48 -----</font><br>
<br>
<font size="1" color="#5f5f5f" face="sans-serif">From: </font><font size="1" face="sans-serif">"Shames, Peter M (312B)" <<a href="mailto:peter.m.shames@jpl.nasa.gov">peter.m.shames@jpl.nasa.gov</a>></font><br>
<font size="1" color="#5f5f5f" face="sans-serif">To: </font><font size="1" face="sans-serif">Boucon Daniele <<a href="mailto:Daniele.Boucon@cnes.fr">Daniele.Boucon@cnes.fr</a>>,
</font><br>
<font size="1" color="#5f5f5f" face="sans-serif">Cc: </font><font size="1" face="sans-serif">"<a href="mailto:moims-dai@mailman.ccsds.org">moims-dai@mailman.ccsds.org</a>" <<a href="mailto:moims-dai@mailman.ccsds.org">moims-dai@mailman.ccsds.org</a>></font><br>
<font size="1" color="#5f5f5f" face="sans-serif">Date: </font><font size="1" face="sans-serif">26/07/2015 08:05</font><br>
<font size="1" color="#5f5f5f" face="sans-serif">Subject: </font><font size="1" face="sans-serif">[Moims-dai] Proposed edits to the MACAO Blue Book</font><br>
<font size="1" color="#5f5f5f" face="sans-serif">Sent by: </font><font size="1" face="sans-serif"><a href="mailto:moims-dai-bounces@mailman.ccsds.org">moims-dai-bounces@mailman.ccsds.org</a></font><br>
<hr noshade="">
<br>
<br>
<font size="2" face="Calibri">[attachment "SANA YB 313x0y1 SEA edits 8Jul15.pdf" deleted by Nestor Peccia/esoc/ESA]
</font><br>
<font size="2" face="Calibri">[attachment "630x0b1_mods-8Jul15.docx" deleted by Nestor Peccia/esoc/ESA]
</font><br>
<font size="2" face="Calibri">[attachment "CCSDS Registry Re-engineering 10Jul15 v2.pptx" deleted by Nestor Peccia/esoc/ESA]
</font><br>
<font size="2" face="Calibri">[attachment "CCSDS SSG Name & Number Registries v13.pptx" deleted by Nestor Peccia/esoc/ESA]
</font><br>
<font size="2" face="Calibri">Dear Daniele,</font> <br>
<br>
<font size="2" face="Calibri">I hope all is well with you. I think that during one of our conversations I mentioned that the CESG and the SANA Steering Group (SSG) were looking into the somewhat confusing state of our registries in the SANA. We have noted
that there are a number of issues and overlaps, particularly in the area of organization and person type registries. The attached presentation, "CCSDS SSG Name & Number Registries", describes the problem in significant detail and also spells out how we propose
to fix it. </font> <br>
<br>
<font size="2" face="Calibri">The presentaiton "CCSDS Registry Re-engineering" is the best current description of the form of "what" we propose to do. What we discovered in analyzing the set of CCSDS registries is that there is a set of registries that have
to do with the "CCSDS enterprise", the agencies, observers, affiliates, and the people that they appoint to do certain tasks or that have certain roles. But what we also discovered is that some of these registries are well formed, others less so, but that
there were overlaps and gaps. </font> <br>
<br>
<font size="2" face="Calibri">We have a proposed plan for clearing all of this up.</font><br>
<br>
<font size="2" face="Calibri">The reason why I am contacting you as DAI WG chair, is the "how" we propose to do it. There are several parts to this that need to have CESG review and CMC concurrence. There is one, in particular, that needs WG concurrence.
In the case of your MACAO Blue Book (CCSDS 630x0b1) we wish to leverage the very good work that has already been done to define and create registries for agencies, and agency sub-elements, and for persons with certain roles. The proposed extensions add some
fields for unique identifiers and also a mechanism for adding new roles for identified persons to allow them to manage other registries than just the MACAO. This is a request for your WG to review what we have proposed to see if you can concur with the proposed
changes which are in the attached mark-up. </font> <br>
<br>
<font size="2" face="Calibri">The related changes we propose require some related edits to other documents. I have drafts of all of these prepared and CESG review is just awaiting some final adjustments:</font><br>
<br>
<font size="2" face="Calibri">SANA YB (CCSDS 313x0y1, SEA/SSG)</font> <br>
<font size="2" face="Calibri">SCID BB (CCSDS 320x0b6, CMC / Secretariat)</font> <br>
<br>
<font size="2" face="Calibri">And the creation of a new one:</font> <br>
<br>
<font size="2" face="Calibri">Registry Management Policy (SEA/SSG)</font> <br>
<br>
<font size="2" face="Calibri">What these changes do is to update the SANA Yellow Book to require WGs to use (or extend) existing registries where that makes sense, and to tell the SANA, in a timely way, when they are creating any new registries or proposing
changes to existing registries. The key registries are those relating to organizations (agency, observer, affiliate) and to persons (with various roles). The change to the SCID BB is to add a few fields to that spec, including unique object identifiers for
spacecraft, and to extend the current definitions of Agency Representative, the person nominated by an Agency (or Observer) to request changes to the SCID registry. We want to use the general pattern for "Agency Representative" as the way to manage all persons
who are assigned (one or more) roles by their agencies. Thus one person (AR) might have only one Role (</font><font size="1" face="Times New Roman">Agency Rep for SCID</font><font size="2" face="Calibri">) or they might have more than one Role (</font><font size="1" face="Times New Roman">Agency
Rep for SCID, Agency Rep for MACAO, MACAO RP submitter).</font> <br>
<br>
<font size="2" face="Calibri">After working over these concepts with the SSG, SANA Operator, and CCSDS website team we are convinced that a separate Registry Management Policy will be the best way to approach this overall body of work, so I have prepared a
draft of that too. That still needs some final changes, so I am not sending it now, just the drafts of the SANA, SCID, and MACAO documents and the analysis and re-engineering materials.</font><br>
<br>
<font size="2" face="Calibri">I think you will find that the proposed changes do not affect any of the key fields, contents, or intent of what has already been defined in the MACAO. What they are intended to do it to adopt and extend the existing features
so that these core enterprise registries can be re-used, and extended, by others. Please review these proposed changes with your WG at the earliest opportunity and let us know if there is an issue. We would all prefer to re-use and extend what is there instead
of creating a parallel set of registries, but we can do that if it is deemed necessary.</font><br>
<br>
<font size="2" face="Calibri">Very best regards, Peter</font> <br>
<font size="2" face="Calibri"> </font> <br>
<br>
<br>
<br>
<br>
<br>
<br>
<tt><font size="2">_______________________________________________<br>
Moims-dai mailing list<br>
<a href="mailto:Moims-dai@mailman.ccsds.org">Moims-dai@mailman.ccsds.org</a><br>
</font></tt><a href="http://mailman.ccsds.org/mailman/listinfo/moims-dai"><tt><font size="2">http://mailman.ccsds.org/mailman/listinfo/moims-dai</font></tt></a><tt><font size="2"><br>
</font></tt><br>
<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>
</div>
</div>
</blockquote>
</span>
</body>
</html>