From: Neal Cardwell <ncardwell@google.com>
To: Eric Dumazet <edumazet@google.com>
Cc: "David S . Miller" <davem@davemloft.net>,
netdev <netdev@vger.kernel.org>,
Eric Dumazet <eric.dumazet@gmail.com>,
Yuchung Cheng <ycheng@google.com>
Subject: Re: [PATCH net-next] tcp: ipv6: support RFC 6069 (TCP-LD)
Date: Wed, 27 May 2020 21:19:05 -0400 [thread overview]
Message-ID: <CADVnQy=2JrtKf-AO8pMn4QFSDQJP4Vm0anBCNx6WggRPd7OA=Q@mail.gmail.com> (raw)
In-Reply-To: <20200528003458.90435-1-edumazet@google.com>
On Wed, May 27, 2020 at 8:35 PM Eric Dumazet <edumazet@google.com> wrote:
>
> Make tcp_ld_RTO_revert() helper available to IPv6, and
> implement RFC 6069 :
>
> Quoting this RFC :
>
> 3. Connectivity Disruption Indication
>
> For Internet Protocol version 6 (IPv6) [RFC2460], the counterpart of
> the ICMP destination unreachable message of code 0 (net unreachable)
> and of code 1 (host unreachable) is the ICMPv6 destination
> unreachable message of code 0 (no route to destination) [RFC4443].
> As with IPv4, a router should generate an ICMPv6 destination
> unreachable message of code 0 in response to a packet that cannot be
> delivered to its destination address because it lacks a matching
> entry in its routing table.
>
> Signed-off-by: Eric Dumazet <edumazet@google.com>
Acked-by: Neal Cardwell <ncardwell@google.com>
Thanks, Eric!
neal
next prev parent reply other threads:[~2020-05-28 1:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-28 0:34 [PATCH net-next] tcp: ipv6: support RFC 6069 (TCP-LD) Eric Dumazet
2020-05-28 0:46 ` Yuchung Cheng
2020-05-28 1:19 ` Neal Cardwell [this message]
2020-05-28 18:02 ` David Miller
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='CADVnQy=2JrtKf-AO8pMn4QFSDQJP4Vm0anBCNx6WggRPd7OA=Q@mail.gmail.com' \
--to=ncardwell@google.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=ycheng@google.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;
as well as URLs for NNTP newsgroup(s).