[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [VER 2] WS-SX TC Minutes, September 27th 2006
|
[VER
2] Added roll, noted no new AIs. WS-SX TC Minutes, September 27th 2006 Summary of new Action Items: none 1. Call to order/roll call Present: Hal Lockhart, BEA Systems, Inc.*
Status
change: Dana Kaufman is a voting member now 2. Reading/Approving minutes from September 20th
2006 http://lists.oasis-open.org/archives/ws-sx/200609/msg00049.html Adopted unanimously. 3. TC Logistics (10 minutes or less) Discussion of F2F deffered until next week. We need phone call sponsors after end of October. 4. Issues list http://docs.oasis-open.org/ws-sx/issues/Issues.xml a) Review of action items AI-2006-09-06-01 - Gudge to make proposal for issue
90 by end of September Should be out today. AI-2006-09-20-01 - Chairs to cancel TC calls for Nov
22, Dec 20 and Dec 27 Closed AI-2006-09-20-02 - Marc and Tony to prepare interop
plan for SP Marc was not available, Greg Carpenter has taken
this on with Tony. http://www.oasis-open.org/archives/ws-sx/200609/msg00051.html Closed b) Issues in Review status i103 - Interop document - Clarify that RSTR is
returned in RSTRC Status changed to closed, adopted unanimously. i104 - Update interop documents to reflect what was
actually tested. Status changed to closed, adopted unanimously. c) New issues PR001 - Question on WS-Trust sections 4.3.5 to 4.3.7 Accepted, Marc asigned as owner. d) Active issues i066 - SecurityPolicy use cases http://www.oasis-open.org/archives/ws-sx/200609/msg00033.html More comments: http://www.oasis-open.org/archives/ws-sx/200609/msg00054.html Comments seem acceptable. Suggestion on title seems correct.
Need a few days to evaluate the direction to take the document in relation to
that. What is the purpose of the document? Trying to show how tokens are used in different
bindings. Is it meant to be a primer? Somewhat, right now it is skeletal to capture the
high level goals. It needs to be filled out a lot more. What do we expect to happen to this document? It would be a TC reference document. A non-normative advisory document? That would be OK, but it should be published. It
should have a concrete reference. Could be a launching point for issue 81. It implies processing semantics so it may not be
non-normative. What do you mean? 2.3.1.3, abstract implies processing semantics, e.g.
key matching. Rich is addressing comments in next draft. The focus is on non-normative material. i081 - Provide policy statements and associated URIs
that can be referenced from wsp:PolicyReference statements Not discussed. i090 - Description of Strict Formatting seems wrong
for EncryptedKey Waiting on AI-2006-09-06-01 i096 - Ensure Appendix A is complete Should be in next SP update. i101 - Need additional SamlToken Assertion Elements
for Holder-of-Key and Sender-Vouches Proposal 2 - http://www.oasis-open.org/archives/ws-sx/200609/msg00032.html Text is getting into processing semantics and not
just wire format. This was done becase there was a preference
expressed to handle this on an inferrential basis. Will look at the comments
and respond. i110 - QName support for specifying elements that
need to be present in the message Proposal 1 - http://www.oasis-open.org/archives/ws-sx/200609/msg00034.html Adopted unanimously, status changed to pending. f) Pending issues i083 - Remove shading from figures, possibly enlarge i086 - No policy support for content encryption? Expect a revision of SP this week with all pending
issues addressed. 5. Next steps SP interop, assume people want more time to look at
this. BE prepared to discuss on next call. 6. AOB There are some editorial issues with some of the
specs, can we cover those here? Please send via email. Note: TC members can file PR issues on SC/Trust
using the normal TC list. 7. Adjournment The meeting adjourned at 7:35am PST |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]