So what you saying is. You just want to see big roman candles. You know, since you just want to simulate the old military rockets..
On a lighter note, I giggled a little when I saw my UID was lower then yours.
I really, really wonder how people who absolutely refuse to ever learn anything make it past first grade.
No, I don't have the customer tell me, via QOS bits, how to shape and police traffic. That does not mean our $100 billion network is nothing but a dumb cable.
Telling us how to shape traffic is not the customer's job.
ISP networks are not dumb cables. But their also not user data centric either. Unless of course you propose that your super-network is performing SPI on all the user data (which your not, BTW). In a best case scenario, there is port based flow going on.
And here's a little hint. When you say the end user routers don't matter? Their NATing all that traffic you pinhead. Those are the routers that are doing the bulk of the prioritization work.
Oh, and I SO hope you work for Comcast, if anything, to point and laugh when ISP networks go down for hours at a time.
There is one super special kind of person who exists on the internet. This particular one who makes claims however provides absolutely no information to back up his claims. Furthermore, believes that somehow, his own positions are validated by making snide comments validates their own idiocy.
Simply put, ISP's do not, without a special contract in place, shape your traffic. They also do not provide QoS on anything without a special contract, except for THEIR OWN traffic.
https://www.ics.uci.edu/~sjord...
Provide a link to a single ISP that provides QoS service on ingress/egress of their network. Just one major provider.
Oh yea, and ding-dong? You're not going to send all your packets thru the buffer, since it's a DSP thing. Your RTP packets have already gone thru the internet, and been delivered to the buffer, flow or not, you moron. And again, we're not talking abnout how YOU treat your packets IN YOUR OWN NETWORKS, we're talking about how your ISP treats your packets.
Well now, wouldn't, based on your logic, the *carrier* be doing all this work? The entire *point* of this entire conversation is, that the public internet actively provides QoS capabilities on the internet as a whole, and that the carriers automatically perform free prioritization, and this is why VoIP can work on the internet at all.
And obviously *YOUR* router performs flow control. But your carriers DON'T, unless you pay for that feature and are specifically routing between your own endpoints. Do you REALLY think that your home networks are doing active flow control? That Comcast Business connections are respecting your QoS bits on packets ingressing into their network? Your being idiotic. COMCAST DOES NOT SUPPORT QOS OF ANY SORT. As a matter of fact, MOST ISP'S DON'T. And their ALSO not performing flow analysis of your traffic. By all means, show me a single shred of evidence that a top 10 ISP utilizes ANY of the points your talking about.
And if your employer is paying you 3 million a year, their obviously not getting their moneys worth, assuming, we are talking about the general internet here. And point to point tunnels do NOT count here, because THAT'S where the money is to provide that capability, and THAT'S not the internet.
Well, you should REALLY tell the rest of the internet that paying extra to ISPs to have them resepect QoS on ingress/egress routes is wasting their money I suppose. I mean, WHY exactly would people pay SO much extra money for such a thing, right?
As for 'your local router', I challenge you to take a cheapo netgear, and a Ubiquity EdgeRouter, connect it to an xfinity gigabit connection, and go ahead and tell me that your local router doesn't matter.
Oh, and for those small companies who are installing Cisco gear, might as well tell them their all wasting their money, since the router can't matter much, might as well just toss some cheap linksys's at them.
Oh yea, and the #1 method used to reduce the jitter is the use of the playout delay buffer in the case of Cisco gear. Might want to give them a call and let them know, total waste of time, and you can handle all their jitter problems. I'm sure they would LOVE to hear from you.
Yes, however, everything about managing the jittering of VoIP is based on the local and remote routers. The internet backbones themselves aren't doing what your talking about. While everything you've said is true, the special handling is NOT occurring outside of your own routers. Raw bandwidth is.
The major difference between bonds and bond traders is that the bonds will eventually mature.