Re: [Cerowrt-devel] [aqm] ping loss "considered harmful"

2015-03-02 Thread Mikael Abrahamsson
On Mon, 2 Mar 2015, Brian Trammell wrote: Gaming protocols do this right - latency measurement is built into the protocol. I believe this is the only way to do it properly, and the most likely easiest way to get this deployed would be to use the TCP stack. We need to give users an easy-to-u

Re: [Cerowrt-devel] [Bloat] [aqm] ping loss "considered harmful"

2015-03-02 Thread Jonathan Morton
> On 2 Mar, 2015, at 12:17, Mikael Abrahamsson wrote: > > On Mon, 2 Mar 2015, Brian Trammell wrote: > >> Gaming protocols do this right - latency measurement is built into the >> protocol. > > I believe this is the only way to do it properly, and the most likely easiest > way to get this dep

Re: [Cerowrt-devel] Bufferbloat and the policy debate on packet loss in nanog

2015-03-02 Thread dpreed
bravo! On Sunday, March 1, 2015 6:22pm, "Dave Taht" said: > There's nothing new here, but it was a nice rant to get out of my system: > > http://permalink.gmane.org/gmane.org.operators.nanog/128201 > > Of late, I have been taking a page from Linus Torvalds' playbook, in > realizing that "on

Re: [Cerowrt-devel] [Bloat] [aqm] ping loss "considered harmful"

2015-03-02 Thread dpreed
On my own web server (running nginx) I provide an HTTP 1.1 accessible statistics service. It returns a single JSON structure with the underlying packet statistics for the server and the current connection. Since this packet is inserted into the HTTP 1.1 stream upon request, it provides both the

Re: [Cerowrt-devel] [aqm] ping loss "considered harmful"

2015-03-02 Thread Brian Trammell
hi Dave, > On 02 Mar 2015, at 04:57, Dave Taht wrote: > > On this thread over here, an otherwise pretty clueful user chose > openwrt's qos-scripts over the sqm-scripts, because sqm-scripts had > *higher ping loss*. I am not proud of the fact that I am not surprised by this. > How can we fix th

Re: [Cerowrt-devel] [aqm] ping loss "considered harmful"

2015-03-02 Thread Dave Dolson
I'm rather new to the aqm community, but IMHO, it is wrong to deprioritize the ping traffic by default. I would not have expected a forwarding agent to do this. And I think measuring ping times and loss is a reasonable thing to do, never expecting forwarding agents along the path to place more

Re: [Cerowrt-devel] [Bloat] [aqm] ping loss "considered harmful"

2015-03-02 Thread Brian Trammell
> On 02 Mar 2015, at 11:54, Jonathan Morton wrote: > > >> On 2 Mar, 2015, at 12:17, Mikael Abrahamsson wrote: >> >> On Mon, 2 Mar 2015, Brian Trammell wrote: >> >>> Gaming protocols do this right - latency measurement is built into the >>> protocol. >> >> I believe this is the only way to

Re: [Cerowrt-devel] [aqm] ping loss "considered harmful"

2015-03-02 Thread David Lang
On Mon, 2 Mar 2015, Andrew Mcgregor wrote: So, are you suggesting that, for example, Chrome's rather extensive network debugging information get more publicised? We can probably arrange that. That would be good. I have no idea what debugging info you are referring to. David Lang_

Re: [Cerowrt-devel] [Bloat] [aqm] ping loss "considered harmful"

2015-03-02 Thread David Lang
On Mon, 2 Mar 2015 15:45:10 +0100, Brian Trammell wrote: On 02 Mar 2015, at 11:54, Jonathan Morton wrote: On 2 Mar, 2015, at 12:17, Mikael Abrahamsson wrote: On Mon, 2 Mar 2015, Brian Trammell wrote: Gaming protocols do this right - latency measurement is built into the protocol. I be

Re: [Cerowrt-devel] Fwd: [homenet] Routing protocol comparison document

2015-03-02 Thread Toke Høiland-Jørgensen
Dave Taht writes: > Any objections here? Yes! I certainly wouldn't want to run that. > Suggestions for how to make one of the ipv6 translation techniques > work right? Turn them off? ;) -Toke ___ Cerowrt-devel mailing list Cerowrt-devel@lists.buffer

Re: [Cerowrt-devel] Fwd: [homenet] Routing protocol comparison document

2015-03-02 Thread Aaron Wood
I would definitely be interested in being involved with how to secure and firewall, but still provide access to, internal IPv6 hosts. Ie, the internet the way it's supposed to work (peer to peer), but with the security that we've inadvertently picked up along the way by using NAT everywhere for th

Re: [Cerowrt-devel] [aqm] ping loss "considered harmful"

2015-03-02 Thread Dave Dolson
Would you do that to TCP or UDP traffic? At IETF I often hear laments about middle-boxes breaking the internet by being "clever" with certain types of traffic. It seems that policing ICMP falls into that category. There may have been bugs in the past, but I'm not aware that ICMP packets are any

Re: [Cerowrt-devel] [aqm] ping loss "considered harmful"

2015-03-02 Thread Dave Taht
On Mon, Mar 2, 2015 at 12:06 PM, Wes Felter wrote: > What about a token bucket policer, so more than N ICMP/second gets penalized > but a normal ping won't be. If I haven't expressed this too many times before, I want to thank you all for existing. It is the quality and caliber of all the folk o

Re: [Cerowrt-devel] [aqm] ping loss "considered harmful"

2015-03-02 Thread David Lang
On Mon, 2 Mar 2015, Dave Dolson wrote: Would you do that to TCP or UDP traffic? At IETF I often hear laments about middle-boxes breaking the internet by being "clever" with certain types of traffic. It seems that policing ICMP falls into that category. There may have been bugs in the past, bu

Re: [Cerowrt-devel] Fwd: [homenet] Routing protocol comparison document

2015-03-02 Thread Dave Taht
On Mon, Mar 2, 2015 at 12:26 PM, Toke Høiland-Jørgensen wrote: > Dave Taht writes: > >> Any objections here? > > Yes! I certainly wouldn't want to run that. Not a problem. You are fortunate enough to have stable ipv6 addresses where you are - and me, I have to go bat-s**t crazy everytime I get r

Re: [Cerowrt-devel] [aqm] ping loss "considered harmful"

2015-03-02 Thread David Lang
On Mon, 2 Mar 2015, Joe Touch wrote: On 3/2/2015 1:40 AM, Brian Trammell wrote: ... The real solution is to create a utility called "ping" that uses traffic that gets prioritized the same way as the traffic you care about instead of ICMP echo request/reply. Users don't care about the packets on

Re: [Cerowrt-devel] [aqm] ping loss "considered harmful"

2015-03-02 Thread David Lang
On Mon, 2 Mar 2015, Joe Touch wrote: On 3/2/2015 3:14 PM, David Lang wrote: On Mon, 2 Mar 2015, Joe Touch wrote: On 3/2/2015 1:40 AM, Brian Trammell wrote: ... The real solution is to create a utility called "ping" that uses traffic that gets prioritized the same way as the traffic you care

Re: [Cerowrt-devel] [aqm] ping loss "considered harmful"

2015-03-02 Thread Andrew Mcgregor
Maybe I should mention https://github.com/apenwarr/blip HTTP ping, using deliberate 204 responses. Will run over whatever version of HTTP/SPDY/QUIC your browser happens to be using at the time. On 3 March 2015 at 10:34, David Lang wrote: > On Mon, 2 Mar 2015, Joe Touch wrote: > > On 3/2/2015

Re: [Cerowrt-devel] [aqm] ping loss "considered harmful"

2015-03-02 Thread Joe Touch
On 3/2/2015 1:40 AM, Brian Trammell wrote: ... > The real solution is to create a utility called "ping" that uses > traffic that gets prioritized the same way as the traffic you care > about instead of ICMP echo request/reply. Users don't care about > the packets on the wire so much as they do t

Re: [Cerowrt-devel] [aqm] ping loss "considered harmful"

2015-03-02 Thread Joe Touch
On 3/2/2015 3:14 PM, David Lang wrote: > On Mon, 2 Mar 2015, Joe Touch wrote: > >> On 3/2/2015 1:40 AM, Brian Trammell wrote: >> ... >>> The real solution is to create a utility called "ping" that uses >>> traffic that gets prioritized the same way as the traffic you care >>> about instead of IC

Re: [Cerowrt-devel] [aqm] ping loss "considered harmful"

2015-03-02 Thread Valdis . Kletnieks
On Mon, 02 Mar 2015 11:17:33 +0100, Mikael Abrahamsson said: > We have a huge amount of information in our TCP stacks that either are > locked in there and not used properly to help users figure out what's > going on, and there is basically zero information flow between the > applications using TC