Messaging-+Incorrect+RelatesTo+responses

Please contribute your comments via the discussion tab above. Outcomes and resolution will be added at the bottom of this page.

=Messaging: Impact of incorrect RelatesTo in responses?=

0 row selected - rows selected - [|clear] || Issue: In some responses to synchronous requests, there is an incorrect RelatesTo id being passed - it is an OID rather than a message ID.
 * ~ 1 - 1 of 1
 * [[image:http://www.wikispaces.com/i/user_none_lg.jpg width="48" height="48" caption="JoeLamy" link="http://www.wikispaces.com/user/view/JoeLamy"]] || [|JoeLamy]

Example: urn:oid:1.3.6.1.4.1.26580

It is unknown at this point how or if systems will process this value. Is it not needed for synchronous requests? The testing team has plans to use it in correlating and evaluating test results.

Tentative severity level: 3-Medium [|[delete]] || =WS-Addressing specification requires valid RelatesTo=

0 row selected - rows selected - [|clear] || If an incoming message contains a wsa:RelatesTo then it MUST have a value that corresponds to some previously sent outgoing message - and that outgoing message MUST have had a wsa:MessageID with that value. So this is a bug and violates the WS-Addressing specification. It is a significant problem because receivers of RelatesTo may be dependant on it being specified correctly and will not work if it is not. [|[delete]] || [|tdavid7] Per the WS-Addressing specification, the MessageID and RelatesTo elements, can be of anyURI type.
 * ~ 1 - 2 of 2
 * [[image:http://www.wikispaces.com/i/user_none_lg.jpg width="48" height="48" caption="witting" link="http://www.wikispaces.com/user/view/witting"]] || [|witting]
 * [[image:http://www.wikispaces.com/i/user_none_lg.jpg width="48" height="48" caption="tdavid7" link="http://www.wikispaces.com/user/view/tdavid7"]] || **re: WS-Addressing specification requires valid RelatesTo**

You will normally see this as a UUID, such as uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6 OR urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6

There is nothing in the specification that would preclude the use of an 'urn:oid' notational format.

The only caveat being, (as Karen pointed out), that the RelatesTo MUST be a MessageID URI from a previously received message.

If the testing scenario is an initial request from an HIE, such as XCPD, than it is unlikely, the the RelatesTo value is valid [|[delete]] ||