Re: [lisp] IPv6 UDP checksum issue

Sam Hartman <hartmans-ietf@mit.edu> Tue, 04 August 2009 13:09 UTC

Return-Path: <hartmans@mit.edu>
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DCC683A68CE; Tue, 4 Aug 2009 06:09:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.823
X-Spam-Level:
X-Spam-Status: No, score=-1.823 tagged_above=-999 required=5 tests=[AWL=0.443, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C4ux2J17-0qb; Tue, 4 Aug 2009 06:09:43 -0700 (PDT)
Received: from carter-zimmerman.suchdamage.org (carter-zimmerman.suchdamage.org [69.25.196.178]) by core3.amsl.com (Postfix) with ESMTP id 6C33028C342; Tue, 4 Aug 2009 06:08:40 -0700 (PDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 6C06A51C3; Tue, 4 Aug 2009 09:08:32 -0400 (EDT)
To: Marshall Eubanks <tme@americafree.tv>
Subject: Re: [lisp] IPv6 UDP checksum issue
References: <F3FC18FF-E085-47E9-8376-2C4DA00D9F03@americafree.tv> <FA1A0C09-FDE5-4ACD-AEA1-476B090C702D@cisco.com> <C3C481AD-5AB6-462C-A48C-F16E968DE03D@nokia.com> <C8F93853-FB91-4ABC-9CF5-E599FD27490E@cisco.com> <0E71FC61-5A42-4C5A-A22A-69B3213A9EBA@nokia.com> <DB892549-640F-437C-BB4C-2C12A985C4F1@cisco.com> <9A49FB30-3293-4681-86FD-0ABF7CD60994@nokia.com> <4A76101E.7070207@gmail.com> <E883B21D-1DC9-423B-90D4-DF1BB1D774C9@americafree.tv>
From: Sam Hartman <hartmans-ietf@mit.edu>
Date: Tue, 04 Aug 2009 09:08:32 -0400
In-Reply-To: <E883B21D-1DC9-423B-90D4-DF1BB1D774C9@americafree.tv> (Marshall Eubanks's message of "Sun\, 2 Aug 2009 18\:31\:08 -0400")
Message-ID: <tslzlafn2un.fsf@mit.edu>
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Mailman-Approved-At: Tue, 04 Aug 2009 06:56:39 -0700
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>, "lisp@ietf.org" <lisp@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Aug 2009 13:09:44 -0000

>>>>> "Marshall" == Marshall Eubanks <tme@americafree.tv> writes:

    Marshall> Dear Brian;
    Marshall> On Aug 2, 2009, at 6:15 PM, Brian E Carpenter wrote:

> Lars,
    >> 
    >> It seems to me that it would not violate the spirit of RFC2460
    >> if we added a rule that stacks MUST follow the RFC2460 rule by
    >> default but MAY deviate from it for duly configured tunnel end
    >> points in routers (where "router" is strictly as defined in
    >> section 2 of 2460 and the Note in that section). That would
    >> fully preserve the requirement as far as hosts and applications
    >> go.
    >> 

This was exactly the intention of

    Marshall> http://tools.ietf.org/html/draft-eubanks-chimento-6man-00

    Marshall> We intend to rev this shortly and comments would be
    Marshall> appreciated.

Margaret brought up a set of questions for LISP if it's going to send
0 UDP checksums, basically surrounding what happens when a packet on
such a tunnel is corrupted and gets received by a node that either
does or does not understand the tunneling protocol.  One of these
questions hinged on the expected behavior of receivers seeing a 0 UDP
checksum.


I suggest that your draft

1) Indicate whether receivers should be specially configured to accept
0 checsums or whether all stacks should accept 0 checksums.

2) Adapt her questions as questions that IETF specs considering this
exception need to answer to make sure that their protocol will work
correctly in this mode.

--Sam