[paolfili]

The ubiquitous *DSL is nowadays the standard.
Huge data flows (10Mbps) are well beyond the acceptable managing limit of the retail traders,as we are.
(also in term of usability).
"Packet loss" in the Network Communication Literature (and in the Network community) has another meaning.

Originally Posted by SNYP40A1 »

As I said before:



If your computer / connection cannot keep up with the real time packet stream, there will be packet loss. Example, try receiving a 10 Mbps real-time stream on a 14.4 kbps dial-up connection. TCP can't perform magic.

[BlowFish]

Originally Posted by paolfili »

What about syn-flood like,Initial Sequence Number attack like ,etc in a your custom IP protocol?
Moreover the hardware (router/bridge) and software(kernel driver) are nowadays very tight to standardized protocols.
(Why reinventing the wheel?)

SYN is a TCP session parameter. If you are not using TCP you will be immune to a SYN Flood (as you are not using TCP you will not reply to SYN requests). By not using TCP you will be immune to attacks that rely on TCP protocols.

To route you need IP and that's it. Nowadays of course routers do all sorts of higher level 'stateful' stuff and look deep into packets to do higher level 'clever' things. (Like traffic shaping and prioritisation for example). None of that information is needed to route.

Why re-invent the wheel? I am certainly not advocating that, it would not make sense for a lot of people. However if you do not require all the bells and whistles provided by TCP (a generic protocol after all) but do require some simple transport control and session management then it might make sense.

Still this goes way beyond the discussion here.

[SNYP40A1]

Originally Posted by paolfili »

The ubiquitous *DSL is nowadays the standard.
Huge data flows (10Mbps) are well beyond the acceptable managing limit of the retail traders,as we are.
(also in term of usability).
"Packet loss" in the Network Communication Literature (and in the Network community) has another meaning.

It was a general example and my point is obvious. If your connection cannot keep up with the stream, packets will be lost.

[SNYP40A1]

Anyone know if Zenfire or Rithmic has made any statement about this?

[paolfili]

Zen.
Yes.No result.
We are probably the 1/1000 of the ZenFire customer interested in correct sybc between trade and best_bid/best_ask.

Originally Posted by SNYP40A1 »

Anyone know if Zenfire or Rithmic has made any statement about this?

[SNYP40A1]

I e-mailed two people at Zen-Fire and have not received comment. They both have responded to my queries before. I suspect that they are not saying anything until they have either determined the cause of the issue and/or the fix. I could be wrong, but their silence tells me that they know about the issue and are still working out the solution.

[paolfili]

How can you syncronize any liable protocol over IP?
Authentication,identifica tion,frame reconstruction,etc....
A lot of RFCs (the base of Internet network) explain the pros and also the cons
of the TCP (and of a lot of other protocols over IP).
Happy to hear about a new Blowfish/IP protocol mentioned as an RFC.

Originally Posted by BlowFish »

SYN is a TCP session parameter. If you are not using TCP you will be immune to a SYN Flood (as you are not using TCP you will not reply to SYN requests). By not using TCP you will be immune to attacks that rely on TCP protocols.

To route you need IP and that's it. Nowadays of course routers do all sorts of higher level 'stateful' stuff and look deep into packets to do higher level 'clever' things. (Like traffic shaping and prioritisation for example). None of that information is needed to route.

Why re-invent the wheel? I am certainly not advocating that, it would not make sense for a lot of people. However if you do not require all the bells and whistles provided by TCP (a generic protocol after all) but do require some simple transport control and session management then it might make sense.

Still this goes way beyond the discussion here.

[BlowFish]

Originally Posted by paolfili »

How can you syncronize any liable protocol over IP?
Authentication,identifica tion,frame reconstruction,etc....
A lot of RFCs (the base of Internet network) explain the pros and also the cons
of the TCP (and of a lot of other protocols over IP).
Happy to hear about a new Blowfish/IP protocol mentioned as an RFC.

You write the code yourself within your application. It's not hard if you know what you are doing.