From: Simon Horman <horms@kernel.org>
To: Justin Iurman <justin.iurman@uliege.be>
Cc: netdev@vger.kernel.org, davem@davemloft.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] uapi: in6: replace temporary label with rfc9486
Date: Tue, 27 Feb 2024 17:37:27 +0000 [thread overview]
Message-ID: <20240227173727.GI277116@kernel.org> (raw)
In-Reply-To: <20240226124921.9097-1-justin.iurman@uliege.be>
On Mon, Feb 26, 2024 at 01:49:21PM +0100, Justin Iurman wrote:
> Not really a fix per se, but IPV6_TLV_IOAM is still tagged as "TEMPORARY
> IANA allocation for IOAM", while RFC 9486 is available for some time
> now. Just update the reference.
>
> Fixes: 9ee11f0fff20 ("ipv6: ioam: Data plane support for Pre-allocated Trace")
> Signed-off-by: Justin Iurman <justin.iurman@uliege.be>
I'm unsure if this is a fix.
But I checked and I agree that 49 (0x31) is
documented as a type for IOM TLVs in Section 6 of RFC 9486.
Reviewed-by: Simon Horman <horms@kernel.org>
next prev parent reply other threads:[~2024-02-27 17:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-26 12:49 [PATCH net] uapi: in6: replace temporary label with rfc9486 Justin Iurman
2024-02-27 17:37 ` Simon Horman [this message]
2024-02-28 3:20 ` patchwork-bot+netdevbpf
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=20240227173727.GI277116@kernel.org \
--to=horms@kernel.org \
--cc=davem@davemloft.net \
--cc=justin.iurman@uliege.be \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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).