Issue 39.
From: Doug Davis
[mailto:dug@us.ibm.com]
Sent: Wednesday, January 24, 2007 12:57 PM
To: ws-rx@lists.oasis-open.org
Subject: [ws-rx] NEW ISSUE: Scope of CS/Offer/Endpoint
Title: Scope of
CS/Offer/Endpoint
Description:
Current RM spec
defines CS/Offer/Endpoint as:
/wsrm:CreateSequence/wsrm:Offer/wsrm:Endpoint
An
RM Source MUST include this element, of type wsa:EndpointReferenceType (as
specified byWS-Addressing). This element specifies the endpoint reference to
which Sequence Lifecycle Messages,Sequence Traffic Messages, Acknowledgement
Requests, and fault messages related to the offeredSequence are to be sent.
Implementations
MUST NOT use an endpoint reference in the Endpoint element that would prevent
the sending of Sequence Lifecycle Message, Sequence Traffic Message, etc. For
example, using the WS-Addressing
"http://www.w3.org/2005/08/addressing/none" IRI would make it
impossible for the RM Destination to ever send Sequence Lifecycle Messages
(e.g. TerminateSequence) to the RM Source for the Offered Sequence.
Implementations MAY use the WS-MakeConnection anonymous URI template and doing
so implies that messages will be retrieved using a mechanism such as the
MakeConnection message.
The inclusion
of the "Sequence Traffic Messages" actually isn't correct.
Sequence Traffic Message (ie. app messages) go to other EPRs, like
wsa:ReplyTo - just like RM was even being used. CS/Offer/Endpoint is
supposed to be for RM protocol messages (Close, Terminate, AckReq...). I
think when we switched over to the new RM terms we got a bit too excited
:-) The old text used to say:
...This element
specifies the endpoint reference to which WS-RM protocol messages related to
the offered Sequence are to be sent.
Proposal:
Remove
"Sequence Traffic Message" from the current definition of
CS/Offer/Endpoint. It appears in 2 spots.
thanks
-Doug
______________________________________________________
STSM | Web Services Architect | IBM Software Group
(919) 254-6905 | IBM T/L 444-6905 | dug@us.ibm.com