Re: RFC5798 - clarification on checksum calculation

Tomoyuki Sahara <[email protected]> Mon, 2 Apr 2012 08:48:01 +0900
Newsgroups gmane.ietf.vrrp
Message-ID <CAH=tA5vaTU9X8t=JiZgxHKjq0-pCuw_vLmSHqjxzazWmrbFR9w@mail.gmail.com>
Hi,

On Thu, Mar 29, 2012 at 4:29 PM, Hermin Anggawijaya
<[email protected]> wrote:
> Would someone be able to help clarifying RFC5798 Sec. 5.2.8 on
> checksum for me please...
>
> It says that
>
> =A0"The checksum is the 16-bit one's complement of the one's complement
> =A0 sum of the entire VRRP message starting with the version field and a
> =A0 "pseudo-header" as defined in Section 8.1 of [RFC2460]. =A0The next
> =A0 header field in the "pseudo-header" should be set to 112 (decimal)
> =A0 for VRRP. =A0For computing the checksum, the checksum field is set to
> =A0 zero. =A0See RFC1071 for more detail [RFC1071]."
>
> My interpretation of the above clause is, for IPv4 VRRP the checksum woul=
d be
> defined as:
>
> "The checksum is the 16-bit one's complement of the one's complement
> =A0sum of the entire VRRP message starting with the version field"
>
> as per RFC 3768, instead of involving "pseudo header" (as defined in
> Section 8.1 of [RFC2460]).

My understanding is only reference text ("as defined in Section 8.1 of
[RFC2460]") is irrelevant for IPv4.  Our implementation calculates checksum
including pseudo header as for TCP/UDP/DCCP.

> If my interpretation is correct, would it be useful to change the text to
> reflect specific checksum detail for IPv4 ?

My interpretation is different from yours but clarification should be
very useful.
It's vital for interoperable implementations of VRRPv3/IPv4.


Thanks,
Tomoyuki
_______________________________________________
vrrp mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/vrrp