IDSource (22) Pivate Security Identifications

, ,
1

Imported from previous forum

2

The FIX 4.2 spec says values of tag 22 in the 100+ range are reserved for private security identifications.

Who allocates these codes?

Can they be allocated within a member firm or do they need to be registed with the FIX committee?

–JT

3

[ original email was from Ryan Pierce - rpierce@taltrade.com ]
> The FIX 4.2 spec says values of tag 22 in the 100+ range are reserved for private security identifications.
>
> Who allocates these codes?
>
> Can they be allocated within a member firm or do they need to be registed with the FIX committee?

No central registration at this time exists for private security identifications as exists with proprietary field tags. So you can go ahead and assign whatever ones you want, however you have no guarantees regarding conflict with other FIX implementations or users. Hence this is something which requires agreement and testing between counterparties.

However, unless the symbology you are using is entirely private and/or proprietary, if other people are using the symbology, the FIX Technical Committee would like to know to consider adding it to future protocol releases.

4

[ original email was from Eric Molas - eric.molas@calyonfinancial.com ]
Does OCC have a designated IDSource value?

The FIX 4.2 spec says values of tag 22 in the 100+ range are reserved
for private security identifications.

Who allocates these codes?

Can they be allocated within a member firm or do they need to be
registed with the FIX committee?

No central registration at this time exists for private security
identifications as exists with proprietary field tags. So you can go
ahead and assign whatever ones you want, however you have no guarantees
regarding conflict with other FIX implementations or users. Hence this
is something which requires agreement and testing between
counterparties.

However, unless the symbology you are using is entirely private and/or
proprietary, if other people are using the symbology, the FIX
Technical Committee would like to know to consider adding it to future
protocol releases.