<font size=2 face="sans-serif">Dear Nestor,</font>
<br>
<br><font size=2 face="sans-serif">thank you very much for your mail with
the information about the CESG decision about the distribution of responsibilities
between the SLS and the SOIS area.</font>
<br><font size=2 face="sans-serif">Looking at the text it is not clear
to me what are the updates you request us to do?</font>
<br><font size=2 face="sans-serif">In particular I can not identify that
any of our modifications would violate the CESG decision.</font>
<br>
<br><font size=2 face="sans-serif">Could you please be more explicit in
describing which updates you would like us to make?</font>
<br>
<br><font size=2 face="sans-serif">Kind regards,</font>
<br><font size=2 face="sans-serif">Martin</font>
<br>
<br><font size=1 color=#808080 face="sans-serif"><b>ESA – European Space
Agency</b></font>
<p><font size=1 color=#00a1e0 face="sans-serif">Martin Suess</font>
<p><font size=1 color=#808080 face="sans-serif">Head of On-board Payload
Data Processing Section<br>
Electrical Engineering Department<b><br>
</b></font>
<p><font size=1 color=#808080 face="sans-serif"><b>ESTEC</b><br>
Keplerlaan 1, PO box 299, <br>
NL-2200 AG Noordwijk, The Netherlands</font><font size=1 color=blue face="sans-serif"><u><br>
</u></font><a href=mailto:martin.suess@esa.int><font size=1 color=#808080 face="sans-serif">martin.suess@esa.int</font></a><font size=1 color=#808080 face="sans-serif">
| </font><a href=http://www.esa.int/><font size=1 color=#808080 face="sans-serif">www.esa.int</font></a><font size=1 color=#808080 face="sans-serif"><br>
T +31 71 56 56198 | F +31 71 56 56791</font>
<p>
<br>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">Nestor Peccia/esoc/ESA</font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">Martin Suess/estec/ESA@ESA</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Cc:
</font><font size=1 face="sans-serif">"Barton, Richard
J. \(JSC-EV411\)" <richard.j.barton@nasa.gov>, cesg@mailman.ccsds.org,
"Brian Oliver" <briano@aiaa.org></font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">27/07/2015 10:03</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">Re: SOIS online
strategic Plan and Goals website update</font>
<br>
<hr noshade>
<br>
<br><font size=2 face="sans-serif">Martin</font>
<br>
<br><font size=2 face="sans-serif">I had a look to your updated text. You
need to consider the agreement between SLS and SOIS Areas wrt RFM vs Wireless,
which states</font>
<br><font size=2 color=red face="sans-serif"><b>CESG Decision</b></font>
<br>
<br><font size=2 color=red face="sans-serif"><b><u>SLS Responsibilities
include:</u></b></font>
<br><font size=2 color=red face="sans-serif"><b>1) point-to-point links
for Planetary Communications</b></font>
<br><font size=2 color=red face="sans-serif"><b>2) multi-point links for
Planetary Communications utilising CCSDS data link and physical layer protocols</b></font>
<br><font size=2 color=red face="sans-serif"><b>3) consideration of usage
of RF bands over space-ground and space-space links </b></font>
<br><font size=2 color=red face="sans-serif"><b>SLS can therefore define
mission scenarios/profiles for Planetary Communications, as well as functional
& performance requirements and develop the pertinent Standards (Magenta
or Blue Books) according to the points 1..3 listed above.</b></font>
<br>
<br><font size=2 color=red face="sans-serif"><b><u>SOIS Responsibilities
include:</u></b></font>
<br><font size=2 color=red face="sans-serif"><b>A) networked multi-point
links utilising commercial wireless network technologies for Communications
onboard a space vehicle or habitat and/or surface links within the proximity
of that vehicle or habitat.</b></font>
<br><font size=2 color=red face="sans-serif"><b>B) cooperation with the
SLS Area for matters related to usage of Radio Frequency bands </b></font>
<br><font size=2 color=red face="sans-serif"><b>SOIS can therefore define
mission scenarios/profiles for Vehicle and vicinity Communications, as
well as functional & performance requirements and develop the pertinent
Standards (Magenta or Blue Books) according to the points A..B listed
above.</b></font>
<br>
<br><font size=2 color=red face="sans-serif"><b>Charters and CWE Projects
of the affected WGs in SLS and SOIS Areas are to be made consistent with
the above set of responsibilities (if not consistent now).
SOLVED</b></font>
<br>
<br><font size=2 face="sans-serif">Please update the proposed text accordingly</font>
<br>
<br><font size=2 face="sans-serif">ciao</font>
<br><font size=2 face="sans-serif">nestor</font>
<br><font size=2 face="sans-serif">--------------------------------------</font>
<br><font size=2 face="sans-serif">Dear Nestor,</font>
<br>
<br><font size=2 face="sans-serif">Richard and I reviewed the online strategic
plan and would like to introduce some minor updates.</font>
<br><font size=2 face="sans-serif">When I tried to implement them on the
website I realised that I could not make any edits.</font>
<br><font size=2 face="sans-serif">May this still have to do with some
permissions which are not properly set for me?</font>
<br><font size=2 face="sans-serif">For your information I attach the updated
version of the SOIS strategic plan below.</font>
<br>
<br><font size=2 face="sans-serif">Regards,</font>
<br><font size=2 face="sans-serif">Martin</font>
<br>
<br>
<br><font size=2 face="sans-serif"><br>
[attachment "SOIS online strategic Plan and Goals.2015-07-24.docx"
deleted by Martin Suess/estec/ESA] </font>
<p><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>