<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: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;
margin-bottom:.0001pt;
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.EmailStyle20
{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:397629007;
mso-list-template-ids:-872282508;}
@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">Dear Andrea & S&CC WG members,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">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 class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">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 class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">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 class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">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 class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Very best regards, 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">SLS-CC <sls-cc-bounces@mailman.ccsds.org> on behalf of "Andrea Modenini (external)" <Andrea.Modenini@esa.int><br>
<b>Date: </b>Wednesday, July 7, 2021 at 9:30 AM<br>
<b>To: </b>Space Link Coding & Synchronization Working Group <sls-cc@mailman.ccsds.org><br>
<b>Subject: </b>[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 all,</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"> I did not receive any comment about the VCM BB from the WG.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">However, considering the outcome of the DVB-S2 BB review we had today, I have myself a comment.
</span><br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">We aligned the SCCC and DVB-S2 BBs for having a sentence that states the need to consider CCSDS 401 BB.</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">On the same line, I would propose to modify Section 2 as provided below (italic part highlights the addition).</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">You can find in attachment also the word file in tracking-changes mode for your convenience.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Please let me know if there is any objection, or additional point to consider,
<u>no later than 12th July EOB</u>.</span> <br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">I will afterward request an Area Resolution for having the technical corrigendum.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Kind Regards,</span>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Andrea</span> <br>
<br>
<br>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">-------------</span>
<o:p></o:p></p>
<div>
<p class="MsoNormal"><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>
<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!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>
<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">Andrea Modenini/estec/ESA</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">"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">10-06-21 17:28</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">[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"><br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Dear colleagues,</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">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>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Regards</span> <br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Andrea</span> <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!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>
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:purple">----- Forwarded by Andrea Modenini/estec/ESA on 10-06-21 17:25 -----</span>
<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">"Jon Hamkins" <Jon.Hamkins@jpl.caltech.edu></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>, "Enrico.Vassallo@esa.int" <Enrico.Vassallo@esa.int></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">09-06-21 18:48</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">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"><br>
<br>
<br>
<span style="font-size:12.0pt">Andrea, Enrico,</span> <br>
<span style="font-size:12.0pt">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>
<br>
<span style="font-size:12.0pt">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" style="margin-bottom:12.0pt"><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>
<br>
<span style="font-size:12.0pt">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>
<br>
<span style="font-size:12.0pt">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>
<br>
<span style="font-size:12.0pt"> ----Jon</span> <br>
<span style="font-size:12.0pt">-- <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)<br>
<b><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><br>
<br>
<o:p></o:p></p>
</div>
<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>