<font size=2 face="sans-serif">Hi Bruno</font>
<br>
<br><font size=2 face="sans-serif">We can discuss in the meetings, but
at least for (2) I think nested TLV would be an overkill. Key lengths will
be the same within an OTAR uplink and thus the data field (V) spec that
we have now (n times [KeyID, Key]) following the T and L fields is much
more efficient. For the security log, we can discuss.</font>
<br>
<br><font size=2 face="sans-serif">In my opinion, we should try to avoid
nested TLV since it add another layer of complexity.</font>
<br><font size=2 face="sans-serif"><br>
Cheers,</font>
<br><font size=2 face="sans-serif">Daniel</font>
<br><font size=2 face="sans-serif"><br>
<br>
<br>
Dr. Daniel Fischer<br>
----------------------------<br>
Data Systems Manager<br>
Ground Segment Engineering Support Office (HSO-GE)<br>
Ground Systems Engineering Department<br>
Directorate of Human Spaceflight and Operations<br>
<br>
European Space Agency - ESOC<br>
Robert-Bosch-Str. 5<br>
D-64293 Darmstadt - Germany<br>
Tel: +49 (0) 6151 90 2718 - Fax: +49 (0) 6151 90 2718<br>
Web: </font><a href=http://www.esa.int/><font size=2 face="sans-serif">http://www.esa.int</font></a>
<br>
<br>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">"Saba Bruno"
<Bruno.Saba@cnes.fr></font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">"Daniel.Fischer@esa.int"
<Daniel.Fischer@esa.int>, "sls-sea-dls@mailman.ccsds.org"
<sls-sea-dls@mailman.ccsds.org></font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">24/09/2015 15:40</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">RE: [Sls-sea-dls]
[SDLS Extended Procedures] TLV Format Question</font>
<br>
<hr noshade>
<br>
<br>
<br><font size=2 color=#004080 face="Calibri">Dear all,</font>
<br><font size=2 color=#004080 face="Calibri"> </font>
<br><font size=2 color=#004080 face="Calibri">In reply to Daniel’s question,
I can see at least two use cases of nested TLV messages :</font>
<br><font size=2 color=#004080 face="Calibri"> </font>
<br><font size=2 color=#004080 face="Calibri">1) Dump
of the “security log”, where the overall message complies with TLV format,
with many embedded TLV messages inside (at least one per event),</font>
<br><font size=2 color=#004080 face="Calibri">2) Key
upload message (OTAR), each key being a TLV massage in itself.</font>
<br><font size=2 color=#004080 face="Calibri"> </font>
<br><font size=2 color=#004080 face="Calibri">Cheers,</font>
<br><font size=2 color=#004080 face="Calibri"> </font>
<br><font size=2 color=#004080 face="Calibri"> </font>
<br><font size=2 color=#004080 face="Arial">Bruno Saba</font><font size=3 color=#004080 face="Times New Roman">
</font><font size=2 color=#004080 face="Arial"><br>
CNES</font><font size=3 color=#004080 face="Times New Roman"> </font><font size=2 color=#004080 face="Arial"><br>
DCT/TV/IN</font><font size=3 color=#004080 face="Times New Roman"> </font><font size=2 color=#004080 face="Arial"><br>
18 Avenue Edouard Belin</font><font size=3 color=#004080 face="Times New Roman">
</font><font size=2 color=#004080 face="Arial"><br>
31401 TOULOUSE Cedex 9</font><font size=3 color=#004080 face="Times New Roman">
</font>
<br><font size=2 color=#004080 face="Arial">Tel : + 33 (0) 5 61 28 28 76</font><font size=3 color=#004080 face="Times New Roman">
</font><font size=2 color=#004080 face="Arial"><br>
Fax : + 33 (0) 5 61 28 19 96</font><font size=3 color=#004080 face="Times New Roman">
</font>
<br><font size=2 color=#004080 face="Calibri"> </font>
<br><font size=2 color=#004080 face="Calibri"> </font>
<br><font size=2 face="Tahoma"><b>De :</b> sls-sea-dls-bounces@mailman.ccsds.org
[</font><a href="mailto:sls-sea-dls-bounces@mailman.ccsds.org"><font size=2 face="Tahoma">mailto:sls-sea-dls-bounces@mailman.ccsds.org</font></a><font size=2 face="Tahoma">]
<b>De la part de</b> Daniel.Fischer@esa.int<b><br>
Envoyé :</b> jeudi 27 août 2015 09:55<b><br>
À :</b> sls-sea-dls@mailman.ccsds.org<b><br>
Objet :</b> [Sls-sea-dls] [SDLS Extended Procedures] TLV Format Question</font>
<br><font size=3 face="Times New Roman"> </font>
<br><font size=2 face="Arial">Dear all,</font><font size=3 face="Times New Roman">
<br>
</font><font size=2 face="Arial"><br>
I am working on the update of the Extended Procedures book.</font><font size=3 face="Times New Roman">
<br>
</font><font size=2 face="Arial"><br>
One of the things agreed during the last meeting was to describe better
the various possibilities of the TLV format. One of the items to be addressed
in nested procedures. i.e. putting another TLV inside the value field.
While I have no problem adding this to the spec, I am wondering if there
is a use case for this in the scope of the Extended Procedures. Looking
at the various proposed procedures, I could not find any.</font><font size=3 face="Times New Roman">
</font><font size=2 face="Arial"><br>
<br>
So if there is no use case for nesting in the scope of the book, do we
really need to specify it?</font><font size=3 face="Times New Roman"> <br>
</font><font size=2 face="Arial"><br>
Cheers,<br>
Daniel</font><font size=3 face="Times New Roman"> </font><font size=2 face="Arial"><br>
<br>
<br>
<br>
Dr. Daniel Fischer<br>
----------------------------<br>
Data Systems Manager<br>
Ground Systems Engineering Support Office<br>
Ground Systems Engineering Department<br>
Directorate of Human Spaceflight and Operations<br>
<br>
European Space Agency - ESOC<br>
Robert-Bosch-Str. 5<br>
D-64293 Darmstadt - Germany<br>
Tel: +49 (0) 6151 90 2718 - Fax: +49 (0) 6151 90 2718<br>
Web: </font><a href=http://www.esa.int/><font size=2 color=blue face="Arial"><u>http://www.esa.int</u></font></a>
<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>
<br>
<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>