General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Neil Davies <neil.davies@pnsol.com>
To: Matt Taggart <matt@lackof.org>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] splitting the ping
Date: Mon, 1 Mar 2021 18:32:00 +0000	[thread overview]
Message-ID: <B09C5506-DD18-42E3-B61D-4EAC4B070216@pnsol.com> (raw)
In-Reply-To: <a88918c8-6cff-9b43-05fb-fbe3c54e7029@lackof.org>


[-- Attachment #1.1: Type: text/plain, Size: 1084 bytes --]

There is some interesting work from the Broadband Forum on this sort of “spatially aware” measurement… https://www.broadband-forum.org/open-broadband/broadband-experience <https://www.broadband-forum.org/open-broadband/broadband-experience>. Including a webinar this week..

https://www.broadband-forum.org/meetings-and-events/quality-of-experience-real-life-examples-implementations-technical-deep-dive-webinar <https://www.broadband-forum.org/meetings-and-events/quality-of-experience-real-life-examples-implementations-technical-deep-dive-webinar>

Neil
Disclaimer - I helped author some of this...

> On 1 Mar 2021, at 17:47, Matt Taggart <matt@lackof.org> wrote:
> 
> I just read this interesting blog post about measuring both directions of icmp ping latency to detect asymmetric routing issues
> 
> https://blog.benjojo.co.uk/post/ping-with-loss-latency-split
> 
> --
> Matt Taggart
> matt@lackof.org
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat


[-- Attachment #1.2: Type: text/html, Size: 1872 bytes --]

[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2021-03-01 18:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-01 17:47 Matt Taggart
2021-03-01 18:32 ` Neil Davies [this message]

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/bloat.lists.bufferbloat.net/

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

  git send-email \
    --in-reply-to=B09C5506-DD18-42E3-B61D-4EAC4B070216@pnsol.com \
    --to=neil.davies@pnsol.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=matt@lackof.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