<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)">
<style><!--
/* Font Definitions */
@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:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"Arial Narrow";
panose-1:2 11 6 6 2 2 2 3 2 4;}
@font-face
{font-family:Cambria;
panose-1:2 4 5 3 5 4 6 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
h1
{mso-style-priority:9;
mso-style-link:"Titre 1 Car";
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:24.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.Titre1Car
{mso-style-name:"Titre 1 Car";
mso-style-priority:9;
mso-style-link:"Titre 1";
font-family:"Calibri Light",sans-serif;
color:#2E74B5;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
p.static, li.static, div.static
{mso-style-name:static;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.Heading1Char
{mso-style-name:"Heading 1 Char";
mso-style-priority:9;
mso-style-link:"Heading 1";
font-family:"Calibri",sans-serif;
font-weight:bold;}
p.Heading1, li.Heading1, div.Heading1
{mso-style-name:"Heading 1";
mso-style-link:"Heading 1 Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.berschrift1, li.berschrift1, div.berschrift1
{mso-style-name:"Überschrift 1";
mso-style-link:"Überschrift 1 Zchn";
margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.berschrift1Zchn
{mso-style-name:"Überschrift 1 Zchn";
mso-style-priority:9;
mso-style-link:"Überschrift 1";
font-family:"Cambria",serif;
color:#365F91;
font-weight:bold;}
span.EmailStyle25
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.menu-item-text
{mso-style-name:menu-item-text;}
span.ms-hidden
{mso-style-name:ms-hidden;}
span.s7
{mso-style-name:s7;}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
span.s5
{mso-style-name:s5;}
span.ms-metadata
{mso-style-name:ms-metadata;}
span.EmailStyle32
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle33
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></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="FR" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D;mso-fareast-language:EN-US">Bonjour all<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US">I would also proceed with the modification for what regards this resolution.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US">Nevertheless, some new SC13 – SC14 interactions were discussed at the last CMC / SC13 meeting and I also saw in the minutes of the SC14 meeting that they have ideas for
some new joint activities.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US">All these aspects should be assembled as agenda items to the SC13 – SC14 FtF meeting that could be organized in the fall, as per the recent discussions in St Hubert.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US">Best regards<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:5.0pt;margin-right:0cm;margin-bottom:5.0pt;margin-left:0cm;text-autospace:none">
<b><i><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial Narrow",sans-serif;color:#1F497D">Jean-Marc Soula
<br>
</span></i></b><i><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial Narrow",sans-serif;color:#1F497D">CNES
</span></i><i><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial Narrow",sans-serif;color:#002060">–
</span></i><i><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial Narrow",sans-serif;color:#1F497D">DNO/TSA/DA<br>
Deputy Head of Telecom, Stations networks and Alert systems Department<br>
18 Avenue Edouard Belin <br>
31401 Toulouse Cedex 9 - France <br>
Tel.: +33 (0)5 61 2 74647 <br>
Fax.: +33 (0)5 61 2 </span></i><i><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial Narrow",sans-serif;color:#002060">73993</span></i><i><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial Narrow",sans-serif;color:#1F497D"><br>
Email: <a href="mailto:jean-marc.soula@cnes.fr"><span style="color:blue">jean-marc.soula@cnes.fr</span></a>
</span></i><i><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial Narrow",sans-serif;color:#002060"><br>
<a href="http://www.cnes.fr/"><span style="color:blue">www.cnes.fr</span></a><o:p></o:p></span></i></p>
</div>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b>De :</b> CMC-EXEC <cmc-exec-bounces@mailman.ccsds.org> <b>
De la part de</b> osvaldo.peinado@dlr.de<br>
<b>Envoyé :</b> mardi 25 juin 2019 14:30<br>
<b>À :</b> peter.m.shames@jpl.nasa.gov; CMC-exec@mailman.ccsds.org<br>
<b>Objet :</b> Re: [CMC Alert] Proposed RID resolution for CMC-P-2018-05-006 Request specific extension of existing TC20/SC13/CCSDS and TC20/SC14 liaison agreement to jointly work on extending the CCSDS Reference Architecture for Space Data Systems (RASDS,
CCSDS 311....<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">Thank you Peter and Edoardo<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">I would proceed with the modifications<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">Best Regards<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D">Osvaldo<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="DE" style="font-size:10.0pt;font-family:"Tahoma",sans-serif">Von:</span></b><span lang="DE" style="font-size:10.0pt;font-family:"Tahoma",sans-serif"> CMC [<a href="mailto:cmc-bounces@mailman.ccsds.org">mailto:cmc-bounces@mailman.ccsds.org</a>]
<b>Im Auftrag von </b>Shames, Peter M (312B) via CMC<br>
<b>Gesendet:</b> Montag, 24. Juni 2019 20:56<br>
<b>An:</b> CMC<br>
<b>Betreff:</b> [CMC] Proposed RID resolution for CMC-P-2018-05-006 Request specific extension of existing TC20/SC13/CCSDS and TC20/SC14 liaison agreement to jointly work on extending the CCSDS Reference Architecture for Space Data Systems (RASDS, CCSDS 311.0-M-1)<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="DE"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Dear CMC members,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">During the CMC poll <a href="https://public.ccsds.org/polls/Lists/CMCP201805006/AllItems.aspx">
<span style="color:windowtext;text-decoration:none">CMC-P-2018-05-006 "Request specific extension of existing TC20/SC13/CCSDS and TC20/SC14 liaison agreement to jointly work on extending the CCSDS Reference Architecture for Space Data Systems (RASDS, CCSDS
311.0-M-1)</span></a>" there was a Condition raised by Eduardo Bergamini:<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" summary="CMC-P-2018-05-006 Request specific extension of existing TC20/SC13/CCSDS and TC20/SC14 liaison agreement to jointly work on extending the CCSDS Reference Architecture for Space Data Systems (RASDS, CCSDS 311.0-M-1)">
<tbody>
<tr>
<td style="padding:.75pt .75pt .75pt .75pt">
<p class="MsoNormal">INPE<o:p></o:p></p>
</td>
<td style="padding:.75pt .75pt .75pt .75pt">
<p class="MsoNormal">Adopt Provisionally (State Conditions)<o:p></o:p></p>
</td>
<td style="padding:.75pt .75pt .75pt .75pt">
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;text-align:justify">
Wherever applicable in the text associated Polling Template, I would like to ask for the change of the current term "CCSDS" by the term "CCSDS-ISO TC20/SC13".
<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;text-align:justify">
It must be reminded that, for many years, CCSDS-ISO TC20/SC13 held JOINT and extensive discussions with ISO TC20/SC14, in this case, with their Liaison representative, Mr. Fred Slane. I (E. Bergamini) had the opportunity of start a series of discussions with
Mr. Fred Slane, years ago, on this subject, at the occasion of a ISO TC20/SC14 Plenary meeting hald in São José dos Campos, years ago. Our late colleague ADRIAN HOOKE, then, as the head of CESG/CCSDS entered in the discussions and started to take active part
in this process. The main objective ofmthis process was to find ways to explore aspects of CCSDS System Architecture that could be of interest for application in the domain of ISO TC20/SC14. Of course, this concept ended up, very naturally, somehow, related
on the work being done by CCSDS SEA WG. SEA WG is being led by the remarkasble work being done by Dr. PETER SHAMES and his WG colleagues, in this case. This is ALL documented in our records. Systematically, whenever possible, Dr. PETER SHAMES has been reporting
to ISO TC20/SC13 meetings on the advancement of his related Liaison activities with Mr. Fred Slane, on the asociated topic. This Liaison work has been officially and explicitly expressed as one of those CCDSDS-ISO TC TC20/SC13 Liaisons with other organizations.
This is important, because ISO TC20/SC13 is the CCSDS "arm" in the domain of ISO. It is also opportune to remind that a Liaison between two different ISO organizations is more flexible and simple to instrument than that when one of the two liaised organi8zations
does not belong to ISO. On behalf of INPE, I do appreciate that this remainder may be taken into consideration by CCSDS, in the request we have expressed in the beginning of the above text. Thank you! <o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">We understand Eduardo's concern and agree that the wording of the text should be changed from referencing "CCSDS" to referencing "CCSDS-ISO TC20/SC13". I think we all understand that we are, in effect, making this liaison
agreement between two ISO organizations, but also that it is the CCSDS "arm" that has the resources to actually do the work. This wording change should reflect that.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">However, in the time since this CESG/CMC poll was initiated (the CESG poll, CESG-P-2017-09-001, dates back to Oct 2017) there has been further discussion between the SEA, on behalf of CCSDS, and the ISO TC20/SC14. In
a recent email exchange our ISO TC20/SC14 colleagues pointed out that there is an existing agreement in place for such work and that there is a process defined for initiating and agreeing on such work. These were created in August 2007 and signed by the relevant
CCSDS – ISO TC20/SC13 and ISO TC20/SC14 leadership, Mike Kearney as the CCSDS General Secretary, Eduardo Bergamini for ISO TC20/SC13, Larry Schultz as the ISO TC20/SC14 Chairman, and Erin Kahn as the ISO TC20/SC14 Secretary. Copies of these documents are
attached.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">In addition to aligning this agreement on joint work with this prior CCSDS – ISO TC20/SC13 and ISO TC20/SC14 agreement, the SC14 would now like to have the text of this Liaison Agreement reflect both extending the CCSDS
Reference Architecture, RASDS, CCSDS 311.0-M-1, and also harmonizing the CCSDS – ISO TC20/SC13 Glossary with the ISO TC20 / SC14 Glossary. In point of fact, they would like to use the SANA Glossary registry to store these harmonized results.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Based on the existing CCSDS – ISO TC20/SC13 and ISO TC20/SC14 agreement it appears that what we should be doing is to handle this according to what is described on pg 2 of the "<b>Agreement for Definition of a Joint Work
Procedure for Identification and Exploration of Liaison Work Related to ISO Standards in Space Systems</b>", in the attached file named "Refs.N405-SC13.&.530-SC14.Agreement.Aug.8.&.6.2007". This allows for creation of an ad hoc Joint Technical Group (JTG),
and that </span><span lang="EN-US" style="font-size:12.0pt">"</span><span class="s7"><span lang="EN-US" style="font-size:12.0pt;font-family:"Arial",sans-serif;color:navy">for each specific work item a corresponding joint agreement, to be expressed in terms
of a</span></span><span class="apple-converted-space"><span lang="EN-US" style="font-size:12.0pt;font-family:"Arial",sans-serif;color:navy"> </span></span><span class="s5"><b><span lang="EN-US" style="font-size:12.0pt;font-family:"Arial",sans-serif;color:navy">'Liaison
Agreement for Work Item'</span></b></span><span class="s7"><span lang="EN-US" style="font-size:12.0pt;font-family:"Arial",sans-serif;color:navy">, or a "LAWI"</span></span><span lang="EN-US" style="font-size:12.0pt">"
</span><span lang="EN-US">I believe that the information that we had in the draft Liaison Agreement, edited to align with this prior agreement, is entirely suitable for this purpose, and I have agreement on this approach from the current ISO TC20 / SC14 Chairman,
Paul Gill, and the current Secretary, Nick Tongson.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">In order to bring all of this proposed work into line with the existing liaison agreement, titled "TechnicalReportContacts.Refs.N406-SC13.&.N531-SC14.Aug.8.&.6.2007", I think we need to make some changes to the wording
of this resolution. In fact, we may need to resubmit it as a new resolution, instead of just finalizing the current one.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Proposed rewording of the resolution …<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><u><span lang="EN-US">From:<o:p></o:p></span></u></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span class="ms-metadata"><span lang="EN-US">TC20/SC14 and SC13/CCSDS agree there is a common, complimentary basis for standards development. From that basis, they agree to the evolution of a common reference
architecture representation. SC14 and SC13/CCSDS agree to exchange information on the evolution of architecture elements such as reference architecture documents, where relevant. The SC14 architectural elements will be developed and approved in SC14. The CCSDS
architectural elements will be developed and approved in CCSDS. They agree to the continued collaboration on standards with common interests.</span></span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><u><span lang="EN-US">To:<o:p></o:p></span></u></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span class="ms-metadata"><span lang="EN-US">CCSDS – ISO TC20/SC13 and ISO TC20/SC14 have an existing framework for standards development, the
</span></span><span lang="EN-US">"<b>Agreement for Definition of a Joint Work Procedure for Identification and Exploration of Liaison Work Related to ISO Standards in Space Systems</b>", documented in the file named "Refs.N405-SC13.&.530-SC14.Agreement.Aug.8.&.6.2007"<span class="ms-metadata">.
From that basis these two organizations agree to create an ad hoc Joint Technical Group to work on two specific topics, as documented in this draft
</span><b>Liaison Agreement for Work Item</b> (LAWI)<span class="ms-metadata">:</span></span><span class="ms-metadata"><span lang="DE"><o:p></o:p></span></span></p>
<p class="MsoListParagraph" style="margin-left:72.0pt;text-indent:-18.0pt"><span class="ms-metadata"><span lang="EN-US">1)</span></span><span class="ms-metadata"><span lang="EN-US" style="font-size:7.0pt;font-family:"Times New Roman",serif">
</span></span><span class="ms-metadata"><span lang="EN-US">Evolution of the CCSDS Reference Architecture for Space Data Systems (RASDS), CCSDS 311.0-M-1, to include new viewpoints required by both organizations<o:p></o:p></span></span></p>
<p class="MsoListParagraph" style="margin-left:72.0pt;text-indent:-18.0pt"><span class="ms-metadata"><span lang="EN-US">2)</span></span><span class="ms-metadata"><span lang="EN-US" style="font-size:7.0pt;font-family:"Times New Roman",serif">
</span></span><span class="ms-metadata"><span lang="EN-US">Harmonization of the Glossary terms common to the two organization and updates to what will become the shared Glossary stored in the CCSDS SANA Glossary registry<o:p></o:p></span></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span class="ms-metadata"><span lang="EN-US"><o:p> </o:p></span></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span class="ms-metadata"><span lang="EN-US">For the first item the CCSDS – TC20/SC13 and TC20/SC14 agree to the Plan of Work that is to evolve a common reference architecture framework and representation. CCSDS
– TC20/SC13 and TC20/SC14 agree to exchange information on the evolution of architecture elements such as reference architecture documents, where relevant. The TC20/SC14 architectural elements will be developed and approved in TC20/SC14. The CCSDS TC20/SC13
architectural elements will be developed and approved in CCSDS. The two organizations agree to identify a suitable path toward publishing the integrated and updated document. This might follow a process similar to that used for the "Conjunction Data Message",
</span></span><span lang="EN-US">CCSDS 508.0-B-1, which is also published as ISO <a href="https://www.iso.org/standard/64784.html?browse=tc" target="_blank">
19389</a>. The Technical Report Contacts for this work item will be: Fred Slane for ISO TC20/SC14 and Peter Shames for CCSDS – ISO TC20/SC13.</span><span lang="DE"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span class="ms-metadata"><span lang="EN-US">For the second item the CCSDS – TC20/SC13 and TC20/SC14 agree to the Plan of Work that is to
</span></span><span lang="EN-US">develop a harmonized set of Glossary terms that are common to the two organizations. The development of the common reference architecture will support identification of the areas of overlap and the areas where the concerns
of the two organizations are disjoint. The existing CCSDS SANA Glossary registry (<a href="https://sanaregistry.org/r/terms">https://sanaregistry.org/r/terms</a>) contains all of the currently identified published CCSDS – TC20/SC13 terms. Work is underway
in various CCSDS Areas to review and update this registry. The TC20/SC14 is also in the process of evaluating their Glossary terms. This Joint Technical Group will be the means to resolve any issues and to manage the process of making updates to what will
become the shared <span class="ms-metadata">CCSDS – TC20/SC13 and TC20/SC14 </span>
Glossary that will be stored in the CCSDS SANA Glossary registry. The Technical Report Contacts for this work item will be: Dan Oltrogge for ISO TC20/SC14 and Peter Shames for CCSDS – ISO TC20/SC13.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">I believe that these changes to the text of the resolution accurately reflect what is required by the existing Liaison Agreement and the procedure that is defined therein. I leave it to the CMC and the Secretariat to
determine if we need a new resolution or if we can just modify the existing one and proceed.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Thanks, Peter Shames<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
</div>
</body>
</html>