Conformance

["Nick Pope" <pope@secstan.com>]

Following the discussions from the last DSS meeting on conformance
requirements on Optional Input and Outputs, I propose the existing text in
2.8 is updated as follows, with ADDITIONAL TEXT ADDED IN CAPITALS.  [Text to
be deleted in in squash brackets]:

"All request messages can contain an <OptionalInputs> element, and all
response messages can contain an <OptionalOutputs> element.  Several
optional inputs and outputs are defined in this document, and profiles can
define additional ones.

The <OptionalInputs> contains additional inputs associated with the
processing of the request WHICH MAY RESULT IN CERTAIN OPTIONAL OUTPUTS BEING
INCLUDED IN THE RESPONSE.  Profiles will specify [the allowed] ANY optional
inputs OR OPTIONAL OUTPUTS THAT ARE REQUIRED TO BE SUPPORTED OR ALWAYS
PRESENT [and their default values].  THIS CORE SPECIFICTION DOES NOT REQUIRE
ANY OPTIONAL INPUT OR OUTPUT TO BE SUPPORTED. The definition of an
<OptionalInput> MAY include a default value , so that a client may omit the
<OptionalInputs> yet still get service from any profile-compliant DSS
server.

If a server doesn’t recognize or can’t handle any optional input, it MUST
reject the request with a <ResultMajor> code of RequesterError and a
<ResultMinor> code of NotSupported (see section 2.6).

The <OptionalOutputs> element contains additional protocol outputs.  The
client MAY request the server to respond with certain optional outputs by
sending certain optional inputs.  The server MAY also respond with outputs
the client didn’t request, depending on the server’s profile and policy."


Nick Pope
Mob: +44 (0) 777 567 2590