IETF Logo Mail Archive

Re: [Tofoo] VXLAN (UDP tunnel protocols) and non-zero checksums

Tom Herbert <therbert@google.com> Fri, 02 May 2014 21:34 UTC

Return-Path: <therbert@google.com>
X-Original-To: tofoo@ietfa.amsl.com
Delivered-To: tofoo@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C68D21A6F38 for <tofoo@ietfa.amsl.com>; Fri, 2 May 2014 14:34:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.029
X-Spam-Level:
X-Spam-Status: No, score=-2.029 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=unavailable
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ml-S2k5T8oUY for <tofoo@ietfa.amsl.com>; Fri, 2 May 2014 14:34:28 -0700 (PDT)
Received: from mail-ie0-x22e.google.com (mail-ie0-x22e.google.com [IPv6:2607:f8b0:4001:c03::22e]) by ietfa.amsl.com (Postfix) with ESMTP id E4C3C1A0A7B for <tofoo@ietf.org>; Fri, 2 May 2014 14:34:27 -0700 (PDT)
Received: by mail-ie0-f174.google.com with SMTP id ar20so5779504iec.33 for <tofoo@ietf.org>; Fri, 02 May 2014 14:34:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=ANL0RxizWgNRn3mid8P57Pb81oLIDJCnrS/Dhf4txSY=; b=knNXXr3B/jEjy7VkJTfDm6eb0bh32to6Ya/W5dqpl1n5qIzNtpDhhHzyiIl6uHoFOQ 88xd8UBFjlfrNfNv12I6UOxM3yKKuXED/suL51yN5/RRvh46A/wFC69wWwBvqu/1ARtp lWpYfx+P1QVTaP0ImWWODqDz2FsCYFDRrULmm4OClI8JLAAm4A1A5lp88orJxAkF6+JX fwL6df2laSqHFKBpGjmq7qiKARt0dNBLzPCNkLiiyaL/ik4HffGQRybFFNDY/1dxultM g/Oi1TNFJMagHBDe6j3sImEEgyez1vn4GRPbsc0EFqvMgXWadd0Do456CcDiol42zkq3 6+xg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=ANL0RxizWgNRn3mid8P57Pb81oLIDJCnrS/Dhf4txSY=; b=CS2zjLq74CvB3gsjyCDuNxbtiDr+PpcHBh9GLJ1kZSRrwRHM0SKCP0zbxYmaqoYOFm vGQ1qKJRRA0E14MpvCWideAfjdL2Mv4ssQPYpzVZZwmFffJ4B4z9YwJwdEq9TGVb/T6F JazwG1l+eCpEqxf/PE/sR59gNq2Hwrvh4rKk+8VuG/JKSEp786UJ6jHdiWavs/oaDFiD AmMOmXT3SZUo5ggFKVYs70zjq8B/EUfXVSTytPWMUy62BJktuvrM2q7X2HZiBDgV4HLX m0gpzfmvjQza2ffc2IE5b0mLtKmcsbJ/evBcp4vpk9v+7oYSUkOEQeSbOA40wAt5fY2x 9zCw==
X-Gm-Message-State: ALoCoQl1rFpQ9zsbE23gr5cyhs41dIPNgAGNNz5ArAQyNFx9xuoa1fT/Z2ERNOOmbl7jQ7nL6E3p
MIME-Version: 1.0
X-Received: by 10.43.59.82 with SMTP id wn18mr19561981icb.6.1399066465372; Fri, 02 May 2014 14:34:25 -0700 (PDT)
Received: by 10.64.148.98 with HTTP; Fri, 2 May 2014 14:34:25 -0700 (PDT)
In-Reply-To: <5362B7E4.8060809@isi.edu>
References: <CA+mtBx8+OyN5UUsL-sS1AuPF69p6=T3kw4Mq-BogjQhEF-Cpsw@mail.gmail.com> <CAC8QAccqYygAZrX=P1S7Av4KXtU82RWANv=BAaKjYm=hDH0hAA@mail.gmail.com> <CA+mtBx9YfBtizy+a1Wi+z5isYQ7AtLm_Hevx7U66U8HS8u_6LQ@mail.gmail.com> <CAC8QAcdXLbdVw3FYcdqSg163_w76ThYXuK3M9-vvw_wx5d52_Q@mail.gmail.com> <5362ACA5.1030102@isi.edu> <CAC8QAcfi=CEc_a43R1ZgidtmdjGL2G4C_+PPj-uDCMkZ+aheuw@mail.gmail.com> <5362AFBB.6080008@isi.edu> <CA+mtBx8G6kBzOiKP2r7W3i1JV43A8feg8Xqbo6t1Kfhj3jwpJA@mail.gmail.com> <5362B7E4.8060809@isi.edu>
Date: Fri, 02 May 2014 14:34:25 -0700
Message-ID: <CA+mtBx8hLyvQ+3Bs9cFjGPV0dWtK+TDO+J6Mg_gLtgxHECiCRw@mail.gmail.com>
From: Tom Herbert <therbert@google.com>
To: Joe Touch <touch@isi.edu>
Content-Type: multipart/alternative; boundary="bcaec51961f1afac9904f8718b4f"
Archived-At: http://mailarchive.ietf.org/arch/msg/tofoo/-ZzzBptmm37dQomh0XZ5bwtplvU
Cc: "tofoo@ietf.org" <tofoo@ietf.org>, sarikaya@ieee.org, "nvo3@ietf.org" <nvo3@ietf.org>, "mallik_mahalingam@yahoo.com" <mallik_mahalingam@yahoo.com>, "ddutt.ietf@hobbesdutt.com" <ddutt.ietf@hobbesdutt.com>
Subject: Re: [Tofoo] VXLAN (UDP tunnel protocols) and non-zero checksums
X-BeenThere: tofoo@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discussion list for Tunneling over Foo \(with\)in IP networks \(TOFOO\)." <tofoo.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tofoo>, <mailto:tofoo-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tofoo/>
List-Post: <mailto:tofoo@ietf.org>
List-Help: <mailto:tofoo-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tofoo>, <mailto:tofoo-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 May 2014 21:34:30 -0000

On Thu, May 1, 2014 at 2:08 PM, Joe Touch <touch@isi.edu> wrote:

>
>
> On 5/1/2014 2:00 PM, Tom Herbert wrote:
> ...
>
>      Receiver processing is simple:
>>
>>              - if the checksum is zero, ignore
>>
>>              - if the checksum is NOT zero, it MUST match
>>
>> This is true with caveat that an implementation MAY ignore a zero
>> checksum, not MUST ignore a zero checksum. This is specified in RFC1122.
>>
>
> It says that the app MAY optionally be able to configure the system to
> pass zero-checksum UDP packets up or discard them.
>
> I.e., a *configuration* MAY decide to accept or drop zero-checksum UDP
> packets; the UDP layer isn't in control of that by itself.
>
>
>    VXLAN draft also breaks this by making accepting packets with zero
>> checksums a MUST.
>>
>
> That's not "breaking" anything; VXLAN is - to UDP - an application.
>
> Perhaps not, but making it a MUST in the encapsulation protocol definition
to always accept UDP packets with zero checksums seems a bit austere. For
instance, if I know within my deployment that all senders are configured to
use checksums, then receiving a packet with zero checksum should be
considered an invalid packet.

Tom

Joe
>

v2.23.0 | Report a Bug | By Email