From: Dave Taht <dave.taht@gmail.com>
To: Herbert Wolverson <herberticus@gmail.com>
Cc: libreqos@lists.bufferbloat.net
Subject: Re: [LibreQoS] how are you doing on ipv4 address supply?
Date: Wed, 26 Oct 2022 12:58:48 -0700 [thread overview]
Message-ID: <CAA93jw43+d4An418Gi10WEDhLgkvZ-h2fC1xK9iQ2+Z7NSinpg@mail.gmail.com> (raw)
In-Reply-To: <CA+erpM4ROP-8QAnNg-Ad1uLGdbGOm2W5UwLc6DyKA3Xuxcdt9Q@mail.gmail.com>
In my case, I'd like to go all-in on ipv6 again. It's been 14 years
since I last tried.
There's an earlier RFC for this concept for ospf I think, and an open
bug with mikrottik on that...
https://datatracker.ietf.org/doc/rfc9229/
next prev parent reply other threads:[~2022-10-26 19:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-26 3:30 Dave Taht
2022-10-26 15:33 ` dan
2022-10-26 16:05 ` Herbert Wolverson
2022-10-26 16:48 ` dan
2022-10-26 19:15 ` Robert Chacón
2022-10-26 19:32 ` Herbert Wolverson
2022-10-26 19:39 ` Robert Chacón
2022-10-26 19:58 ` Dave Taht [this message]
2022-10-26 20:18 ` Dave Taht
2022-10-26 20:52 ` Toke Høiland-Jørgensen
2022-10-26 22:38 ` dan
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=CAA93jw43+d4An418Gi10WEDhLgkvZ-h2fC1xK9iQ2+Z7NSinpg@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=herberticus@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