<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=us-ascii">
<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:"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: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:12.0pt;
font-family:"Times New Roman","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";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#44546A;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@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="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Calibri","sans-serif";color:#44546A">Great, thanks much.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Calibri","sans-serif";color:#44546A"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Calibri","sans-serif";color:#44546A"> --keith<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:14.0pt;font-family:"Calibri","sans-serif";color:#44546A"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> Felix.Flentge@esa.int [mailto:Felix.Flentge@esa.int]
<br>
<b>Sent:</b> Friday, October 17, 2014 10:06 AM<br>
<b>To:</b> Scott, Keith L.<br>
<b>Cc:</b> Chris Taylor (chris.taylor@esa.int); Pitts, Robert L. (MSFC-EO50)[HOSC SERVICES CONTRACT]; sis-dtn@mailman.ccsds.org<br>
<b>Subject:</b> Re: DTPC RID against BP-for-CCSDS<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Dear Keith,</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">fine for me. I have been assuming that there are some practical reasons to have it in the BP book and I am happy to hear that there is also an implementation in DTN2.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Regards,<br>
Felix</span> <br>
<span style="font-size:10.0pt;font-family:"Arial","sans-serif"">-- <br>
Dr. Felix Flentge<br>
ESA/ESOC - European Space Agency / European Space Operations Centre<br>
Human Spaceflight and Operations, Ground Segment Engineering Department, HSO-GIB<br>
ESA/ESOC, Robert-Bosch-Strasse 5, D-64293 Darmstadt, Germany<br>
Tel: +49 6151 90 3173<br>
e-mail: <a href="mailto:Felix.Flentge@esa.int">Felix.Flentge@esa.int</a></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"">"Scott, Keith L." <<a href="mailto:kscott@mitre.org">kscott@mitre.org</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"">"<a href="mailto:felix.flentge@esa.int">felix.flentge@esa.int</a>" <<a href="mailto:felix.flentge@esa.int">felix.flentge@esa.int</a>>,
</span><br>
<span style="font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F">Cc: </span><span style="font-size:7.5pt;font-family:"Arial","sans-serif"">"Chris Taylor (<a href="mailto:chris.taylor@esa.int">chris.taylor@esa.int</a>)" <<a href="mailto:chris.taylor@esa.int">chris.taylor@esa.int</a>>,
"Pitts, Robert L. (MSFC-EO50)[HOSC SERVICES CONTRACT]" <<a href="mailto:robert.l.pitts@nasa.gov">robert.l.pitts@nasa.gov</a>>, "<a href="mailto:sis-dtn@mailman.ccsds.org">sis-dtn@mailman.ccsds.org</a>" <<a href="mailto:sis-dtn@mailman.ccsds.org">sis-dtn@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"">17/10/2014 15:26</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"">DTPC RID against BP-for-CCSDS</span>
<o:p></o:p></p>
<div class="MsoNormal" align="center" style="margin-left:.5in;text-align:center">
<hr size="3" width="100%" noshade="" style="color:#A0A0A0" align="center">
</div>
<p class="MsoNormal" style="margin-left:.5in"><br>
<br>
<br>
<span style="font-size:13.5pt;font-family:"Calibri","sans-serif"">Felix,</span> <br>
<span style="font-size:13.5pt;font-family:"Calibri","sans-serif""> </span> <br>
<span style="font-size:13.5pt;font-family:"Calibri","sans-serif"">First, thanks very much for your review and RIDS on the BP-for-CCSDS book. I think they’ve improved the book’s overall quality.</span>
<br>
<span style="font-size:13.5pt;font-family:"Calibri","sans-serif""> </span> <br>
<span style="font-size:13.5pt;font-family:"Calibri","sans-serif""> </span> <br>
<span style="font-size:13.5pt;font-family:"Calibri","sans-serif"">Regarding your RID against the Delay-Tolerant Payload Conditioning Specification:</span>
<br>
<span style="font-size:13.5pt;font-family:"Calibri","sans-serif"">I am wondering if "Annex E Delay-Tolerant Payload Conditioning Specification" should not be a separate document. For me it is a specific way (an “application service”) of how to apply BP and
does not need to be part of the CCSDS BP Standard. Also, I am not sure about the maturity of that protocol (Has it been tested with two independent implementations?). So, it might be better to separate it (maybe as a Magenta Book) and have "independent lifecycles".</span>
<br>
<span style="font-size:13.5pt;font-family:"Calibri","sans-serif""> </span> <br>
<span style="font-size:13.5pt;font-family:"Calibri","sans-serif""> </span> <br>
<span style="font-size:13.5pt;font-family:"Calibri","sans-serif"">I think the WG’s current leaning is to reject the RID and keep the DTPC annex in the book. I would concur that in a perfect world it would be split off as a separate book, but as I recall the
capability was strongly desired and there was some concern about ‘# of books explosion’ and the agency review resources that would be needed if it were done separately. Also, removing the annex now would require another agency review.</span>
<br>
<span style="font-size:13.5pt;font-family:"Calibri","sans-serif""> </span> <br>
<span style="font-size:13.5pt;font-family:"Calibri","sans-serif"">There are two implementations of DTPC (ION and DTN2), and since it’s a normative part of the book it WILL be interoperability tested before the book goes Blue.</span>
<br>
<span style="font-size:13.5pt;font-family:"Calibri","sans-serif""> </span> <br>
<span style="font-size:13.5pt;font-family:"Calibri","sans-serif""> </span> <br>
<span style="font-size:13.5pt;font-family:"Calibri","sans-serif"">Given the above, I think the WG would like to reject the RID and keep DTPC in the current book. Would you be able to concur with this?</span>
<br>
<span style="font-size:13.5pt;font-family:"Calibri","sans-serif""> </span> <br>
<span style="font-size:13.5pt;font-family:"Calibri","sans-serif""> Best Regards,</span>
<br>
<span style="font-size:13.5pt;font-family:"Calibri","sans-serif""> </span> <br>
<span style="font-size:13.5pt;font-family:"Calibri","sans-serif""> --keith</span>
<br>
<span style="font-size:13.5pt;font-family:"Calibri","sans-serif""> </span> <br>
<span style="font-size:13.5pt;font-family:"Calibri","sans-serif""> </span> <br>
<span style="font-size:10.0pt;font-family:"Calibri","sans-serif""> </span> <br>
<b><span style="font-size:7.5pt;font-family:"Calibri","sans-serif";color:#5F5F5F">Dr. Keith Scott</span></b><span style="font-size:7.5pt;font-family:"Calibri","sans-serif";color:#5F5F5F">
Office: +1.703.983.6547</span> <br>
<span style="font-size:7.5pt;font-family:"Calibri","sans-serif";color:#5F5F5F">Chief Engineer, J86A Fax: +1.703.983.7142</span>
<br>
<span style="font-size:7.5pt;font-family:"Calibri","sans-serif";color:#5F5F5F">Communications Network Engineering & Analysis Email:
<a href="mailto:kscott@mitre.org">kscott@mitre.org</a></span> <br>
<a href="http://www.mitre.org/"><span style="font-size:7.5pt;font-family:"Calibri","sans-serif";color:#0082BF">The MITRE Corporation</span></a><span style="font-size:7.5pt;font-family:"Calibri","sans-serif";color:#5F5F5F">
M/S H300</span> <br>
<span style="font-size:7.5pt;font-family:"Calibri","sans-serif";color:#5F5F5F">7515 Colshire Drive</span>
<br>
<span style="font-size:7.5pt;font-family:"Calibri","sans-serif";color:#5F5F5F">McLean, VA 22102</span>
<br>
<span style="font-size:7.5pt;font-family:"Calibri","sans-serif";color:#5F5F5F"> </span>
<br>
<span style="font-size:7.5pt;font-family:"Calibri","sans-serif";color:#5F5F5F">Area Director,</span><span style="font-size:7.5pt;font-family:"Calibri","sans-serif"">
</span><a href="http://www.ccsds.org/"><span style="font-size:7.5pt;font-family:"Calibri","sans-serif";color:#0082BF">CCSDS</span></a><span style="font-size:7.5pt;font-family:"Calibri","sans-serif"">
</span><a href="http://cwe.ccsds.org/sis/default.aspx"><span style="font-size:7.5pt;font-family:"Calibri","sans-serif";color:#0082BF">Space Internetworking Services</span></a>
<br>
<span style="font-size:7.5pt;font-family:"Calibri","sans-serif""> </span> <br>
<span style="font-size:7.5pt;font-family:"Calibri","sans-serif";color:#5F5F5F">MITRE self-signs its own certificates. Information about the MITRE PKI Certificate Chain is available from
</span><a href="http://www.mitre.org/tech/mii/pki/"><span style="font-size:7.5pt;font-family:"Calibri","sans-serif";color:#0082BF">http://www.mitre.org/tech/mii/pki/</span></a>
<br>
<span style="font-size:13.5pt;font-family:"Calibri","sans-serif""> </span> <br>
<span style="font-size:13.5pt;font-family:"Calibri","sans-serif""> </span> <o:p></o:p></p>
<pre style="margin-left:.5in">This message and any attachments are intended for the use of the addressee or addressees only.<o:p></o:p></pre>
<pre style="margin-left:.5in">The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its<o:p></o:p></pre>
<pre style="margin-left:.5in">content is not permitted.<o:p></o:p></pre>
<pre style="margin-left:.5in">If you received this message in error, please notify the sender and delete it from your system.<o:p></o:p></pre>
<pre style="margin-left:.5in">Emails can be altered and their integrity cannot be guaranteed by the sender.<o:p></o:p></pre>
<pre style="margin-left:.5in"><o:p> </o:p></pre>
<pre style="margin-left:.5in">Please consider the environment before printing this email.<o:p></o:p></pre>
</div>
</body>
</html>