From: "David S. Miller" <davem@redhat.com>
To: yoshfuji@linux-ipv6.org
Cc: netdev@oss.sgi.com, yoshfuji@linux-ipv6.org
Subject: Re: [BK-PATCH 2.4] IPV6: ensure to evaluate checksum
Date: Thu, 20 May 2004 08:14:21 -0700 [thread overview]
Message-ID: <20040520081421.594c5447.davem@redhat.com> (raw)
In-Reply-To: <20040520.193312.19702393.yoshfuji@linux-ipv6.org>
On Thu, 20 May 2004 19:33:12 +0900 (JST)
YOSHIFUJI Hideaki / ^[$B5HF#1QL@^[(B <yoshfuji@linux-ipv6.org> wrote:
> Following changesets fixes checksum for rawv6 sockets.
> - don't receive packets with incorrect checksum
I notice now how ipv6 RAW behaves differently here
than ipv4 RAW. In ipv4, packet is accepted regardless
of checksum correctness.
I can see both advantages and disadvantages of this
behavior. But what I want to ask is if ipv6 RAW is
being different on purpose, for example does the ipv6
advanced API specify this perhaps?
next prev parent reply other threads:[~2004-05-20 15:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-20 10:33 [BK-PATCH 2.4] IPV6: ensure to evaluate checksum YOSHIFUJI Hideaki / 吉藤英明
2004-05-20 15:14 ` David S. Miller [this message]
2004-05-20 15:55 ` YOSHIFUJI Hideaki / 吉藤英明
2004-05-20 16:32 ` David S. 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=20040520081421.594c5447.davem@redhat.com \
--to=davem@redhat.com \
--cc=netdev@oss.sgi.com \
--cc=yoshfuji@linux-ipv6.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).