<font size=2 face="sans-serif">Dear All,</font>
<br><font size=2 face="sans-serif"> please
let me know if - after Erik mail - it is clear </font>
<br><font size=2 face="sans-serif">1) the kind of feedback expected from
your WG, and</font>
<br><font size=2 face="sans-serif">2) which sections are really of interest
to your WG </font>
<br>
<br><font size=2 face="sans-serif">Thanks</font>
<br>
<br><font size=2 face="sans-serif">Gian Paolo. </font>
<br><font size=1 color=#800080 face="sans-serif">----- Forwarded by Gian
Paolo Calzolari/esoc/ESA on 02/09/2016 10:37 -----</font>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">"Barkley, Erik
J (3970)" <erik.j.barkley@jpl.nasa.gov></font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">"Gian.Paolo.Calzolari@esa.int"
<Gian.Paolo.Calzolari@esa.int></font>
<br><font size=1 color=#5f5f5f face="sans-serif">Cc:
</font><font size=1 face="sans-serif">"CESG -- CCSDS-Engineering
Steering Group (cesg@mailman.ccsds.org) (cesg@mailman.ccsds.org)"
<cesg@mailman.ccsds.org>, "SLS - Space Link Services Area"
<sls@mailman.ccsds.org></font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">02/09/2016 03:05</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">RE: [CESG] CSS
Area Technical Note: Functional Resource Model</font>
<br>
<hr noshade>
<br>
<br>
<br><font size=2 color=#004080 face="Calibri">Dear Gian Paolo,</font>
<br><font size=2 color=#004080 face="Calibri"> </font>
<br><font size=2 color=#004080 face="Calibri">Perhaps if I work from an
example it will help.</font>
<br><font size=2 color=#004080 face="Calibri"> </font>
<br><font size=2 color=#004080 face="Calibri">If you look at figure 2-2,
and following the “wiring” from the Forward Frame CSTS Provider box,
we see 3 possible outputs: a) all TC VC frames for one VC to the TC VC
Mux function, b) AOS VC frames for one VC to an AOS Mux function, and c)
all MC CADUs for one physical channel symbol stream to a Fwd AOS Sync and
Channel Encoding function. And if you study the diagram you can
see that there are other logical entry points for the Mux/Encoding functions
(e.g, if we enter the functionality from forward file or CFDP sender).
A key question is if this abstraction of functionality/process
is correct? We believe it to be so, but input/checking will be appreciated.
Very closely related is </font>
<br><font size=2 color=#004080 face="Calibri">If we then jump to the details
on the Forward AOS Synchronization and Channel Encoding type, its functions
are described as:</font>
<br><font size=2 color=#004080 face="Calibri"> </font>
<br><font size=2 color=#004080 face="Calibri">“…</font>
<div><font size=3 face="Times New Roman">a) the multiplexing
and idle data unit insertion that is nominally specified in the AOS Space
Data Link Recommended Standard to be performed on transfer frames. In the
IOAG service set, these functions are performed on already-coded and synch-markered
channel access data units (CADUs) instead, in order to provide the CADU
mode of the Forward Frames CSTS. The resultant waveform on the space link
carrier is the same as that produced by conformance to the AOS Space Data
Link Protocol and TM Synchronization and Channel Coding Recommended Standards.;
and</font>
<br><font size=3 face="Times New Roman">b) the (optional)
frame randomization, block (Reed Solomon, Turbo, or LDPC) encoding, frame
synchronization marker attachment, and (optional) convolutional encoding
functions specified in the TM Synchronization and Channel Coding Recommended
Standard.</font>
<br><font size=2 color=#004080 face="Calibri">…” </font>
<br><font size=2 color=#004080 face="Calibri"> </font>
<br><font size=2 color=#004080 face="Calibri">So this would be kind of
the first order check – that wiring and associated functional descriptions
are correct. </font>
<br><font size=2 color=#004080 face="Calibri"> </font>
<br><font size=2 color=#004080 face="Calibri">A 2<sup>nd</sup> order consideration
is then the various profiles listed later in the document which we believe
are what the “sensible” (leading to standardized) combinations of these
functional resources are. This then influences such things as what
and how CSTS identifies standardized monitor data, service control directives,
etc. </font>
<br><font size=2 color=#004080 face="Calibri"> </font>
<br><font size=2 color=#004080 face="Calibri">I realize this is a non-trivial
document, so I think just looking at the diagram and checking that the
pathways make sense will be a good first step.</font>
<br><font size=2 color=#004080 face="Calibri"> </font>
<br><font size=2 color=#004080 face="Calibri">Best regards,</font>
<br><font size=2 color=#004080 face="Calibri">-Erik </font>
<br><font size=2 color=#004080 face="Calibri"> </font>
<br><font size=2 face="Calibri"><b>From:</b> Gian.Paolo.Calzolari@esa.int
[</font><a href=mailto:Gian.Paolo.Calzolari@esa.int><font size=2 face="Calibri">mailto:Gian.Paolo.Calzolari@esa.int</font></a><font size=2 face="Calibri">]
<b><br>
Sent:</b> Thursday, August 25, 2016 6:06 AM<b><br>
To:</b> Barkley, Erik J (3970) <erik.j.barkley@jpl.nasa.gov><b><br>
Cc:</b> CESG -- CCSDS-Engineering Steering Group (cesg@mailman.ccsds.org)
(cesg@mailman.ccsds.org) <cesg@mailman.ccsds.org>; SLS - Space Link
Services Area <sls@mailman.ccsds.org><b><br>
Subject:</b> Re: [CESG] CSS Area Technical Note: Functional Resource Model</font>
<br><font size=3 face="Times New Roman"> </font>
<br><font size=2 face="Arial">Dear Erik,</font><font size=3 face="Times New Roman">
</font><font size=2 face="Arial"><br>
you say "</font><font size=2 color=#004080 face="Calibri">
I believe it will be of particular interest for the SLS Area as we believe
these are the experts that will really know if the wiring makes sense</font><font size=2 face="Arial">".</font><font size=3 face="Times New Roman">
</font><font size=2 face="Arial"><br>
However the document - even accepting changes - is about 190 pages, so
it would be nice to understand what kind of feedback you expect from SLS
Area as well as knowing which sections would really be of interest of any
given WG in SLS. I think specially the latter would prevent misunderstanding
and overlooking of interesting items.</font><font size=3 face="Times New Roman">
<br>
</font><font size=2 face="Arial"><br>
Thanks</font><font size=3 face="Times New Roman"> <br>
</font><font size=2 face="Arial"><br>
Gian Paolo</font><font size=3 face="Times New Roman"> <br>
<br>
<br>
</font><font size=1 color=#5f5f5f face="Arial"><br>
From: </font><font size=1 face="Arial">"Barkley,
Erik J (3970)" <</font><a href=mailto:erik.j.barkley@jpl.nasa.gov><font size=1 color=blue face="Arial"><u>erik.j.barkley@jpl.nasa.gov</u></font></a><font size=1 face="Arial">></font><font size=3 face="Times New Roman">
</font><font size=1 color=#5f5f5f face="Arial"><br>
To: </font><font size=1 face="Arial">"CESG
-- CCSDS-Engineering Steering Group (</font><a href=mailto:cesg@mailman.ccsds.org><font size=1 color=blue face="Arial"><u>cesg@mailman.ccsds.org</u></font></a><font size=1 face="Arial">)
(</font><a href=mailto:cesg@mailman.ccsds.org><font size=1 color=blue face="Arial"><u>cesg@mailman.ccsds.org</u></font></a><font size=1 face="Arial">)"
<</font><a href=mailto:cesg@mailman.ccsds.org><font size=1 color=blue face="Arial"><u>cesg@mailman.ccsds.org</u></font></a><font size=1 face="Arial">></font><font size=3 face="Times New Roman">
</font><font size=1 color=#5f5f5f face="Arial"><br>
Date: </font><font size=1 face="Arial">24/08/2016
20:45</font><font size=3 face="Times New Roman"> </font><font size=1 color=#5f5f5f face="Arial"><br>
Subject: </font><font size=1 face="Arial">[CESG]
CSS Area Technical Note: Functional Resource Model</font><font size=3 face="Times New Roman">
</font><font size=1 color=#5f5f5f face="Arial"><br>
Sent by: </font><font size=1 face="Arial">"CESG"
<</font><a href="mailto:cesg-bounces@mailman.ccsds.org"><font size=1 color=blue face="Arial"><u>cesg-bounces@mailman.ccsds.org</u></font></a><font size=1 face="Arial">></font><font size=3 face="Times New Roman">
</font>
<div align=center>
<hr noshade></div>
<br><font size=3 face="Times New Roman"><br>
<br>
</font><font size=2 color=#004080 face="Calibri"><br>
CESG Colleagues,</font><font size=3 face="Times New Roman"> </font><font size=2 color=#004080 face="Calibri"><br>
</font><font size=3 face="Times New Roman"> </font><font size=2 color=#004080 face="Calibri"><br>
Following up from the spring 2016 CESG meeting notes, I have the
action “EB to distribute TN”. The TN referred to here is the Functional
Resources Model which is now one of the key “pillars” for standards
being developed in the CSS Area. It can be viewed as the next logical
layer down from the Cross Support Architecture documents. You may
recall at the last CESG meeting I noted that it will be good to have CESG
review and comment on this. As this can also be viewed as the abstract
“wiring” diagram for cross-support component at the link level, I believe
it will be of particular interest for the SLS Area as we believe these
are the experts that will really know if the wiring makes sense.
<br>
</font><font size=3 face="Times New Roman"> </font><font size=2 color=#004080 face="Calibri"><br>
Here are some notes/background to help guide you in reading through this:</font><font size=3 face="Times New Roman">
</font><font size=2 color=#004080 face="Calibri"><br>
</font><font size=3 face="Times New Roman"> </font><font size=2 color=#004080 face="Calibri"><br>
a) In general, the Cross Support Services Area has
the job of developing recommended standards to facilitate cross support
between agencies between the various agency ground station networks and
the various spacecraft. This means that we are faced with the problem of
identifying the various components that render the various cross support
services without discussing these in terms of specific equipment implementation
details. The functional resource model represents our current best understanding
of the various service resources required in the cross support setting
but at an abstract level.</font><font size=3 face="Times New Roman"> </font><font size=2 color=#004080 face="Calibri"><br>
b) In general, the cross support services area recommendations
have to allow for extensibility. For example, as optical communication
becomes more and more of a reality, presumably we do not want to have the
cross support services recommendations being redeveloped from scratch to
address the management of optical space links versus the more traditional
radio frequency space links. The functional resource model supports such
an extensible capability.</font><font size=3 face="Times New Roman"> </font><font size=2 color=#004080 face="Calibri"><br>
c) Please ignore the editorial comments in the document
– these are essentially status notes from the technical note author and
are indications for the work that we in the cross support services area
need to do on the functional resource model. However the main body of the
technical note is sufficiently intact that I believe it is more beneficial
to take a look now rather than waiting for the updates to be performed.</font><font size=3 face="Times New Roman">
</font><font size=2 color=#004080 face="Calibri"><br>
d) If you are pressed for time and/or to gain some
basic familiarity my suggestion is to look at figures/diagrams 2-1 through
2-4. <br>
</font><font size=3 face="Times New Roman"> </font><font size=2 color=#004080 face="Calibri"><br>
I realize this is a rather substantial technical note (it is sufficiently
substantial that it may one day be put on a normative document track),
but any comments you may have by the time of the Rome meetings will be
appreciated. Given the non-trivial nature of this I think we can
also consider more discussions at the San Antonio meetings as well.</font><font size=3 face="Times New Roman">
</font><font size=2 color=#004080 face="Calibri"><br>
</font><font size=3 face="Times New Roman"> </font><font size=2 color=#004080 face="Calibri"><br>
Best regards,</font><font size=3 face="Times New Roman"> </font><font size=2 color=#004080 face="Calibri"><br>
-Erik</font><font size=3 face="Times New Roman"> </font><font size=2 color=#004080 face="Calibri"><br>
</font><font size=3 face="Times New Roman"> </font><font size=2 color=#004080 face="Calibri"><br>
</font><font size=3 face="Times New Roman"> </font><font size=2 face="Calibri"><b><br>
From:</b> </font><a href="mailto:cesg-bounces@mailman.ccsds.org"><font size=2 color=blue face="Calibri"><u>cesg-bounces@mailman.ccsds.org</u></font></a><font size=2 face="Calibri">
[</font><a href="mailto:cesg-bounces@mailman.ccsds.org"><font size=2 color=blue face="Calibri"><u>mailto:cesg-bounces@mailman.ccsds.org</u></font></a><font size=2 face="Calibri">]
<b>On Behalf Of </b></font><a href=mailto:Nestor.Peccia@esa.int><font size=2 color=blue face="Calibri"><u>Nestor.Peccia@esa.int</u></font></a><font size=2 face="Calibri"><b><br>
Sent:</b> Monday, April 11, 2016 4:15 PM<b><br>
To:</b> CESG -- CCSDS-Engineering SteeringGroup(</font><a href=mailto:cesg@mailman.ccsds.org)(cesg@mailman.ccsds.org)><font size=2 color=blue face="Calibri"><u>cesg@mailman.ccsds.org)(cesg@mailman.ccsds.org)</u></font></a><font size=2 face="Calibri">
<</font><a href=mailto:cesg@mailman.ccsds.org><font size=2 color=blue face="Calibri"><u>cesg@mailman.ccsds.org</u></font></a><font size=2 face="Calibri">><b><br>
Subject:</b> [CESG] CESG Meeting on 11th April 2016 : Draft Motes</font><font size=3 face="Times New Roman">
<br>
</font><font size=2 face="Arial"><br>
Dear all,</font><font size=3 face="Times New Roman"> </font><font size=2 face="Arial"><br>
draft notes attached</font><font size=3 face="Times New Roman"> <br>
</font><font size=2 face="Arial"><br>
<br>
Comments by Friday 15th April 2016 cob</font><font size=3 face="Times New Roman">
</font><font size=2 face="Arial"><br>
<br>
ciao</font><font size=3 face="Times New Roman"> </font><font size=2 face="Arial"><br>
nestor</font><font size=3 face="Times New Roman"> </font><font size=2 face="Courier New"><br>
This message and any attachments are intended for the use of the addressee
or addressees only.</font><font size=3 face="Times New Roman"> </font><font size=2 face="Courier New"><br>
The unauthorised disclosure, use, dissemination or copying (either in whole
or in part) of its</font><font size=3 face="Times New Roman"> </font><font size=2 face="Courier New"><br>
content is not permitted.</font><font size=3 face="Times New Roman"> </font><font size=2 face="Courier New"><br>
If you received this message in error, please notify the sender and delete
it from your system.</font><font size=3 face="Times New Roman"> </font><font size=2 face="Courier New"><br>
Emails can be altered and their integrity cannot be guaranteed by the sender.</font><font size=3 face="Times New Roman">
</font><font size=2 face="Courier New"><br>
</font><font size=3 face="Times New Roman"> </font><font size=2 face="Courier New"><br>
Please consider the environment before printing this email.[attachment
"FunctResRefModel_TechNote-TN-0.11-160707.docx" deleted by Gian
Paolo Calzolari/esoc/ESA] _______________________________________________<br>
CESG mailing list</font><font size=2 color=blue face="Courier New"><u><br>
</u></font><a href=mailto:CESG@mailman.ccsds.org><font size=2 color=blue face="Courier New"><u>CESG@mailman.ccsds.org</u></font></a><font size=3 color=blue face="Times New Roman"><u><br>
</u></font><a href="https://mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg"><font size=2 color=blue face="Courier New"><u>https://mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg</u></font></a><font size=2 face="Courier New"><br>
</font>
<br><font size=2 face="Courier New">This message and any attachments are
intended for the use of the addressee or addressees only.</font>
<br><font size=2 face="Courier New">The unauthorised disclosure, use, dissemination
or copying (either in whole or in part) of its</font>
<br><font size=2 face="Courier New">content is not permitted.</font>
<br><font size=2 face="Courier New">If you received this message in error,
please notify the sender and delete it from your system.</font>
<br><font size=2 face="Courier New">Emails can be altered and their integrity
cannot be guaranteed by the sender.</font>
<br><font size=2 face="Courier New"> </font>
<br><font size=2 face="Courier New">Please consider the environment before
printing this email.</font>
<br></div><PRE>This message and any attachments are intended for the use of the addressee or addressees only.
The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its
content is not permitted.
If you received this message in error, please notify the sender and delete it from your system.
Emails can be altered and their integrity cannot be guaranteed by the sender.
Please consider the environment before printing this email.
</PRE>