<font size=2 face="sans-serif">Dear Keith,</font>
<br>
<br><font size=2 face="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.</font>
<br>
<br><font size=2 face="sans-serif">Regards,<br>
Felix</font>
<br><font size=2 face="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: Felix.Flentge@esa.int</font>
<br>
<br>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">"Scott, Keith
L." <kscott@mitre.org></font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">"felix.flentge@esa.int"
<felix.flentge@esa.int>, </font>
<br><font size=1 color=#5f5f5f face="sans-serif">Cc:
</font><font size=1 face="sans-serif">"Chris Taylor
(chris.taylor@esa.int)" <chris.taylor@esa.int>, "Pitts,
Robert L. (MSFC-EO50)[HOSC SERVICES CONTRACT]" <robert.l.pitts@nasa.gov>,
"sis-dtn@mailman.ccsds.org" <sis-dtn@mailman.ccsds.org></font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">17/10/2014 15:26</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">DTPC RID against
BP-for-CCSDS</font>
<br>
<hr noshade>
<br>
<br>
<br><font size=4 face="Calibri">Felix,</font>
<br><font size=4 face="Calibri"> </font>
<br><font size=4 face="Calibri">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.</font>
<br><font size=4 face="Calibri"> </font>
<br><font size=4 face="Calibri"> </font>
<br><font size=4 face="Calibri">Regarding your RID against the Delay-Tolerant
Payload Conditioning Specification:</font>
<br><font size=4 face="Calibri">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".</font>
<br><font size=4 face="Calibri"> </font>
<br><font size=4 face="Calibri"> </font>
<br><font size=4 face="Calibri">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.</font>
<br><font size=4 face="Calibri"> </font>
<br><font size=4 face="Calibri">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.</font>
<br><font size=4 face="Calibri"> </font>
<br><font size=4 face="Calibri"> </font>
<br><font size=4 face="Calibri">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?</font>
<br><font size=4 face="Calibri"> </font>
<br><font size=4 face="Calibri">
Best Regards,</font>
<br><font size=4 face="Calibri"> </font>
<br><font size=4 face="Calibri">
--keith</font>
<br><font size=4 face="Calibri"> </font>
<br><font size=4 face="Calibri"> </font>
<br><font size=2 face="Calibri"> </font>
<br><font size=1 color=#5f5f5f face="Calibri"><b>Dr. Keith Scott</b>
Office: +1.703.983.6547</font>
<br><font size=1 color=#5f5f5f face="Calibri">Chief Engineer, J86A
Fax: +1.703.983.7142</font>
<br><font size=1 color=#5f5f5f face="Calibri">Communications Network Engineering
& Analysis
Email: kscott@mitre.org</font>
<br><a href=http://www.mitre.org/><font size=1 color=#0082bf face="Calibri"><u>The
MITRE Corporation</u></font></a><font size=1 color=#5f5f5f face="Calibri">
M/S H300</font>
<br><font size=1 color=#5f5f5f face="Calibri">7515 Colshire Drive</font>
<br><font size=1 color=#5f5f5f face="Calibri">McLean, VA 22102</font>
<br><font size=1 color=#5f5f5f face="Calibri"> </font>
<br><font size=1 color=#5f5f5f face="Calibri">Area Director,</font><font size=1 face="Calibri">
</font><a href=http://www.ccsds.org/><font size=1 color=#0082bf face="Calibri"><u>CCSDS</u></font></a><font size=1 face="Calibri">
</font><a href=http://cwe.ccsds.org/sis/default.aspx><font size=1 color=#0082bf face="Calibri"><u>Space
Internetworking Services</u></font></a>
<br><font size=1 face="Calibri"> </font>
<br><font size=1 color=#5f5f5f face="Calibri">MITRE self-signs its own
certificates. Information about the MITRE PKI Certificate Chain is
available from </font><a href=http://www.mitre.org/tech/mii/pki/><font size=1 color=#0082bf face="Calibri"><u>http://www.mitre.org/tech/mii/pki/</u></font></a>
<br><font size=4 face="Calibri"> </font>
<br><font size=4 face="Calibri"> </font>
<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>