<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=us-ascii"><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:"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;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.MsoList, li.MsoList, div.MsoList
{mso-style-priority:99;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:14.15pt;
text-indent:-14.15pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#993366;}
.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><!--[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" style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal><span style='color:#993366'>Just a quick recap of what (I think) we discussed today. You might refer to the PPT that was sent with the email below last Thursday.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#993366'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#993366'>David’s point: Nothing significant has changed. The basic scenario was the deployment approach we’ve been talking about all along. <o:p></o:p></span></p><p class=MsoNormal><span style='color:#993366'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#993366'>Mike’s understanding: There was general agreement that our normative standards would stick with only the Basic Scenario as far as deployment. Our informative documents might discuss that Scenarios 1, 2, 3, or 4 might be implemented, but they would not be able to cite compliance or conformance with OAIS-IF. <o:p></o:p></span></p><p class=MsoNormal><span style='color:#993366'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#993366'>Steve had concerns about ground-ruling out Scenario 4 (chart 3), because PDS has some approaches where the archive provides tools and APIs to users that could be interpreted as supporting Scenario 4. That generated a discussion about “ownership” or “provision” being on the archive side vs. the user side, which is a slightly different topic than the location or deployment of the software being on the archive side vs. the user side. Additionally the introduction of things being provided by a 3<sup>rd</sup>-party source further complicated the concept. This may warrant further discussion. However, Steve’s concerns were somewhat abated when we discussed chart 7. Bottom line is, I think, that the understanding above still holds… Normative documents won’t address scenarios 1, 2, 3, or 4, and implementation of those scenarios are not considered compliant with OAIS-IF. <o:p></o:p></span></p><p class=MsoNormal><span style='color:#993366'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#993366'>Mike went on to explain how the scenarios on charts 4 and 5 illustrated “broken interoperability.” No one disagreed with this, though David’s concern with the four deployment scenarios was more related to implementation concerns. <o:p></o:p></span></p><p class=MsoNormal><span style='color:#993366'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#993366'>Due to time constraints, we didn’t have time for a good discussion of charts 6 and 7, though they were well received. Mike related a discussion with Vint Cerf about his TCP/IP history, and advocated that the last option on the right side of chart 7 (only interace 2 exposed) was a “TCP/IP-like approach” where the protocol across the comm interface was the main focus, and perhaps should be our first (and most important) effort. <o:p></o:p></span></p><p class=MsoNormal><span style='color:#993366'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#993366'>David also advocated that a graphic that showed *<b>many</b>* users would easily illustrate that the Basic Scenario (perhaps called the “baseline scenario?”) was the only really viable scenario. <o:p></o:p></span></p><p class=MsoNormal><span style='color:#993366'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#993366'>Probably, more discussion of the “native” adapter scenarios on chart 7 warrant more discussion at some future telecon. Also, I think that David’s topic of JAR files as generic adapters warrants more discussion. <o:p></o:p></span></p><p class=MsoNormal><span style='color:#993366'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#993366'>Those are the summary minutes as I perceived from today’s telecon. Corrections and additions are welcome from anyone. <o:p></o:p></span></p><p class=MsoNormal><span style='color:#993366'><o:p> </o:p></span></p><div><p class=MsoNormal><span style='color:#002060'> -=- Mike<o:p></o:p></span></p><p class=MsoNormal><span style='color:#002060'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#993366'>Mike Kearney</span><span style='color:#002060'><o:p></o:p></span></p><p class=MsoNormal><span style='color:#002060'>Huntsville, Alabama, USA <o:p></o:p></span></p></div><p class=MsoNormal><span style='color:#993366'><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>From:</b> kearneysolutions@gmail.com <kearneysolutions@gmail.com> <br><b>Sent:</b> Thursday, October 14, 2021 1:25 PM<br><b>To:</b> 'MOIMS-Data Archive Interoperability' <moims-dai@mailman.ccsds.org><br><b>Subject:</b> Deployment options topic for the next telecon<o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='color:#1F497D'>In the agenda (below) for the 19<sup>th</sup>, we have a discussion about deployment options. I’ve prepared a PPT to walk us through the discussion during the telecon, attached. The first chart is really just historical architecture mapping, and the deployment options discussion starts on chart 2. <o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>I’m afraid I’ve got only an hour in the telecon on Tuesday, so hopefully we can start this discussion without too much delay. <o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Thanks,<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><div><p class=MsoNormal><span style='color:#002060'> -=- Mike<o:p></o:p></span></p><p class=MsoNormal><span style='color:#002060'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Mike Kearney</span><span style='color:#002060'><o:p></o:p></span></p><p class=MsoNormal><span style='color:#002060'>Huntsville, Alabama, USA <o:p></o:p></span></p></div><p class=MsoNormal><span style='color:#1F497D'><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>From:</b> MOIMS-DAI <<a href="mailto:moims-dai-bounces@mailman.ccsds.org">moims-dai-bounces@mailman.ccsds.org</a>> <b>On Behalf Of </b><a href="mailto:david@giaretta.org">david@giaretta.org</a><br><b>Sent:</b> Thursday, October 7, 2021 6:28 AM<br><b>To:</b> <a href="mailto:techsupport@mailman.ccsds.org">techsupport@mailman.ccsds.org</a><br><b>Cc:</b> 'Stafford, Laura' <<a href="mailto:LStafford@asrcfederal.com">LStafford@asrcfederal.com</a>>; MOIMS-DAI List <<a href="mailto:moims-dai@mailman.ccsds.org">moims-dai@mailman.ccsds.org</a>><br><b>Subject:</b> Re: [Moims-dai] [Cesg-all] CCSDS Fall 2021 Technical Meetings Agenda Request - Requires Your Input<o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoList>The draft agenda for MOIMS-DAI Fall 2021 meeting is available at <a href="https://cwe.ccsds.org/moims/docs/MOIMS-DAI/Meeting%20Materials%20and%20Minutes/2021-10%20Virtual/CCSDS%20MOIMS-DAI%20Fall%202021%20Agenda.docx?d=w425d83c18771488c9007b6a2348dc7cf">https://cwe.ccsds.org/moims/docs/MOIMS-DAI/Meeting%20Materials%20and%20Minutes/2021-10%20Virtual/CCSDS%20MOIMS-DAI%20Fall%202021%20Agenda.docx?d=w425d83c18771488c9007b6a2348dc7cf</a> <span lang=EN-GB><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB>Regards<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB>..David<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><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>From:</b> CESG-All <<a href="mailto:cesg-all-bounces@mailman.ccsds.org">cesg-all-bounces@mailman.ccsds.org</a>> <b>On Behalf Of </b>Stafford, Laura via CESG-All<br><b>Sent:</b> 30 September 2021 18:30<br><b>To:</b> <a href="mailto:cesg-all@mailman.ccsds.org">cesg-all@mailman.ccsds.org</a><br><b>Subject:</b> [Cesg-all] CCSDS Fall 2021 Technical Meetings Agenda Request - Requires Your Input<o:p></o:p></p></div></div><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;color:black'>Dear Chairs and Area Directors,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;color:black'>The Agendas webpage for the CCSDS Fall 202</span><span style='font-size:12.0pt'>1<span style='color:black'> Technical Meetings requires your input. <o:p></o:p></span></span></p><p class=MsoNormal><a href="https://public.ccsds.org/meetings/2021Fall/2021FallAgendas.aspx">https://public.ccsds.org/meetings/2021Fall/2021FallAgendas.aspx</a> <o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt;color:black'>As an Area Director, WG, SIG, or BOF Chairman it is your responsibility to keep an updated agenda for your meeting(s) loaded at the CCSDS website.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;color:black'>Send your agendas (or e-mail us your agenda URL in the CWE) to CCSDS Tech Support at (mailto:</span><u><span style='font-size:12.0pt;color:blue'><a href="mailto:techsupport@mailman.ccsds.org">techsupport@mailman.ccsds.org</a></span></u><span style='font-size:12.0pt;color:black'>).<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;color:black'>Thanks,<o:p></o:p></span></p><p class=MsoNormal><b><span style='color:#424242'>Laura Stafford</span></b><span style='font-size:9.0pt;color:#DC4912'><br></span><i><span style='font-size:9.0pt;color:#424242'>CCSDS IT Tech Support</span></i><span style='font-size:9.0pt;color:black'><o:p></o:p></span></p><p class=MsoNormal style='line-height:12.0pt'><u><span style='font-size:9.0pt;color:#0563C1'><a href="mailto:lstafford@asrcfederal.com%20%0d">lstafford@asrcfederal.com </a></span><span style='color:#0563C1'><o:p></o:p></span></u></p><p class=MsoNormal style='line-height:12.0pt'><span style='font-size:9.0pt;color:#BE811B'>c:</span><span style='font-size:9.0pt;color:#424242'> (937) 499-3591</span><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal style='line-height:12.0pt'><span style='font-size:9.0pt;color:#424242'>7000 Muirkirk Meadows Drive, Beltsville, MD 20705</span><span style='font-size:9.0pt;color:black'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:9.0pt;color:black'><a href="https://www.asrcfederal.com/" target="_blank"><span style='color:#044A91'>asrcfederal.com</span></a></span><b><span style='font-size:9.0pt;color:#3C6477'> </span></b><span style='font-size:9.0pt;color:#BE811B'>|</span><b><span style='font-size:9.0pt;color:#3C6477'> </span></b><span style='font-size:9.0pt;color:#3C6477'>Purpose Driven. Enduring Commitment.</span><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><div class=MsoNormal align=center style='text-align:center'><hr size=2 width="100%" align=center></div><p class=MsoNormal><span style='font-size:7.5pt;font-family:"Arial",sans-serif;color:gray'><br>The preceding message (including attachments) is covered by the Electronic Communication Privacy Act, 18 U.S.C. sections 2510-2512, is intended only for the person or entity to which it is addressed, and may contain information that is confidential, protected by attorney-client or other privilege, or otherwise protected from disclosure by law. If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited. Please reply to the sender that you have received the message in error and destroy the original message and all copies.</span><o:p></o:p></p></div></body></html>