<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: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=us-ascii">
<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:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">CSTSWG colleagues ---<o:p></o:p></p>
<p class="MsoNormal">I have just concluded a review of the definitions of the Functional Resources that are associated with Forward Frame CSTS. This review included both the higher-level definitions found in the
<i>Functional Resource Reference Model</i> Tech Note and the detailed parameter, event, and directive (PED) definitions found in the Candidate SANA FR Registry. The results are documented in the White Paper Functional Resources for the Forward Frame CSTS, which
has been posted at URL<o:p></o:p></p>
<p class="MsoNormal"><a href="https://cwe.ccsds.org/css/docs/CSS%20Area/CWE%20Private/Functional%20Resources%20and%20Service%20Components/FunctionalResourcesForForwardFrameCsts-181008.docx">https://cwe.ccsds.org/css/docs/CSS%20Area/CWE%20Private/Functional%20Resources%20and%20Service%20Components/FunctionalResourcesForForwardFrameCsts-181008.docx</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The format of the White Paper is to document each FF-CSTS-related FR, using both the corresponding higher-level descriptive material from the FR RM Tech Note and tables of (a) the configuration parameters, (b) read-only parameters, (c)
notification events, and (d) directives of each FR type. The core content of these tables is based on the current contents of the Candidate SANA FR Registry. PEDs that are acceptable as-is are labeled as “See the SANA FR Registry”. PEDs that need adjustment
of some sort are so annotated with the description of the needed adjustment(s), and new PEDS are annotated with “NEW PARAMETER (EVENT, DIRECTIVE)”.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">There has been some question as to whether the forthcoming Unified Space Data Link Protocol (USLP) should be represented by existing FR types (e.g., Forward TC, Forward AOS, and Return TM AOS) or have its own set of FRs. Given that USLP
combines subsets of capabilities of TC, TM, and AOS (as well as Prox-1, which we don’t have to concern ourselves with since the FRs are currently confined to ESLTs) , I have come to the conclusion that it is easier/better overall to create separate USLP-specific
FRs than to try to sprinkle “If the frames are USLP fixed/variable-length frame” kinds of statements throughout the definitions of the current TC, TM, and AOS SDLP FR types. So the White Paper contains new FR definitions for USLP.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I have also updated the SANA FR Registry Items spreadsheet to include the issues and concerns that arose during this evaluation. It has been posted at URL<o:p></o:p></p>
<p class="MsoNormal"><a href="https://cwe.ccsds.org/css/docs/CSS-CSTS/CWE%20Private/Functional%20Resources%20Definition/SANA/FR_Registry_Items-2018-10-04.xlsx">https://cwe.ccsds.org/css/docs/CSS-CSTS/CWE%20Private/Functional%20Resources%20Definition/SANA/FR_Registry_Items-2018-10-04.xlsx</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Hopefully we can find some time next week to discuss these results .<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Best regards,<o:p></o:p></p>
<p class="MsoNormal">John<o:p></o:p></p>
</div>
</body>
</html>