RE: [ws-sx] WS-SX TC Minutes, July 12 2006

["Marc Goodner" <mgoodner@microsoft.com>]

I always try to capture "I will do x" as an action item, I rarely bother
to call out on the call that is being done leaving it to the minutes. I
will make more of an effort to call these out during the call going
forward.

Your statement matches my recollection that you did not feel it was
necessary but would do so as a courtesy. That is why it was recorded as
an action. I overlooked recording your opinion of the matter, my
apologies. The discussion in VER 2 of the minutes should capture this
and strikes the related AI.

-----Original Message-----
From: Prateek Mishra [mailto:prateek.mishra@oracle.com] 
Sent: Wednesday, July 12, 2006 11:17 AM
To: Marc Goodner
Cc: ws-sx@lists.oasis-open.org; Chris Kaler; Kelvin Lawrence
Subject: Re: [ws-sx] WS-SX TC Minutes, July 12 2006

I dont recall accepting an action along the lines of "AI-2006-07-12-03".

If fact, what I said on the call was that we did NOT feel we had to
provide this kind of citation. However, as a courtesy, we will make an
effort to connect these use-cases to public sources.

If there are concerns that we have left some specific links or citations
out, TC members should contact the Editors privately or publically
(depending on their preference).

- prateek

> WS-SX TC Minutes, July 12 2006
>
> Summary of new Action Items:
>
> AI-2006-07-12-01 - Kelvin to inform OASIS staff of problems with 
> infrastructure used to support the TC.
>
> AI-2006-07-12-02 - Hal will provide reference to BSP requirement 
> related to issue 90.
>
> AI-2006-07-12-03 - Prateek to provide information on how the issue 66 
> use cases are related WS-I BSP uses cases, WSS interop tests, or other

> public material.
>
> 1. Call to order/roll call
>
> Present:
>
> tbd
>
> 2. Reading/Approving minutes of last meeting (June 28)
>
>http://lists.oasis-open.org/archives/ws-sx/200606/msg00080.html
>
> Adopted unanimously.
>
> 3. TC Logistics (10 minutes or less)
>
> None.
>
> During other discussion it was noted that there have been problems 
> with delays related to mail being reflected from the TC list, we now 
> see a missing message, and the rosters are not working correctly.
>
> New AI-2006-07-12-01 - Kelvin to inform OASIS staff of problems with 
> infrastructure used to support the TC.
>
> 4. Issues list
>
> http://docs.oasis-open.org/ws-sx/issues/Issues.xml
>
> a) Review of action items
>
> AI-2006-04-04-03 - Tony Nadalin to identify possible issues for 
> SecurityPolicy based on the changes proposed for Issue 52.
>
> http://lists.oasis-open.org/archives/ws-sx/200607/msg00031.html
>
> Close action.
>
> Review proposal for next week's call.
>
> AI-2006-04-04-08 - Marc Goodner with help from Prateek Mishra to 
> document interop message flows based on the current version of
SC/Trust.
>
> http://lists.oasis-open.org/archives/ws-sx/200607/msg00032.html
>
> Seems editorial, agreed to apply edits.
>
> There was a second mail from Vijay Gargalla that does not appear in 
> the archives or seem to have been reflected by the mail list. Decision

> was to proactively apply those edits as well with change bars in the 
> intrest of time.
>
> Send respond to message to participate in private discussions about 
> virtual interop.
>
> http://lists.oasis-open.org/archives/ws-sx/200607/msg00033.html
>
> You can also send email to mgoodner@microsoft.com 
> <mailto:mgoodner@microsoft.com> to be added to the private DL.
>
> AI-2006-05-03-03 - Tony will investigate and start thread on issue 67.
>
> In progress. Will close it by next week.
>
> b) Issues in Review status
>
> None.
>
> c) New issues
>
> i081 - Provide policy statements and associated URIs that can be 
> referenced from wsp:PolicyReference statements
>
> Accepted. Frederick assigned as owner.
>
> This may be related to issue 66.
>
> i082 - Remove duplicate RFC2119 reference
>
> Accepted, moved to pending assigned to editors.
>
> i083 - Remove shading from figures, possibly enlarge
>
> Accepted, moved to pending assigned to editors.
>
> i084 - Assertions with nested policy do not indicate it
>
> Accepted, moved to pending assigned to editors.
>
> i085 - Replace ID with Id for Id attribute
>
> Accepted, moved to pending assigned to editors.
>
> Note, editors to identify correct edit and notify TC.
>
> i086 - No policy support for content encryption?
>
> Accepted. Frederick assigned as owner.
>
> Debate about whether there is a use case or not for this. Left open to

> discuss over next week.
>
> i087 - Matching assertion with empty nested Policy with assertion with

> no nested policy
>
> Accepted. Frederick assigned as owner.
>
> May be better handled by Policy WG at W3C.
>
> Close with no action, point to new issue at Policy WG
>
> http://lists.w3.org/Archives/Public/public-ws-policy/2006Jul/0013.html
>
> i088 - No XPath default
>
> Accepted, moved to pending with alternate proposal:
>
> http://lists.oasis-open.org/archives/ws-sx/200607/msg00029.html
>
> Assigned to editors.
>
> i089 - Minor editorial comments on security policy
>
> Accepted, moved to pending with revised proposal:
>
> http://lists.oasis-open.org/archives/ws-sx/200607/msg00023.html
>
> Assigned to editors.
>
> i090 - Description of Strict Formatting seems wrong for EncryptedKey
>
> Accepted. Hal assigned as owner.
>
> Noted BSP assumes processing described in proposal for this issue
>
> New AI-2006-07-12-02 - Hal will provide reference to BSP requirement 
> related to issue 90.
>
> i091 - security policy help for example C.3.2
>
> http://lists.oasis-open.org/archives/ws-sx/200607/msg00008.html
>
> Accepted. Frederick assigned as owner.
>
> d) Active issues
>
> i004 - Transitive closure spec dependencies
>
> Update provided on call on status
>
> i008 - Need well formed XML examples
>
> Ongoing. Not needed to worry about until we get to a public doc.
>
> i066 - SecurityPolicy use cases
>
> More comments,
> http://lists.oasis-open.org/archives/ws-sx/200607/msg00018.html
>
> Keep open as long as discussion is ongoing.
>
> One use case from WS-I BSP is described here, question on which one.
>
> Also developed from WSS interop tests.
>
> Discussion on how understanding the source material could help in 
> understanding the use cases.
>
> New AI-2006-07-12-03 Prateek to provide information on how the issue
> 66 use cases are related WS-I BSP uses cases, WSS interop tests, or 
> other public material.
>
> i067 - Resolving Policies if more than one SecureConversationToken is 
> present
>
> See AI-2006-05-03-03
>
> i070 - Clarify relationship between extensibility model and policy 
> intersection
>
> Please review proposal 3 as the most current
>
> http://lists.oasis-open.org/archives/ws-sx/200606/msg00068.html
>
> i077 - Use of Section 8 from WS-SC forces applications to be WSS 
> schema aware
>
> http://lists.oasis-open.org/archives/ws-sx/200607/msg00034.html
>
> Prateek will respond to continue discussion.
>
> i078 - Specify Reference Types for References to SCT
>
> Hal expects to make a proposal later this week.
>
> i079 - Is Bootstrap policy a PolicyAssertion
>
> Needs discussion.
>
> i080 - Handling EncryptParts specified under SupportingTokens
>
> Needs discussion.
>
> f) Pending issues
>
> i071 - Guidance on Policy Application
>
> i074 - Add <EncryptSupportingToken> element to Sections 7.4 and7.5
>
> 5. AOB
>
> Reminder to send respond to message to participate in private 
> discussions about virtual interop.
>
> http://lists.oasis-open.org/archives/ws-sx/200607/msg00033.html
>
> You can also send email to mgoodner@microsoft.com 
> <mailto:mgoodner@microsoft.com> to be added to the private DL.
>
> 6. Adjournment
>
> The meeting adjourned at 7:55am PST
>