<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Dear CSTS WG members,<br>
<br>
this is to let you know that I have just uploaded the latest version
of the SFW as a zipped file to the CWE at <br>
<span id="ctl00_PlaceHolderTitleBreadcrumb_ContentMap"><span></span><span><a
class="ms-sitemapdirectional" href="http://cwe.ccsds.org/css">Cross
Support Services Area (CSS)</a></span><span> > </span><span><a
class="ms-sitemapdirectional"
href="http://cwe.ccsds.org/css/docs/Forms/AllItems.aspx?View=%7B8045374D-F8E0-4356-83CA-993252A38FE8%7D">Documents</a></span><span>
> </span><span><a class="ms-sitemapdirectional"
href="http://cwe.ccsds.org/css/docs/Forms/AllItems.aspx?RootFolder=%2Fcss%2Fdocs%2FCSS%2DCSTS&View=%7B8045374D-F8E0-4356-83CA-993252A38FE8%7D">CSS-CSTS</a></span><span>
> </span><span><a class="ms-sitemapdirectional"
href="http://cwe.ccsds.org/css/docs/Forms/AllItems.aspx?RootFolder=%2Fcss%2Fdocs%2FCSS%2DCSTS%2FCWE%20Private&View=%7B8045374D-F8E0-4356-83CA-993252A38FE8%7D">CWE
Private</a></span><span> > </span><span
class="ms-sitemapdirectional">CSTS Framework and Concept</span></span><br>
<br>
The most recent changes applied are those resulting from the
discussion of how the Service Instance Identifier should be built
and how to deal with the issue that the recording buffer was
supposed to be in essence left unspecified while the BDD procedure
in complete delivery mode had to make at least a few assumptions
regarding the recording buffer characteristics.<br>
<br>
Please note that the SII related updates not only affect the BIND
operation, but given that the "attributes" OID subbranch is no
longer needed, various updates had to be made to annex C and annex
K. Furthermore the ASN.1 module specifying the
ServiceInstanceIdentifier type had to be rewritten and is much
simpler now.<br>
<br>
The BDD procedure has been reworked such that it now contains a
formal specification of the associated recording buffer type as
needed by the BDD procedure. Derived procedures may have to specify
a variant of the recording buffer which shall however as a minimum
have the characteristics of the BDD recording buffer. Given that the
recording buffer is a resource that may be shared by several CSTS
instances, I have opted for modeling it as a Functional Resource as
to have the means to refer to associated parameters and events. John
would prefer to associate the parameters and events with the
procedure. The pros and cons will be one of the topics discussed at
the forthcoming webex session.<br>
<br>
I shall prepare a brief presentation summarizing all updates
implemented since the Pasadena meeting<br>
<br>
Best regards,<br>
Wolfgang <br>
</body>
</html>