<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body dir="auto">
Sounds like a good plan.<br>
<br>
<div id="AppleMailSignature" dir="ltr">
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt;"><span style="background-color: rgba(255, 255, 255, 0);">Daniel L. Oltrogge<o:p></o:p></span></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt;"><span style="background-color: rgba(255, 255, 255, 0);">Director, Center for Space Standards and Innovation<o:p></o:p></span></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt;"><span style="background-color: rgba(255, 255, 255, 0);">Analytical Graphics, Incorporated<o:p></o:p></span></p>
<p class="MsoNormal" style="margin: 0in 0in 0.0001pt;"><span style="background-color: rgba(255, 255, 255, 0);">Voice: <a href="tel:719-482-4552" dir="ltr" x-apple-data-detectors="true" x-apple-data-detectors-type="telephone" x-apple-data-detectors-result="1">719-482-4552</a> ҉
E-mail: <a href="mailto:oltrogge@agi.com" dir="ltr" x-apple-data-detectors="true" x-apple-data-detectors-type="link" x-apple-data-detectors-result="2">oltrogge@agi.com</a></span></p>
</div>
<div dir="ltr"><br>
On Jun 7, 2019, at 18:29, Berry, David S (3920) <<a href="mailto:david.s.berry@jpl.nasa.gov">david.s.berry@jpl.nasa.gov</a>> wrote:<br>
<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:0 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Courier;
panose-1:2 0 5 0 0 0 0 0 0 0;}
@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:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"Times New Roman \(Body CS\)";
panose-1:2 2 6 3 5 4 5 2 3 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:Courier;
color:windowtext;}
p.p1, li.p1, div.p1
{mso-style-name:p1;
margin:0in;
margin-bottom:.0001pt;
font-size:7.0pt;
font-family:Helvetica;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@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]-->
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier">Dan, Alexandru:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier"><o:p> </o:p></span></p>
<p class="p1"><span style="font-size:12.0pt;font-family:Courier">Regarding THRUST_ACCELERATION: There are two instances of this keyword in the document (one in Table 3-3 and one in Annex A), and five total instances of the word "acceleration" (four associated
with this keyword). The fifth instance of "acceleration" is irrelevant to this keyword. The Description in Table 3-3 states "The object’s acceleration due to
<span style="color:red">in-track thrust </span>used to propagate the state vector and covariance to NOMINAL_RENTRY_EPOCH (if a controlled re-entry)", which seems to clearly indicate the in-track nature of the acceleration. The Description in Annex A (the ICS
Proforma) states "Object’s acceleration used in OD and propagation", i.e., it does not include the "in-track" qualification. Although Section 3 and Annex A are both normative, I think that implementers are more likely to use Table 3-3 than Annex A in creating
an RDM processor. However, it would be easy to add the word "in-track" in Annex A; page numbering would NOT be affected.<o:p></o:p></span></p>
<p class="p1"><span style="font-size:12.0pt;font-family:Courier"><o:p> </o:p></span></p>
<p class="p1"><span style="font-size:12.0pt;font-family:Courier">Regarding RECOMMENDED_OD_SPAN: It's an optional keyword, and leaving it in the document seems fairly innocuous at this point. It's been in the document since RDM Draft 0 in July 2016. The keyword
was used in some of the prototype RDM samples. <o:p></o:p></span></p>
<p class="p1"><span style="font-size:12.0pt;font-family:Courier"><o:p> </o:p></span></p>
<p class="p1"><b><span style="font-size:12.0pt;font-family:Courier">MY PROPOSAL</span></b><span style="font-size:12.0pt;font-family:Courier">:<o:p></o:p></span></p>
<p class="p1"><span style="font-size:12.0pt;font-family:Courier"><o:p> </o:p></span></p>
<p class="p1"><span style="font-size:12.0pt;font-family:Courier">1. THRUST_ACCELERATION: I add the word "in-track" to the instance in Annex A before sending the document to Mario for his Area Director Review.<o:p></o:p></span></p>
<p class="p1"><span style="font-size:12.0pt;font-family:Courier"><o:p> </o:p></span></p>
<p class="p1"><span style="font-size:12.0pt;font-family:Courier">2. RECOMMENDED_OD_SPAN: I suggest we leave it in the document.<o:p></o:p></span></p>
<p class="p1"><span style="font-size:12.0pt;font-family:Courier"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier">Regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier">David<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:Courier"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">MOIMS-NAV-EXEC <<a href="mailto:moims-nav-exec-bounces@mailman.ccsds.org">moims-nav-exec-bounces@mailman.ccsds.org</a>> on behalf
of "Alexandru Mancas (external)" <<a href="mailto:Alexandru.Mancas@esa.int">Alexandru.Mancas@esa.int</a>><br>
<b>Date: </b>Friday, June 7, 2019 at 5:10 AM<br>
<b>To: </b>"Oltrogge, Daniel" <<a href="mailto:doltrogge@agi.com">doltrogge@agi.com</a>><br>
<b>Cc: </b>"<a href="mailto:moims-nav-exec@mailman.ccsds.org">moims-nav-exec@mailman.ccsds.org</a>" <<a href="mailto:moims-nav-exec@mailman.ccsds.org">moims-nav-exec@mailman.ccsds.org</a>><br>
<b>Subject: </b>[EXTERNAL] Re: [MOIMS-NAV-EXEC] [CCSDS/RDM] Final Re-entry Data Message Red Book (v1.7) and CRM<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Dear Daniel,</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">My understanding is that at this point (after agency review and prototyping) we are dealing with editorial comments only. There were multiple opportunities to get technical comments during the White
Book iterations. I think removing/re-scoping keywords is well beyond our current purpose, could result in the need to redo at least some of the prototyping, and set back the entire process by at least one year. If you still have technical points you do not
think are addressed in Red Book 1.7, I suggest we deal with those in RDM v2.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Best regards</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Alexandru Mancas</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">______________________________________________________________<br>
<br>
</span><span style="font-size:7.5pt;font-family:"Verdana",sans-serif;color:#00A1E0">ir Alexandru Mancas</span>
<br>
<span style="font-size:7.5pt;font-family:"Verdana",sans-serif;color:gray">GMV Insyen AG</span>
<br>
<span style="font-size:7.5pt;font-family:"Verdana",sans-serif;color:gray">Space Debris Monitoring Systems Engineer<br>
Space Debris Office (OPS-SD) | Directorate of Operations</span> <br>
<span style="font-size:7.5pt;font-family:"Verdana",sans-serif;color:gray"> </span>
<br>
<b><span style="font-size:7.5pt;font-family:"Verdana",sans-serif;color:gray">ESA/ESOC</span></b><span style="font-size:7.5pt;font-family:"Verdana",sans-serif;color:gray"><br>
Robert-Bosch Str. 5<br>
64293, Darmstadt, Germany<br>
<a href="mailto:alexandru.mancas@esa.int">alexandru.mancas@esa.int</a> | </span><a href="www.esa.int"><span style="font-size:7.5pt;font-family:"Verdana",sans-serif;color:gray">www.esa.int</span></a><span style="font-size:7.5pt;font-family:"Verdana",sans-serif;color:gray"><br>
T +49 6151 90 2205</span> <o:p></o:p></p>
<p><span style="font-size:7.5pt;font-family:"Verdana",sans-serif;color:gray">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.
<br>
<br>
Please consider the environment before printing this email.</span> <br>
<br>
<br>
<br>
<span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#5F5F5F">From: </span><span style="font-size:7.5pt;font-family:"Arial",sans-serif">"Oltrogge, Daniel" <<a href="mailto:doltrogge@agi.com">doltrogge@agi.com</a>></span>
<br>
<span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#5F5F5F">To: </span><span style="font-size:7.5pt;font-family:"Arial",sans-serif">"Alexandru Mancas (external)" <<a href="mailto:Alexandru.Mancas@esa.int">Alexandru.Mancas@esa.int</a>>,
"<a href="mailto:moims-nav-exec@mailman.ccsds.org">moims-nav-exec@mailman.ccsds.org</a>" <<a href="mailto:moims-nav-exec@mailman.ccsds.org">moims-nav-exec@mailman.ccsds.org</a>></span>
<br>
<span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#5F5F5F">Date: </span><span style="font-size:7.5pt;font-family:"Arial",sans-serif">07/06/2019 11:56</span>
<br>
<span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#5F5F5F">Subject: </span><span style="font-size:7.5pt;font-family:"Arial",sans-serif">RE: [MOIMS-NAV-EXEC] [CCSDS/RDM] Final Re-entry Data Message Red Book (v1.7) and CRM</span>
<o:p></o:p></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="0" width="100%" noshade="" style="color:#A0A0A0" align="center">
</div>
<p class="MsoNormal"><br>
<br>
<br>
<span style="font-size:12.0pt">I want to get to the beer stage as well, but I hope that we can first iterate on these comments and proposed dispositions.</span>
<br>
<span style="font-size:12.0pt"> </span> <br>
<span style="font-size:12.0pt">Regarding </span><span style="font-size:10.0pt">THRUST_ACCELERATION, if the intent is that it be limited to in-track, then that should more clearly be stated. I believe the reason this was constrained in that way in the CDM is
because that is what the 18<sup>th</sup> can model. </span> <br>
<span style="font-size:12.0pt"> </span> <br>
<span style="font-size:12.0pt">Regarding the </span><span style="font-size:10.0pt">RECOMMENDED_OD_SPAN, the suggestion that this should be there to be consistent with the CDM is confusing to me, in that there is other content in the CDM that is not incorporated
in the RDM as well. I’m not seeing the benefit of this keyword being included in the RDM.</span>
<br>
<span style="font-size:12.0pt"> </span> <br>
<span style="font-size:10.0pt">Dan</span> <br>
<span style="font-size:10.0pt"> </span> <br>
<span style="font-size:10.0pt">Daniel L. Oltrogge</span> <br>
<span style="font-size:10.0pt">Director, Center for Space Standards and Innovation</span>
<br>
<span style="font-size:10.0pt">Analytical Graphics, Incorporated</span> <br>
<span style="font-size:10.0pt">Voice: 719-482-4552 </span><span style="font-size:13.5pt">҉</span><span style="font-size:10.0pt"> E-mail:
</span><a href="mailto:oltrogge@agi.com"><span style="font-size:10.0pt;color:#0082BF">oltrogge@agi.com</span></a>
<br>
<span style="font-size:12.0pt"> </span> <br>
<b><span style="font-size:10.0pt">From:</span></b><span style="font-size:10.0pt"> MOIMS-NAV-EXEC <<a href="mailto:moims-nav-exec-bounces@mailman.ccsds.org">moims-nav-exec-bounces@mailman.ccsds.org</a>>
<b>On Behalf Of </b>Alexandru Mancas (external)<b><br>
Sent:</b> Friday, June 7, 2019 3:10 AM<b><br>
To:</b> <a href="mailto:moims-nav-exec@mailman.ccsds.org">moims-nav-exec@mailman.ccsds.org</a><b><br>
Subject:</b> [MOIMS-NAV-EXEC] [CCSDS/RDM] Final Re-entry Data Message Red Book (v1.7) and CRM</span>
<br>
<span style="font-size:10.0pt"> </span> <br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Dear CCSDS NAVigators,</span><span style="font-size:10.0pt">
<br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
Thank you all for your very hard work proofreading Red Book 1.6 of the Re-entry Data Message. I have incorporated your comments in the final RDM Red Book, version 1.7.</span><span style="font-size:10.0pt">
<br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
Please find attached RDM Red Book 1.7 and the CRM with all the comments and my answers.</span><span style="font-size:10.0pt">
<br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
David, please let me know if there are any more steps needed on my side to start the ball rolling on the publication process.</span><span style="font-size:10.0pt">
<br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
Best regards</span><span style="font-size:10.0pt"> </span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
Alexandru Mancas</span><span style="font-size:10.0pt"> <br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
______________________________________________________________<br>
</span><span style="font-size:7.5pt;font-family:"Verdana",sans-serif;color:#00A1E0"><br>
ir Alexandru Mancas</span><span style="font-size:10.0pt"> </span><span style="font-size:7.5pt;font-family:"Verdana",sans-serif;color:gray"><br>
GMV Insyen AG</span><span style="font-size:10.0pt"> </span><span style="font-size:7.5pt;font-family:"Verdana",sans-serif;color:gray"><br>
Space Debris Monitoring Systems Engineer<br>
Space Debris Office (OPS-SD) | Directorate of Operations</span><span style="font-size:10.0pt">
</span><span style="font-size:7.5pt;font-family:"Verdana",sans-serif;color:gray"><br>
</span><span style="font-size:10.0pt"> </span><b><span style="font-size:7.5pt;font-family:"Verdana",sans-serif;color:gray"><br>
ESA/ESOC</span></b><span style="font-size:7.5pt;font-family:"Verdana",sans-serif;color:gray"><br>
Robert-Bosch Str. 5<br>
64293, Darmstadt, Germany</span><u><span style="font-size:7.5pt;font-family:"Verdana",sans-serif;color:blue"><br>
</span></u><a href="mailto:alexandru.mancas@esa.int"><span style="font-size:7.5pt;font-family:"Verdana",sans-serif">alexandru.mancas@esa.int</span></a><span style="font-size:7.5pt;font-family:"Verdana",sans-serif;color:gray"> |
</span><a href="www.esa.int"><span style="font-size:7.5pt;font-family:"Verdana",sans-serif;color:gray">www.esa.int</span></a><span style="font-size:7.5pt;font-family:"Verdana",sans-serif;color:gray"><br>
T +49 6151 90 2205</span><span style="font-size:10.0pt"> </span><o:p></o:p></p>
<p style="margin-bottom:12.0pt"><span style="font-size:7.5pt;font-family:"Verdana",sans-serif;color:gray">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.
<br>
<br>
Please consider the environment before printing this email.</span> <br>
<span style="font-size:10.0pt;font-family:"Courier New"">This message is intended only for the recipient(s) named above. It may contain proprietary information and/or</span>
<br>
<span style="font-size:10.0pt;font-family:"Courier New"">protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received</span>
<br>
<span style="font-size:10.0pt;font-family:"Courier New"">this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect</span>
<br>
<span style="font-size:10.0pt;font-family:"Courier New"">personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (</span><a href="mailto:dpo@esa.int"><span style="font-size:10.0pt;font-family:"Courier New"">dpo@esa.int</span></a><span style="font-size:10.0pt;font-family:"Courier New"">).</span>
<o:p></o:p></p>
<pre>This message is intended only for the recipient(s) named above. It may contain proprietary information and/or<o:p></o:p></pre>
<pre>protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received<o:p></o:p></pre>
<pre>this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect<o:p></o:p></pre>
<pre>personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (<a href="mailto:dpo@esa.int">dpo@esa.int</a>).<o:p></o:p></pre>
</div>
</div>
</blockquote>
</body>
</html>