<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:mv="http://macVmlSchemaUri" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Title" content="">
<meta name="Keywords" content="">
<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:"Courier New";
panose-1:2 7 3 9 2 2 5 2 4 4;}
@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:sans-serif;
panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
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",serif;}
tt
{mso-style-priority:99;
font-family:"Courier New",serif;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:"Courier",serif;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.msoIns
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:underline;
color:teal;}
.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;}
--></style>
</head>
<body bgcolor="white" lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal">Hi Gippo,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks for processing this request to make the limited set of changes to the SPP and OSCP docs. They are really over-due and I am glad to see the plan to make these repairs being put into motion.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I do not think that the second project is in progress yet. And I still question the logic of creating two separate projects against one document. How do you think this is going to be handled? Two separate versions of the same document?
Two separate agency reviews for the same document? Is there going to be an enforced delay in publishing the second version with the second set of updates in order to maintain document stability?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Just what do you think the plan is to deal with these considerations?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">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" style="margin-left:.5in"><b><span style="font-size:12.0pt;color:black">From:
</span></b><span style="font-size:12.0pt;color:black">Gian Paolo Calzolari <Gian.Paolo.Calzolari@esa.int><br>
<b>Date: </b>Wednesday, November 22, 2017 at 2:41 AM<br>
<b>To: </b>Peter Shames <peter.m.shames@jpl.nasa.gov><br>
<b>Cc: </b>CCSDS Engineering Steering Group - CESG Exec <cesg@mailman.ccsds.org><br>
<b>Subject: </b>Re: [CESG] Additional presentation to CMC for extra items // SPP delays?
<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt;font-family:"sans-serif",serif">Peter,</span>
<br>
<span style="font-size:10.0pt;font-family:"sans-serif",serif"> thanks to the excellent cooperation by Greg Kazz (but not only) the SLS-SLP request to start two projects (instead of one as originally planned in The Hague) is out for starting CMC Poll
less than two weeks after the The Hague Meetings.</span> <br>
<br>
<span style="font-size:10.0pt;font-family:"sans-serif",serif">I think we all shall be happy for this timely achievement.</span>
<br>
<br>
<span style="font-size:10.0pt;font-family:"sans-serif",serif">Regards</span> <br>
<br>
<span style="font-size:10.0pt;font-family:"sans-serif",serif">Gippo</span> <br>
<br>
<br>
<br>
<span style="font-size:7.5pt;font-family:"sans-serif",serif;color:#5F5F5F">From: </span><span style="font-size:7.5pt;font-family:"sans-serif",serif">Gian.Paolo.Calzolari@esa.int</span>
<br>
<span style="font-size:7.5pt;font-family:"sans-serif",serif;color:#5F5F5F">To: </span><span style="font-size:7.5pt;font-family:"sans-serif",serif">"Shames, Peter M (312B)" <peter.m.shames@jpl.nasa.gov></span>
<br>
<span style="font-size:7.5pt;font-family:"sans-serif",serif;color:#5F5F5F">Cc: </span><span style="font-size:7.5pt;font-family:"sans-serif",serif">"CESG -- CCSDS-Engineering SteeringGroup\(cesg@mailman.ccsds.org\)\(cesg@mailman.ccsds.org\)" <cesg@mailman.ccsds.org></span>
<br>
<span style="font-size:7.5pt;font-family:"sans-serif",serif;color:#5F5F5F">Date: </span><span style="font-size:7.5pt;font-family:"sans-serif",serif">13/11/2017 12:07</span>
<br>
<span style="font-size:7.5pt;font-family:"sans-serif",serif;color:#5F5F5F">Subject: </span><span style="font-size:7.5pt;font-family:"sans-serif",serif">Re: [CESG] Additional presentation to CMC for extra items // SPP delays?</span>
<br>
<span style="font-size:7.5pt;font-family:"sans-serif",serif;color:#5F5F5F">Sent by: </span><span style="font-size:7.5pt;font-family:"sans-serif",serif">"CESG" <cesg-bounces@mailman.ccsds.org></span>
<o:p></o:p></p>
<div class="MsoNormal" align="center" style="margin-left:.5in;text-align:center">
<hr size="2" width="100%" noshade="" style="color:#A0A0A0" align="center">
</div>
<p class="MsoNormal" style="margin-left:.5in"><br>
<br>
<span style="font-size:10.0pt;font-family:"sans-serif",serif">[attachment "ConceptPaper-uplink coding_green_V2(cleanFinal).pdf" deleted by Gian Paolo Calzolari/esoc/ESA]
</span><br>
<br>
<span style="font-size:10.0pt;font-family:"sans-serif",serif">Peter, <br>
it looks as you were not there when I clearly told Greg that "despite not strictly needed for updating of documents, you may want to prepare a concept paper to support the SLS resolution as it is much simpler editing in word that putting dates in CWE".</span><span style="font-size:12.0pt">
<br>
</span><span style="font-size:10.0pt;font-family:"sans-serif",serif"><br>
The Concept Paper we refer to is like the attached one (BTW, done by JPL guys) and contains the information to be relied anyhow to CMC to allow them to approve the new project.
</span><span style="font-size:12.0pt"><br>
</span><span style="font-size:10.0pt;font-family:"sans-serif",serif"><br>
If you think that providing this kind of information (normally 1 page of text and 1 or 2 pages for project definition) is provoking big delays, I will have to live with this.</span><span style="font-size:12.0pt">
<br>
</span><span style="font-size:10.0pt;font-family:"sans-serif",serif"><br>
Regards</span><span style="font-size:12.0pt"> <br>
</span><span style="font-size:10.0pt;font-family:"sans-serif",serif"><br>
Gian Paolo</span><span style="font-size:12.0pt"> <br>
<br>
<br>
</span><span style="font-size:7.5pt;font-family:"sans-serif",serif;color:#5F5F5F"><br>
From: </span><span style="font-size:7.5pt;font-family:"sans-serif",serif">"Shames, Peter M (312B)" <peter.m.shames@jpl.nasa.gov></span><span style="font-size:12.0pt">
</span><span style="font-size:7.5pt;font-family:"sans-serif",serif;color:#5F5F5F"><br>
To: </span><span style="font-size:7.5pt;font-family:"sans-serif",serif">"Gian.Paolo.Calzolari@esa.int" <Gian.Paolo.Calzolari@esa.int></span><span style="font-size:12.0pt">
</span><span style="font-size:7.5pt;font-family:"sans-serif",serif;color:#5F5F5F"><br>
Cc: </span><span style="font-size:7.5pt;font-family:"sans-serif",serif">"Nestor.Peccia@esa.int" <Nestor.Peccia@esa.int>, "CESG -- CCSDS-Engineering SteeringGroup(cesg@mailman.ccsds.org)(cesg@mailman.ccsds.org)" <cesg@mailman.ccsds.org></span><span style="font-size:12.0pt">
</span><span style="font-size:7.5pt;font-family:"sans-serif",serif;color:#5F5F5F"><br>
Date: </span><span style="font-size:7.5pt;font-family:"sans-serif",serif">13/11/2017 01:09</span><span style="font-size:12.0pt">
</span><span style="font-size:7.5pt;font-family:"sans-serif",serif;color:#5F5F5F"><br>
Subject: </span><span style="font-size:7.5pt;font-family:"sans-serif",serif">Re: [CESG] Additional presentation to CMC for extra items</span><span style="font-size:12.0pt">
</span><o:p></o:p></p>
<div class="MsoNormal" align="center" style="margin-left:.5in;text-align:center">
<hr size="2" width="100%" noshade="" style="color:#A0A0A0" align="center">
</div>
<p class="MsoNormal" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in">
<span style="font-size:12.0pt"><br>
<br>
</span><span style="font-size:10.0pt"><br>
Gippo,</span><span style="font-size:12.0pt"> </span><span style="font-size:10.0pt"><br>
</span><span style="font-size:12.0pt"> </span><span style="font-size:10.0pt"><br>
I know that these issues were raised prior to the WG and that both of them were discussed within the meetings. Ken Andrews gave a presentation on the coding issue and Greg Kazz gave a presentation on the SPP which you, I, Jonathan, and Scott were all present
for.</span><span style="font-size:12.0pt"> </span><span style="font-size:10.0pt"><br>
</span><span style="font-size:12.0pt"> </span><span style="font-size:10.0pt"><br>
Given this situation, and the very straightforward fact that text was left out of a revised document without any explanation, I do not think that what I have stated is in any way unilateral. In fact, it seems to me that it is you who are unilaterally throwing
roadblocks in the way of forward progress in both of these cases.</span><span style="font-size:12.0pt">
</span><span style="font-size:10.0pt"><br>
</span><span style="font-size:12.0pt"> </span><span style="font-size:10.0pt"><br>
Regards, Peter</span><span style="font-size:12.0pt"> </span><span style="font-size:10.0pt"><br>
</span><span style="font-size:12.0pt"> </span><span style="font-size:10.0pt"><br>
</span><span style="font-size:12.0pt"> <b><br>
From: </b>Gian Paolo Calzolari <Gian.Paolo.Calzolari@esa.int><b><br>
Date: </b>Sunday, November 12, 2017 at 1:15 PM<b><br>
To: </b>Peter Shames <peter.m.shames@jpl.nasa.gov><b><br>
Cc: </b>Nestor Peccia <Nestor.Peccia@esa.int>, CCSDS Engineering Steering Group - CESG Exec <cesg@mailman.ccsds.org><b><br>
Subject: </b>Re: [CESG] Additional presentation to CMC for extra items </span><span style="font-size:10.0pt"><br>
</span><span style="font-size:12.0pt"> </span><span style="font-size:10.0pt"><br>
Peter. <br>
Your points look as something that should have been discussed in WGs (were you there?)</span><span style="font-size:12.0pt">
</span><span style="font-size:10.0pt"><br>
</span><span style="font-size:12.0pt"> </span><span style="font-size:10.0pt"><br>
I do not share your view and I reserve to complain if unilaterally presented to CMC.
<br>
</span><span style="font-size:12.0pt"> </span><span style="font-size:10.0pt"><br>
Ciao</span><span style="font-size:12.0pt"> </span><span style="font-size:10.0pt"><br>
</span><span style="font-size:12.0pt"> </span><span style="font-size:10.0pt"><br>
Gian Paolo</span><span style="font-size:12.0pt"> </span><span style="font-size:10.0pt"><br>
Sent from my iPhone</span><span style="font-size:12.0pt"> </span><span style="font-size:10.0pt"><br>
<br>
On 12. Nov 2017, at 22:08, Shames, Peter M (312B) <</span><a href="mailto:peter.m.shames@jpl.nasa.gov"><span style="font-size:10.0pt;color:#0082BF">peter.m.shames@jpl.nasa.gov</span></a><span style="font-size:10.0pt">> wrote:</span><span style="font-size:12.0pt">
</span><span style="font-size:10.0pt"><br>
Hi Nestor,</span><span style="font-size:12.0pt"> </span><span style="font-size:10.0pt"><br>
</span><span style="font-size:12.0pt"> </span><span style="font-size:10.0pt"><br>
There is no NWI page for the SecWG inputs because they do not yet have a plan for the work with work level estimates. What they have is a "plan for a plan". When they get done planning I'll submit the requests.</span><span style="font-size:12.0pt">
</span><span style="font-size:10.0pt"><br>
</span><span style="font-size:12.0pt"> </span><span style="font-size:10.0pt"><br>
And on the subject of "things causing delays to projects", I would point out that the CESG approval cycle for draft and "proposed for publication" document is not the only place where delays are introduced. It's just the one where there are currently issues
being voiced. I have also given voice to the sorts of delays that have recently been introduced in the SPP and the AOS coding topics where work is being started, or errors are being fixed. These were not included in the materials you prepared, but they are
very real sources of delays and thus should also be addressed.</span><span style="font-size:12.0pt">
</span><span style="font-size:10.0pt"><br>
</span><span style="font-size:12.0pt"> </span><span style="font-size:10.0pt"><br>
SPP</span><span style="font-size:12.0pt"> </span><span style="font-size:10.0pt"><br>
In the case of SPP, even though there was a meeting that arrived at consensus on the need and the topics to be covered, involving people from three SLS working groups, and the SIS, SOIS and SEA areas, there was an added request to create a white paper prior
to starting the project in the WG. This is certainly covered by the procedures, but it is usually invoked when there is a totally new, and not well understood, topic being introduced. In this case the work is quite well understood and the delay somewhat
uncalled for. Just as you have "streamlined" some of the CESG voting procedures to avoid delays the same thing could have been done in this case.</span><span style="font-size:12.0pt">
</span><span style="font-size:10.0pt"><br>
</span><span style="font-size:12.0pt"> </span><span style="font-size:10.0pt"><br>
AOS coding</span><span style="font-size:12.0pt"> </span><span style="font-size:10.0pt"><br>
In the case of the AOS coding for uplink there is a clear and documented situation where the topic of using TM coding for AOS, for uplink and downlink, were documented in an earlier CCSDS spec, "TM Channel Coding", CCSDS 101.0-B-6, but got dropped from the
current "TM Synch and Channel Coding" spec, CCSDS <br>
In the original 101.0 document, under Sec 1.3 Applicability, it stated, very clearly (<b><u>emphasis</u></b> added):</span><span style="font-size:12.0pt">
</span><span style="font-size:10.0pt"><br>
</span><span style="font-size:12.0pt"> </span><span style="font-size:10.0pt;color:#0082BF"><br>
In addition to being applicable to conventional Packet Telemetry systems [1], <b>
<u>the codes in this recommendation are applicable to the forward and return links of Advanced Orbiting Systems (AOS) [2]</u></b>. For coding purposes, the terms ìTransfer Frameî and ìReed-Solomon Codeblockî as used in this recommendation are understood to
be equivalent to the AOS terms ìVirtual Channel Data Unitî (VCDU), and ìCoded Virtual Channel Data Unitî (CVCDU), respectively.
</span><span style="font-size:10.0pt"><br>
</span><span style="font-size:12.0pt"> </span><span style="font-size:10.0pt"><br>
For reasons that are totally unexplained in any form that anyone can unearth, this was modified in the current 131.0, under Sec 1.0 Purpose, to read:</span><span style="font-size:12.0pt">
</span><span style="font-size:10.0pt"><br>
</span><span style="font-size:12.0pt"> </span><span style="font-size:10.0pt;color:#0082BF"><br>
The purpose of this Recommended Standard is to specify synchronization and channel coding schemes used with the TM Space Data Link Protocol (reference [1]) or the AOS Space Data Link Protocol (reference [2]). These schemes are to be used over space-to- ground
or space-to-space communications links by space missions. </span><span style="font-size:10.0pt"><br>
</span><span style="font-size:12.0pt"> </span><span style="font-size:10.0pt"><br>
The consequence of this change, which appears to be both editorial and wrongly placed, iy should be in Applicability, as before, is to arbitrarily remove the explicit coverage for AOS uplink from the TM Synch and Channel Coding book. The only explanation given
was "this spec if for telemetry", therefore it should not be used for forward links. But in the original 101.0 spec this case was covered, with no apparent issue being identified.
<br>
</span><span style="font-size:12.0pt"> </span><span style="font-size:10.0pt"><br>
The "remedy" proposed for this editorial error is, instead of just fixing the error, to require that a new "Magenta Book" be produced. I'll leave out of the discussion that this would actually need to be a Blue Book, of type "utilization profile". Requiring
that this error be remedied by creation of a new Blue Book appears to be punitive and will cause expense of resources that could well be invested otherwise. It also is calling for creation of a new type of document within SLS, for which there is no precedent.
If one were to treat this request as a new policy on SLS document there would be a whole slew of new documents required, specifying how to use TC over specific codes, TM over other codes, etc. This is a waste of time and resources which could be very easily
avoided by simply using a corriegendum to repair the missing text.</span><span style="font-size:12.0pt">
</span><span style="font-size:10.0pt"><br>
</span><span style="font-size:12.0pt"> </span><span style="font-size:10.0pt"><br>
So my request is that you either treat all of these sources of delays in an even handed fashion or that you treat none of them. Furthermore, if you do decide to include the materials that we discussed I would request that you explicitly include the points
I made during the meeting on the proximal source of the issue being inadequate quality control at the originating WG and Area level. All of these issues could have been avoided at CESG review if the documents had been closer to error free and complete when
submitted.</span><span style="font-size:12.0pt"> </span><span style="font-size:10.0pt"><br>
</span><span style="font-size:12.0pt"> </span><span style="font-size:10.0pt"><br>
Best regards, Peter</span><span style="font-size:12.0pt"> </span><span style="font-size:10.0pt"><br>
</span><span style="font-size:12.0pt"> </span><span style="font-size:10.0pt"><br>
</span><span style="font-size:12.0pt"> </span><span style="font-size:10.0pt"><br>
</span><span style="font-size:12.0pt"> </span><span style="font-size:10.0pt"><br>
</span><span style="font-size:12.0pt"> <b><br>
From: </b>CESG <</span><a href="mailto:cesg-bounces@mailman.ccsds.org"><span style="font-size:12.0pt;color:#0082BF">cesg-bounces@mailman.ccsds.org</span></a><span style="font-size:12.0pt">> on behalf of Nestor Peccia <</span><a href="mailto:Nestor.Peccia@esa.int"><span style="font-size:12.0pt;color:#0082BF">Nestor.Peccia@esa.int</span></a><span style="font-size:12.0pt">><b><br>
Date: </b>Sunday, November 12, 2017 at 6:33 AM<b><br>
To: </b>CCSDS Engineering Steering Group - CESG Exec <</span><a href="mailto:cesg@mailman.ccsds.org"><span style="font-size:12.0pt;color:#0082BF">cesg@mailman.ccsds.org</span></a><span style="font-size:12.0pt">><b><br>
Subject: </b>[CESG] Additional presentation to CMC for extra items </span><span style="font-size:10.0pt"><br>
</span><span style="font-size:12.0pt"> </span><span style="font-size:10.0pt;font-family:"sans-serif",serif"><br>
Dear all.</span><span style="font-size:10.0pt"> </span><span style="font-size:10.0pt;font-family:"sans-serif",serif"><br>
<br>
Please find attached the additional presentation to CMC.</span><span style="font-size:10.0pt">
</span><span style="font-size:10.0pt;font-family:"sans-serif",serif"><br>
<br>
It still miss some inputs from SEA SEC WG for the NWIs.</span><span style="font-size:10.0pt">
</span><span style="font-size:10.0pt;font-family:"sans-serif",serif"><br>
<br>
Comments welcome</span><span style="font-size:10.0pt"> <br>
<br>
</span><span style="font-size:10.0pt;font-family:"sans-serif",serif"><br>
<br>
ciao</span><span style="font-size:10.0pt"> </span><span style="font-size:10.0pt;font-family:"sans-serif",serif"><br>
nestor</span><span style="font-size:10.0pt"> </span><span style="font-size:10.0pt;font-family:"Courier New",serif"><br>
This message and any attachments are intended for the use of the addressee or addressees only.</span><span style="font-size:12.0pt">
</span><span style="font-size:10.0pt;font-family:"Courier New",serif"><br>
The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its</span><span style="font-size:12.0pt">
</span><span style="font-size:10.0pt;font-family:"Courier New",serif"><br>
content is not permitted.</span><span style="font-size:12.0pt"> </span><span style="font-size:10.0pt;font-family:"Courier New",serif"><br>
If you received this message in error, please notify the sender and delete it from your system.</span><span style="font-size:12.0pt">
</span><span style="font-size:10.0pt;font-family:"Courier New",serif"><br>
Emails can be altered and their integrity cannot be guaranteed by the sender.</span><span style="font-size:12.0pt">
</span><span style="font-size:10.0pt;font-family:"Courier New",serif"><br>
</span><span style="font-size:12.0pt"> </span><span style="font-size:10.0pt;font-family:"Courier New",serif"><br>
Please consider the environment before printing this email.</span><span style="font-size:12.0pt">
</span><span style="font-size:10.0pt;font-family:"Courier New",serif"><br>
</span><span style="font-size:12.0pt"> </span><span style="font-size:10.0pt;font-family:"Courier New",serif"><br>
This message and any attachments are intended for the use of the addressee or addressees only.</span><span style="font-size:12.0pt">
</span><span style="font-size:10.0pt;font-family:"Courier New",serif"><br>
The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its</span><span style="font-size:12.0pt">
</span><span style="font-size:10.0pt;font-family:"Courier New",serif"><br>
content is not permitted.</span><span style="font-size:12.0pt"> </span><span style="font-size:10.0pt;font-family:"Courier New",serif"><br>
If you received this message in error, please notify the sender and delete it from your system.</span><span style="font-size:12.0pt">
</span><span style="font-size:10.0pt;font-family:"Courier New",serif"><br>
Emails can be altered and their integrity cannot be guaranteed by the sender.</span><span style="font-size:12.0pt">
</span><span style="font-size:10.0pt;font-family:"Courier New",serif"><br>
</span><span style="font-size:12.0pt"> </span><span style="font-size:10.0pt;font-family:"Courier New",serif"><br>
Please consider the environment before printing this email.</span><span style="font-size:12.0pt">
</span><span style="font-size:10.0pt;font-family:"Courier New",serif"><br>
</span><span style="font-size:12.0pt"> <br>
</span><br>
<tt><span style="font-size:12.0pt">This message and any attachments are intended for the use of the addressee or addressees only.</span></tt><span style="font-size:12.0pt;font-family:"Courier New",serif"><br>
<tt>The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its</tt><br>
<tt>content is not permitted.</tt><br>
<tt>If you received this message in error, please notify the sender and delete it from your system.</tt><br>
<tt>Emails can be altered and their integrity cannot be guaranteed by the sender.</tt><br>
<br>
<tt>Please consider the environment before printing this email.</tt><br>
<br>
</span><tt><span style="font-size:10.0pt">_______________________________________________</span></tt><span style="font-size:10.0pt;font-family:"Courier New",serif"><br>
<tt>CESG mailing list</tt><br>
<tt>CESG@mailman.ccsds.org</tt><br>
</span><a href="https://mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg"><tt><span style="font-size:10.0pt">https://mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg</span></tt></a><span style="font-size:10.0pt;font-family:"Courier New",serif"><br>
<br>
</span><o:p></o:p></p>
<pre style="margin-left:.5in">This message and any attachments are intended for the use of the addressee or addressees only.<o:p></o:p></pre>
<pre style="margin-left:.5in">The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its<o:p></o:p></pre>
<pre style="margin-left:.5in">content is not permitted.<o:p></o:p></pre>
<pre style="margin-left:.5in">If you received this message in error, please notify the sender and delete it from your system.<o:p></o:p></pre>
<pre style="margin-left:.5in">Emails can be altered and their integrity cannot be guaranteed by the sender.<o:p></o:p></pre>
<pre style="margin-left:.5in"><o:p> </o:p></pre>
<pre style="margin-left:.5in">Please consider the environment before printing this email.<o:p></o:p></pre>
<pre style="margin-left:.5in"><o:p> </o:p></pre>
</div>
</body>
</html>