From: Fernando Fernandez Mancera <fmancera@suse.de>
To: Eric Dumazet <edumazet@google.com>
Cc: Simon Horman <horms@kernel.org>,
Fernando Gont <fgont@si6networks.com>,
netdev@vger.kernel.org, pabeni@redhat.com, kuba@kernel.org,
davem@davemloft.net
Subject: Re: [PATCH net] ipv6: addrconf: reduce default temp_valid_lft to 2 days
Date: Sat, 14 Feb 2026 14:43:10 +0100 [thread overview]
Message-ID: <4398e57a-343b-431c-a5cc-0aae65676023@suse.de> (raw)
In-Reply-To: <CANn89i+fNkeMJbNBJjqv15Rih1tUdC8ZwGqxjMZaxovcSt=hgQ@mail.gmail.com>
On 2/14/26 2:37 PM, Eric Dumazet wrote:
> On Sat, Feb 14, 2026 at 2:28 PM Fernando Fernandez Mancera
> <fmancera@suse.de> wrote:
>
>> I noticed the patch is marked as "Changes Requested", is there some
>> action pending from me?
>
> Quite confusing. The blamed commit mentioned RFC 4941
>
> commit 969c54646af0d7d94a5f0f37adbbfe024e85466e
> Author: Fernando Gont <fgont@si6networks.com>
> Date: Fri May 1 00:51:47 2020 -0300
>
> ipv6: Implement draft-ietf-6man-rfc4941bis
>
> So please add a comment like this one ?
>
> /* TEMP_VALID_LIFETIME default value as specified in RFC 8981 3.8 */
>
Sure, I will. FWIW, the blamed commit mentioned the draft revision for
RFC 4941, but at that time, being a draft, it did not have an
appropriate RFC number assigned to it.
Thanks Eric.
next prev parent reply other threads:[~2026-02-14 13:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-11 20:20 [PATCH net] ipv6: addrconf: reduce default temp_valid_lft to 2 days Fernando Fernandez Mancera
2026-02-13 14:00 ` Simon Horman
2026-02-13 14:34 ` Eric Dumazet
2026-02-13 14:44 ` Fernando Fernandez Mancera
2026-02-14 13:27 ` Fernando Fernandez Mancera
2026-02-14 13:37 ` Eric Dumazet
2026-02-14 13:43 ` Fernando Fernandez Mancera [this message]
2026-02-15 9:16 ` Fernando Gont
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=4398e57a-343b-431c-a5cc-0aae65676023@suse.de \
--to=fmancera@suse.de \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fgont@si6networks.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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