From: Jakub Kicinski <kuba@kernel.org>
To: Yonglong Li <liyonglong@chinatelecom.cn>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
davem@davemloft.net, dsahern@kernel.org, edumazet@google.com
Subject: Re: [PATCH] seg6: inherit inner IPv4 TTL on ip4ip6 encapsulation
Date: Mon, 20 Jan 2025 14:51:44 -0800 [thread overview]
Message-ID: <20250120145144.3e072efe@kernel.org> (raw)
In-Reply-To: <1736995236-23063-1-git-send-email-liyonglong@chinatelecom.cn>
On Thu, 16 Jan 2025 10:40:36 +0800 Yonglong Li wrote:
> inherit inner IPv4 TTL on ip4ip6 SHR encapsulation like as inherit
> inner hop_limit on ip6ip6 SHR encapsulation
Could you add some references to RFCs which recommend this behavior
to the commit message?
--
pw-bot: cr
next prev parent reply other threads:[~2025-01-20 22:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-16 2:40 [PATCH] seg6: inherit inner IPv4 TTL on ip4ip6 encapsulation Yonglong Li
2025-01-20 22:51 ` Jakub Kicinski [this message]
[not found] ` <CAAvhMUmdse_8GJtn_dD0psRmSA_BCy-fv6eYj9CorpaeVm-H3g@mail.gmail.com>
2025-01-22 16:13 ` David Ahern
2025-01-23 15:48 ` Jakub Kicinski
2025-02-05 7:25 ` YonglongLi
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=20250120145144.3e072efe@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liyonglong@chinatelecom.cn \
--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).