From: Ben Hutchings <ben@decadent.org.uk>
To: Thorsten Glaser <t.glaser@tarent.de>, 966459@bugs.debian.org
Cc: netdev <netdev@vger.kernel.org>
Subject: Re: Bug#966459: linux: traffic class socket options (both IPv4/IPv6) inconsistent with docs/standards
Date: Mon, 03 Aug 2020 04:32:36 +0100 [thread overview]
Message-ID: <db7d2f4dde6db2af82c880756d76af1b7c1e41e8.camel@decadent.org.uk> (raw)
In-Reply-To: <alpine.DEB.2.23.453.2008022243310.15898@tglase-nb.lan.tarent.de>
[-- Attachment #1: Type: text/plain, Size: 663 bytes --]
On Sun, 2020-08-02 at 22:44 +0200, Thorsten Glaser wrote:
> On Sun, 2 Aug 2020, Ben Hutchings wrote:
>
> > The RFC says that the IPV6_TCLASS option's value is an int, and that
>
> for setsockopt (“option's”), not cmsg
>
> > No, the wording is *not* clear.
>
> Agreed.
>
> So perhaps let’s try to find out what’s actually right…
For what it's worth, FreeBSD/Darwin and Windows also put 4 bytes of
data in a IPV6_TCLASS cmsg. So whether or not it's "right", it's
consistent between three independent implementations.
Ben.
--
Ben Hutchings
For every complex problem
there is a solution that is simple, neat, and wrong.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-08-03 3:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <159596111771.2639.6929056987566441726.reportbug@tglase-nb.lan.tarent.de>
2020-08-02 17:49 ` Bug#966459: linux: traffic class socket options (both IPv4/IPv6) inconsistent with docs/standards Ben Hutchings
2020-08-02 19:29 ` Thorsten Glaser
2020-08-02 20:29 ` Ben Hutchings
2020-08-02 20:44 ` Thorsten Glaser
2020-08-03 3:32 ` Ben Hutchings [this message]
2020-08-03 16:58 ` Thorsten Glaser
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=db7d2f4dde6db2af82c880756d76af1b7c1e41e8.camel@decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=966459@bugs.debian.org \
--cc=netdev@vger.kernel.org \
--cc=t.glaser@tarent.de \
/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).