Use of FaultTo when propagating WS-A Faults

Related to LC76, we came to the agreement that ReplyTo would NOT be used
when a message contains an imperfect set of WS-A Headers, like a missing
WS-A: Action.

 

What about the use of FaultTo for a Fault?  Imagine the scenario where
FaultTo is non-anonymous and Action is missing.  The receiver decides to
Fault (perhaps because mU was on a WS-A header).  

 

I think the correct behaviour is that the FaultTo should not be used for
propagating the Fault, because the FaultTo is part of the overall WS-A
set of headers which aren't valid.  But that does seem a little
counter-intuitive.

 

If the FaultTo is ignored, then Fault would probably be sent back over
an HTTP Connection if one exists.  This is like changing the faultTo to
become anonymous.  This seems to be yet another scenario where even
though the sender believes it is a one-way message, it will allow for a
soap fault in the response if it wants as much information as possible.

 

Cheers,

Dave