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

RE: D-AR006.13 -- guidelines for ws sec admin

From: Darran Rolls <Darran.Rolls@waveset.com>
Date: Mon, 13 May 2002 13:12:16 -0500
Message-ID: <6244FCD1F88EC14BACDD2A319FD338242DC607@hawaii.waveset.com>
To: "Joseph Hui" <Joseph.Hui@exodus.net>, <www-ws-arch@w3.org>
I'll provide the beans....

Seriously, I don't believe this requirement to be any further out that
the QOS and instrumentation ideas in D-AC018.  <SOAP-BOX> I firmly
believe that the adoption and rollout of WS will be directly driven by
the ability to manage the technology through deployment and into the
full life-cycle of the service </SOAP_BOX>

PS, I take sugar in my coffee too ;-)

Darran Rolls                      http://www.waveset.com
Waveset Technologies Inc          drolls@waveset.com 
(512) 657 8360                    

-----Original Message-----
From: Joseph Hui [mailto:Joseph.Hui@exodus.net] 
Sent: Monday, May 13, 2002 12:52 PM
To: www-ws-arch@w3.org
Subject: D-AR006.13 -- guidelines for ws sec admin

Hi all,

Last week Darran Rolls of Waveset proposed in [1] a requirement
to call out the administrative aspect of WS security.  Our
rehashing of the idea off-line, in the interest of shaping it into
an "instantly consumable" form, resulting in the following proposed
requirement for further deliberation by the WG and the public:

   D-AR006.13 --
      The security framework document SHOULD provide guidelines
      for would-be WS providers and consumers to administrate
      their security functionalities.

Add water, milk, steam, ... comments? :-)

Joe Hui
Exodus, a Cable & Wireless service

[1] http://lists.w3.org/Archives/Public/www-ws-arch/2002May/0234.html 
Received on Monday, 13 May 2002 14:12:47 UTC

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