<font size=2 face="sans-serif">Gilles,</font>
<br>
<br><font size=2 face="sans-serif">as far as I remember some RFM WG members
expressed concerns about creating a GB since the MO of this group is to
develop BB first and the accompanying GB later to explain the BB. I think
we did not agree to proceed directly to checking agencies resources for
supporting a GB.</font>
<br>
<br><font size=2 face="sans-serif">Therefore, I would propose to change
the text from</font>
<br>
<br>
<br><font size=3 face="Times New Roman"><b>Way forward discussed and proposed:</b></font>
<br><font size=3 face="Wingdings">§ </font><font size=3 face="Times New Roman">Start
from the “Threats to space missions” GB to identify those threats which
could be advantageously mitigated by techniques at physical layer</font>
<br><font size=3 face="Wingdings">§ </font><font size=3 face="Times New Roman">Identify
corresponding security services which could be provided at physical layer</font>
<br><font size=3 color=red face="Wingdings">§ </font><font size=3 color=red face="Times New Roman">If
at least 2 agencies agree on providing resources, develop Green Book documenting
the appropriate physical layer security techniques providing those security
services.</font>
<br><font size=3 color=red face="Wingdings">§ </font><font size=3 color=red face="Times New Roman">If
at least 2 agencies agree on providing resources, develop Blue Book for
those physical layer security techniques which have reached the sufficient
level of maturity for standardization and which provide security services
needed by space missions in an efficient manner.</font>
<br>
<br>
<br>
<br><font size=2 face="sans-serif">to</font>
<br>
<br><font size=3 face="Times New Roman"><b>Way forward discussed and proposed:</b></font>
<br><font size=3 face="Wingdings">§ </font><font size=3 face="Times New Roman">Start
from the “Threats to space missions” GB to identify those threats which
could be advantageously mitigated by techniques at physical layer</font>
<br><font size=3 face="Wingdings">§ </font><font size=3 face="Times New Roman">Identify
corresponding security services which could be provided at physical layer</font>
<br><font size=3 color=red face="Wingdings">§ </font><font size=3 color=red face="Times New Roman">Discuss
possible future developments (Green Book and/or Blue Book on physical layer
security techniques) and associated timeline.</font>
<br>
<br><font size=2 face="sans-serif">Additionally, I propose to add a link
to the agreed tasks, changing the text from</font>
<br>
<br><font size=3 face="Times New Roman">I.Aguilar and C.Sheehe have agreed
to continue investigating the subject following the agreed way forward.
A white paper will be produced for next meeting where a joint session SDLS/SEC/RFM/C&S
could be organized.</font>
<br>
<br><font size=2 face="sans-serif">to</font>
<br>
<br><font size=3 face="Times New Roman">I.Aguilar and C.Sheehe have agreed
to continue investigating the subject following the agreed way forward.
A white paper </font><font size=3 color=red face="Times New Roman">covering
the first two bullets above </font><font size=3 face="Times New Roman">will
be produced for next meeting where a joint session SDLS/SEC/RFM/C&S
could be organized.</font>
<br>
<br>
<br><font size=2 face="sans-serif">I hope you can accept these changes
which reflect the opinion of the RFM WG.</font>
<br>
<br><font size=2 face="sans-serif">Best Regards, Enrico</font>
<br>
<br>
<br>
<br>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">"Moury Gilles"
<Gilles.Moury@cnes.fr></font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">"sls-sea-dls@mailman.ccsds.org"
<sls-sea-dls@mailman.ccsds.org>, "Enrico.Vassallo@esa.int"
<Enrico.Vassallo@esa.int>, "Massimo.Bertinelli@esa.int"
<Massimo.Bertinelli@esa.int>, "Kazz, Greg J (312B)" <greg.j.kazz@jpl.nasa.gov></font>
<br><font size=1 color=#5f5f5f face="sans-serif">Cc:
</font><font size=1 face="sans-serif">"Calzolari Gian-Paolo"
<Gian.Paolo.Calzolari@esa.int></font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">07/06/2017 18:53</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">CCSDS SDLS WG:
May 8-12 meeting minutes</font>
<br>
<hr noshade>
<br>
<br>
<br><font size=2 face="Calibri">Dear SDLS WG member,</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">Please find attached for comments the draft
minutes of our May meeting in San Antonio. All files including attachments
to these minutes have been uploaded to CWE private > meeting material
> May 2017 meeting.</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">Enrico, Massimo, Greg: could you please
circulate those minutes to your respective WG for what concerns the following
joint sessions we had:</font>
<br><font size=2 face="Calibri"> </font>
<ul>
<li><font size=2 face="Calibri">RFM/C&S/SDLS joint session on May 8
about physical layer security (§3.1)</font>
<li><font size=2 face="Calibri">SLP/SDLS joint session on May 11 about
D-GVCID/D-MAPID (§3.3)</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">Best regards,</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri">Gilles</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 color=#000080 face="Arial"><b>Gilles MOURY</b></font><font size=2 face="Arial"><br>
CNES Toulouse<br>
CCSDS SDLS WG Co-chairman</font>
<br><font size=2 face="Calibri"> </font>
<br><font size=2 face="Calibri"> [attachment "SDLS WG MoM - May2017.docx"
deleted by Enrico Vassallo/esoc/ESA] </font>
<br>
<br></ul>
<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>