RE: issue 8273: proposal for WS-Eventing

I have some minor comments (mostly editorial) on this proposal included in the attached file. Does this proposal intend to drop the existing references to WS-Security, WS-Trust, WS-SecureConversation, WS-SecurityPolicy?

Thanks.

From: public-ws-resource-access-request@w3.org [mailto:public-ws-resource-access-request@w3.org] On Behalf Of Gilbert Pilz
Sent: Thursday, April 01, 2010 2:52 PM
To: Doug Davis
Cc: public-ws-resource-access@w3.org
Subject: Re: issue 8273: proposal for WS-Eventing

Attached is version 2 of the WS-Eventing proposal for 8273. I've attached an ODT with changes included and a PDF that shows the changes. I've cleaned up the RFC2119 language to just what I think is necessary, added Katy's suggestion on authenticating Notifications, fixed the spelling error, and made a couple of editorial tweaks.

- gp

On 3/30/2010 2:51 PM, Doug Davis wrote:

Overall looks really good.  just a few comments:
- s/identify/identity/    section 1.2 third line.
- we need to go thru and determine which uses of the RFC2919 keywords was intentional.

thanks
-Doug
______________________________________________________
STSM |  Standards Architect  |  IBM Software Group
(919) 254-6905  |  IBM 444-6905  |  dug@us.ibm.com<mailto:dug@us.ibm.com>
The more I'm around some people, the more I like my dog.

Gilbert Pilz <gilbert.pilz@oracle.com><mailto:gilbert.pilz@oracle.com>
Sent by: public-ws-resource-access-request@w3.org<mailto:public-ws-resource-access-request@w3.org>

03/30/2010 03:27 PM

To

"public-ws-resource-access@w3.org"<mailto:public-ws-resource-access@w3.org> <public-ws-resource-access@w3.org><mailto:public-ws-resource-access@w3.org>

cc

Subject

issue 8273: proposal for WS-Eventing







Attached is a proposal to replace Section 7 of WS-Eventing. It's main purpose is to discuss the specific security issues that relate to WS-Eventing and not WS-* security in general.

- gp[attachment "ws-ev-sec.odt" deleted by Doug Davis/Raleigh/IBM] [attachment "ws-ev-sec.pdf" deleted by Doug Davis/Raleigh/IBM]