Imported from previous forum
Hello everybody,
We have a question about the changes proposed to FIX specification for MiFID ( see http://www.fixprotocol.org/pages/3167/Summary%20of%20Changes%20to%20FIX%20for%20MiFID.htm ). There is a change proposed to the FIX specification about a new accepted value for tag 21 ( new enum: Best Execution ).
All the documents in http://www.fixprotocol.org/mifid are related to FIX 5.0, but in a previous draft this changes were proposed for FIX4.4 (Draft MiFID Gap Analysis - FIX 4.4 Version 1.6 Dated 10 May 2006). The last document (http://www.fixprotocol.org/documents/3180/MiFID_FPL_Gap2.0.pdf) is for FIX 5.0.
Someone knows if this changes are going to be added only in FIX 5.0, or it will be added in FIX 4.4 as well?
Regards
Abel Monroy
Hello everybody,
We have a question about the changes proposed to FIX specification for
MiFID ( see http://www.fixprotocol.org/pages/3167/Summary%20of%20Chan-
ges%20to%20FIX%20for%20MiFID.htm ). There is a change proposed to the
FIX specification about a new accepted value for tag 21 ( new enum:
Best Execution ). All the documents in
http://www.fixprotocol.org/mifid are related to FIX 5.0, but in a
previous draft this changes were proposed for FIX4.4 (Draft MiFID Gap
Analysis - FIX 4.4 Version 1.6 Dated 10 May 2006). The last document
(http://www.fixprotocol.org/documents/3180/MiFID_FPL_Gap2.0.pdf) is
for FIX 5.0.Someone knows if this changes are going to be added only in FIX 5.0, or
it will be added in FIX 4.4 as well?Regards Abel Monroy
There are no current plans to change FIX 4.4 or any of the earlier versions. The changes in the document have been applied to Version 5.0 only
Just one more question about this issue. The number assigned to BestExecution into tag 21, I assume it’s 4, is that right?
Regards
Abel Monroy
Hello everybody,
We have a question about the changes proposed to FIX specification for
MiFID ( see http://www.fixprotocol.org/pages/3167/Summary%20of%20Chan-
ges%20to%20FIX%20for%20MiFID.htm ). There is a change proposed to the
FIX specification about a new accepted value for tag 21 ( new enum:
Best Execution ). All the documents in
http://www.fixprotocol.org/mifid are related to FIX 5.0, but in a
previous draft this changes were proposed for FIX4.4 (Draft MiFID Gap
Analysis - FIX 4.4 Version 1.6 Dated 10 May 2006). The last document
(http://www.fixprotocol.org/documents/3180/MiFID_FPL_Gap2.0.pdf) is
for FIX 5.0.Someone knows if this changes are going to be added only in FIX 5.0,
or it will be added in FIX 4.4 as well?Regards Abel Monroy
There are no current plans to change FIX 4.4 or any of the
earlier versions. The changes in the document have been applied
to Version 5.0 only
It looks as if BestExecution was added to ExecInst (tag 18) in the end for FIX 5.0. Tag 21 (HandlInst) is geared towards floor trading. The last document you refer to below is ambiguous in this respect as the text mentions HandlInst but the table of chapter 13 names ExecInst with a new value Best Execution and the FIX 5.0 spec shows value “k” for this. The latter is what FIX 5.0 engines will accept as a standard.
Regards,
Hanno.
Just one more question about this issue. The number assigned to
BestExecution into tag 21, I assume it’s 4, is that right?Regards Abel Monroy
Hello everybody,
We have a question about the changes proposed to FIX specification
for MiFID ( see http://www.fixprotocol.org/pages/3167/Summary%20of%20Chan-
ges%20to%20FIX%20for%20MiFID.htm ). There is a change proposed to
the FIX specification about a new accepted value for tag 21 ( new
enum: Best Execution ). All the documents in
http://www.fixprotocol.org/mifid are related to FIX 5.0, but in a
previous draft this changes were proposed for FIX4.4 (Draft MiFID
Gap Analysis - FIX 4.4 Version 1.6 Dated 10 May 2006). The last
document
(http://www.fixprotocol.org/documents/3180/MiFID_FPL_Gap2.0.pdf) is
for FIX 5.0.Someone knows if this changes are going to be added only in FIX 5.0,
or it will be added in FIX 4.4 as well?Regards Abel Monroy
There are no current plans to change FIX 4.4 or any of the earlier
versions. The changes in the document have been applied to Version
5.0 only