<span style=" font-size:10pt;font-family:sans-serif">Dear Enrico,</span>
<br><span style=" font-size:10pt;font-family:sans-serif">
frankly speaking, the third possibility look to me
the best one.</span>
<br><span style=" font-size:10pt;font-family:sans-serif">If strongly needed,
a note could be added about using historical titles.</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">The general problem
is that using new/different terms - as you correctly remarks - 401.0-B
may enter in conflict with different fora including usage within CCSDS.</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">As an example,
the notation forward/return (link) is mainly used to generalise the diction
specially when one side in not on Earth as done in Proximity-1 Physical
Layer book (see </span><a href=https://public.ccsds.org/Pubs/211x1b4e1.pdf><span style=" font-size:10pt;color:blue;font-family:sans-serif">https://public.ccsds.org/Pubs/211x1b4e1.pdf</span></a><span style=" font-size:10pt;font-family:sans-serif">
)</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Ciao</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Gian Paolo</span>
<br>
<br>
<br>
<br>
<br>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">From:
</span><span style=" font-size:9pt;font-family:sans-serif">Enrico.Vassallo@esa.int</span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">To:
</span><span style=" font-size:9pt;font-family:sans-serif">sls-rfm@mailman.ccsds.org</span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Date:
</span><span style=" font-size:9pt;font-family:sans-serif">08-04-21
10:05</span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Subject:
</span><span style=" font-size:9pt;font-family:sans-serif">[Sls-rfm]
CCSDS 401 structure naming convention - proposed changes</span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Sent
by: </span><span style=" font-size:9pt;font-family:sans-serif">"SLS-RFM"
<sls-rfm-bounces@mailman.ccsds.org></span>
<br>
<hr noshade>
<br>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">Dear RFM WG colleagues,</span><span style=" font-size:12pt">
<br>
</span><span style=" font-size:10pt;font-family:sans-serif"><br>
discussing high rate 22 GHz uplink recommendations, we noted that the current
structure naming convention may not be appropriate to cover "generic"
data transfer applications:</span><span style=" font-size:12pt"> </span>
<br><span style=" font-size:11pt;font-family:Roman">
2.1<i> Earth-to-Space Radio Frequency</i>
2.4<i>
Telemetry</i></span><span style=" font-size:12pt"> </span><span style=" font-size:11pt;font-family:Roman"><br>
2.2<i> Telecommand</i>
2.5<i>
Radio Metric</i></span><span style=" font-size:12pt">
</span><span style=" font-size:11pt;font-family:Roman"><br>
2.3<i> Space-to-Earth
Radio Frequency</i> 2.6<i>
Spacecraft</i></span><span style=" font-size:12pt">
<br>
</span><span style=" font-size:10pt;font-family:sans-serif"><br>
One possible solution would be to change the title of section 2.2 to something
like "Telecommand and forward data" and that of section 2.4 to
something like "Telemetry and return data".</span><span style=" font-size:12pt">
<br>
</span><span style=" font-size:10pt;font-family:sans-serif"><br>
This is to distinguish between telecommand and uplink data transfers (like
on-board software patch uploading, etc.) and between (HK) telemetry and
payload transmissions. <br>
Note that already now recs 2.4.8 and 2.4.23 do not mention telemetry in
the title and deal with payload data. However, both recommendations have
pictures for symbol rate definition with captions indicating telemetry
symbol rate. I assume we will have the same in section 2.2.</span><span style=" font-size:12pt">
</span><span style=" font-size:10pt;font-family:sans-serif"><br>
One would need to check in detail all recommendations in 2.2 and 2.4, which
is a lot of work I think.</span><span style=" font-size:12pt"> <br>
</span><span style=" font-size:10pt;font-family:sans-serif"><br>
Another possibility is to change the section titles to "Telecommand
(including data transfer)" and "Telemetry (including data transfer)"
so that we can avoid checking current recommendations for consistency.</span><span style=" font-size:12pt">
<br>
</span><span style=" font-size:10pt;font-family:sans-serif"><br>
In addition, one could use as alternative to "data transfer"
the "payload" word although this is not generally utilized to
indicate the same thing in different fora.</span><span style=" font-size:12pt">
<br>
</span><span style=" font-size:10pt;font-family:sans-serif"><br>
The third possibility is to ignore this semantic problem and leave everything
unchanged.</span><span style=" font-size:12pt"> <br>
</span><span style=" font-size:10pt;font-family:sans-serif"><br>
Could I have your view by April 15 COB?</span><span style=" font-size:12pt">
<br>
<br>
<br>
</span><span style=" font-size:10pt;font-family:sans-serif"><br>
Regards, Enrico</span><span style=" font-size:12pt"> </span>
<br>
<br><tt><span style=" font-size:12pt">This message is intended only for
the recipient(s) named above. It may contain proprietary information and/or<br>
protected content. Any unauthorised disclosure, use, retention or dissemination
is prohibited. If you have received<br>
this e-mail in error, please notify the sender immediately. ESA applies
appropriate organisational measures to protect<br>
personal data, in case of data privacy queries, please contact the ESA
Data Protection Officer (dpo@esa.int).<br>
</span></tt><tt><span style=" font-size:10pt">_______________________________________________<br>
SLS-RFM mailing list<br>
SLS-RFM@mailman.ccsds.org<br>
</span></tt><a href="https://mailman.ccsds.org/cgi-bin/mailman/listinfo/sls-rfm"><tt><span style=" font-size:10pt">https://mailman.ccsds.org/cgi-bin/mailman/listinfo/sls-rfm</span></tt></a><tt><span style=" font-size:10pt"><br>
</span></tt>
<br>
<br><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>