<font size=2 face="sans-serif">Dear Erik,</font>
<br><font size=2 face="sans-serif"> 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="sans-serif">".</font>
<br><font size=2 face="sans-serif">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>
<br>
<br><font size=2 face="sans-serif">Thanks</font>
<br>
<br><font size=2 face="sans-serif">Gian Paolo</font>
<br>
<br>
<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">"CESG -- CCSDS-Engineering
Steering Group (cesg@mailman.ccsds.org) (cesg@mailman.ccsds.org)"
<cesg@mailman.ccsds.org></font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">24/08/2016 20:45</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">[CESG] CSS Area
Technical Note: Functional Resource Model</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Sent by:
</font><font size=1 face="sans-serif">"CESG"
<cesg-bounces@mailman.ccsds.org></font>
<br>
<hr noshade>
<br>
<br>
<br><font size=2 color=#004080 face="Calibri">CESG Colleagues,</font>
<br><font size=2 color=#004080 face="Calibri"> </font>
<br><font size=2 color=#004080 face="Calibri">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. </font>
<br><font size=2 color=#004080 face="Calibri"> </font>
<br><font size=2 color=#004080 face="Calibri">Here are some notes/background
to help guide you in reading through this:</font>
<br><font size=2 color=#004080 face="Calibri"> </font>
<br><font size=2 color=#004080 face="Calibri">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>
<br><font size=2 color=#004080 face="Calibri">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>
<br><font size=2 color=#004080 face="Calibri">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>
<br><font size=2 color=#004080 face="Calibri">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. </font>
<br><font size=2 color=#004080 face="Calibri"> </font>
<br><font size=2 color=#004080 face="Calibri">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>
<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 color=#004080 face="Calibri"> </font>
<br><font size=2 face="Calibri"><b>From:</b> cesg-bounces@mailman.ccsds.org
[</font><a href="mailto:cesg-bounces@mailman.ccsds.org"><font size=2 face="Calibri">mailto:cesg-bounces@mailman.ccsds.org</font></a><font size=2 face="Calibri">]
<b>On Behalf Of </b>Nestor.Peccia@esa.int<b><br>
Sent:</b> Monday, April 11, 2016 4:15 PM<b><br>
To:</b> CESG -- CCSDS-Engineering SteeringGroup(cesg@mailman.ccsds.org)(cesg@mailman.ccsds.org)
<cesg@mailman.ccsds.org><b><br>
Subject:</b> [CESG] CESG Meeting on 11th April 2016 : Draft Motes</font>
<br><font size=3 face="Times New Roman"> </font>
<br><font size=2 face="Arial">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>
<br>
</font><font size=2 face="Arial"><br>
Comments by Friday 15th April 2016 cob</font><font size=3 face="Times New Roman">
<br>
</font><font size=2 face="Arial"><br>
ciao</font><font size=3 face="Times New Roman"> </font><font size=2 face="Arial"><br>
nestor</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.[attachment "FunctResRefModel_TechNote-TN-0.11-160707.docx"
deleted by Gian Paolo Calzolari/esoc/ESA] </font><tt><font size=2>_______________________________________________<br>
CESG mailing list<br>
CESG@mailman.ccsds.org<br>
</font></tt><a href="https://mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg"><tt><font size=2>https://mailman.ccsds.org/cgi-bin/mailman/listinfo/cesg</font></tt></a><tt><font size=2><br>
</font></tt>
<br>
<br><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>