Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Dolson <ddolson@sandvine.com>
To: Wes Felter <wmf@felter.org>, "aqm@ietf.org" <aqm@ietf.org>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>,
	"bloat@lists.bufferbloat.net" <bloat@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [aqm] ping loss "considered harmful"
Date: Mon, 2 Mar 2015 20:33:56 +0000	[thread overview]
Message-ID: <E8355113905631478EFF04F5AA706E9830B5923E@wtl-exchp-2.sandvine.com> (raw)
In-Reply-To: <md2fsa$o1s$1@ger.gmane.org>

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 more dangerous than UDP or TCP. And if the RFCs can be believed, ICMPv6 is critical to determining Path-MTU. Don't drop those.

One may wish to rate-limit ICMP (or DNS or TCP) flows as a matter of network policy, but in my opinion this should be kept orthogonal to solving buffer bloat.

Taken to the extreme, a network should support full utilization of a link doing only ping. If I wish to use my connection to the internet to ping hosts at full line rate, why not?


David Dolson
Senior Software Architect, Sandvine Inc.



-----Original Message-----
From: aqm [mailto:aqm-bounces@ietf.org] On Behalf Of Wes Felter
Sent: Monday, March 02, 2015 3:07 PM
To: aqm@ietf.org
Cc: cerowrt-devel@lists.bufferbloat.net; bloat@lists.bufferbloat.net
Subject: Re: [aqm] ping loss "considered harmful"

What about a token bucket policer, so more than N ICMP/second gets 
penalized but a normal ping won't be.

-- 
Wes Felter


_______________________________________________
aqm mailing list
aqm@ietf.org
https://www.ietf.org/mailman/listinfo/aqm

  parent reply	other threads:[~2015-03-02 20:33 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-02  3:57 [Cerowrt-devel] " Dave Taht
2015-03-02  4:00 ` [Cerowrt-devel] [aqm] " Andrew Mcgregor
2015-03-02  4:05 ` Mikael Abrahamsson
2015-03-02  4:06 ` [Cerowrt-devel] " David Lang
2015-03-02  9:40 ` [Cerowrt-devel] [aqm] " Brian Trammell
2015-03-02 10:17   ` Mikael Abrahamsson
2015-03-02 10:54     ` [Cerowrt-devel] [Bloat] " Jonathan Morton
2015-03-02 12:44       ` dpreed
2015-03-02 14:45       ` Brian Trammell
2015-03-02 18:41         ` David Lang
2015-03-03  6:45     ` [Cerowrt-devel] " Valdis.Kletnieks
2015-03-04  8:14       ` Mikael Abrahamsson
2015-03-02 21:53   ` Joe Touch
2015-03-02 23:14     ` David Lang
2015-03-02 23:25       ` Joe Touch
2015-03-02 23:34         ` David Lang
2015-03-03  0:07           ` Andrew Mcgregor
2015-03-02 10:47 ` Dave Dolson
2015-03-02 10:49   ` Andrew Mcgregor
2015-03-02 18:36     ` David Lang
     [not found] ` <md2fsa$o1s$1@ger.gmane.org>
2015-03-02 20:33   ` Dave Dolson [this message]
2015-03-02 20:39     ` David Lang
2015-03-02 20:38   ` Dave Taht
2015-03-04  8:12     ` Mikael Abrahamsson
2015-03-03 17:20 ` Fred Baker (fred)
2015-03-03 17:29   ` [Cerowrt-devel] [Bloat] " Wesley Eddy
2015-03-03 18:00     ` [Cerowrt-devel] [aqm] [Bloat] " Fred Baker (fred)
2015-03-04  5:24       ` Dave Taht
2015-03-05 18:56         ` Curtis Villamizar
2015-03-05 19:50           ` [Cerowrt-devel] [Bloat] [aqm] " Rich Brown
2015-03-04 17:34       ` [Cerowrt-devel] [aqm] [Bloat] " dpreed
2015-03-04 19:45         ` Mikael Abrahamsson
2015-03-05 20:38 ` [Cerowrt-devel] " Matt Taggart
2015-03-05 20:53   ` Dave Taht

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E8355113905631478EFF04F5AA706E9830B5923E@wtl-exchp-2.sandvine.com \
    --to=ddolson@sandvine.com \
    --cc=aqm@ietf.org \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=wmf@felter.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox