Message routing with four parties

, ,
1

Imported from previous forum

2

We are looking at a situation in which four parties are involved in routing a FIX message. A buy-side (A), ASP (B), order routine network ©, and sell-side (D). The sell-side only wants to see the buy-side and the ORN and each party is connected to the next via FIX engines (with the possible exception of A->B). There is only one ORN but there may be several ASPs, each with several buy-side clients.

We are consider the following contents for the routing fields (apologies if the formatting is lost):

Field A->B B->C C->D

SenderCompID A B C
TargetCompID B C D
OnBehalfOfCompID A A
DeliverToCompID D D

                D->C   C->B   B->A

SenderCompID D C B
TargetCompID C B A
OnBehalfOfCompID D D
DeliverToCompID A A

Is this a valid extension of the three party example given in the FIX protocol spec?

Also, is it a requirement of FIX engines that the party at each end of the connection be the same as the contents of the SenderCompID and TargetCompID fields?

Thanks for any comments (and thanks for the comments on my last question).

David.

3

Yes, your example looks correct.

No, it is not a requirement from a FIX Protocol-perspective that each party has the same understanding of CompIDs “all the way through”. It should be fine if “A” is represented by C to D as “AA” in OnBehalfOfCompID/DeliverToCompID provided that the appropriate mapping of firm’s identites is performed all the way through.

> We are looking at a situation in which four parties are involved in routing a FIX message. A buy-side (A), ASP (B), order routine network ©, and sell-side (D). The sell-side only wants to see the buy-side and the ORN and each party is connected to the next via FIX engines (with the possible exception of A->B). There is only one ORN but there may be several ASPs, each with several buy-side clients.
>
> We are consider the following contents for the routing fields (apologies if the formatting is lost):
>
> Field A->B B->C C->D
>
> SenderCompID A B C
> TargetCompID B C D
> OnBehalfOfCompID A A
> DeliverToCompID D D
>
> D->C C->B B->A
>
> SenderCompID D C B
> TargetCompID C B A
> OnBehalfOfCompID D D
> DeliverToCompID A A
>
> Is this a valid extension of the three party example given in the FIX protocol spec?
>
> Also, is it a requirement of FIX engines that the party at each end of the connection be the same as the contents of the SenderCompID and TargetCompID fields?
>
> Thanks for any comments (and thanks for the comments on my last question).
>
> David.
>
>