General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Michael Richardson <mcr@sandelman.ca>
To: Dave Taht <dave.taht@gmail.com>, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Fwd: REGISTRATION NOW OPEN - Broadband Forum's BASe & USP Summit 2024
Date: Tue, 09 Jan 2024 10:24:07 -0500	[thread overview]
Message-ID: <16524.1704813847@obiwan.sandelman.ca> (raw)
In-Reply-To: <CAA93jw6nMboL4qFFAkiSV36vdQ0u-Qo--T667PtCaC_pNU6Fzw@mail.gmail.com>

Dave Taht via Bloat <bloat@lists.bufferbloat.net> wrote:
    > I have prior to now, ignored this conference because it was not
    > particularly technical. Does anyone go?

I don't know what it's like.
I read some of the USP agenda and I'm interested in a "if I'm nearby" level a
few months ago.

      reply	other threads:[~2024-01-09 15:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1141078415537.1125065769993.1003772341.0.300901JL.2002@synd.ccsend.com>
2024-01-09 14:14 ` Dave Taht
2024-01-09 15:24   ` Michael Richardson [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=16524.1704813847@obiwan.sandelman.ca \
    --to=mcr@sandelman.ca \
    --cc=bloat@lists.bufferbloat.net \
    --cc=dave.taht@gmail.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