4 edits | reply to Ignite
Re: Ellacoya Simply a CMTS will have more backbone connectivity than HFC side connectivity, this is just the way it is. Yes, that;s true. Backbone connections are usually in units of 100M or 1G and it is not related to the HFC interface (line card) performance. Though on high density CMTS the goal and system requirements is to stand in wirespeed for smallest possible packet. not many do it but with time they improve. Shaw is going to provide VoIP services, right ? 100% availability, no packet loss, etc. etc. If Ellacoya is their only solution it IS scary.
I have to admit that ISPs do have every right to either increase prices so that they can cope with the P2P traffic that consumes 60 - 70% of their bandwidth and remain profitable, or to manage this traffic level down. Fair enough, but do not tell that you provide better service than DSL at lower price. Inform your clients in timely manner that you are going to install additional equipment enforcing network policy. It is bad PR, but who promised to Shaw shareholders that the life is going to be picnic ?
The TCP keepalives you are discussing assume that the Ellacoya switches hold connection states for a considerable time. This probably isn't the case, I'd expect the session purging period for the device to be a matter of a few seconds rather than 30 or more, it's more efficient on its' memory to hold states briefly and makes the device more resilient to any DoS attack going through it. If they keep connections briefly it's worse for them, because establishing of the connection is more costly than just checking the packet against existing connection.
Your project is an interesting one, will be intriguing to see if it comes to fruition One of the important parts of protocol is the message structure. The idea is taken from telecom protocols with main goal to make packets as small as possible and define information elements in a way that the packets can be easily handled in hardware. For example, very simple FPGA can distinguish between LOOK and DATA request and make forwarding decision accordingly. There are many things i already thought about and many things to think remain, but overall this approach to the problem of data delivery is the right one. if not me, than somebody else eventually will do it and content providers will get the protection they deserve.
Have you worked for a service provider? No. I am a developer and most of my experience in telecom, not datacom. I met with technicians and provided field support for different devices. But it was occasional and not mainstream. |
