W3C home > Mailing lists > Public > www-ws-arch@w3.org > May 2002

D-AR006.11 discussion points

From: Christopher Ferris <chris.ferris@sun.com>
Date: Sat, 04 May 2002 09:59:40 -0400
Message-ID: <3CD3E94C.3020600@sun.com>
To: wsawg public <www-ws-arch@w3.org>
SUNW: This requirement goes "inside" a web service and places requirements
on how it is designed.  We should be focusing on externally observable
(through the web service interfaces) behaviour

SYBS: Implementation details. Don't seem to fit in Web Services Architecture

W3C: See http://lists.w3.org/Archives/Public/www-ws-arch/2002May/0015.html

ORCL: I don't quite see how "an architecture" can actually provide an
interface. And in this case the goal may be too ambitious given the
number of different possible "infrastructures".

PF: I just don't see the need for this.

TIB: not clear to me that individual Web services would ever want to
know whether they were under DOS at some lower layer

CrossWeave: Don't understand this

CMPQ: The interface is for negotiating services that an infrastructure may
provide to, or perform on behalf of, a requesting Web Services.
Such value-added services may include: security, content delivery,
QoS, etc. For instance, a Web service may instruct (via the interface) the security
agents of its infrastructure to defend against DOS/DDOS attacks on its behalf.

This seems to say that the requirement is
"The security framework must provide for negotiations pertaining to
security considerations."

That is, the requirement is for negotiation support;  within security context,
it is security negotiation, within QoS context, it is QoS negotiation, etc.
Received on Saturday, 4 May 2002 10:01:53 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:40:56 UTC