<html 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:Aptos;
        panose-1:2 11 0 4 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        font-size:10.0pt;
        font-family:"Aptos",sans-serif;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
        {mso-style-priority:34;
        mso-margin-top-alt:auto;
        margin-right:0in;
        mso-margin-bottom-alt:auto;
        margin-left:0in;
        font-size:12.0pt;
        font-family:"Aptos",sans-serif;}
span.EmailStyle21
        {mso-style-type:personal-reply;
        font-family:"Aptos",sans-serif;
        color:windowtext;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;
        mso-ligatures:none;}
@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:78793938;
        mso-list-template-ids:-1021391664;}
@list l1
        {mso-list-id:215090979;
        mso-list-template-ids:-506579476;}
@list l2
        {mso-list-id:288245091;
        mso-list-template-ids:1503408106;}
@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:;
        mso-level-tab-stop:1.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@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:Symbol;}
@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:Symbol;}
@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:Symbol;}
@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:Symbol;}
@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:Symbol;}
@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:Symbol;}
@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:Symbol;}
@list l3
        {mso-list-id:1161695364;
        mso-list-template-ids:-2056610040;}
@list l3: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 l3:level2
        {mso-level-number-format:bullet;
        mso-level-text:;
        mso-level-tab-stop:1.0in;
        mso-level-number-position:left;
        text-indent:-.25in;
        mso-ansi-font-size:10.0pt;
        font-family:Symbol;}
@list l3: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:Symbol;}
@list l3: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:Symbol;}
@list l3: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:Symbol;}
@list l3: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:Symbol;}
@list l3: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:Symbol;}
@list l3: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:Symbol;}
@list l3: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:Symbol;}
ol
        {margin-bottom:0in;}
ul
        {margin-bottom:0in;}
--></style>
</head>
<body lang="EN-US" link="#467886" vlink="#96607D" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt">Hi David,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">I think I just sent you the link.  LMK if you did not see it.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Thanks, Peter<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<div id="mail-editor-reference-message-container">
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><span lang="EN-GB" style="font-size:12.0pt;color:black">From:
</span></b><span lang="EN-GB" style="font-size:12.0pt;color:black">david@giaretta.org <david@giaretta.org><br>
<b>Date: </b>Monday, August 12, 2024 at 7:00</span><span lang="EN-GB" style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black"> </span><span lang="EN-GB" style="font-size:12.0pt;color:black">AM<br>
<b>To: </b>Shames, Peter M (US 312B) <peter.m.shames@jpl.nasa.gov>, 'SEA-SA' <sea-sa@mailman.ccsds.org>, 'Josiah Johnson' <josiah.m.johnson@nasa.gov>, 'Ramon Krosley' <r.krosley@andropogon.org>, Cheng, Shelbun K (US 312H) <shelbun.k.cheng@jpl.nasa.gov>, 'Fred
 Slane' <freds@spacestandards.org><br>
<b>Cc: </b>Crichton, Daniel J (US 1900) <daniel.j.crichton@jpl.nasa.gov>, Hughes, J S (US 398B) <john.s.hughes@jpl.nasa.gov>, 'Daniel Fischer' <Daniel.Fischer@esa.int><br>
<b>Subject: </b>[EXTERNAL] RE: Meetings notes for SEA - SA, RASDS Subset meeting, 10 June 24<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt">Is there a link available for the upcoming meeting?<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt">..David<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt"> <o:p></o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Shames, Peter M (US 312B) <peter.m.shames@jpl.nasa.gov>
<br>
<b>Sent:</b> Wednesday, June 12, 2024 6:01 PM<br>
<b>To:</b> SEA-SA (sea-sa@mailman.ccsds.org) <sea-sa@mailman.ccsds.org>; Josiah Johnson <josiah.m.johnson@nasa.gov>; Ramon Krosley (r.krosley@andropogon.org) <r.krosley@andropogon.org>; Cheng, Shelbun K (US 312H) <shelbun.k.cheng@jpl.nasa.gov>; Fred Slane (freds@spacestandards.org)
 <freds@spacestandards.org><br>
<b>Cc:</b> Crichton, Daniel J (US 1900) <daniel.j.crichton@jpl.nasa.gov>; Hughes, J S (US 398B) <john.s.hughes@jpl.nasa.gov>; David Giaretta (david@giaretta.org) <david@giaretta.org>; Daniel Fischer <Daniel.Fischer@esa.int><br>
<b>Subject:</b> Meetings notes for SEA - SA, RASDS Subset meeting, 10 June 24</span><span lang="EN-GB" style="font-size:11.0pt"><o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#212121">Dear SEA SAWG team,</span><span lang="EN-GB" style="font-size:11.0pt"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#212121"> </span><span lang="EN-GB" style="font-size:11.0pt"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#212121">Attendees: Josiah Johnson, Ramon Krosley, Shelbun Cheng, Fred Slane, Peter Shames</span><span lang="EN-GB" style="font-size:11.0pt"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#212121"> </span><span lang="EN-GB" style="font-size:11.0pt"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#212121">Great meeting Monday, 10 June 24, so glad to have your participation.  The focus was largely on the proposed new work item, the refresh of the Reference Architecture
 for Space Information Management (RASIM), CCSDS 312.0-G-1.  </span><span lang="EN-GB" style="font-size:11.0pt"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#212121"> </span><span lang="EN-GB" style="font-size:11.0pt"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#212121">Further work on RASDSv2 will be delayed until after the results of the Agency review have been returned.</span><span lang="EN-GB" style="font-size:11.0pt"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#212121"> </span><span lang="EN-GB" style="font-size:11.0pt"><o:p></o:p></span></p>
<p class="MsoNormal"><u><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#212121">General notes from the telecon:</span></u><span lang="EN-GB" style="font-size:11.0pt"><o:p></o:p></span></p>
<ol start="1" type="1">
<li class="MsoListParagraph" style="color:#212121;mso-list:l1 level1 lfo1"><span style="font-family:"Calibri",sans-serif">Peter has shifted to working 1/2 time, but will continue to lead the SE Area and the SAWG.  A certain amount of effort will go into mentoring
 replacements.</span><span lang="EN-GB"><o:p></o:p></span></li><li class="MsoListParagraph" style="color:#212121;mso-list:l1 level1 lfo1"><span style="font-family:"Calibri",sans-serif">RASDSv2 has passed CESG review for release to Agency Review and is in the CCSDS CTE queue being prepped for that.  We discussed the review
 and approval flow for RASDS so that the team knows what to expect.</span><span lang="EN-GB"><o:p></o:p></span></li><li class="MsoListParagraph" style="color:#212121;mso-list:l1 level1 lfo1"><span style="font-family:"Calibri",sans-serif">We discussed the overall CCSDS document creation and review process flow for those who are new to this work.</span><span lang="EN-GB"><o:p></o:p></span></li><li class="MsoListParagraph" style="color:#212121;mso-list:l1 level1 lfo1"><span style="font-family:"Calibri",sans-serif">We discussed the specifics of the review and approval flow for the RASDSv2 document, which is to be published eventually as a joint CCSDS
 and ISO TC20/SC14 document, would occur.  We also touched on the few other CCSDS documents that have such shared “ownership”, such as the MOIMS Nav WG CDM (SC14) and SM&C WG XTCE (OMG), and the SIS DTN BPv7 (IETF).</span><span lang="EN-GB"><o:p></o:p></span></li><li class="MsoListParagraph" style="color:#212121;mso-list:l1 level1 lfo1"><span style="font-family:"Calibri",sans-serif">We spent much of the remainder of the time discussing the proposed set of RASIM mods</span><span lang="EN-GB"><o:p></o:p></span></li></ol>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#212121"> </span><span lang="EN-GB" style="font-size:11.0pt"><o:p></o:p></span></p>
<p class="MsoNormal"><u><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#212121">Mods proposed for the Reference Architecture for Space Information Management (RASIM), CCSDS 312.0-G-1</span></u><span lang="EN-GB" style="font-size:11.0pt"><o:p></o:p></span></p>
<ol start="1" type="1">
<li class="MsoListParagraph" style="color:#212121;mso-list:l0 level1 lfo2"><span style="font-family:"Calibri",sans-serif">Josiah Johnson had agreed to be the lead editor for this document and he has approval of his organization to do this work.</span><span lang="EN-GB"><o:p></o:p></span></li><li class="MsoListParagraph" style="color:#212121;mso-list:l0 level1 lfo2"><span style="font-family:"Calibri",sans-serif">Josiah mentioned the shift over time from client / server architectures to web based, and from that to web services using HTTP(S) and to
 other deployment modes.</span><span lang="EN-GB"><o:p></o:p></span></li><li class="MsoListParagraph" style="color:#212121;mso-list:l0 level1 lfo2"><span style="font-family:"Calibri",sans-serif">We discussed the continuing evolution to virtualized / containerized / cloud deployments. In the context of fig 4-5 and 4-6 (attached,
 with annotations).</span><span lang="EN-GB"><o:p></o:p></span></li><li class="MsoListParagraph" style="color:#212121;mso-list:l0 level1 lfo2"><span style="font-family:"Calibri",sans-serif">We agreed that these kinds of web service aspects can best be modelled as aspects of
<b><i>where</i></b> instantiations of user or service applications are deployed (thin or thick clients, or web browser clients), and of which technologies are adopted for the messaging middleware.</span><span lang="EN-GB"><o:p></o:p></span></li><li class="MsoListParagraph" style="color:#212121;mso-list:l0 level1 lfo2"><span style="font-family:"Calibri",sans-serif">The same kind of analysis led to a belief that virtual and cloud deployments can similarly be treated as aspects of
<b><i>how</i></b> instantiations of user or service applications are deployed, on local servers or in some virtual or containerized environment.</span><span lang="EN-GB"><o:p></o:p></span></li><li class="MsoListParagraph" style="color:#212121;mso-list:l0 level1 lfo2"><span style="font-family:"Calibri",sans-serif">We agreed that the topics of hypervisor or orchestration can best be addressed by considering those as “on the side” functions, separate
 from the stack itself, that monitor and manage the environment and the deployments.  This is shown as a “cross cutting” orange “management” box to the left side of the existing stack.</span><span lang="EN-GB"><o:p></o:p></span></li><li class="MsoListParagraph" style="color:#212121;mso-list:l0 level1 lfo2"><span style="font-family:"Calibri",sans-serif">Similarly, various security considerations may be modelled as a different kind of cross cutting functions, shown as a red “security” box
 on the right side of the existing stack.</span><span lang="EN-GB"><o:p></o:p></span></li><li class="MsoListParagraph" style="color:#212121;mso-list:l0 level1 lfo2"><span style="font-family:"Calibri",sans-serif">The possibility of hybrid architectures was also briefly discussed.  The assumption being that different parts of the extended system would
 evolve at different rates, or adopt architecture features, driven by local choices or available resources, especially with space deployments.  The possibility of deployments of something that might be described as a “private cloud” being deployed in a space
 habitat context was proposed, or of various distributed servers.  This all warrants much more discussion.</span><span lang="EN-GB"><o:p></o:p></span></li></ol>
<p class="MsoListParagraph" style="margin-left:.75in;text-indent:-.25in;mso-list:l2 level1 lfo3">
<![if !supportLists]><span lang="EN-GB" style="font-size:10.0pt;font-family:Symbol;color:#212121"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">        
</span></span></span><![endif]><span style="font-family:"Calibri",sans-serif;color:#212121">We agreed to consider inclusion of a new “Deployment Section” that would show various abstract versions of these different deployment approaches.  This is TBD.</span><span lang="EN-GB" style="color:#212121"><o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:.75in;text-indent:-.25in;mso-list:l2 level1 lfo3">
<![if !supportLists]><span lang="EN-GB" style="font-size:10.0pt;font-family:Symbol;color:#212121"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">        
</span></span></span><![endif]><span style="font-family:"Calibri",sans-serif;color:#212121">We agreed to consider inclusion of one or more deployment options that would be suitable for Lunar (and future Mars) environments.  This is TBD.</span><span lang="EN-GB" style="color:#212121"><o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:.75in;text-indent:-.25in;mso-list:l2 level1 lfo3">
<![if !supportLists]><span lang="EN-GB" style="font-size:10.0pt;font-family:Symbol;color:#212121"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">        
</span></span></span><![endif]><span style="font-family:"Calibri",sans-serif;color:#212121">We agreed to use a PPT file, with a combination of text (intended to address new topics in the document) and drawings (intended to become figures in the revised document).
   We used this approach with RASDSv2 and it was very effective.</span><span lang="EN-GB" style="color:#212121"><o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin-left:.75in;text-indent:-.25in;mso-list:l2 level1 lfo3">
<![if !supportLists]><span lang="EN-GB" style="font-size:10.0pt;font-family:Symbol;color:#212121"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">        
</span></span></span><![endif]><span style="font-family:"Calibri",sans-serif;color:#212121">We agreed to consider how trade studies and cost considerations might be addressed in the updated document.</span><span lang="EN-GB" style="color:#212121"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#212121">Action Items:</span><span lang="EN-GB" style="font-size:11.0pt"><o:p></o:p></span></p>
<ul type="disc">
<li class="MsoListParagraph" style="color:#212121;mso-list:l3 level1 lfo4"><span style="font-family:"Calibri",sans-serif">Team: review these notes and propose any changes, updates, or edits</span><span lang="EN-GB"><o:p></o:p></span></li><li class="MsoListParagraph" style="color:#212121;mso-list:l3 level1 lfo4"><span style="font-family:"Calibri",sans-serif">Josiah: create a PPT file and use it to propose how to include these edits, or not, into the next revision of RASIM</span><span lang="EN-GB"><o:p></o:p></span></li><li class="MsoListParagraph" style="color:#212121;mso-list:l3 level1 lfo4"><span style="font-family:"Calibri",sans-serif">Fred: propose to SC14 the adoption of RASIM as a companion document and see if one or more of the SC14 leads might join the group and actively
 contribute</span><span lang="EN-GB"><o:p></o:p></span></li><li class="MsoListParagraph" style="color:#212121;mso-list:l3 level1 lfo4"><span style="font-family:"Calibri",sans-serif">Peter: reach out to Dan Crichton and to members of the existing MOIMS DAI WG to see if they are interested in either active participation
 or direct involvement</span><span lang="EN-GB"><o:p></o:p></span></li></ul>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#212121">See you all next month.</span><span lang="EN-GB" style="font-size:11.0pt"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#212121"> </span><span lang="EN-GB" style="font-size:11.0pt"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#212121">Best regards, Peter</span><span lang="EN-GB" style="font-size:11.0pt"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#212121"> </span><span lang="EN-GB" style="font-size:11.0pt"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><span lang="EN-GB" style="font-size:11.0pt"><o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</body>
</html>