<font size=2 face="sans-serif">Scott,</font>
<br><font size=2 face="sans-serif"> just
as devil's advocate, since the Annex would not be exhaustive of all "specific
ways" of implementing the service, a caveat for the limits of applicability
of the Annex and for remarking that other "specific ways" can
be compliant with the Blue Book is strongly required.</font>
<br>
<br><font size=2 face="sans-serif">Regards</font>
<br>
<br><font size=2 face="sans-serif">Gian Paolo</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>, "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 16:24</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">[Sis-dtn] RE:
DTPC RID against BP-for-CCSDS</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Sent by:
</font><font size=1 face="sans-serif">sis-dtn-bounces@mailman.ccsds.org</font>
<br>
<hr noshade>
<br>
<br>
<br><font size=4 color=#37605e face="Calibri">Great, thanks much.</font>
<br><font size=4 color=#37605e face="Calibri"> </font>
<br><font size=4 color=#37605e face="Calibri">
--keith</font>
<br><font size=4 color=#37605e face="Calibri"> </font>
<br><font size=2 face="Calibri"><b>From:</b> Felix.Flentge@esa.int [</font><a href=mailto:Felix.Flentge@esa.int><font size=2 face="Calibri">mailto:Felix.Flentge@esa.int</font></a><font size=2 face="Calibri">]
<b><br>
Sent:</b> Friday, October 17, 2014 10:06 AM<b><br>
To:</b> Scott, Keith L.<b><br>
Cc:</b> Chris Taylor (chris.taylor@esa.int); Pitts, Robert L. (MSFC-EO50)[HOSC
SERVICES CONTRACT]; sis-dtn@mailman.ccsds.org<b><br>
Subject:</b> Re: DTPC RID against BP-for-CCSDS</font>
<br><font size=3 face="Times New Roman"> </font>
<br><font size=2 face="Arial">Dear Keith,</font><font size=3 face="Times New Roman">
<br>
</font><font size=2 face="Arial"><br>
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><font size=3 face="Times New Roman"> <br>
</font><font size=2 face="Arial"><br>
Regards,<br>
Felix</font><font size=3 face="Times New Roman"> </font><font size=2 face="Arial"><br>
-- <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: </font><a href=mailto:Felix.Flentge@esa.int><font size=2 color=blue face="Arial"><u>Felix.Flentge@esa.int</u></font></a><font size=3 face="Times New Roman">
<br>
<br>
<br>
</font><font size=1 color=#5f5f5f face="Arial"><br>
From: </font><font size=1 face="Arial">"Scott,
Keith L." <</font><a href=mailto:kscott@mitre.org><font size=1 color=blue face="Arial"><u>kscott@mitre.org</u></font></a><font size=1 face="Arial">></font><font size=3 face="Times New Roman">
</font><font size=1 color=#5f5f5f face="Arial"><br>
To: </font><font size=1 face="Arial">"</font><a href=mailto:felix.flentge@esa.int><font size=1 color=blue face="Arial"><u>felix.flentge@esa.int</u></font></a><font size=1 face="Arial">"
<</font><a href=mailto:felix.flentge@esa.int><font size=1 color=blue face="Arial"><u>felix.flentge@esa.int</u></font></a><font size=1 face="Arial">>,
</font><font size=1 color=#5f5f5f face="Arial"><br>
Cc: </font><font size=1 face="Arial">"Chris
Taylor (</font><a href=mailto:chris.taylor@esa.int><font size=1 color=blue face="Arial"><u>chris.taylor@esa.int</u></font></a><font size=1 face="Arial">)"
<</font><a href=mailto:chris.taylor@esa.int><font size=1 color=blue face="Arial"><u>chris.taylor@esa.int</u></font></a><font size=1 face="Arial">>,
"Pitts, Robert L. (MSFC-EO50)[HOSC SERVICES CONTRACT]" <</font><a href=mailto:robert.l.pitts@nasa.gov><font size=1 color=blue face="Arial"><u>robert.l.pitts@nasa.gov</u></font></a><font size=1 face="Arial">>,
"</font><a href="mailto:sis-dtn@mailman.ccsds.org"><font size=1 color=blue face="Arial"><u>sis-dtn@mailman.ccsds.org</u></font></a><font size=1 face="Arial">"
<</font><a href="mailto:sis-dtn@mailman.ccsds.org"><font size=1 color=blue face="Arial"><u>sis-dtn@mailman.ccsds.org</u></font></a><font size=1 face="Arial">></font><font size=3 face="Times New Roman">
</font><font size=1 color=#5f5f5f face="Arial"><br>
Date: </font><font size=1 face="Arial">17/10/2014
15:26</font><font size=3 face="Times New Roman"> </font><font size=1 color=#5f5f5f face="Arial"><br>
Subject: </font><font size=1 face="Arial">DTPC
RID against BP-for-CCSDS</font><font size=3 face="Times New Roman"> </font>
<div align=center>
<hr noshade></div>
<br><font size=3 face="Times New Roman"><br>
<br>
</font><font size=4 face="Calibri"><br>
Felix,</font><font size=3 face="Times New Roman"> </font><font size=4 face="Calibri"><br>
</font><font size=3 face="Times New Roman"> </font><font size=4 face="Calibri"><br>
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><font size=3 face="Times New Roman">
</font><font size=4 face="Calibri"><br>
</font><font size=3 face="Times New Roman"> </font><font size=4 face="Calibri"><br>
</font><font size=3 face="Times New Roman"> </font><font size=4 face="Calibri"><br>
Regarding your RID against the Delay-Tolerant Payload Conditioning Specification:</font><font size=3 face="Times New Roman">
</font><font size=4 face="Calibri"><br>
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><font size=3 face="Times New Roman">
</font><font size=4 face="Calibri"><br>
</font><font size=3 face="Times New Roman"> </font><font size=4 face="Calibri"><br>
</font><font size=3 face="Times New Roman"> </font><font size=4 face="Calibri"><br>
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><font size=3 face="Times New Roman">
</font><font size=4 face="Calibri"><br>
</font><font size=3 face="Times New Roman"> </font><font size=4 face="Calibri"><br>
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><font size=3 face="Times New Roman"> </font><font size=4 face="Calibri"><br>
</font><font size=3 face="Times New Roman"> </font><font size=4 face="Calibri"><br>
</font><font size=3 face="Times New Roman"> </font><font size=4 face="Calibri"><br>
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><font size=3 face="Times New Roman">
</font><font size=4 face="Calibri"><br>
</font><font size=3 face="Times New Roman"> </font><font size=4 face="Calibri"><br>
Best Regards,</font><font size=3 face="Times New Roman"> </font><font size=4 face="Calibri"><br>
</font><font size=3 face="Times New Roman"> </font><font size=4 face="Calibri"><br>
--keith</font><font size=3 face="Times New Roman">
</font><font size=4 face="Calibri"><br>
</font><font size=3 face="Times New Roman"> </font><font size=4 face="Calibri"><br>
</font><font size=3 face="Times New Roman"> </font><font size=2 face="Calibri"><br>
</font><font size=3 face="Times New Roman"> </font><font size=1 color=#5f5f5f face="Calibri"><b><br>
Dr. Keith Scott</b>
Office: +1.703.983.6547</font><font size=3 face="Times New Roman">
</font><font size=1 color=#5f5f5f face="Calibri"><br>
Chief Engineer, J86A
Fax:
+1.703.983.7142</font><font size=3 face="Times New Roman">
</font><font size=1 color=#5f5f5f face="Calibri"><br>
Communications Network Engineering & Analysis
Email: </font><a href=mailto:kscott@mitre.org><font size=1 color=blue face="Calibri"><u>kscott@mitre.org</u></font></a><font size=3 face="Times New Roman">
</font><font size=3 color=blue face="Times New Roman"><u><br>
</u></font><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><font size=3 face="Times New Roman">
</font><font size=1 color=#5f5f5f face="Calibri"><br>
7515 Colshire Drive</font><font size=3 face="Times New Roman"> </font><font size=1 color=#5f5f5f face="Calibri"><br>
McLean, VA 22102</font><font size=3 face="Times New Roman"> </font><font size=1 color=#5f5f5f face="Calibri"><br>
</font><font size=3 face="Times New Roman"> </font><font size=1 color=#5f5f5f face="Calibri"><br>
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><font size=3 face="Times New Roman">
</font><font size=1 face="Calibri"><br>
</font><font size=3 face="Times New Roman"> </font><font size=1 color=#5f5f5f face="Calibri"><br>
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><font size=3 face="Times New Roman">
</font><font size=4 face="Calibri"><br>
</font><font size=3 face="Times New Roman"> </font><font size=4 face="Calibri"><br>
</font><font size=3 face="Times New Roman"> </font>
<br><font size=2 face="Courier New">This message and any attachments are
intended for the use of the addressee or addressees only.</font>
<br><font size=2 face="Courier New">The unauthorised disclosure, use, dissemination
or copying (either in whole or in part) of its</font>
<br><font size=2 face="Courier New">content is not permitted.</font>
<br><font size=2 face="Courier New">If you received this message in error,
please notify the sender and delete it from your system.</font>
<br><font size=2 face="Courier New">Emails can be altered and their integrity
cannot be guaranteed by the sender.</font>
<br><font size=2 face="Courier New"> </font>
<br><font size=2 face="Courier New">Please consider the environment before
printing this email.</font><tt><font size=2>_______________________________________________<br>
Sis-dtn mailing list<br>
Sis-dtn@mailman.ccsds.org<br>
</font></tt><a href="http://mailman.ccsds.org/cgi-bin/mailman/listinfo/sis-dtn"><tt><font size=2>http://mailman.ccsds.org/cgi-bin/mailman/listinfo/sis-dtn</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>