<font size=2 face="sans-serif">Hello John,</font>
<br><font size=2 face="sans-serif">Thanks for the updated list. I fully
agree to leave out USLP for the 'first tier priority FRs'. I think this
is in line with the practical adoption of USLP. USLP will be adopted, but
until we have the practical need to monitor USLP parameters of a mission,
it might still be a while. At least from all I can see.</font>
<br>
<br><font size=2 face="sans-serif">Best regards,</font>
<br><font size=2 face="sans-serif">Holger</font>
<br>
<br><font size=2 face="sans-serif">Holger Dreihahn<br>
European Spacecraft Operations Centre | European Space Agency | S-431<br>
+49 6151 90 2233 | </font><a href=http://www.esa.int/esoc><font size=2 face="sans-serif">http://www.esa.int/esoc</font></a>
<br>
<br>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">"John Pietras"
<john.pietras@gst.com></font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">"CCSDS_CSTSWG
(css-csts@mailman.ccsds.org)" <css-csts@mailman.ccsds.org>,
"Wolfgang Hell" <wo_._he@t-online.de></font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">05/08/2019 21:57</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">[Css-csts] functional
resource priority lsit</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Sent by:
</font><font size=1 face="sans-serif">"CSS-CSTS"
<css-csts-bounces@mailman.ccsds.org></font>
<br>
<hr noshade>
<br>
<br>
<br><font size=3 face="Calibri">CSTSWG colleagues ---</font>
<br><font size=3 face="Calibri">Last month the CSS Area concurred to create
separate functional resource sets for AOS, TC, and Unified space data link
protocols in both the forward and return direction. This will result in
the following changes to the baseline set of FRs:</font>
<br><font size=3 face="Calibri">- A new
Forward USLP FR Set (the lower layers of this are already in the FR Reference
Model Tech Note);</font>
<br><font size=3 face="Calibri">- Splitting
the current Return TM/AOS SDLP Reception FR Set into separate Return TM
SDLP Reception and Return AOS SDLP Reception FR Sets; and</font>
<br><font size=3 face="Calibri">- Adding
a new Return USLP Reception FR Set.</font>
<br><font size=3 face="Calibri"> </font>
<br><font size=3 face="Calibri">At the spring Workshop, the WG updated
the priority list for which FRs would be targeted for inclusion in the
end-of-year “drop” for the SANA Registry. That list contains no USLP
FRs (in part because at the time we thought that USLP was going to be folded
into the AOS, TC, and TM FR Sets). Should the FRs of the USLP FR Sets be
added to the end-of-year list? This might be difficult, not only because
of time and resource constraints, but because Wolfgang and I have discovered
several ambiguities (and even possible errors) in the USLP specification,
and it might be better to wait until those issues are resolved before we
commit to a representation in the SANA Registry.</font>
<br><font size=3 face="Calibri"> </font>
<br><font size=3 face="Calibri">Whatever happens regarding USLP, I propose
that the split into return TM and AOS FR Sets be included in the end-of-year
drop, since the combined FR Set has been included in the earlier priority
list. Wolfgang has already done a lot of work on this and so I think it
will largely be a matter of making 2 copies of the existing FR Set and
down-scoping the two sets to the specific SDLPs. I can also be available
to do some of this tailoring (e.g., for the AOS set).</font>
<br><font size=3 face="Calibri"> </font>
<br><font size=3 face="Calibri">I have attached a strawman update of the
priority list that reflects these changes. As before, the color-coding
uses green to indicate that the FR is in the end-of-year drop. I have color-coded
the USLP FRs orange to indicate that the WG has not yet determined
their status with respect to the year-end drop.</font>
<br><font size=3 face="Calibri"> </font>
<br><font size=3 face="Calibri">I look forward to your comments.</font>
<br><font size=3 face="Calibri"> </font>
<br><font size=3 face="Calibri">Best regards,</font>
<br><font size=3 face="Calibri">John[attachment "fr_work_table-2019-08-05-strawman.xlsx"
deleted by Holger Dreihahn/esoc/ESA] </font><tt><font size=2>_______________________________________________<br>
CSS-CSTS mailing list<br>
CSS-CSTS@mailman.ccsds.org<br>
</font></tt><a href="https://mailman.ccsds.org/cgi-bin/mailman/listinfo/css-csts"><tt><font size=2>https://mailman.ccsds.org/cgi-bin/mailman/listinfo/css-csts</font></tt></a><tt><font size=2><br>
</font></tt>
<br>
<br>
<PRE>This message is intended only for the recipient(s) named above. It may contain proprietary information and/or
protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received
this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect
personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (dpo@esa.int).
</PRE>