Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Joe Touch <touch@isi.edu>
To: Brian Trammell <ietf@trammell.ch>, Dave Taht <dave.taht@gmail.com>
Cc: "aqm@ietf.org" <aqm@ietf.org>,
	"cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>,
	bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [aqm] ping loss "considered harmful"
Date: Mon, 02 Mar 2015 13:53:13 -0800	[thread overview]
Message-ID: <54F4DBC9.1010700@isi.edu> (raw)
In-Reply-To: <7B3E53F5-2112-4A50-A777-B76F928CE8F2@trammell.ch>



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 that you're supposed to
> ping things.

There are three separate problems:

1. a ping that doesn't use ICMP
	there are dozens of these

2. needing a reflector
	ping gets around this only because the reflector is widely
	deployed (and integrated into most OSes)

3. using the same port as the traffic you care about
	transport protocol is only one problem (ICMP being a "transport
	protocol" by virtue of using the IP protocol number field)

	the other is differential prioritization based on port number

	there's no easy solution to that;
	every service would need an integrated
	ping reflector

I suspect #3 is the ultimate killer of this idea.

Joe

  parent reply	other threads:[~2015-03-02 21:53 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 [this message]
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
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=54F4DBC9.1010700@isi.edu \
    --to=touch@isi.edu \
    --cc=aqm@ietf.org \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --cc=ietf@trammell.ch \
    /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