OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

dss message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: [dss] core spec wd-16



>
> The document has 4 outstanding issues:
>
>   1) URLs or URNs for the schema namespace URI?
> http://lists.oasis-open.org/archives/dss/200403/msg00004.html

No strong view but suggest that we should follow whatever the convention has
been for other OASIS protocols.
>
>   2) Should we add a WSS security binding (or bindings)?
> WSS isn't a security protocol, it's more like a set of building
> blocks for
> making security protocols.  Building a security protocol out of these
> blocks seems complicated.  I think we should leave this for a separate
> document.

Can this be worked on separately then added at a later date?

>
>   3) Should we support an External Policy Authority vouching for some
> portion of the request?
> http://lists.oasis-open.org/archives/dss/200402/msg00046.html
> http://lists.oasis-open.org/archives/dss/200402/msg00041.html
> Paul presented a proposal and use case.  I'm still a little
> unclear on the
> use-case (see response to 2nd link).

I believe that we need to understand how signature policies fit in with
profiles before putting this in the Core.

>
>   4) Should RequestID be removed?
> This was to correlate requests and responses.  The HTTP POST binding
> doesn't need it.  The SOAP binding will mostly run over HTTP (?),
> in which
> case it doesn't need it.  So do we need this?

It is an optional element that could be useful.  I also vote for keeping it
in.

Nick




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]