From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] [PATCH] ipv6 flow label support
Date: Sat, 25 Nov 2023 21:46:09 +0100 [thread overview]
Message-ID: <AC9687511792744096FE36FA9EA29735@felloff.net> (raw)
In-Reply-To: <1375031432.2686734.1700936861177@comcenter.netcologne.de>
hey man,
this looks pretty wild and i cant wrap my head around
why the hell would the *SENDER* put the hash instead
of the receiveriver calculating it...
currently, the user can set the tos field for its
connection using a ctl message... that should
go into the flow label field so its up to the user
making the connection.
is here any RFC suggesting the flowlabel should be
a hash that could easilly be calculated by the
receiver on the existing ip header fields?
i really need more context to convince me that this
is the right thing todo.
a rfc would do.
--
cinap
next prev parent reply other threads:[~2023-11-25 20:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-25 18:27 Arne Meyer
2023-11-25 20:46 ` cinap_lenrek [this message]
2023-11-25 20:51 ` cinap_lenrek
2023-11-25 21:03 ` Arne Meyer
2023-11-25 21:05 ` cinap_lenrek
2023-11-25 21:49 ` Arne Meyer
2023-11-26 13:28 ` cinap_lenrek
2023-11-27 19:17 ` Arne Meyer
2023-11-26 16:51 ` ori
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=AC9687511792744096FE36FA9EA29735@felloff.net \
--to=cinap_lenrek@felloff.net \
--cc=9front@9front.org \
/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).