Ted H. Kim writes: > My hope is that our stack can deal with using a similar > large value around 64K. It sounds like for simplicity > (and RFC4755 recommends also) though we should try to > use a max value that works for both IPv4 and IPv6, which > based on the previous conversation sounds like 64K > (though would get pushed down to 65520 when talking to Linux).
Nit: that'd be 64K-1 (65535) as the minimum of the max MTUs for IPv4 and IPv6. > I am not as concerned about the checksum > stability since IB has it's own stronger 32-bit end-to-end > checksum (plus a 16-bit checksum to cover > the much smaller changes that occur hop-by-hop). Right; that's just an issue for the Ethernet integrity check, and related schemes that run CRC over the whole packet (such as, for instance, AAL5). -- James Carlson, Solaris Networking <[EMAIL PROTECTED]> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ networking-discuss mailing list [email protected]
