Subject: Re: agenda topics, WG last call for DPV requirements

From: Peter Sylvester <[email-masked]>
Date: Mon, 25 Feb 2002 19:26:54 +0100 (MET)

There are some comments for DPV that have been ignored.

The last three blocks in chapter 4 talk about security
requirements, but the following two are not mentioned
(unless I miss something).

>
>- Security requirements
>
>   - a method to authenticate a server before sending any request
>     (for example this can be achieved by SSL).
      (Another example would be using encryption.)
>
>   - a method to ensure confidentiality of the transport
>
>   - a method that client and server provide their identity
>     in the requests and responses: 'You, the client X, has
>     asked me, the server Y, the following question, and
>     I, the server Y, with the help of server Z respond.'
This allows to be able to determine the participating entities
without having access to whatever particular authentication 
method information.

The following requirements may be used for example in case of
validation of an encryption certificate before usage.

One may resume the relaying requirements into one: 

- The protocol MUST provide a means to allow (visible) relaying
  of requests and responses. 

>
>- Relaying requirements:
>
>   - depending on policy, a server may just impersonate another
>     server, i.e., take the responses of another server, and create
>     its own reponse out of them.
>
>   - a server should be able to include the response of a relayed
>     server into his response.
>
>   - a server should be able to simple add another authentication
>     scheme to a response from another server (for example by
>     using a second signature or a counter signature.)
>
>   - a server that acts as a relay should be able to tell to the
>     next server that it is acting on behalf of a end user, and
>     the final server should be able to note this in the response.
>
>   - For relaying, the protocol MUST provide an efficient means
>     to detect loops.
>

>
>- Requirements for incomplete answers:
>
>   - a server may indicate an incomplete response,
>     and provide a method to update the response later.
>