<span style=" font-size:10pt;font-family:sans-serif">Dear colleagues,</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">this is the list
of inputs I've received for the Spring meeting (I didn't compile an actual
agenda, it doesn't make much sense).</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif"><u>C&S/RFM</u></span>
<br><span style=" font-size:10pt;font-family:sans-serif">- VCM (NASA)
(SLS-CS_20-01) we should be able to discuss
it via emails and call a telco only if required. Please copy RFM WG, this
is a joint matter</span>
<br><span style=" font-size:10pt;font-family:sans-serif">- Proposal for
simulation channel model (ESA) Not urgent,
delayed until the next meeting</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif"><u>C&S only</u></span>
<br><span style=" font-size:10pt;font-family:sans-serif">- TC coding Green
Book
We should be able to process this via
emails and call a telco for discussion, if needed</span>
<br><span style=" font-size:10pt;font-family:sans-serif">- TC coding Blue
Book
We
may need a telco for discussion</span>
<br><span style=" font-size:10pt;font-family:sans-serif">- Standarding
PN shift registers... (NASA) (SLS-CS_20-02)
I assume email discussion will be sufficient, but I would need to see the
input first to be sure</span>
<br><span style=" font-size:10pt;font-family:sans-serif">- Revision of
TM coding Blue Book...(NASA) (SLS-CS_20-03)
Let's start by email discussion and see if telco is needed</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">- Allowable links/codes/modulations/directions
(NASA) I'm not sure how to treat this
input. Given the title, it seems it affects RFM WG as well so it shouldn't
be treated as C&S item only.</span>
<br><span style=" font-size:10pt;font-family:sans-serif">
I suppose a decision will be taken once the input
is avaible so that we can better classify it.
</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">My propoposal
is the following: inputs should be provided by the original deadline (Monday
20 April), as if the meeting would take place normally.</span>
<br><span style=" font-size:10pt;font-family:sans-serif">Then, I would
recommend that we discuss via email to tha largest possible extend, sending
comments to the inputs byt the original start date of the meeting (4 May).</span>
<br><span style=" font-size:10pt;font-family:sans-serif">Probably we'll
manage to close some of the points via email, while for others we'll need
further discussions. In such cases, I will propose ad-hoc telcos that I
will organize based</span>
<br><span style=" font-size:10pt;font-family:sans-serif">on the identified
needs.</span>
<br><span style=" font-size:10pt;font-family:sans-serif">I will not be
able to hold such remote meetings, at a time reasonable to all potential
participants, during the week originally allocated for the CCSDS meeting,
so I will propose alternative, later dates.</span>
<br><span style=" font-size:10pt;font-family:sans-serif">I hope this way
of handling the meeting can be acceptable to all WG members</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">For the joint
with RFM/SLP/OPT about the OPT proposal on GFP, I am of the opinion that
such a discussion should be delayed until a face to face meeting is actually
possiblle. </span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Kind regards,</span>
<br><span style=" font-size:10pt;font-family:sans-serif">Massimo</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif"><br>
<br>
---------------------------------------------------<br>
Massimo Bertinelli<br>
Communication Systems Engineer<br>
ESA/Estec<br>
<br>
Tel. +31 (0)71 5653435<br>
--------------------------------------------------</span><PRE>This message is intended only for the recipient(s) named above. It may contain proprietary information and/or
protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received
this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect
personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (dpo@esa.int).
</PRE>