[Moims-dai] Deployment options discussion from the last telecon

Tue Oct 19 17:29:27 UTC 2021

Mike

A couple of clarifications.

"The basic scenario was the deployment approach."

Should be           "The basic scenario was the design approach.".

The BB will define the interfaces and protocols and the GB will describe a
number of deployment options.

                             "a graphic that showed *many* users would
easily illustrate."

Should be           "a graphic that showed even 2 users and 2 archives and
would easily illustrate."

..David

From: MOIMS-DAI <moims-dai-bounces at mailman.ccsds.org> On Behalf Of
kearneysolutions at gmail.com
Sent: 19 October 2021 18:05
To: 'MOIMS-Data Archive Interoperability' <moims-dai at mailman.ccsds.org>
Subject: [Moims-dai] Deployment options discussion from the last telecon

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.

David's point:  Nothing significant has changed.  The basic scenario was the
deployment approach we've been talking about all along.  

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.  

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 3rd-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.  

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.  

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.  

David also advocated that a graphic that showed *many* users would easily
illustrate that the Basic Scenario (perhaps called the "baseline scenario?")
was the only really viable scenario.   

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.  

Those are the summary minutes as I perceived from today's telecon.
Corrections and additions are welcome from anyone.  

   -=- Mike

Mike Kearney

Huntsville, Alabama, USA 

From: kearneysolutions at gmail.com <mailto:kearneysolutions at gmail.com>
<kearneysolutions at gmail.com <mailto:kearneysolutions at gmail.com> > 
Sent: Thursday, October 14, 2021 1:25 PM
To: 'MOIMS-Data Archive Interoperability' <moims-dai at mailman.ccsds.org
<mailto:moims-dai at mailman.ccsds.org> >
Subject: Deployment options topic for the next telecon

In the agenda (below) for the 19th, 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.  

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.  

Thanks,

   -=- Mike

Mike Kearney

Huntsville, Alabama, USA 

From: MOIMS-DAI <moims-dai-bounces at mailman.ccsds.org
<mailto:moims-dai-bounces at mailman.ccsds.org> > On Behalf Of
david at giaretta.org <mailto:david at giaretta.org> 
Sent: Thursday, October 7, 2021 6:28 AM
To: techsupport at mailman.ccsds.org <mailto:techsupport at mailman.ccsds.org> 
Cc: 'Stafford, Laura' <LStafford at asrcfederal.com
<mailto:LStafford at asrcfederal.com> >; MOIMS-DAI List
<moims-dai at mailman.ccsds.org <mailto:moims-dai at mailman.ccsds.org> >
Subject: Re: [Moims-dai] [Cesg-all] CCSDS Fall 2021 Technical Meetings
Agenda Request - Requires Your Input

The draft agenda for MOIMS-DAI Fall 2021 meeting is available at
https://cwe.ccsds.org/moims/docs/MOIMS-DAI/Meeting%20Materials%20and%20Minut
es/2021-10%20Virtual/CCSDS%20MOIMS-DAI%20Fall%202021%20Agenda.docx?d=w425d83
c18771488c9007b6a2348dc7cf 

Regards

..David

From: CESG-All <cesg-all-bounces at mailman.ccsds.org
<mailto:cesg-all-bounces at mailman.ccsds.org> > On Behalf Of Stafford, Laura
via CESG-All
Sent: 30 September 2021 18:30
To: cesg-all at mailman.ccsds.org <mailto:cesg-all at mailman.ccsds.org> 
Subject: [Cesg-all] CCSDS Fall 2021 Technical Meetings Agenda Request -
Requires Your Input

Dear Chairs and Area Directors,

The Agendas webpage for the CCSDS Fall 2021 Technical Meetings requires your
input. 

https://public.ccsds.org/meetings/2021Fall/2021FallAgendas.aspx 

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.

Send your agendas (or e-mail us your agenda URL in the CWE) to CCSDS Tech
Support at (mailto:techsupport at mailman.ccsds.org
<mailto:techsupport at mailman.ccsds.org> ).

Thanks,

Laura Stafford
CCSDS IT Tech Support

lstafford at asrcfederal.com  <mailto:lstafford at asrcfederal.com%20%0d> 

c: (937) 499-3591

7000 Muirkirk Meadows Drive, Beltsville, MD 20705

 <https://www.asrcfederal.com/> asrcfederal.com | Purpose Driven. Enduring
Commitment.

  _____  

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.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ccsds.org/pipermail/moims-dai/attachments/20211019/194a45c0/attachment-0001.htm>