RE: [wss] Agenda for Sept 4th/5th meeting

[Tim Moses <tim.moses@entrust.com>]

Title: RE: [wss] Agenda for Sept 4th/5th meeting

Krishna - In light of Chris's warning.  Perhaps, we should restrict our discussion to whether or not the topic is in-scope.  If it is determined to be in-scope, then we can talk about solutions during and after the face-to-face.  All the best.  Tim.

-----------------------------------------
Tim Moses
Tel: 613.270.3183

-----Original Message-----
From: Krishna Sankar [mailto:ksankar@cisco.com]
Sent: Monday, September 02, 2002 12:39 AM
To: wss@lists.oasis-open.org
Subject: RE: [wss] Agenda for Sept 4th/5th meeting

Tim,

        Good thoughts.

        By quality do you envision different trust levels - possibly
increasing security strengths ? For example weather service could be
level 1 while a super secret military could be 10. Basically some
increasing (or decreasing) security quality levels and the corresponding
functionalities - shared understanding by all. If the levels do not have
any numerical relationships/connotations (like the Richter scale - easy
to think being in SFO :o()), would it be similar to the classification
by the military ?

        Second, how would they manifest in the WSDL ? As sub elements to
a <Security-QOS> element with an associated namespace and schema ?

        Third, why WS-Security ? Do you see the <Security-QOS> as a part
of the WS-Security namespace ?

        Fourth, how would one measure the Sec-QoS with intermediaries ?
The least of all or some other Sec-QoS algebra ?

PS : Just saw reply from Ed and Novell's Extension Attributes.
Interesting ... BTW, it is already version 0.998 - not that far away
from 1.0 unless we go to 6 or 7 digits of precision :o)

cheers
-----Original Message-----
From: Tim Moses [mailto:tim.moses@entrust.com]
Sent: Sunday, September 01, 2002 9:43 AM
To: wss@lists.oasis-open.org
Subject: RE: [wss] Agenda for Sept 4th/5th meeting

Colleagues - I would like to suggest that the WS Security TC tackle the
question of Quality of Security. TLS has its cipher suites, S/MIME has
its supportedAlgorithms directory attribute. SOAP security needs
something similar. QOS for SOAP is complicated by the fact that XML DSig
and XML Enc can define a set of nodes to be protected. Whereas, for TLS
and S/MIME, it is "all or nothing". Perhaps, the answer is to adapt WSDL
to accommodate QOS information. But, I feel that wsstc is the place to
develop the solution - not necessarily in the core specification, but,
perhaps, in a supporting document. All the best. Tim.
-----------------------------------------
Tim Moses
Tel: 613.270.3183

-----Original Message-----
From: klawrenc@us.ibm.com [mailto:klawrenc@us.ibm.com]
Sent: Tuesday, August 27, 2002 11:11 AM
To: wss@lists.oasis-open.org
Subject: [wss] Agenda for Sept 4th/5th meeting

Dear WSS TC members, here is the agenda for our initial face to face
meeting next week.

On Wednesday 4th, the meeting will start at 10:am and close at 5pm
On Thursday 5th, the meeting will start at 9am and close at 4pm

Welcome and Introductions/roll call
Assign minute taker(s)
Review of OASIS TC process
Review of TC charter
Establish standing rules for this TC
Assign roles (webmaster, editor etc.)
Discussion of how this TC relates to other committees in the security
area
Discuss assigning a liaison to other security related standards
committees
Update for this team on the OASIS/W3C joint meeting in Boston .  
Submission of input documents
Discuss phone call sponsor for next call and agree schedule for phone
calls.
Discuss location of next F2F meeting and sponsor
Main part of meeting - group discussion
Any other business
Close

Chris Kaler
Kelvin Lawrence
(co-chairs WSS TC)

----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>