<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:x="urn:schemas-microsoft-com:office:excel" 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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.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>
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:black">Dear SEA-SAWG,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">Please see attached. I have not yet parsed the inputs for Barkley, but we will need to do so. And we do not yet have inputs from Wilmot.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">Mario, for some unknown reason, decided not to vote. Maybe he plans to do it on the next go-round.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">Cheers, Peter<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></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 style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-left:.5in"><b><span style="font-size:12.0pt;color:black">From:
</span></b><span style="font-size:12.0pt;color:black">Tom Gannett <thomas.gannett@tgannett.net><br>
<b>Date: </b>Tuesday, April 21, 2020 at 7:52 AM<br>
<b>To: </b>Peter Shames <peter.m.shames@jpl.nasa.gov><br>
<b>Cc: </b>Erik Barkley <erik.j.barkley@jpl.nasa.gov>, Gian Paolo Calzolari <Gian.Paolo.Calzolari@esa.int>, "Wilmot, Jonathan J. (GSFC-5820)" <jonathan.j.wilmot@nasa.gov><br>
<b>Subject: </b>[EXTERNAL] Re: CESG-P-2020-03-001 Approval to publish CCSDS 371.0-G-1, Application and Support Layer Architecture (Green Book, Issue 1)<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Peter:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">The CESG poll to approve publication of CCSDS
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">371.0-G-1, Application and Support Layer
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Architecture (Green Book, Issue 1) concluded with
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">conditions. Please negotiate disposition of the
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">conditions directly with the AD(s) who voted to
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">approve with conditions and CC the Secretariat on all related correspondence.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">CESG E-Poll Identifier: CESG-P-2020-03-001
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Approval to publish CCSDS 371.0-G-1, Application
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">and Support Layer Architecture (Green Book, Issue 1)<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Results of CESG poll beginning 31 March 2020 and ending 17 April 2020:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"> Abstain: 0 (0%)<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Approve Unconditionally: 2 (40%) (Shames, Burleigh)<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Approve with Conditions: 3 (60%) (Barkley, Calzolari, Wilmot)<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Disapprove with Comment: 0 (0%)<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">CONDITIONS/COMMENTS:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"> Erik Barkley (Approve with Conditions): I
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">am this close ("") to voting disapprove. However
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">I think CCSDS needs an a good architetural
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">overview of the upper layers. Unfortunately I
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">find that there is still work to be
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">done. Several observations are listed below.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">1) Page 1-3, section 1.4: suggest revising FROM
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">"ASL Reference Architecture: describes the
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">approach of describing the reference architecture
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">in terms of seven modelling viewpoints and
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">introduces the graphical notation used." TO "ASL
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Reference Architecture: defines the seven
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">modeling viewpoints and the graphical notations
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">used in this document" or something like that.
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">RATIONALE: as currently written we essentially
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">have the the reference architecture as describing
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">the describing for the reference architecture; circular to say the least.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">2) Page 2-1 Section 2 and onward -- a general
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">finding throughout the remainder of the document:
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">the question of architecture versus org chart
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">figures prominently here as this seems to want to
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">describe the architecture in terms of two CCSDS
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">areas: SOIS and MOIMS. An immediate practical
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">concern emerges in terms of considering document
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">maintenance down the road. What happens if CCSDS
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">is reorganized (and that has happened in the
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">past) and the notion of areas and/or their names
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">change? It may not be such a simple editing job
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">of changing the names as some bits and pieces of
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">functionality may move to an entirely different
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">new organization in terms of working groups etc.
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">It's a bit distressing that a more genuine
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">approach to actually identifying the functions
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">independent of the areas has not been pursued.
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Suggest revision to the document to anchor this
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">firmly in functional terms rather than CCSDS area
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">organizations. As a point of comparison, note
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">that the Space Communications Cross
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Support--Architecture Description Document (CCSDS
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">901.0-G-1) makes no mention any CCSDS
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Area. Furthermore it has only one note with the
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">term "Working Group" to indicate that WGs will produce future standards.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">3) Page 2-1, Section 2.2.1 as follow-up from the
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">immediately preceding observation the document
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">talks about describing "...MOIMS interaction with
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">the onboard environment..." -- Of course MOIMS
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">has no interaction with anything in terms of an
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">onboard spacecraft environment as it is an area
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">in CCSDS with multiple working groups. I suspect
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">the more functional aspect that is being
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">attempted here is MO (mission operations).<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">4) Page 2-4, 2nd paragraph as yet further
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">follow-up to the immediately two preceding
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">observations I think that the phrase "based on
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">CCSDS SLS SIS CSS and SEA standards" can be
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">deleted. The protocol stack is already indicated
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">as being defined in SCCS-ADD -- the areas
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">producing the various standards involved are not
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">really germane to description of the architecture.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">5) Page 2-6, 1st paragraph: FROM "..Some
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">platforms use Application Programming Interface
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">(API) calls for communication with services. Some
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">platforms use a software message bus for the same
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">purpose. Some platforms are Time and Space
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Partitioned (TSP), with messages passed between
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">partitions" TO -- something more technically
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">correct. RATIONALE: these two sentences are
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">confusing and not technically correct. Any kind
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">of software messaging bus comes with an API for
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">sending the messages and/or receiving them from
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">the message bus. How this differs from an "API
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">for communication with services" is not at all made clear.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">6) Page 2-9 A further follow up related to item
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">2) above about focus on areas rather than
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">functions. In particular suggest revision to
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">"But it is necessary to describe how the MOIMS
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">services interface with the spacecraft
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">environment..." -- again MOIMS as an area; if
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">you read expanding the acronym you get Mission
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Operation and Information Services services
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">interface with the spacecraft environment..." I
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">suspect the real object is more just MO and not the entire area within CCSDS.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">7) Page 3-1, 5th para: FROM "MOIMS aspects" to
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">"Mission Operations aspects" and FROM "SOIS
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">aspects" to on board the spacecraft aspects" --
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">again confusion of areas vs functionalities<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">8) Page 3-2, 2nd para: delete this <o:p>
</o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">paragraph. Rationale: This has all been well
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">established prior in the document.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">9) Page 3-3, last para: FROM "Two formulations
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">of the Functional Viewpoint diagrams are
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">provided. The standard diagram is <o:p>
</o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">function-oriented and shows functions connected
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">by logical interfaces. These are contained in the
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">body of the document. A set of alternative
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">diagrams are contained in annex B and are
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">service-oriented." TO something that is less
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">confusion prone. RATIONALE: if the alternative
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">diagrams contained in annex B are service
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">oriented then why are they indicated as a
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">formulation of the functional viewpoint diagram
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">when in fact we have a service viewpoint as well?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">10) Page 3-4, last para: Please better clarify
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">offline in "Such interactions may be supported as
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">simple offline transfer of data, typically as a
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">file transfer, or more complex online
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">interactions between service consumer and
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">provider functions." RATIONALE: CFDP is a file
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">transfer which I believe many people consider to be something that is "online".<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">11) Page 3-5, second to last bullet: Please
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">clarify for "… service interaction using message
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">transfer;" -- does this include streaming applications?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">12) Page 3-7 section 3.2, last paragraph in
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">particular: this seems to argue that the
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">implementation viewpoint is not really part of
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">the architecture as it is essentially just examples. Please clarify.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">13) Page 3-9, figure 3-2 (Graphical Notation for
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Functional Viewpoint Diagrams), Page 3-13, Figure
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">3-5 (Graphical Graphical Notation for
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Communication Viewpoint Diagrams) , Page 3-15,
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Figure 3-7 (Graphical Notaion for Deployment
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Viewpoint Diagrams), Page 3-17, Figure 3-9
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">(Graphical Notation for Implementation Viewpoint
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Process View -- by the way should not.B viewpoint
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">diagrams and not viewpoint view?) all use the
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">same color (a light value of yellow) to denote
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">different things. The Color Keys legend in
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Figure 3-1 does not address this. In Figure 3-5,
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">the communications view, functions are shown in a
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">pinkish color. In Figure 3-7, functions are
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">shown with no distinct colors and are shown with
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">the same light yellow color as the nodes. Figure
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">3-6 (Graphical Notation for Physical Vuiewpoint
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Digrams), does by contrast, have a viewpoint
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">specific color coding key. Please provide and
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">use consistently, viewpoint specific color coding
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">keys. Given that many of the same shapes show up
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">in different viewpoint diagrams it be difficult
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">if not confusing to quickly glean what is being addressd.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">14) Page 4-3, Section 4.2.2.: FROM "MOIMS AREA
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">CONTEXT" TO "MO CONTEXT". RATIONALE: MOIMS is
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">part of the CCSDS organization and it's hard to
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">see how Working Groups and Area Director/Deputy
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Area Director in fact participate in the
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">operational concerns indicated in the diagram.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">15) Page 4-3 Context diagram -- this type of
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">diagram is not introduced in the reference
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">architecture section. Please provide at least a
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">note that this will be included in architectural
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">viewpoints. Perhaps the inetnation is that for
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">each viewpoint there is an OV-1 type diagram?
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">(<a href="https://en.wikipedia.org/wiki/Operational_View">https://en.wikipedia.org/wiki/Operational_View</a>) ?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">16) Page 4-45: this seems to be a general
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">discussion about two areas in CCSDS and security
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">rather than any real architectural considerations
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">with regard to security. Please revise to state
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">the functions needed for the ASL security architecture.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">17) Page 4-46: re observation 16, immediately
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">above, what is stated as terms seem to be in fact
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">the security functions needed. Please consider revising accordingly.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">18) Page 5-2: bottom third of page, page 5-3 top
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">~quarter of page: Suggest either consistently
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">ensuring all abbreviations are in the appropriate
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">annex or consistently expanding them; as
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">presented here it seems a bit haphazard as to why
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">some abbreviations are spelled out in full while
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">as others are not. There appears to be some
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">sort of assumption that many of the abbreviations
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">are widely understood while there are some new
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">ones introduced here when in fact for reader
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">coming across is the first time they're all essentially foreign.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">19) General: the document gives an overall
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">impression of providing viewpoints to describe an
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">architecture into standards being developed
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">within the MOIMS and SOIS areas. That in and of
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">itself is okay and of value. However the document
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">purports to be an architecture description
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">document. By the end of the document I had not
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">seen anything that shows how the MO and On-Board
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">functions were being arranged in architectural
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">sense. For example,where is a diagram that shows
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">the functional realtionship between device
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">enumeration, not to mention Electronic Data Sheet
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">and MO Monitor and Control? Presumably there
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">would also be some sort of information kind of
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">consideration in that the device enumeration/EDS
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">would have some bearing on the parameters being
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">configured for reporting monitor data. And
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">presumably the on-board Time Access Service would
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">have a bearing in this example as well.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">20) Page 10-3, Section 10.2.3 -- this introduces
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">an implementation view sub-view, "COMPONENT VIEW"
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">this is not defined, identified in the reference
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">arcthiectrue section. Consequently its not clear
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">what the concerns are of this view point. Please
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">address in the reference arcthiecture section.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">21 Page 10-4 Section 10.2.4 -- Process view
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">another view being introduced that is not defined
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">in the reference arcitecture. Same type of comment as 20 immediately above.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">22) Section 3 -- general -- highly recommend that
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">each of the viewpoint description sections begin
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">by indicating the types of concerns/types of
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">questions that the viewpoint is intended to
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">address. I believe that checking the resulting
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">descriptions/diagrams for each of the views will
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">help to validate that the correct views have been
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">developed. For example, the functional viewpoint
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">begins the description that "… The model is
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">broken down hierarchically into a set of
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">functions corresponding to recognizable areas of
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">functionality within space systems which are
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">often associated with particular type of
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">information". But what are we trying to achieve
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">with the functional view? Identification of the
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">functions that a mission needs for operating?
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Prioritization of the functions in terms of the
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">need for standardization? And to get to these
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">types of questions I think the stakeholders need
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">to be identified. And presumably at the end of
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">the day, the stakeholders would get into mission
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">classes -- perhaps a set something like a list
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">along the lines of Earth Observation, Navigation,
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Telecommunication / Relay. Astronomical /
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Astrophysical Observation, Space Platform
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Servicing. Solar System Body Observation /
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Orbiter / Flyby, Solar System Body <o:p>
</o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Lander/Penetrator / In-situ Exploration, Sample
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">return, Technology Demonstration. It seems to me
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">that one of the key stakeholders ultimately are
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">the missions that would implement the standards
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">and not having their concerns mapped out with
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">respect to the architecture seems to me to be a
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">disservice having invested the time to understand
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">the architecture such as it's laid out.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"> Gian Paolo Calzolari (Approve with
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Conditions): SPP (Ref.[3]) is mentioned 3 times
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">in the document. At least the first occurence
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">should also mention EPP 133.1-B. For the second
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">one, MOIMS should check/consider if SM&C allows using Encapsulation Packets.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"> Jonathan Wilmot (Approve with <o:p>
</o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Conditions): SOIS area is in process of
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">consolodating comments from NASA, CAST and ESA
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">reveiwers and will provide those to SEA/Systems
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Architecture Working Group by 4/24/2020<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Total Respondents: 5<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">No response was received from the following Area(s):<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"> MOIMS<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">SECRETARIAT INTERPRETATION OF RESULTS: Approved with Conditions<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">PROPOSED SECRETARIAT ACTION: Generate
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">CMC poll after conditions have been addressed<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">* * * * * * * * * * * * * * * * * * * * * * * *<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><o:p> </o:p></p>
</div>
</div>
</body>
</html>