From: Roman Mamedov <rm@romanrm.net>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: Reid Rankin <reidrankin@gmail.com>,
ch@ntrv.dk, WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Standardized IPv6 ULA from PublicKey
Date: Mon, 29 Jun 2020 15:31:18 +0500 [thread overview]
Message-ID: <20200629153118.4d72f447@natsu> (raw)
In-Reply-To: <875zbai32e.fsf@toke.dk>
On Mon, 29 Jun 2020 12:22:49 +0200
Toke Høiland-Jørgensen <toke@toke.dk> wrote:
> Reid Rankin <reidrankin@gmail.com> writes:
>
> > Each IPv6 network device is *required* to have a link-local
> > address by the RFC
>
> Given this
What you quoted is the shakiest statement of the entire proposal. Might be a
cool idea and all, but I don't think RFCs say anything about "requiring" that
for point-to-point L3 interfaces, where there's no functioning multicast or
broadcast to begin with. And it doesn't seem nice that submitter is trying to
skew facts in their favor like that.
--
With respect,
Roman
next prev parent reply other threads:[~2020-06-29 10:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-04 16:52 Lonnie Abelbeck
2017-12-04 17:14 ` Aaron Jones
2017-12-05 2:53 ` Luis Ressel
2017-12-05 3:31 ` Jason A. Donenfeld
2020-06-24 15:37 ` Florian Klink
2020-06-24 17:08 ` Chriztoffer Hansen
2020-06-24 17:30 ` JuniorJPDJ
2020-06-27 21:43 ` Reid Rankin
2020-06-28 10:15 ` Arti Zirk
2020-06-28 15:19 ` Derrick Lyndon Pallas
2020-06-29 10:22 ` Toke Høiland-Jørgensen
2020-06-29 10:31 ` Roman Mamedov [this message]
2020-06-29 10:52 ` Justin Kilpatrick
2020-06-29 11:03 ` Toke Høiland-Jørgensen
2020-06-29 11:38 ` Roman Mamedov
2020-06-29 12:15 ` Toke Høiland-Jørgensen
2020-06-29 17:01 ` Arti Zirk
2020-06-29 18:01 ` Jason A. Donenfeld
2020-06-29 19:58 ` Reid Rankin
2020-06-30 1:24 ` Jason A. Donenfeld
2020-06-30 8:01 ` Reid Rankin
2020-06-29 18:49 ` Luiz Angelo Daros de Luca
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200629153118.4d72f447@natsu \
--to=rm@romanrm.net \
--cc=ch@ntrv.dk \
--cc=reidrankin@gmail.com \
--cc=toke@toke.dk \
--cc=wireguard@lists.zx2c4.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;
as well as URLs for NNTP newsgroup(s).