Many ISPs need the kinds of quality shaping cake can do
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: libreqos <libreqos@lists.bufferbloat.net>
Subject: [LibreQoS] Fwd: Survey on Internet Traffic Engineering practices.
Date: Mon, 9 Sep 2024 11:20:17 -0700	[thread overview]
Message-ID: <CAA93jw7gddkyKhTS5QrSusxdvs7okNOHfk8waN4OQzt5qzmK0A@mail.gmail.com> (raw)
In-Reply-To: <CAGYia1wtmL3_vvAtTXnxgsXYG-ieB_ih+cM_Fg5o7JvuLUYX0A@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1544 bytes --]

---------- Forwarded message ---------
From: Kévin Vermeulen <kevinmylinhvermeulen@gmail.com>
Date: Mon, Sep 9, 2024 at 10:39 AM
Subject: Survey on Internet Traffic Engineering practices.
To: <nanog@nanog.org>
Cc: cristel <cristel@pelsser.eu>, Omar Darwich <omar.darwich@laas.fr>, <
kevin.vermeulen@laas.fr>


Hey Nanog,

We are a group of researchers from LAAS-CNRS and UCLouvain. We are
currently conducting a research study on inter-domain traffic engineering
practices and their impact on the internet.
We are reaching out to network operators to gather insights on practical
implementations of inter-domain traffic engineering. Specifically, we are
interested in understanding the timeframes and prefixes involved in traffic
engineering efforts. If you have conducted inter-domain traffic
engineering, could you kindly provide information about your traffic
engineering practices. You can do so via our survey form
https://forms.gle/2B6hW5Rs98rjiLLN7.
Your participation would greatly contribute to our understanding of current
practices and trends in network traffic engineering. We assure you that any
information shared will be treated with strict confidentiality and used
solely for research purposes. Any findings that will be published will be
anonymized.

For any questions please let us know.

Best regards,

Omar Darwich, Kevin Vermeulen, Cristel Pelsser


-- 
Artists/Musician Campout Aug 9-11
https://www.eventbrite.com/e/healing-arts-event-tickets-928910826287
Dave Täht CSO, LibreQos

[-- Attachment #2: Type: text/html, Size: 2429 bytes --]

           reply	other threads:[~2024-09-09 18:20 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <CAGYia1wtmL3_vvAtTXnxgsXYG-ieB_ih+cM_Fg5o7JvuLUYX0A@mail.gmail.com>]

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

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

  git send-email \
    --in-reply-to=CAA93jw7gddkyKhTS5QrSusxdvs7okNOHfk8waN4OQzt5qzmK0A@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=libreqos@lists.bufferbloat.net \
    /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