Imported from previous forum
[ original email was from Bob Lamoureux - blamoureux@bridge.com ]
I have been woefully negligent in my duties as chairperson for this group. There was/is a lot of great interest in this sub-committee and I should not hamper that.
In that spirit, I would like to make a call for specific proposals from the people who are following this thread. The proprosals should roughly follow this outline
I. Proposed Encryption Method
1. Brief Description
2. Origins (i.e. University, company, research)
3. Current Usage
4. FIX protocol impact
5. Platform availability
6. Export Controls/Issues
7. Cost/Licensing Issues
8. Strengths / Weaknesses
9. Administrative Issues
*10.Comparison to current PGP standard
Starting with these, I wil lthen schedule a face-to-face gathering (probably in New York) to talk about these and any other proposals that may surface. Our goal should be to whittle the list down to the top 3 or 4 and work those out in more detail.
Again, sorry for the lapse and I look forward to hearing from you again
[ original email was from Charles Blauner - blauner_c@jpmorgan.com ]
Bob;
Do you have a specific timeframe in mind.
Myself and a number of my peers at the other major
Wall Street firms would like to develop a proposal, but I don’t have a schedule to build
against which I can develop a project plan.
Charles
> I have been woefully negligent in my duties as chairperson for this group. There was/is a lot of great interest in this sub-committee and I should not hamper that.
>
> In that spirit, I would like to make a call for specific proposals from the people who are following this thread. The proprosals should roughly follow this outline
>
> I. Proposed Encryption Method
> 1. Brief Description
> 2. Origins (i.e. University, company, research)
> 3. Current Usage
> 4. FIX protocol impact
> 5. Platform availability
> 6. Export Controls/Issues
> 7. Cost/Licensing Issues
> 8. Strengths / Weaknesses
> 9. Administrative Issues
> *10.Comparison to current PGP standard
>
> Starting with these, I wil lthen schedule a face-to-face gathering (probably in New York) to talk about these and any other proposals that may surface. Our goal should be to whittle the list down to the top 3 or 4 and work those out in more detail.
>
> Again, sorry for the lapse and I look forward to hearing from you again
>
>
[ original email was from Ryan Pierce - rpierce@taltrade.com ]
I’m interested in developing a proposall based around SSLv3 / TLS. I’m wondering if any other firms are interested in this as well, and if it would make sense to work together on it.
My experience is with FIX in C++ under Win32. It would be especially helpful if a firm doing FIX in C/C++ under Unix, and especially a firm doing FIX in Java, would be able to work on this as well, so we can make sure we have the major FIX platforms out their covered.
I’m thinking it may be helpful to actually try wrapping SSL around our existing FIX engines; this way, we can guarantee that we have implementations which work, and can identify potential snags in the proposal.