Fwd: RFC5798 - clarification on checksum calculation

Hello

I am thinking of submitting an errata for RFC 5798 Sec. 5.2.8 to make
it more precise in describing the checksum calculation for each address fam=
ily.

But reading a few responses here, I gathered that there is no general
agreement as to the original intention of the text,
I believe that for IPv4, the checksum is calculated without
pseudo-header so that it is backward compatible with RFC 3768.

Any other opinions - particularly from original authors ?


Kind Regards

Hermin Anggawijaya



On Tue, May 15, 2012 at 2:41 PM, =A0<[email protected]> wrote:
> Hello list,
>
> Has there been any progress with regard to this topic?
> I know that in an implementation of VRRPv3 for IPv4 the checksum
> is calculated without pseudo-header currently, but I believe that
> pseudo-header should be involved in the calculation as same as
> IPv6 case.
>
> Regards,
> --
> Tomohiko Kurahashi <[email protected]>
>
>
> From: [email protected]
> Date: Mon Apr 02 2012 20:41:51 JST
>>
>> Forwarded.
>> Any other VRRPv3/IPv4 implementation?
>>
>>
>> Thanks,
>> Tomoyuki
>>
>>
>> Date: Mon, 2 Apr 2012 03:26:15 +0200
>> Subject: Re: [VRRP] RFC5798 - clarification on checksum calculation
>> From: Hermin Anggawijaya <[email protected]>
>> To: Tomoyuki Sahara <[email protected]>
>>
>> Sahara-san
>>
>> Thanks for your input.
>>
>> Anyone else with either/other interpretation of the clause ?
>>
>>
>> Thanks
>>
>> On Mon, Apr 2, 2012 at 1:48 AM, Tomoyuki Sahara <[email protected]> wrote:
>> > 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 compleme=
nt
>> >> =A0 sum of the entire VRRP message starting with the version field an=
d a
>> >> =A0 "pseudo-header" as defined in Section 8.1 of [RFC2460]. =A0The ne=
xt
>> >> =A0 header field in the "pseudo-header" should be set to 112 (decimal)
>> >> =A0 for VRRP. =A0For computing the checksum, the checksum field is se=
t to
>> >> =A0 zero. =A0See RFC1071 for more detail [RFC1071]."
>> >>
>> >> My interpretation of the above clause is, for IPv4 VRRP the checksum =
would 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. =A0Our implementation calculates c=
hecksum
>> > including pseudo header as for TCP/UDP/DCCP.
>> >
>> >> If my interpretation is correct, would it be useful to change the tex=
t 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
_______________________________________________
vrrp mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/vrrp