RE: [wsdm] MOWS RequestProcessingNotification

["Andrea Westerinen" <andreaw@cisco.com>]

Isn't this info appropriate for the model/format of the notification?
Something that CIM and/or CBE already covers. I continue to caution about
going down the slippery slope of the model or overloading what MUST be sent
in every notification.  CIM allows a client to choose the data that they
want.  "From" addressing seems one of these things.

Andrea  

> -----Original Message-----
> From: Sedukhin, Igor S [mailto:Igor.Sedukhin@ca.com] 
> Sent: Thursday, August 05, 2004 11:52 AM
> To: Murray, Bryan P.; wsdm@lists.oasis-open.org
> Subject: RE: [wsdm] MOWS RequestProcessingNotification
> 
> 
> Makes sense, but this needs a proper representation. I'm not 
> even sure that the endpoint necessarily works on an 
> TCP/IP-based network not to say that it uses HTTP. 
> 
> We could have something along the lines
> <Request>
> <From Address="xsd:anyURI">
> {any}*
> </From>
> </Request>
> 
> However doesn't it mimic WS-Addressing...
> 
> 
> -- Igor Sedukhin .. (igor.sedukhin@ca.com)
> -- (631) 342-4325 .. 1 CA Plaza, Islandia, NY 11788
> 
> -----Original Message-----
> From: Murray, Bryan P. [mailto:bryan.murray@hp.com] 
> Sent: Thursday, August 05, 2004 2:42 PM
> To: wsdm@lists.oasis-open.org
> Subject: [wsdm] MOWS RequestProcessingNotification
> 
> In the RequestProcessingNotification another item that would 
> be useful to consumers is to include an indication of where 
> the request came from. This data might be available in the 
> SOAP headers, but it might not. Usually, transports will have 
> some idea of where a request came from. But, different 
> transports are likely to represent this information in 
> different ways. For instance, an HTTP request might have the 
> source IP address.
> 
> One reason this information would be useful is if a large 
> number of messages are originating from a single user (maybe 
> a denial of service
> attack) an administrator could notice this and change the 
> authorization policy to reject or limit messages from that originator.
> 
> Bryan
> 
> To unsubscribe from this mailing list (and be removed from 
> the roster of the OASIS TC), go to 
> http://www.oasis-open.org/apps/org/workgroup/wsdm/members/leav
e_workgroup.php.



To unsubscribe from this mailing list (and be removed from the roster of the
OASIS TC), go to
http://www.oasis-open.org/apps/org/workgroup/wsdm/members/leave_workgroup.ph
p.