From: Wesley Eddy <wes@mti-systems.com>
To: "Fred Baker (fred)" <fred@cisco.com>, 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] [Bloat] [aqm] ping loss "considered harmful"
Date: Tue, 03 Mar 2015 12:29:31 -0500 [thread overview]
Message-ID: <54F5EF7B.4000006@mti-systems.com> (raw)
In-Reply-To: <F2745259-5DEB-49B1-AB7C-C8E4E1217360@cisco.com>
On 3/3/2015 12:20 PM, Fred Baker (fred) wrote:
>
>> On Mar 1, 2015, at 7:57 PM, Dave Taht <dave.taht@gmail.com
>> <mailto:dave.taht@gmail.com>> wrote:
>>
>> How can we fix this user perception, short of re-prioritizing ping in
>> sqm-scripts?
>
> IMHO, ping should go at the same priority as general traffic - the
> default class, DSCP=0. When I send one, I am asking whether a random
> packet can get to a given address and get a response back. I can imagine
> having a command-line parameter to set the DSCP to another value of my
> choosing.
>
I generally agree, however ...
The DSCP of the response isn't controllable though, and likely the DSCP
that is ultimately received will not be the one that was sent, so it
can't be as simple as echoing back the same one. Ping doesn't tell you
latency components in the forward or return path (some other protocols
can do this though).
So, setting the DSCP on the outgoing request may not be all that useful,
depending on what the measurement is really for.
--
Wes Eddy
MTI Systems
next prev parent reply other threads:[~2015-03-03 17:29 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
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 ` Wesley Eddy [this message]
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=54F5EF7B.4000006@mti-systems.com \
--to=wes@mti-systems.com \
--cc=aqm@ietf.org \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=fred@cisco.com \
/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