<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: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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
h1
{mso-style-priority:9;
mso-style-link:"Heading 1 Char";
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:24.0pt;
font-family:"Calibri",sans-serif;
font-weight:bold;}
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:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
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.static, li.static, div.static
{mso-style-name:static;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
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;}
.MsoChpDefault
{mso-style-type:export-only;}
@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:911624528;
mso-list-type:hybrid;
mso-list-template-ids:-1867731076 67698705 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-text:"%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l1
{mso-list-id:946931636;
mso-list-type:hybrid;
mso-list-template-ids:-1867731076 67698705 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
{mso-level-text:"%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l1:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l1:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l2
{mso-list-id:1391348584;
mso-list-template-ids:502410070;}
@list l2: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 l2: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 l2: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 l2: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 l2: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 l2: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 l2: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 l2: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 l2: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="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">Dear CMC members,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">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></p>
<p class="MsoNormal"><o:p> </o:p></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"><o:p> </o:p></p>
<p class="MsoNormal">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></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">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></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">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></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">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 style="font-size:12.0pt">"</span><span class="s7"><span 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 style="font-size:12.0pt;font-family:"Arial",sans-serif;color:navy"> </span></span><span class="s5"><b><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:navy">'Liaison
Agreement for Work Item'</span></b></span><span class="s7"><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:navy">, or a "LAWI"</span></span><span style="font-size:12.0pt">"
</span>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></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">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></p>
<p class="MsoNormal">Proposed rewording of the resolution …<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><u>From:<o:p></o:p></u></p>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span class="ms-metadata">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><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><u>To:<o:p></o:p></u></p>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span class="ms-metadata">CCSDS – ISO TC20/SC13 and ISO TC20/SC14 have an existing framework for standards development, the
</span>"<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">:<o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:1.0in;text-indent:-.25in;mso-list:l0 level1 lfo2">
<![if !supportLists]><span class="ms-metadata"><span style="mso-list:Ignore">1)<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span class="ms-metadata">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></p>
<p class="MsoListParagraph" style="margin-left:1.0in;text-indent:-.25in;mso-list:l0 level1 lfo2">
<![if !supportLists]><span class="ms-metadata"><span style="mso-list:Ignore">2)<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span class="ms-metadata">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></p>
<p class="MsoNormal" style="margin-left:.5in"><span class="ms-metadata"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span class="ms-metadata">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>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.<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><span class="ms-metadata">For the second item the CCSDS – TC20/SC13 and TC20/SC14 agree to the Plan of Work that is to
</span>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 (https://sanaregistry.org/r/terms) 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></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">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></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks, Peter Shames<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>