Re: [lisp] Judging Consensus on the UDP Checksum Issue

Margaret Wasserman <mrw@sandstorm.net> Wed, 12 August 2009 15:43 UTC

Return-Path: <mrw@sandstorm.net>
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 5E0A13A6B56 for <lisp@core3.amsl.com>; Wed, 12 Aug 2009 08:43:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.26
X-Spam-Level:
X-Spam-Status: No, score=-2.26 tagged_above=-999 required=5 tests=[AWL=0.005, 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 On1vNobmNKS3 for <lisp@core3.amsl.com>; Wed, 12 Aug 2009 08:43:02 -0700 (PDT)
Received: from sirocco.sandstorm.net (sirocco.sandstorm.net [69.33.111.75]) by core3.amsl.com (Postfix) with ESMTP id 5A4C93A6838 for <lisp@ietf.org>; Wed, 12 Aug 2009 08:43:02 -0700 (PDT)
Received: from lilac.sandstorm.net (ip-69-33-111-74.bos.megapath.net [69.33.111.74]) (authenticated bits=0) by sirocco.sandstorm.net (8.13.8/8.13.3) with ESMTP id n7CFfFmN073727 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 12 Aug 2009 11:41:15 -0400 (EDT) (envelope-from mrw@sandstorm.net)
Message-Id: <75C38DEF-C419-448D-84B6-542429305792@sandstorm.net>
From: Margaret Wasserman <mrw@sandstorm.net>
To: Dino Farinacci <dino@cisco.com>
In-Reply-To: <3FB04D1B-83CE-4A22-BC4B-A067C4BB15B4@cisco.com>
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: Wed, 12 Aug 2009 11:38:18 -0400
References: <20090812000815.6D2A06BE5CC@mercury.lcs.mit.edu> <tslocqloh4f.fsf@mit.edu> <3FB04D1B-83CE-4A22-BC4B-A067C4BB15B4@cisco.com>
X-Mailer: Apple Mail (2.935.3)
Cc: lisp@ietf.org, fred@cisco.com, Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: Re: [lisp] Judging Consensus on the 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: Wed, 12 Aug 2009 15:43:03 -0000

On Aug 12, 2009, at 11:22 AM, Dino Farinacci wrote:

> On Aug 11, 2009, at 8:17 PM, Sam Hartman wrote:
>
>> You'd need to word it as an ITR MAY send a zero checksum, an ETR MUST
>> accept a 0 checksum and MAY ignore the checksum completely.  And of
>
> Anyone object to me putting this text in the -04 spec now?

While this doesn't address all of my concerns about the UDP checksum  
handling, I consider this text to be much better than the current  
text, so go ahead and include it.

You should include a normative reference to Marshall's IPv6 zero  
checksum draft after "ITRs MAY send a zero checksum", because you will  
need a normative reference to a standards track RFC that says this is  
an okay thing to do in IPv6.  His draft can be found here:

http://www.ietf.org/id/draft-eubanks-chimento-6man-00.txt

You should also include a "[Ref Needed]" placeholder, or something  
similar, after "MAY ignore the checksum completely", because you will  
need a normative reference to a standards track RFC that indicates  
that this is an okay thing to do for both IPv4 and IPv6, as well.

Margaret