<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Aptos;
panose-1:2 11 0 4 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:10.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
font-size:10.0pt;
font-family:"Calibri",sans-serif;}
p.p1, li.p1, div.p1
{mso-style-name:p1;
margin:0in;
font-size:9.0pt;
font-family:"Times New Roman",serif;
color:black;}
span.s1
{mso-style-name:s1;
font-family:"Arial",sans-serif;}
span.EmailStyle23
{mso-style-type:personal-reply;
font-family:"Aptos",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
mso-ligatures:none;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif">SEA Resolution - SEA-R-2024-09-01 Request Agency Review of D-DOR RDEF update 506.1_W_2<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif">The CCSDS Systems Engineering Area (SEA) Area Director,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif">CONSIDERING that the Delta-DOR Working Group (DDOR WG) has:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif">o Updated the original version of the Delta-DOR Raw Data Exchange Format (RDEF) CCSDS 506.1-W-2, and<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif">o Accommodated the new DOR tones (with reference to
</span><span lang="EN-GB" style="font-size:11.0pt;font-family:"Aptos",sans-serif">CCSDS 401.0-B update)
</span><span style="font-size:11.0pt;font-family:"Aptos",sans-serif">and the use of SANA registries, and that<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif">o The WG has reached consensus on requesting Agency review of this update, and<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif">o The SEA AD has reviewed this document and concurs that it is ready for Agency review.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif">RESOLVES to request The Secretariat to process the attached draft document and to send it for CESG, and then CMC, approval to release for Agency Review.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif">RECOMMENDS that the CESG and CMC approve this resolution and, finally<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif">REQUESTS that a CESG poll, and then a CMC poll, be conducted to approve release of this document for Agency review.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif"><o:p> </o:p></span></p>
<div id="mail-editor-reference-message-container">
<div>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><span lang="EN-GB" style="font-size:12.0pt;font-family:"Aptos",sans-serif;color:black">From:
</span></b><span lang="EN-GB" style="font-size:12.0pt;font-family:"Aptos",sans-serif;color:black">Javier De Vicente <Javier.DeVicente@esa.int><br>
<b>Date: </b>Wednesday, September 18, 2024 at 6:41</span><span lang="EN-GB" style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black"> </span><span lang="EN-GB" style="font-size:12.0pt;font-family:"Aptos",sans-serif;color:black">AM<br>
<b>To: </b>Shames, Peter M (US 312B) <peter.m.shames@jpl.nasa.gov><br>
<b>Cc: </b>Volk, Christopher P (US 335D) <christopher.p.volk@jpl.nasa.gov><br>
<b>Subject: </b>[EXTERNAL] RE: 506.1_W_2 for AD review: Updated version as per Spring24 discussions<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Aptos",sans-serif">Thanks Peter,</span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Aptos",sans-serif"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Aptos",sans-serif">I am fine with the edits, I made a small addition (blue text) in the case of B2.3, B2.4 and B2.5 (B2.3 shown as example):</span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Aptos",sans-serif"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Aptos",sans-serif">Format in the Alias field is DDOR:aaaa<span style="color:#4E95D9">, where each a value corresponds to an alphanumeric character</span>.</span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Aptos",sans-serif"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Aptos",sans-serif">Acronyms have been reviewed and updated.
</span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Aptos",sans-serif"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Aptos",sans-serif">Clean copy attached. I am also attaching the original graphic files in case you then proceed to forward to the Chief Technical Editor. Please copy us if you do so
so that we are aware.</span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Aptos",sans-serif"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Aptos",sans-serif">Note for yellow highlighted text: Linked to the final version of the RFM Systems Blue Book and the publication of rec. 2.5.7B.</span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Aptos",sans-serif"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Aptos",sans-serif">Regards,</span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Aptos",sans-serif"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Aptos",sans-serif"> Javier</span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Aptos",sans-serif"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Aptos",sans-serif"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt">From:</span></b><span style="font-size:11.0pt"> Shames, Peter M (US 312B) <peter.m.shames@jpl.nasa.gov>
<br>
<b>Sent:</b> Friday, September 13, 2024 2:56 AM<br>
<b>To:</b> Javier De Vicente <Javier.DeVicente@esa.int><br>
<b>Cc:</b> Volk, Christopher P (US 335D) <christopher.p.volk@jpl.nasa.gov><br>
<b>Subject:</b> Re: 506.1_W_2 for AD review: Updated version as per Spring24 discussions</span><span lang="EN-GB"><o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-GB"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif">Hi Javier,</span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif">I made a few edits to Annex B to further clarify what it is that I think you are trying to accomplish. See if it makes sense to you.</span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif">I also found a few missing acronyms… there may be more, please check.</span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif">If this is acceptable to the WG please send me back the clean copy to be sent out for review.</span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif">Thanks, Peter</span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<div id="mail-editor-reference-message-container">
<div>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><span lang="EN-GB" style="font-size:12.0pt;font-family:"Aptos",sans-serif;color:black">From:
</span></b><span lang="EN-GB" style="font-size:12.0pt;font-family:"Aptos",sans-serif;color:black">Javier De Vicente <</span><span lang="EN-GB"><a href="mailto:Javier.DeVicente@esa.int"><span style="font-size:12.0pt;font-family:"Aptos",sans-serif">Javier.DeVicente@esa.int</span></a></span><span lang="EN-GB" style="font-size:12.0pt;font-family:"Aptos",sans-serif;color:black">><br>
<b>Date: </b>Friday, August 23, 2024 at 7:15</span><span lang="EN-GB" style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black"> </span><span lang="EN-GB" style="font-size:12.0pt;font-family:"Aptos",sans-serif;color:black">AM<br>
<b>To: </b>Shames, Peter M (US 312B) <</span><span lang="EN-GB"><a href="mailto:peter.m.shames@jpl.nasa.gov"><span style="font-size:12.0pt;font-family:"Aptos",sans-serif">peter.m.shames@jpl.nasa.gov</span></a></span><span lang="EN-GB" style="font-size:12.0pt;font-family:"Aptos",sans-serif;color:black">><br>
<b>Cc: </b>Volk, Christopher P (US 335D) <</span><span lang="EN-GB"><a href="mailto:christopher.p.volk@jpl.nasa.gov"><span style="font-size:12.0pt;font-family:"Aptos",sans-serif">christopher.p.volk@jpl.nasa.gov</span></a></span><span lang="EN-GB" style="font-size:12.0pt;font-family:"Aptos",sans-serif;color:black">><br>
<b>Subject: </b>[EXTERNAL] RE: 506.1_W_2 for AD review: Updated version as per Spring24 discussions</span><span lang="EN-GB"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Aptos",sans-serif">Thanks Peter,</span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Aptos",sans-serif"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Aptos",sans-serif">Find attached the updated doc, which I hope addresses all your comments. As usual, clean and track change versions are attached.</span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Aptos",sans-serif"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Aptos",sans-serif">I also attach an answer to your question about local aperture and spacecraft names in table 5-1.</span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Aptos",sans-serif"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Aptos",sans-serif">Please also note my question about the publication of the future DDOR Architecture MB (CCSDS 506.2-R-0), where as far as I can tell the Agency Review process was
successful (see my email on May29th) but where I am not aware of any further developments. I have gone through my emails and unless I have missed it I haven’t seen an ‘Autorization to Publish’ the document.
</span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Aptos",sans-serif"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Aptos",sans-serif">Regards,</span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Aptos",sans-serif"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Aptos",sans-serif"> Javier</span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Aptos",sans-serif"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt">From:</span></b><span style="font-size:11.0pt"> Shames, Peter M (US 312B) <</span><span lang="EN-GB"><a href="mailto:peter.m.shames@jpl.nasa.gov"><span lang="EN-US" style="font-size:11.0pt">peter.m.shames@jpl.nasa.gov</span></a></span><span style="font-size:11.0pt">>
<br>
<b>Sent:</b> Tuesday, June 25, 2024 12:00 AM<br>
<b>To:</b> Javier De Vicente <</span><span lang="EN-GB"><a href="mailto:Javier.DeVicente@esa.int"><span lang="EN-US" style="font-size:11.0pt">Javier.DeVicente@esa.int</span></a></span><span style="font-size:11.0pt">><br>
<b>Cc:</b> Volk, Christopher P (US 335D) <</span><span lang="EN-GB"><a href="mailto:christopher.p.volk@jpl.nasa.gov"><span lang="EN-US" style="font-size:11.0pt">christopher.p.volk@jpl.nasa.gov</span></a></span><span style="font-size:11.0pt">><br>
<b>Subject:</b> Re: 506.1_W_2 for AD review: Updated version as per Spring24 discussions</span><span lang="EN-GB"><o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-GB"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif">Hi Javier,</span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif">Well, the ball is now within sight of the goal, but it’s not yet in the goal. Here is what is present, and what is missing:</span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif">In sec 1.6 you identify and name the several new SANA registries. Good.</span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif">In sec 4 you identify where the contents of the various registries are to be used in file names and headers. Good.</span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif">In sec 5, in table 5-1, it appears that you are still allowing local aperture and spacecraft names to be used instead of adopting the new, defined, names from the new SANA registries.
I do not understand how this provides interoperability.</span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif">In sec 6 you do reference using the new registries for mission, aperture, etc.</span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif">In Annex A you identify how the aperture, mission, agency, aliases are to be used. </span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif">The biggest missing part is the pieces that must appear in the SANA Considerations section, in Annex B. This is where, for each new registry that you wish to set up, you must
tell the SANA Operator what the fields are in the new registry, what the allowed values are, and what policies are to be used to assign values. You have parts of this defined within the other sections, like the size and format of the data fields and the keys
to be used. </span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif">In sec 5 & 6 you mention the sizes of the new fields you want to reference. Let’s just use Mission (spacecraft) as an example for now, but you’ll need to do the same for each
new registry that you require.</span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif">New Mission registry (Reference 8)</span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif">Create a registry that has the following fields:</span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:1.0in;text-indent:-.25in"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif">Mission Alias, 4 characters, alphameric</span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:1.0in;text-indent:-.25in"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif">Agency assigned Spacecraft Name, max 32 characters, copied from Spacecraft Registry, Name field, for reference
</span><span lang="EN-GB"><a href="https://urldefense.us/v3/__https:/sanaregistry.org/r/spacecraft/__;!!PvBDto6Hs4WbVuu7!K_9N8fwuqjQwFTCXdjdq5XNMlvoUmtbl-QvRpVzGAb6Cbpjq4_9kRJiPnsr1dMnxBIZAd_4hsNcwCsrxtyue2f7Xv9D-xgX2Yk9o$"><span lang="EN-US" style="font-size:11.0pt;font-family:"Aptos",sans-serif">https://sanaregistry.org/r/spacecraft/</span></a><o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:1.0in;text-indent:-.25in"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif">Spacecraft OID, from Spacecraft Registry, OID field,
</span><span lang="EN-GB"><a href="https://urldefense.us/v3/__https:/sanaregistry.org/r/spacecraft/__;!!PvBDto6Hs4WbVuu7!K_9N8fwuqjQwFTCXdjdq5XNMlvoUmtbl-QvRpVzGAb6Cbpjq4_9kRJiPnsr1dMnxBIZAd_4hsNcwCsrxtyue2f7Xv9D-xgX2Yk9o$"><span lang="EN-US" style="font-size:11.0pt;font-family:"Aptos",sans-serif">https://sanaregistry.org/r/spacecraft/</span></a><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="p1" style="margin-left:.5in"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif">Registration Rule (from 313x0y3):
</span>b)<span class="s1"> </span>Change requires an engineering review by a designated expert or expert group<span lang="EN-GB"><o:p></o:p></span></p>
<p class="p1" style="margin-left:.5in">(see 3.19). This is the Review Authority for the registry. The Review Authority for that registry is assigned by the CESG based on the WG recommendation.<span lang="EN-GB"><o:p></o:p></span></p>
<p class="p1" style="margin-left:.5in"> <span lang="EN-GB"><o:p></o:p></span></p>
<p class="p1" style="margin-left:.5in"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif">The Expert Group is the SEA D-DOR WG. Requests for a new Mission Alias registry entry shall be sent to the Chair of the SEA D-DOR WG, or, if the WG is no longer
operational, to the SEA AD. The Expert Group will assign the Alias and request the SANA Operator to create the entry, tied to the existing Spacecraft Name, and to make the update.</span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif">Do the same sort of thing for each of the other new “alias” registries that you need. This becomes both the design of the registries that the SANA operator will create and the
process for populating them, as needed. </span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif">I hope this makes sense.</span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif">Thanks, Peter</span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Aptos",sans-serif"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<div id="mail-editor-reference-message-container">
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><span lang="EN-GB" style="font-size:12.0pt;font-family:"Aptos",sans-serif;color:black">From:
</span></b><span lang="EN-GB" style="font-size:12.0pt;font-family:"Aptos",sans-serif;color:black">Javier De Vicente <</span><span lang="EN-GB"><a href="mailto:Javier.DeVicente@esa.int"><span style="font-size:12.0pt;font-family:"Aptos",sans-serif">Javier.DeVicente@esa.int</span></a></span><span lang="EN-GB" style="font-size:12.0pt;font-family:"Aptos",sans-serif;color:black">><br>
<b>Date: </b>Monday, June 24, 2024 at 1:35</span><span lang="EN-GB" style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black"> </span><span lang="EN-GB" style="font-size:12.0pt;font-family:"Aptos",sans-serif;color:black">AM<br>
<b>To: </b>Shames, Peter M (US 312B) <</span><span lang="EN-GB"><a href="mailto:peter.m.shames@jpl.nasa.gov"><span style="font-size:12.0pt;font-family:"Aptos",sans-serif">peter.m.shames@jpl.nasa.gov</span></a></span><span lang="EN-GB" style="font-size:12.0pt;font-family:"Aptos",sans-serif;color:black">><br>
<b>Cc: </b>Volk, Christopher P (US 335D) <</span><span lang="EN-GB"><a href="mailto:christopher.p.volk@jpl.nasa.gov"><span style="font-size:12.0pt;font-family:"Aptos",sans-serif">christopher.p.volk@jpl.nasa.gov</span></a></span><span lang="EN-GB" style="font-size:12.0pt;font-family:"Aptos",sans-serif;color:black">><br>
<b>Subject: </b>[EXTERNAL] FW: 506.1_W_2 for AD review: Updated version as per Spring24 discussions</span><span lang="EN-GB"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Aptos",sans-serif">I didn’t attach a clean version (no track changes) of the document, here it is.</span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Aptos",sans-serif"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Aptos",sans-serif">Regards,</span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Aptos",sans-serif"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Aptos",sans-serif"> Javier</span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Aptos",sans-serif"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Aptos",sans-serif"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt">From:</span></b><span style="font-size:11.0pt"> Javier De Vicente
<br>
<b>Sent:</b> Monday, June 24, 2024 10:23 AM<br>
<b>To:</b> Shames, Peter M (US 312B) <</span><span lang="EN-GB"><a href="mailto:peter.m.shames@jpl.nasa.gov"><span lang="EN-US" style="font-size:11.0pt">peter.m.shames@jpl.nasa.gov</span></a></span><span style="font-size:11.0pt">><br>
<b>Cc:</b> Volk, Christopher P (US 335D) <</span><span lang="EN-GB"><a href="mailto:christopher.p.volk@jpl.nasa.gov"><span lang="EN-US" style="font-size:11.0pt">christopher.p.volk@jpl.nasa.gov</span></a></span><span style="font-size:11.0pt">><br>
<b>Subject:</b> 506.1_W_2 for AD review: Updated version as per Spring24 discussions</span><span lang="EN-GB"><o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-GB"> <o:p></o:p></span></p>
<div id="mail-editor-reference-message-container">
<div>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Aptos",sans-serif">Hi Peter,</span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Aptos",sans-serif"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Aptos",sans-serif">It took a bit longer than expected, but here is the update of the DDOR RDEF BB following the discussions/agreements at the Spring24 meeting and a further review
of the updated doc by the DDOR WG.</span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Aptos",sans-serif"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Aptos",sans-serif">The text highlighted in yellow ‘assumes’ the update of CCSDS 401.0-B-32 to include PN DOR rec. 2.5.7.B (I guess as part of CCSDS 401.0-B-33, which I am not aware
has yet been published).</span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Aptos",sans-serif"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Aptos",sans-serif">Unless you tell me differently, I plan to send the doc to the SANA team upon your confirmation of readiness to submit to the CCSDS Chief Technical Editor.</span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Aptos",sans-serif"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Aptos",sans-serif">On another note, I am still awaiting feedback on the publication of the future DDOR Architecture MB (CCSDS 506.2-R-0), where as far as I can tell the Agency Review
process was successful (see my email on May29th). </span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Aptos",sans-serif"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Aptos",sans-serif">Regards,</span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Aptos",sans-serif"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Aptos",sans-serif"> Javier
</span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Aptos",sans-serif"> </span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Aptos",sans-serif"> </span><span lang="EN-GB"><o:p></o:p></span></p>
</div>
</div>
</div>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:12.0pt;font-family:"Aptos",sans-serif">This message is intended only for the recipient(s) named above. It may contain proprietary information and/or protected content. Any unauthorised disclosure, use,
retention or dissemination is prohibited. If you have received this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect personal data, in case of data privacy queries, please contact the ESA Data
Protection Officer (</span><span lang="EN-GB"><a href="mailto:dpo@esa.int"><span style="font-size:12.0pt;font-family:"Aptos",sans-serif">dpo@esa.int</span></a></span><span lang="EN-GB" style="font-size:12.0pt;font-family:"Aptos",sans-serif">).
</span><span lang="EN-GB"><o:p></o:p></span></p>
</div>
</div>
</div>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:12.0pt;font-family:"Aptos",sans-serif">This message is intended only for the recipient(s) named above. It may contain proprietary information and/or protected content. Any unauthorised disclosure, use,
retention or dissemination is prohibited. If you have received this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect personal data, in case of data privacy queries, please contact the ESA Data
Protection Officer (</span><span lang="EN-GB"><a href="mailto:dpo@esa.int"><span style="font-size:12.0pt;font-family:"Aptos",sans-serif">dpo@esa.int</span></a></span><span lang="EN-GB" style="font-size:12.0pt;font-family:"Aptos",sans-serif">).
</span><span lang="EN-GB"><o:p></o:p></span></p>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:12.0pt;font-family:"Aptos",sans-serif">This message is intended only for the recipient(s) named above. It may contain proprietary information and/or protected content. Any unauthorised disclosure, use,
retention or dissemination is prohibited. If you have received this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect personal data, in case of data privacy queries, please contact the ESA Data
Protection Officer (dpo@esa.int). <o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</body>
</html>