[NEW ISSUE] Make Accept/AcksTo consistent

[Doug Davis <dug@us.ibm.com>]

Title: Make Accept/AcksTo consistent

Description/Justification: 

The definition of CS/AcksTo says:
... It specifies the endpoint reference to which messages
containing 
<wsrm:SequenceAcknowledgement> header blocks
and faults related to 
the created Sequence are to be sent, unless otherwise
noted in this 
specification (for example, see Section 3.2).

However, the Accept/AcksTo says:
... The RM Source SHOULD send messages with <wsrm:SequenceAcknowledgement>

header blocks related to the accepted Sequence to
the referenced endpoint.


This is a bit inconsistent since the 2nd one doesn't
say anything about
sending faults the EPR.  Since the Offered sequence
should be no different
from a sequence created using a CS we need to align
these two 
definitions.

Target: wsrm spec

Type: design

Proposal:

Modify the Accept/AcksTo to say:
... Like the wsrm:CreateSequence/wsrm:AcksTo element,
this element
specifies the endpoint reference to which messages
containing
<wsrm:SequenceAcknowledgement> header blocks
and faults related to
the offered Sequences are to be sent, unless otherwise
noted in 
this specification (for example, see Section 3.2).

Implementations MUST NOT use an endpoint reference
in the AcksTo element 
that would prevent the sending of Sequence Acknowledgements
back to the 
RM Source. For example, using the WS-Addressing "none"
IRI would make it 
impossible for the RM Destination to ever send Sequence
Acknowledgements.



I basically stole the CS/AcksTo text.