From: Michael Richardson <mcr@sandelman.ca>
To: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] apparently this is an end goal of a lot of ipv6 work in the ietf
Date: Sat, 04 Jul 2020 20:12:00 -0400 [thread overview]
Message-ID: <5032.1593907920@localhost> (raw)
In-Reply-To: <CAKiAkGQqLYyx4J3yS8eg6PLOz6e1DRgoSWmt=sZGUqEhYeMYCg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 840 bytes --]
Joel Wirāmu Pauling <joel@aenertia.net> wrote:
> I read this as basically Huawei and China led Consumers of Huawei kit.
Yes.
I would not say that it's "IETF".
The IETF, as a group, doesn't believe in very much, sometimes not even running code :-(
> I guess potentially if they can solve v6 fragmentation problems then I
> would be for it, Segment routing, also should have been a thing for a long
> time.
I think that there are some good outcomes to simplifying all forwarding
silicon to doing IPv6, and making everything else be an overlay/adaptation.
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works | IoT architect [
] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on rails [
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
prev parent reply other threads:[~2020-07-05 0:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-02 18:04 Dave Taht
2020-07-02 19:37 ` Sebastian Moeller
2020-07-02 20:01 ` David P. Reed
2020-07-04 21:31 ` Valdis Klētnieks
2020-07-04 22:31 ` Joel Wirāmu Pauling
2020-07-05 0:12 ` 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/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=5032.1593907920@localhost \
--to=mcr@sandelman.ca \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@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