Re: Draft registration of application/soap+xml

Rich, I was about to update the draft to incorporate your suggestion, but
had the following thought;

> > That's an interesting point, but the processing model doesn't specify
> > how to route, only how to target.
> 
> 
> A recipient receiving a message with an encrypted actor and/or 
> mustUnderstand cannot properly send a SOAP "actor" fault back, since 
> (obviously) it doesn't know who the actor was. :)  I believe this 
> impacts the processing model.

Should the processing model permit encrypted actors?  Or perhaps more
precisely, is an encrypted actor still an actor as far as the processing
model is concerned?

If it's encrypted, a processor won't know it may have been targetted,
and therefore it might do something bad like forward the header when
it wasn't supposed to.

MB
-- 
Mark Baker, Chief Science Officer, Planetfred, Inc.
Ottawa, Ontario, CANADA.      mbaker@planetfred.com
http://www.markbaker.ca   http://www.planetfred.com