Re: IPv6 Advanced Socket API extension for Mobile IP

JINMEI Tatuya / 神明達哉 <[email protected]> Fri, 18 Jul 2003 02:18:31 +0900
Newsgroups gmane.ietf.ipv6,gmane.ietf.mobileip
Organization Research & Development Center, Toshiba Corp., Kawasaki, Japan.
Message-ID <[email protected]>
>>>>> On Fri, 11 Jul 2003 14:08:12 -0400, 
>>>>> Vladislav Yasevich <[email protected]> said:

> In Section 4.1, the draft describes how to use the IPV6_CHECKSUM
> option on mobility headers.  The draft seems to turn off "kernel"
> checksumming by default on the IPPROTO_MH socket.  I belive
> that the checksumming should be on by default (similar to ICMPv6)
> with the ability to turn it off by the socket. 

I don't have a particular opinion on whether the checksum calculation
on a IPPROTO_MH socket should be enabled or disabled by default, but
would like to clarify one thing:

> The reason is that
> most Mobile IPv6 implementation are supported in the "kernel" and
> already do checksumming.

What exactly do you imagine about the implementation that supports
mobile IPv6 in the kernel?  If it generates, does checksumming, and
sends a packet with a mobile header completely within the kernel (the
KAME implementation apparently acts like this), it can do so without
conflicting with any API spec.  So I don't get why this is the reason
for specifying the behavior on a raw socket used by applications
(i.e., not by the kernel.)

					JINMEI, Tatuya
					Communication Platform Lab.
					Corporate R&D Center, Toshiba Corp.
					[email protected]
--------------------------------------------------------------------
IETF IPng Working Group Mailing List
IPng Home Page:                      http://playground.sun.com/ipng
FTP archive:                      ftp://playground.sun.com/pub/ipng
Direct all administrative requests to [email protected]
--------------------------------------------------------------------