Re: [lisp] IPv6 UDP checksum issue

Marshall Eubanks <tme@americafree.tv> Tue, 04 August 2009 14:30 UTC

Return-Path: <tme@americafree.tv>
X-Original-To: lisp@core3.amsl.com
Delivered-To: lisp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 628283A6ABD; Tue, 4 Aug 2009 07:30:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.547
X-Spam-Level:
X-Spam-Status: No, score=-2.547 tagged_above=-999 required=5 tests=[AWL=0.052, BAYES_00=-2.599]
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 YuHVD1OUgi4X; Tue, 4 Aug 2009 07:30:13 -0700 (PDT)
Received: from mail.americafree.tv (rossini.americafree.tv [63.105.122.34]) by core3.amsl.com (Postfix) with ESMTP id 5662C28C303; Tue, 4 Aug 2009 07:30:13 -0700 (PDT)
Received: from [IPv6:::1] (rossini.americafree.tv [63.105.122.34]) by mail.americafree.tv (Postfix) with ESMTP id EC0F94669D88; Tue, 4 Aug 2009 10:30:11 -0400 (EDT)
Message-Id: <DB7AE657-09FE-4E62-961E-0BE6D087C270@americafree.tv>
From: Marshall Eubanks <tme@americafree.tv>
To: Sam Hartman <hartmans-ietf@mit.edu>
In-Reply-To: <tslzlafn2un.fsf@mit.edu>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Tue, 04 Aug 2009 10:30:11 -0400
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> <tslzlafn2un.fsf@mit.edu>
X-Mailer: Apple Mail (2.935.3)
Cc: "Philip F. Chimento" <Philip.Chimento@jhuapl.edu>, 6man 6man <ipv6@ietf.org>, lisp@ietf.org
Subject: Re: [lisp] IPv6 UDP checksum issue
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: List for the discussion of the Locator/ID Separation Protocol <lisp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/lisp>, <mailto:lisp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/lisp>
List-Post: <mailto:lisp@ietf.org>
List-Help: <mailto:lisp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lisp>, <mailto:lisp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Aug 2009 14:30:14 -0000

On Aug 4, 2009, at 9:08 AM, Sam Hartman wrote:

>>>>>> "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.
>

I personally think that receivers SHOULD require special configuration  
to
accept UDP 0 checksums. Receivers that are acting as tunnel end points  
are
likely to require special optimizations anyway.

> 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.
>

OK, thanks, will look at this.

Marshall

> --Sam
>