| To: | davem@xxxxxxxxxx |
|---|---|
| Subject: | Re: [BK-PATCH 2.4] IPV6: ensure to evaluate checksum |
| From: | YOSHIFUJI Hideaki / 吉藤英明 <yoshfuji@xxxxxxxxxxxxxx> |
| Date: | Fri, 21 May 2004 00:55:50 +0900 (JST) |
| Cc: | netdev@xxxxxxxxxxx, yoshfuji@xxxxxxxxxxxxxx |
| In-reply-to: | <20040520081421.594c5447.davem@redhat.com> |
| Organization: | USAGI Project |
| References: | <20040520.193312.19702393.yoshfuji@linux-ipv6.org> <20040520081421.594c5447.davem@redhat.com> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
In article <20040520081421.594c5447.davem@xxxxxxxxxx> (at Thu, 20 May 2004 08:14:21 -0700), "David S. Miller" <davem@xxxxxxxxxx> says: > 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? Yes. RFC3542 (Advanced Sockets Application Program Interface (API) for IPv6) says: | For other raw IPv6 sockets (that is, for raw IPv6 sockets created | with a third argument other than IPPROTO_ICMPV6), the application | must set the new IPV6_CHECKSUM socket option to have the kernel (1) | compute and store a checksum for output, and (2) verify the received | checksum on input, discarding the packet if the checksum is in error. --yoshfuji |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [BK-PATCH 2.6] IPV6: Fix checksum for rawv6 sockets, David S. Miller |
|---|---|
| Next by Date: | Re: [BK-PATCH 2.4] IPV6: ensure to evaluate checksum, David S. Miller |
| Previous by Thread: | Re: [BK-PATCH 2.4] IPV6: ensure to evaluate checksum, David S. Miller |
| Next by Thread: | Re: [BK-PATCH 2.4] IPV6: ensure to evaluate checksum, David S. Miller |
| Indexes: | [Date] [Thread] [Top] [All Lists] |