<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:0 0 0 0 0 0 0 0 0 0;}
@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;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
        {mso-style-priority:34;
        margin-top:0in;
        margin-right:0in;
        margin-bottom:0in;
        margin-left:.5in;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri",sans-serif;}
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;}
/* List Definitions */
@list l0
        {mso-list-id:246428114;
        mso-list-type:hybrid;
        mso-list-template-ids:-1339513468 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
        {mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l0:level2
        {mso-level-number-format:alpha-lower;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l0:level3
        {mso-level-number-format:roman-lower;
        mso-level-tab-stop:none;
        mso-level-number-position:right;
        text-indent:-9.0pt;}
@list l0:level4
        {mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l0:level5
        {mso-level-number-format:alpha-lower;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l0:level6
        {mso-level-number-format:roman-lower;
        mso-level-tab-stop:none;
        mso-level-number-position:right;
        text-indent:-9.0pt;}
@list l0:level7
        {mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l0:level8
        {mso-level-number-format:alpha-lower;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l0:level9
        {mso-level-number-format:roman-lower;
        mso-level-tab-stop:none;
        mso-level-number-position:right;
        text-indent:-9.0pt;}
@list l1
        {mso-list-id:1465348647;
        mso-list-type:hybrid;
        mso-list-template-ids:1909349514 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
        {mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l1:level2
        {mso-level-number-format:alpha-lower;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l1:level3
        {mso-level-number-format:roman-lower;
        mso-level-tab-stop:none;
        mso-level-number-position:right;
        text-indent:-9.0pt;}
@list l1:level4
        {mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l1:level5
        {mso-level-number-format:alpha-lower;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l1:level6
        {mso-level-number-format:roman-lower;
        mso-level-tab-stop:none;
        mso-level-number-position:right;
        text-indent:-9.0pt;}
@list l1:level7
        {mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l1:level8
        {mso-level-number-format:alpha-lower;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l1:level9
        {mso-level-number-format:roman-lower;
        mso-level-tab-stop:none;
        mso-level-number-position:right;
        text-indent:-9.0pt;}
ol
        {margin-bottom:0in;}
ul
        {margin-bottom:0in;}
--></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 uploaded the current draft of the FF-CSTS Red Book to the CWE at URL<o:p></o:p></p>
<p class="MsoNormal"><a href="https://cwe.ccsds.org/css/docs/CSS-CSTS/CWE%20Private/Future%20Services%20using%20Toolkit/Forward%20Frame%20CSTS/FF-CSTS-922x3r2.2-191126.doc?Web=1">https://cwe.ccsds.org/css/docs/CSS-CSTS/CWE%20Private/Future%20Services%20using%20Toolkit/Forward%20Frame%20CSTS/FF-CSTS-922x3r2.2-191126.doc?Web=1</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">This version contains the changes resulting from the pseudo RIDs discussed and approved at the fall Workshop. For the most part, the changes involved clarification and addition of the new informative annex that discusses the relationship
 between the FF service to provision of DTN services by an ESLT (new annex K).  This new annex has already undergone one review cycle with Peter Shames and the current version has been sent to him for concurrence or further revision.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">However, there were several changes that could affect the prototyping, depending on whether the prototyping implements the affected items:<o:p></o:p></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo2"><![if !supportLists]><span style="mso-list:Ignore">1.<span style="font:7.0pt "Times New Roman"">      
</span></span><![endif]>The pseudoRID JP-8 replaced the BFDP-specific <span style="font-family:"Courier New"">
transfer-mode</span> configuration parameter with the data-transfer-mode inherited from the parent (SFW) Buffered Data Processing procedure. This change could affect the prototypes to the extent that any setting or querying of this parameter must now be done
 in term of the pBDPdataTransferMode OID and PBDPdataTransferModeType.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo2"><![if !supportLists]><span style="mso-list:Ignore">2.<span style="font:7.0pt "Times New Roman"">      
</span></span><![endif]>PseudoRID ESA WH-1has also introduced technical changes in the specification that may or may not affect the prototyping effort, depending on whether the affected elements are actually being prototyped. Wolfgang’s pseudoRID pointed out
 that the read-only parameters specified in tables 4-4 and 5-4 were specified only as service management parameters, that is, there were no corresponding procedure-level parameters. As a result of the RID, the read-only
<span style="font-family:"Courier New"">number-of-data-units-received</span>, <span style="font-family:"Courier New"">
number-of-data-units-submitted-to-processing</span>, and <span style="font-family:"Courier New"">
number-of-data-units-processed</span> parameters in tables 4-4 and 5-4 have been respecified as read-only *<b>procedure</b>* parameters, and the
<span style="font-family:"Courier New"">current-input-queue-size</span> parameters have been deleted. Instead of using the separate
<span style="font-family:"Courier New"">current-input-queue-size</span> parameters, the current values of the input queue size are now specified to be reported using the respective
<span style="font-family:"Courier New"">input-queue-size</span> configuration parameters of the procedures. These changes might affect the prototyping if the
<span style="font-family:"Courier New"">number-of-data-units-received</span>, <span style="font-family:"Courier New"">
number-of-data-units-submitted-to-processing</span>, <span style="font-family:"Courier New"">
number-of-data-units-processed</span>, or <span style="font-family:"Courier New"">
current-input-queue-size</span> read-only parameters are being prototyped.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo2"><![if !supportLists]><span style="mso-list:Ignore">3.<span style="font:7.0pt "Times New Roman"">      
</span></span><![endif]>A third change to the ASN.1 has been made to the ASN.1 has been made to eliminate a possible source of confusion in the FF book. Both the Sequence-Controlled Frame Data Processing (SCFDP) and the Buffered Frame Data Processing (BFDP)
 procedures had derived-procedure configuration parameters <span style="font-family:"Courier New"">
gvcid-bit-mask</span>, <span style="font-family:"Courier New"">authorized-gvcid</span>,  <span style="font-family:"Courier New"">minimum-frame-length</span>, and
<span style="font-family:"Courier New"">maximum-frame-length</span>. For the SCFDP procedure, the corresponding parameter identifiers are
<span style="font-family:"Courier New"">pSCFDPgvcidBitMask</span>, <span style="font-family:"Courier New"">
pSCFDPauthorizedGvcid</span>, <span style="font-family:"Courier New"">pSCFDPminFrameLen</span>, and<span style="font-family:"Courier New""> pSCFDPminFrameLen</span>, respectively (table 4-3). For the BFDP procedure, the corresponding parameter identifiers are
<span style="font-family:"Courier New"">pBFDPgvcidBitMask</span>, <span style="font-family:"Courier New"">
pBFDPauthorizedGvcid</span>, <span style="font-family:"Courier New"">pBFDPminFrameLen</span>, and<span style="font-family:"Courier New""> pBFDPminFrameLen</span>, respectively (table 5-3). However, each of the four pairs had mapped to the same configuration
 parameter type, which is simply prefixed “PFDP”. E.g., <span style="font-family:"Courier New"">
pSCFDPgvcidBitMask</span> and <span style="font-family:"Courier New"">pBFDPgvcidBitMask</span> were both of type
<span style="font-family:"Courier New"">PFDPgvcidBitMaskType</span>, etc. These 4 common types were created before we switched to the Embedded PDV approach that heavily relies on the parameter OID being used to identify the syntax of the type of that parameter.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:.5in">In effect, tables 4-3 and 5-3 that there were two OIDs that could be used to identify the same syntax, which could be confusing for implementers.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:.5in">Therefore, the following changes were made:<o:p></o:p></p>
<p class="MsoListParagraph" style="margin-left:1.0in;text-indent:-.25in;mso-list:l1 level2 lfo1">
<![if !supportLists]><span style="mso-list:Ignore">a.<span style="font:7.0pt "Times New Roman"">      
</span></span><![endif]>The “PFDP”-prefixed types are now used as core types<o:p></o:p></p>
<p class="MsoListParagraph"><o:p> </o:p></p>
<p class="MsoListParagraph" style="margin-left:1.0in;text-indent:-.25in;mso-list:l1 level2 lfo1">
<![if !supportLists]><span style="mso-list:Ignore">b.<span style="font:7.0pt "Times New Roman"">      
</span></span><![endif]>Procedure-specific types are cast of those “PFDP”-prefixed types. E.g.,
<br>
<span style="font-family:"Courier New"">PSCFDPgvcidBitMaskType ::= PFDPgvcidBitMaskType<br>
PBFDPgvcidBitMaskType  ::= PFDPgvcidBitMaskType</span><o:p></o:p></p>
<p class="MsoListParagraph"><o:p> </o:p></p>
<p class="MsoListParagraph" style="margin-left:1.0in;text-indent:-.25in;mso-list:l1 level2 lfo1">
<![if !supportLists]><span style="mso-list:Ignore">c.<span style="font:7.0pt "Times New Roman"">      
</span></span><![endif]>Tthe procedure-specific types are used in tables 4-3 and 5-3 and in annex F. E.g.,
<span style="font-family:"Courier New"">pSCFDPgvcidBitMask</span> is of type <span style="font-family:"Courier New"">
PSCFDPgvcidBitMaskType</span>. In annex F, the OID specification for the classifier
<span style="font-family:"Courier New"">pSCFDPgvcidBitMask</span> are immediately followed by the type definition (<span style="font-family:"Courier New"">PSCFDPgvcidBitMaskType ::= PFDPgvcidBitMaskType</span>) to unambiguously specify the OID to identify both
 the parameter and the syntax.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:.5in">Possible effects on the prototyping could result to the extent that the prototypes implement the setting and querying of the
<span style="font-family:"Courier New"">gvcid-bit-mask</span>, <span style="font-family:"Courier New"">
authorized-gvcid</span>,  <span style="font-family:"Courier New"">minimum-frame-length</span>, and
<span style="font-family:"Courier New"">maximum-frame-length</span> procedure configuration parameters.<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>