<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:12.0pt;
font-family:"Times New Roman";}
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";}
tt
{mso-style-priority:99;
font-family:"Courier New";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Courier;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:Calibri;
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"><span style="font-size:11.0pt;font-family:Calibri">Hi Gippo,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Thanks for being thorough. Apparently I missed those. I'll make the changes and send the revised doc to Tom Gannett today. The rest of the resolution and poll processing can stand as
they are.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">It's a little hard to tell exactly what was requested in some of these changes, so I have marked what I think is the affected text in
<span style="color:red">red</span>. Please verify that these are correct.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Thanks, Peter<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<blockquote style="border:none;border-left:solid #B5C4DF 4.5pt;padding:0in 0in 0in 4.0pt;margin-left:3.75pt;margin-right:0in">
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-family:Calibri;color:black">From: </span>
</b><span style="font-family:Calibri;color:black">Gian Paolo Calzolari <Gian.Paolo.Calzolari@esa.int><br>
<b>Date: </b>Wednesday, September 28, 2016 at 8:01 AM<br>
<b>To: </b>Peter Shames <peter.m.shames@jpl.nasa.gov><br>
<b>Cc: </b>Tom Gannett <thomas.gannett@tgannett.net>, "Enrico.Vassallo@esa.int" <Enrico.Vassallo@esa.int>, CCSDS Engineering Steering Group - CESG Exec <cesg@mailman.ccsds.org><br>
<b>Subject: </b>Old comemnts........: [CESG] SEA Resolution SEA-R-2016-09-001: Request Agency Review for publication of revised CCSDS SCID Code Assignment Control Procedures<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:"sans-serif","serif"">Dear Peter,</span>
<br>
<span style="font-size:10.0pt;font-family:"sans-serif","serif""> it looks as the comments provided in the attached mail on July 12 have been overlooked.</span>
<br>
<span style="font-size:10.0pt;font-family:"sans-serif","serif"">Ciao</span> <br>
<br>
<span style="font-size:10.0pt;font-family:"sans-serif","serif"">Gian Paolo</span>
<br>
<br>
<br>
<span style="font-size:7.5pt;font-family:"sans-serif","serif";color:purple">----- Forwarded by Gian Paolo Calzolari/esoc/ESA -----</span>
<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"">"CCSDS CESG --" <cesg@mailman.ccsds.org></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"">"Tom Gannett" <thomas.gannett@tgannett.net>, Enrico.Vassallo@esa.int, "SANA Steering Group\(SSG\)"
<ssg@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"">12/07/2016 11:43</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] SEA Resolution SEA-R-2016-07-001: Request publication of revised CCSDS SCID Code Assignment
Control Procedures</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="text-align:center">
<hr size="2" width="100%" noshade="" style="color:#AAAAAA" align="center">
</div>
<p class="MsoNormal"><br>
<br>
<br>
<span style="font-size:10.0pt;font-family:"sans-serif","serif"">Dear Peter,</span>
<span style="font-size:10.0pt;font-family:"sans-serif","serif""><br>
I passed the document to Enrico that had a quick look at it with the result given by the attached comments to be considered at the appropriate point in time with respect to Poll Preatation, Agency Review or other.</span>
<br>
<span style="font-size:10.0pt;font-family:"sans-serif","serif""><br>
Thanks to Enrico and best regards to everybody</span> <br>
<span style="font-size:10.0pt;font-family:"sans-serif","serif""><br>
Gian Paolo</span> <br>
<span style="font-size:10.0pt;font-family:"sans-serif","serif""><br>
--------------------------------------------------------------------------------------------------------------</span>
<br>
<span style="font-size:10.0pt;font-family:"sans-serif","serif""><br>
1) Ka-band missing frequency range in Table 2</span> <o:p></o:p></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="616" style="width:462.0pt;border-collapse:collapse">
<tbody>
<tr style="height:6.0pt">
<td width="193" valign="top" style="width:144.75pt;border:none;border-right:solid black 1.0pt;padding:.75pt .75pt .75pt .75pt;height:6.0pt">
<p class="MsoNormal">Ka-Band SRS or EES <b>27-40 GHz</b> <o:p></o:p></p>
</td>
<td width="156" valign="top" style="width:117.0pt;border:none;border-right:solid black 1.0pt;padding:.75pt .75pt .75pt .75pt;height:6.0pt">
<p class="MsoNormal"><span style="color:red">25.5 - 27 GHz </span><o:p></o:p></p>
</td>
<td width="37" valign="top" style="width:27.75pt;border:none;border-right:solid black 1.0pt;padding:.75pt .75pt .75pt .75pt;height:6.0pt">
<p class="MsoNormal">Ka-NE <o:p></o:p></p>
</td>
<td width="163" valign="top" style="width:122.25pt;border:none;border-right:solid black 1.0pt;padding:.75pt .75pt .75pt .75pt;height:6.0pt">
<p class="MsoNormal">31.8 – 32.3 GHz <o:p></o:p></p>
</td>
<td width="51" valign="top" style="width:38.25pt;border:none;padding:.75pt .75pt .75pt .75pt;height:6.0pt">
<p class="MsoNormal">Ka-DS<o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal"><br>
<br>
<span style="font-size:10.0pt;font-family:"sans-serif","serif""><br>
<span style="color:red">I suggest adding an additional line as:</span></span><span style="color:red">
<o:p></o:p></span></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="616" style="width:462.0pt;border-collapse:collapse">
<tbody>
<tr style="height:6.0pt">
<td width="198" valign="top" style="width:148.5pt;border:none;border-right:solid black 1.0pt;padding:.75pt .75pt .75pt .75pt;height:6.0pt">
<p class="MsoNormal"><span style="color:red">Ka-Band SRS <b><br>
27-40 GHz</b> <o:p></o:p></span></p>
</td>
<td width="159" valign="top" style="width:119.25pt;border:none;border-right:solid black 1.0pt;padding:.75pt .75pt .75pt .75pt;height:6.0pt">
<p class="MsoNormal"><span style="color:red">37.0-38.0 GHz <o:p></o:p></span></p>
</td>
<td width="38" valign="top" style="width:28.5pt;border:none;border-right:solid black 1.0pt;padding:.75pt .75pt .75pt .75pt;height:6.0pt">
<p class="MsoNormal"><span style="color:red">Ka <o:p></o:p></span></p>
</td>
<td width="166" valign="top" style="width:124.5pt;border:none;border-right:solid black 1.0pt;padding:.75pt .75pt .75pt .75pt;height:6.0pt">
<p class="MsoNormal"><span style="color:red">37.0-38.0 GHz <o:p></o:p></span></p>
</td>
<td width="38" valign="top" style="width:28.5pt;border:none;padding:.75pt .75pt .75pt .75pt;height:6.0pt">
<p class="MsoNormal"><span style="color:red">Ka<o:p></o:p></span></p>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal"><br>
<br>
<span style="font-size:10.0pt;font-family:"sans-serif","serif""><br>
This allocation can be used for both NE and DS missions so I suggest calling it simply Ka. Please note that I do not know what the color code in table 2 means (some frequencies in blue...)</span>
<br>
<span style="font-size:10.0pt;font-family:"sans-serif","serif""><br>
2) Statement below table 2</span> <br>
<span style="font-size:10.0pt;font-family:"sans-serif","serif""><br>
Replace allocated by assigned and allocation by assignment (they have different meanings in ITU).</span>
<br>
<span style="font-size:10.0pt;font-family:"sans-serif","serif""><br>
From:</span> <br>
<br>
The SCID assignment procedures require that each registered spacecraft specify the one (or more) frequency bands that they have been allocated by their agency spectrum manager. It is expected that every spacecraft, early in its development process, will acquire
a frequency allocation for uplink and downlink. The assignment of one or more GSCIDs will be done relative to the number of frequency bands that a spacecraft uses, but every attempt will be made to assign the same SCID in all bands if that is possible.
<br>
<span style="font-size:10.0pt;font-family:"sans-serif","serif""><br>
To:</span> <br>
<br>
The SCID assignment procedures require that each registered spacecraft specify the one (or more) frequency bands that they have been
<b><span style="color:red">assigned</span></b><span style="color:red"> </span>by their agency spectrum manager. It is expected that every spacecraft, early in its development process, will acquire a frequency
<b><span style="color:red">assignment</span></b><span style="color:red"> </span>for uplink and downlink. The assignment of one or more GSCIDs will be done relative to the number of frequency bands that a spacecraft uses, but every attempt will be made to
assign the same SCID in all bands if that is possible. <br>
<span style="font-size:10.0pt;font-family:"sans-serif","serif""><br>
3) SCID request form (non normative)</span> <br>
<span style="font-size:10.0pt;font-family:"sans-serif","serif""><br>
The given print out in old Annex A provided as example shows that the exact frequencies have to be entered differently from the rest of the document specifying only the frequency bins. It is believed that many agencies would not like to have the exact frequencies
in a SANA on-line database. <b><span style="color:red">Therefore, the form even if called example should be adjusted to align with the text:</span></b></span><span style="color:red">
</span><br>
NOTE - The form requests only the frequency bands, it does not require the exact operating frequencies. As long as the same VN and FB is used for uplink and downlink only one GSCID need be assigned.
<br>
<span style="font-size:10.0pt;font-family:"sans-serif","serif""><br>
Alternatively, the example shall be deleted.</span> <br>
<br>
<span style="font-size:10.0pt;font-family:"sans-serif","serif""><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"sans-serif","serif";color:red">I'll ask the SANA guys to fix this if they have not already. I think that the form, in general, needs to be updated. I would prefer to leave in an example (a correct
one) since it shows users what to expect.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"sans-serif","serif""><br>
4) <b><span style="color:red">Editorials</span></b></span><span style="color:red">
</span><br>
<span style="font-size:10.0pt;font-family:"sans-serif","serif""><br>
<span style="color:red">In Table 2, EES shall be replaced by EESS (occurs twice).
</span></span><span style="color:red"><br>
</span><span style="font-size:10.0pt;font-family:"sans-serif","serif";color:red"><br>
ITC shall be changed to ITU in Annex A. </span><span style="color:red"><br>
</span><span style="font-size:10.0pt;font-family:"sans-serif","serif";color:red"><br>
In ITU, the T stands for Telecommunication (singular). In the magenta book all occurrences are in plural.
</span><span style="color:red"><br>
</span><span style="font-size:10.0pt;font-family:"sans-serif","serif";color:red"><br>
WRC in Annex A is spelled out as Radiocommunications (plural) whereas it is singular.</span><span style="color:red">
<br>
</span><br>
<br>
<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"">"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">To: </span><span style="font-size:7.5pt;font-family:"sans-serif","serif"">"CCSDS Secretariat" <secretariat@mailman.ccsds.org>, "Tom Gannett" <thomas.gannett@tgannett.net></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"">"SANA Steering Group\(SSG\)" <ssg@mailman.ccsds.org>, "CCSDS Engineering Steering Group - CESG Exec"
<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"">23/09/2016 23:46</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"">[CESG] SEA Resolution SEA-R-2016-09-001: Request Agency Review for publication of revised CCSDS
SCID Code Assignment Control Procedures</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="text-align:center">
<hr size="2" width="100%" noshade="" style="color:#AAAAAA" align="center">
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
<br>
<span style="font-size:13.5pt;font-family:Calibri">[attachment "320x0b6c1_mods_7-23Sep16.docx" deleted by Gian Paolo Calzolari/esoc/ESA]
</span><br>
<br>
<span style="font-size:13.5pt;font-family:Calibri">Dear CCSDS Secretariat,</span>
<br>
<span style="font-size:13.5pt;font-family:Calibri"> </span> <br>
<span style="font-size:13.5pt;font-family:Calibri">Please find attached the SEA resolution concerning the request for Agency Review for publication of the revised CCSDS SCID Code Assignment Control Procedures Magenta Book. The major changes are the inclusion
of frequency band bins for allocation of Qualified SCID (Q-SCID), references to the new registries defined in the RMP, and re-classifying the document as a Magenta Book based upon its type.</span>
<br>
<span style="font-size:13.5pt;font-family:Calibri"> </span> <br>
<span style="font-size:13.5pt;font-family:Calibri">This fixes all of the conditions raised in the earlier CESG vote and the CMC feedback that we also received. There are no remaining conditions that I am aware of aside from the one requesting that this document
be given an Agency review because it is a major change to a key document and has an effect on the Agency procedures for requesting and relinquishing SCIDs. In accordance with one CMC condition it does not require the specification of uplink and downlink
<b><i>frequencies</i></b>, but it does require correct specification of the uplink and downlink
<b><i>frequency bands</i></b>, aligned to the actual frequency ranges and not just to some colloquial use of, for example, "K-band" when the actual frequency in use falls into the X-band range.
</span><br>
<span style="font-family:Calibri"> </span> <br>
<span style="font-size:13.5pt;font-family:Calibri">Thanks, Peter</span> <br>
<span style="font-size:13.5pt;font-family:Calibri"> </span> <br>
<span style="font-size:13.5pt;font-family:Calibri">==========================================================================</span>
<br>
<span style="font-size:13.5pt;font-family:Calibri"> </span> <br>
<b><span style="font-size:13.5pt;font-family:Calibri">SEA-R-2016-09-001 Request Agency Review of revised CCSDS SCID Code Assignment Control Procedures</span></b>
<br>
<span style="font-size:13.5pt;font-family:Calibri">--------------------------------------------------------------------------------</span>
<br>
<span style="font-size:13.5pt;font-family:Calibri"> </span> <br>
<span style="font-size:13.5pt;font-family:Calibri">The <b>System Engineering Area,</b></span>
<br>
<span style="font-size:13.5pt;font-family:Calibri"> </span> <br>
<b><span style="font-size:13.5pt;font-family:Calibri">CONSIDERING</span></b><span style="font-size:13.5pt;font-family:Calibri"> that:</span>
<br>
<span style="font-size:13.5pt;font-family:Calibri"> </span> <br>
<span style="font-size:13.5pt;font-family:Calibri">The SEA SANA Steering Group (SSG) has produced a revision of the existing Blue Book called the CCSDS GLOBAL SPACECRAFT IDENTIFIER FIELD:</span>
<br>
<span style="font-size:13.5pt;font-family:Calibri">CODE ASSIGNMENT CONTROL PROCEDURES (CCSDS 320.0-B-6), and that</span>
<br>
<span style="font-size:13.5pt;font-family:Calibri">The source document, CCSDS 320.0-B-1, was originally directly published as a CMC Blue Book document, and that</span>
<br>
<span style="font-size:13.5pt;font-family:Calibri">The specific major changes to the document have already been reviewed and agreed to by the CESG and CMC, and that</span>
<br>
<span style="font-size:13.5pt;font-family:Calibri">All of the requested updates have been made to satisfy the identified conditions.</span>
<br>
<span style="font-size:13.5pt;font-family:Calibri"> </span> <br>
<span style="font-size:13.5pt;font-family:Calibri">And <b>RECOGNIZING</b> that: </span>
<br>
<span style="font-size:13.5pt;font-family:Calibri"> </span> <br>
<span style="font-size:13.5pt;font-family:Calibri">A CCSDS Area Director is responsible for requesting CESG concurrence prior to publication, and that</span>
<br>
<span style="font-size:13.5pt;font-family:Calibri">The CCSDS Organization and Processes (A02.1-Y-4 cor 2) in Section 6.2.2.2 requests that the AD forward the draft documents to the CESG, and</span>
<br>
<span style="font-size:13.5pt;font-family:Calibri">notify the Chief Technical Editor.</span>
<br>
<span style="font-size:13.5pt;font-family:Calibri"> </span> <br>
<span style="font-size:13.5pt;font-family:Calibri">And <b>RECOGNIZING</b> that:</span>
<br>
<span style="font-size:13.5pt;font-family:Calibri"> </span> <br>
<span style="font-size:13.5pt;font-family:Calibri">The CCSDS Organization and Processes (A02.1-Y-4 cor 2) in Section 6.1.4.3 defines this type of book (a process or procedure description) as a Magenta Book, and that</span>
<br>
<span style="font-size:13.5pt;font-family:Calibri">Sec 6.2.7 requires periodic review and re-confirmation of Normative Track documents.</span>
<br>
<span style="font-size:13.5pt;font-family:Calibri"> </span> <br>
<b><span style="font-size:13.5pt;font-family:Calibri">RESOLVES</span></b><span style="font-size:13.5pt;font-family:Calibri"> to request:</span>
<br>
<span style="font-size:13.5pt;font-family:Calibri"> </span> <br>
<span style="font-size:13.5pt;font-family:Calibri">That the Chief Technical Editor ready the document for review, and that</span>
<br>
<span style="font-size:13.5pt;font-family:Calibri">The document be re-classified as a Magenta Book, to properly characterize it based on its contents, and that</span>
<br>
<span style="font-size:13.5pt;font-family:Calibri">The Secretariat create the necessary CESG poll to request the CESG review and approve release of this document for Agency Review, and that</span>
<br>
<span style="font-size:13.5pt;font-family:Calibri">Once the CESG poll succeeds that the CMC be polled to approve the document for Agency Review.</span>
<br>
<span style="font-size:13.5pt;font-family:Calibri"> </span> <br>
<span style="font-size:13.5pt;font-family:Calibri"> </span> <br>
<span style="font-size:13.5pt;font-family:Calibri"> </span><tt><span style="font-size:10.0pt">_______________________________________________</span></tt><span style="font-size:10.0pt;font-family:"Courier New""><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><o:p></o:p></p>
<pre>This message and any attachments are intended for the use of the addressee or addressees only.<o:p></o:p></pre>
<pre>The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its<o:p></o:p></pre>
<pre>content is not permitted.<o:p></o:p></pre>
<pre>If you received this message in error, please notify the sender and delete it from your system.<o:p></o:p></pre>
<pre>Emails can be altered and their integrity cannot be guaranteed by the sender.<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Please consider the environment before printing this email.<o:p></o:p></pre>
</blockquote>
</div>
</body>
</html>