[Css-csts] Discardability of NotifyInvocations in the Buffered Data Delivery procedure

[John Pietras]

Yves,
In section 4.4.3.2.1.1.1 of the v0.13 Framework document, the value of
the notification-type parameter is specified as being one of the types
specified for the common NOTIFY operation, 'data discarded due to excess
backlog', 'end of data', or one or more extension notifications. 

- No discardability requirement is stated for the inherited production
status values; 
- 'data discarded due to excess backlog' is defined to be discardable;
- 'end of data' is defined to be non-discardable;
- The definition of the discardability of each extension value is left
to the *service* using the buffered data delivery procedure.

1) Should the production status values be defined as discardable (since
that's what they were considered to be before we introduced the notion
of non-discardable)? If they are not assigned in the base buffered data
delivery procedure, then the procedure will never be able to be used
without derivation, because each service that uses it will in effect
have to declare some behavior of the procedure.

2) Should the discardability of any extension value be able to be
specified in a derived procedure as well as a service specification? 

Best regards,
John


John Pietras
Global Science & Technology, Inc. (GST)
7855 Walker Drive
Suite 200
Greenbelt, Maryland, USA
20770-3239
Direct:   +1-240-542-1155
GST Main: +1-301-474-9696
Fax:      +1-301-474-5970