<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Tms Rmn";
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:TimesNewRomanPSMT;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:Times;
panose-1:0 0 5 0 0 0 0 2 0 0;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
font-size:10.0pt;
font-family:"Courier New";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:254411411;
mso-list-template-ids:-511510720;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">Hi Andrea,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks for this feedback. I have heard about this topic from both Ken Andrews and John Pietras. I must say, in all honesty, that I am both not surprised and also disappointed by the choice that the SLS CC WG has made. I also wonder
if the RFM WG would agree with your characterization that the “<span style="font-size:10.0pt;font-family:"Arial",sans-serif">RFM Blue Book 401 rather provides a set of requirements to be fulfilled when transmitting at Radio Frequency, but not a function.</span>”
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">In fact, that “pseudo protocol stack” diagram from 431, and also 131.0, .1, .2 makes direct reference to “Relationship to OSI Layers”. This is not “functions”, per se, but “OSI layers”. The text above this figure, in 431.0-B, says:<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<span style="font-size:12.0pt;font-family:"TimesNewRomanPSMT",serif;color:#0070C0">“The synchronization and channel coding sublayer provides methods of synchronization and channel coding for transferring Transfer Frames over a space link while the Physical
Layer provides the RF and modulation methods for transferring a stream of bits over a space link in a single direction.
</span><span style="color:#0070C0"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<span style="font-size:12.0pt;font-family:"TimesNewRomanPSMT",serif;color:#0070C0">This Recommended Standard covers functions in both the Synchronization and Channel Coding Sublayer and the Physical Layer. “</span><span style="color:#0070C0"><o:p></o:p></span></p>
<p class="MsoNormal">I think that we would all have to agree that the “functions” in the OSI Layer 1 relative to RF transmission include all of the physical layer aspects required to apply modulation, and to do filtering, signal shaping, and actual radiation
of the RF signal. For VCM we can add “physical layer signaling” to that set of functions. All of these, as far as I can tell, are “functions” of Layer 1.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I could quote all of the relevant section of the BRM, ISO 7498, but I suspect you are familiar with them. I will quote the most relevant parts:<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in;background:white">
<b><span style="font-family:Times;color:#0070C0">7.7.3.3. Physical Connections<o:p></o:p></span></b></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in;background:white">
<b><span style="font-family:Times;color:#0070C0">7.7.3.3.1 </span></b><span style="font-size:10.0pt;font-family:Times;color:#0070C0">The Physical Layer provides for the transparent transmission of bit streams between data-link</span><span style="font-family:Times;color:#0070C0">-</span><span style="font-size:10.0pt;font-family:Times;color:#0070C0">entities
across physical-connections. </span><span style="color:#0070C0"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in;background:white">
<b><span style="font-family:Times;color:#0070C0">7.7.3.3.2 </span></b><b><span style="font-size:10.0pt;font-family:Times;color:#0070C0">A
</span></b><span style="font-size:10.0pt;font-family:Times;color:#0070C0">data-circuit is a communication path in the physical media for OSI among two or more physical-entities, together with the facilities necessary in the Physical Layer for the transmission
of bits on it. </span><span style="color:#0070C0"><o:p></o:p></span></p>
<p class="MsoNormal">I think we all know that the BRM does not expressly cover RF communications, nor does it cover optical comms. That said, it does use sufficiently broad language that it is, in my opinion, still an extremely useful reference. In this case
“<span style="font-size:10.0pt;font-family:Times;color:#0070C0">facilities necessary in the Physical Layer for the transmission of bits</span>” equates, in my mind, exactly to “modulation, filtering, signal shaping, and actual radiation of the RF signal”.
Whether the term of art is “facilities” or “functions” is a terminology distinction that does not feel like it is worth arguing about. The BRM uses both “function” and “facility” and seems to mean more or less the same thing in both instances.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The last point I will make about this figure 2-1 is that it clearly states that the “VCM Protocol” covers all of the “Physical Layer”, which seems to mean all of OSI Layer 1. I do believe that the VCM includes some physical layer functions,
like a selection of modulations and pilot signals, but not all of them, so I continue to believe that this figure, on the surface of it, is both mis-leading and inaccurate. I also believe that in the absence of the functions, features, and facilities defined
in the CCSDS 401.0-B that you would be lacking the required definitions for several key functions and / or facilities for RF signal radiation, and constraints thereon, that are only documented in CCSDS 401.0-B. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">My conclusion, therefore, is that if the CCSDS stack does not include, explicitly, CCSDS 401.0-B, there is no complete guidance for RF radiation, and therefore Layer 1 is incomplete.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I really wish that you guys would just fix these figures so that this ambiguity is removed. The corresponding figure and text in TM Synch and channel coding, CCSDS 131.0-B, contains no such ambiguity.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks, Peter<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">"Andrea Modenini (external)" <Andrea.Modenini@esa.int><br>
<b>Date: </b>Monday, July 26, 2021 at 12:58 AM<br>
<b>To: </b>Peter Shames <peter.m.shames@jpl.nasa.gov><br>
<b>Cc: </b>Space Link Coding & Synchronization Working Group <sls-cc@mailman.ccsds.org><br>
<b>Subject: </b>Re: [EXTERNAL] Re: [SLS-CC] VCM technical corrigendum wording (AI_21_01)<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Dear Peter,</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"> sorry for the late reply, I have been hold by other activities, and I am also in a personal leave.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Regarding the stack, in our opinion the VCM Blue Book defines also the physical layer function, since it fully specifies the modulations and constellations to be implemented.</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">In this respect, the RFM Blue Book 401 rather provides a set of requirements to be fulfilled when transmitting at Radio Frequency, but not a function.
</span><br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Hence, our preference as WG is to insert the sentences as indicated in my previous email, but to not modify the stack.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Please let us know your opinion, so that we could possible proceed with the WG resolution.</span>
<br>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Regards</span> <br>
<br>
<br>
<br>
<b><span style="font-size:8.0pt;font-family:"Verdana",sans-serif;color:gray">HE Space Operations for ESA - European Space Agency</span></b>
<br>
<b><span style="font-size:8.0pt;font-family:"Verdana",sans-serif;color:#00A1E0">Ph.D. Andrea Modenini</span></b><b><span style="font-size:8.0pt;font-family:"Verdana",sans-serif;color:gray"><br>
Communication Systems & Technologies Engineer</span></b><b><span style="font-size:12.0pt;font-family:"Tms Rmn",serif">
</span></b><span style="font-size:8.0pt;font-family:"Verdana",sans-serif;color:gray"><br>
TT&C and PDT Systems & Techniques Section (TEC-EST)<br>
RF Systems Division<b><br>
ESTEC</b><br>
Keplerlaan 1, PO Box 299<br>
NL-2200 AG Noordwijk, The Netherlands</span><u><span style="font-size:8.0pt;font-family:"Verdana",sans-serif;color:blue"><br>
</span></u><span style="font-size:8.0pt;font-family:"Verdana",sans-serif;color:gray">andrea.modenini@esa.int |
</span><a href="https://urldefense.us/v3/__http:/www.esa.int/__;!!PvBDto6Hs4WbVuu7!d5Sq5RR5u3CiQHi0pPU9SNMfwjuy8mRQK2_zDmvs_G35TZ11GNTO6MRtZEi46MbTmcjuyrPF$"><span style="font-size:8.0pt;font-family:"Verdana",sans-serif;color:#8F8F8F">www.esa.int</span></a><span style="font-size:8.0pt;font-family:"Verdana",sans-serif;color:gray"><br>
T +31 71 56 53439, M +31 6 484 56 527</span> <br>
<br>
<br>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">From: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"Shames, Peter M (US 312B)" <peter.m.shames@jpl.nasa.gov></span>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">To: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"Andrea Modenini (external)" <Andrea.Modenini@esa.int>, "Space Link Coding & Synchronization Working Group"
<sls-cc@mailman.ccsds.org></span> <br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">Date: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">07-07-21 21:05</span>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F">Subject: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">Re: [EXTERNAL] Re: [SLS-CC] VCM technical corrigendum wording (AI_21_01)</span>
<o:p></o:p></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="0" width="100%" noshade="" style="color:#A0A0A0" align="center">
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
<p style="margin:0in">Dear Andrea & S&CC WG members,<o:p></o:p></p>
<p style="margin:0in"> <o:p></o:p></p>
<p style="margin:0in">I fully support the idea of aligning all three of the “VCM suite” coding and synch standards. As we have tried to make clear in the updates we are making to the SCCS-ARD, our analysis shows that all three of these approaches are very
nearly identical technically, with only what appear to be modest differences in how they are designed. I do not wish to get into the whole discussion of how we arrived at this situation, only to point out that this is where we are, and that this is how we
view the technical details.<o:p></o:p></p>
<p style="margin:0in"> <o:p></o:p></p>
<p style="margin:0in">In the attached slides I have included, as pgs 2 & 3, the way that we are approaching the description of what we are calling the “VCM Suite” and how we plan to document these relative to the rest of the S&CC specs as well as how they
relate to the several link layer protocols. We reviewed these diagrams during the “SCCS Coordination” meeting that involved SLS, SIS, CSS, and SEA WG and Area leads. And we just discussed these during the follow up SAWG meeting that Gilles was present at.
We agreed to ask your WG for feedback, so I am taking this opportunity to do this.<o:p></o:p></p>
<p style="margin:0in"> <o:p></o:p></p>
<p style="margin:0in">I have also included, on pg 1, a proposed markup of your text and Fig 2-1 from the 431.1 document. We think it will be clearer if this figure, and the associated text, for the 431.1 (and the others in the VCM Suite) all use the identical
figure, and that this figure, and the related text, clearly states that these standards only address the upper part (modulation sub-layer) of the Physical Layer and not the lower sub-layer where the 401.0 document addresses the RF frequency bands, bandwidth
limitations, etc.<o:p></o:p></p>
<p style="margin:0in"> <o:p></o:p></p>
<p style="margin:0in">Please review this feedback and see if you can agree to it. Also, it would be very useful to us if your WG would review the VCM Suite diagrams I have sent and make sure that they are technically correct.<o:p></o:p></p>
<p style="margin:0in"> <o:p></o:p></p>
<p style="margin:0in">Very best regards, Peter<o:p></o:p></p>
<p style="margin:0in"> <o:p></o:p></p>
<p style="margin:0in"> <o:p></o:p></p>
<p style="margin:0in"><b><span style="font-size:12.0pt">From: </span></b><span style="font-size:12.0pt">SLS-CC <sls-cc-bounces@mailman.ccsds.org> on behalf of "Andrea Modenini (external)" <Andrea.Modenini@esa.int><b><br>
Date: </b>Wednesday, July 7, 2021 at 9:30 AM<b><br>
To: </b>Space Link Coding & Synchronization Working Group <sls-cc@mailman.ccsds.org><b><br>
Subject: </b>[EXTERNAL] Re: [SLS-CC] VCM technical corrigendum wording (AI_21_01)</span><o:p></o:p></p>
<p style="margin:0in"> <o:p></o:p></p>
<p style="margin:0in"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Dear all,</span>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
I did not receive any comment about the VCM BB from the WG.</span> <br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
However, considering the outcome of the DVB-S2 BB review we had today, I have myself a comment.
<br>
We aligned the SCCC and DVB-S2 BBs for having a sentence that states the need to consider CCSDS 401 BB.</span>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
On the same line, I would propose to modify Section 2 as provided below (italic part highlights the addition).</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
You can find in attachment also the word file in tracking-changes mode for your convenience.</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
Please let me know if there is any objection, or additional point to consider, <u>
no later than 12th July EOB</u>.</span> <span style="font-size:10.0pt;font-family:"Arial",sans-serif">
<br>
I will afterward request an Area Resolution for having the technical corrigendum.</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
Kind Regards,</span> <span style="font-size:10.0pt;font-family:"Arial",sans-serif">
<br>
Andrea</span> <br>
<br>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
-------------</span> <o:p></o:p></p>
<p style="margin:0in"><span style="font-size:12.0pt;font-family:"Times New Roman",serif">This Recommended Standard covers functions in both the Synchronization and Channel Coding Sublayer and the Physical Layer<i>, the latter for what concerns the modulation
schemes. CCSDS 401.0-B [5] covers additional features of the Physical Layer like frequency bands, polarizations, etc. that are not described or referenced here.</i></span>
<br>
<br>
<b><span style="font-size:8.0pt;font-family:"Verdana",sans-serif;color:gray"><br>
HE Space Operations for ESA - European Space Agency</span></b> <b><span style="font-size:8.0pt;font-family:"Verdana",sans-serif;color:#00A1E0"><br>
Ph.D. Andrea Modenini</span></b><b><span style="font-size:8.0pt;font-family:"Verdana",sans-serif;color:gray"><br>
Communication Systems & Technologies Engineer</span></b><b><span style="font-size:12.0pt;font-family:"Tms Rmn",serif">
</span></b><span style="font-size:8.0pt;font-family:"Verdana",sans-serif;color:gray"><br>
TT&C and PDT Systems & Techniques Section (TEC-EST)<br>
RF Systems Division<b><br>
ESTEC</b><br>
Keplerlaan 1, PO Box 299<br>
NL-2200 AG Noordwijk, The Netherlands<br>
andrea.modenini@esa.int | </span><a href="https://urldefense.us/v3/__http:/www.esa.int/__;!!PvBDto6Hs4WbVuu7!ZprtUS7KJ1pZpltt-3sln6BkmB--RAe2fXWcA3tewDmnD-hvb2k5FJtUbftvY77dWfg0GNDT$"><span style="font-size:8.0pt;font-family:"Verdana",sans-serif;color:#8F8F8F">www.esa.int</span></a><span style="font-size:8.0pt;font-family:"Verdana",sans-serif;color:gray"><br>
T +31 71 56 53439</span> <br>
<br>
<br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"><br>
From: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">Andrea Modenini/estec/ESA</span>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"><br>
To: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"Space Link Coding & Synchronization Working Group" <sls-cc@mailman.ccsds.org></span>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"><br>
Date: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">10-06-21 17:28</span>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"><br>
Subject: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">[SLS-CC] VCM technical corrigendum wording (AI_21_01)</span>
<o:p></o:p></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="0" width="100%" noshade="" style="color:#A0A0A0" align="center">
</div>
<p style="margin:0in"><br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
Dear colleagues,</span> <br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
please find enclosed the proposed changes by Jon to the VCM BB discussed during the joint C&S/RFM meeting. Please send your comments before
<b>1st July 2021</b> (if any) directly to John with CC Enrico and I, and C&S mailing list.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
Regards</span> <span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
Andrea</span> <br>
<br>
<b><span style="font-size:8.0pt;font-family:"Verdana",sans-serif;color:gray"><br>
HE Space Operations for ESA - European Space Agency</span></b> <b><span style="font-size:8.0pt;font-family:"Verdana",sans-serif;color:#00A1E0"><br>
Ph.D. Andrea Modenini</span></b><b><span style="font-size:8.0pt;font-family:"Verdana",sans-serif;color:gray"><br>
Communication Systems & Technologies Engineer</span></b><b><span style="font-size:12.0pt;font-family:"Tms Rmn",serif">
</span></b><span style="font-size:8.0pt;font-family:"Verdana",sans-serif;color:gray"><br>
TT&C and PDT Systems & Techniques Section (TEC-EST)<br>
RF Systems Division<b><br>
ESTEC</b><br>
Keplerlaan 1, PO Box 299<br>
NL-2200 AG Noordwijk, The Netherlands<br>
andrea.modenini@esa.int | </span><a href="https://urldefense.us/v3/__http:/www.esa.int/__;!!PvBDto6Hs4WbVuu7!ZprtUS7KJ1pZpltt-3sln6BkmB--RAe2fXWcA3tewDmnD-hvb2k5FJtUbftvY77dWfg0GNDT$"><span style="font-size:8.0pt;font-family:"Verdana",sans-serif;color:#8F8F8F">www.esa.int</span></a><span style="font-size:8.0pt;font-family:"Verdana",sans-serif;color:gray"><br>
T +31 71 56 53439</span> <span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:purple">
<br>
----- Forwarded by Andrea Modenini/estec/ESA on 10-06-21 17:25 -----</span> <br>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"><br>
From: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"Jon Hamkins" <Jon.Hamkins@jpl.caltech.edu></span>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"><br>
To: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">"Andrea Modenini (external)" <Andrea.Modenini@esa.int>, "Enrico.Vassallo@esa.int" <Enrico.Vassallo@esa.int></span>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"><br>
Date: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">09-06-21 18:48</span>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#5F5F5F"><br>
Subject: </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif">VCM technical corrigendum wording (AI_21_01)</span>
<o:p></o:p></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="0" width="100%" noshade="" style="color:#A0A0A0" align="center">
</div>
<p style="margin:0in"><br>
<br>
<span style="font-size:12.0pt"><br>
Andrea, Enrico,</span> <span style="font-size:12.0pt"><br>
Attached is a draft VCM technical corrigendum in response to AI_21_01 from the C&S WG. I completed this in consultation with Ken Andrews and John Pietras.</span>
<span style="font-size:12.0pt"><br>
The main changes are in two places: Section 3.2.3 and Section 3.3.2.3 to 3.3.2.4. In summary, with the new wording the randomization is determined by VCM type:</span>
<o:p></o:p></p>
<ul type="disc">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<span style="font-size:12.0pt">Type 1 (SCCC-like) VCM will randomize the Transfer Frames as the SCCC standard does, using the TM randomizer.</span>
<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<span style="font-size:12.0pt">Type 2 (DVB-S2-like) VCM will randomize the sliced encoder-inputs as the DVB-S2 standard does, using the ETSI DVB-S2 baseband scrambler.</span><o:p></o:p></li></ul>
<p class="MsoNormal"><span style="font-size:12.0pt">This will make the CCSDS VCM standard consistent with the 131.2-B-1 and 131.3-B-1 books (SCCC and DVB-S2), with respect to randomization.</span>
<span style="font-size:12.0pt"><br>
These changes are not related to randomization that occurs after encoding. The VCM protocol standard already applies post-encoding randomization, at the physical layer.</span>
<span style="font-size:12.0pt"><br>
Can you forward this message to the RFM and C&S mailing lists along with your guidance on how/when to respond with comments? I believe we agreed to resolve this action by email.</span>
<span style="font-size:12.0pt"><br>
----Jon</span> <span style="font-size:12.0pt"><br>
-- <b><br>
Jon Hamkins</b><br>
Chief Technologist, Communications, Tracking, and Radar Division<b><br>
O</b> 818-354-4764 (preferred) | <b>M</b> 626-658-6220 (does not work at home)<b><br>
<br>
JPL</b> | jpl.nasa.gov [attachment "2021-05-27-VCM-431.1-technical-corrigendum-post-discussion-v3.doc" deleted by Andrea Modenini/estec/ESA]
</span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:10.0pt;font-family:"Courier New"">This message is intended only for the recipient(s) named above. It may contain proprietary information and/or</span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:10.0pt;font-family:"Courier New"">protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received</span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:10.0pt;font-family:"Courier New"">this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect</span><o:p></o:p></p>
<p style="margin:0in"><span style="font-size:10.0pt;font-family:"Courier New"">personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (dpo@esa.int).[attachment "2021-05-27 VCM 431.1 Fig 2-1.pptx" deleted by Andrea Modenini/estec/ESA]
</span><o:p></o:p></p>
<pre>This message is intended only for the recipient(s) named above. It may contain proprietary information and/or<o:p></o:p></pre>
<pre>protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received<o:p></o:p></pre>
<pre>this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect<o:p></o:p></pre>
<pre>personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (dpo@esa.int).<o:p></o:p></pre>
</div>
</body>
</html>