IETF Logo Mail Archive

Re: [spring] L4 Checksum and draft-ietf-6man-segment-routing-header

otroan@employees.org Sun, 15 May 2016 18:06 UTC

Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 231BA12D511; Sun, 15 May 2016 11:06:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.427
X-Spam-Level:
X-Spam-Status: No, score=-3.427 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=employees.org; domainkeys=pass (1024-bit key) header.from=otroan@employees.org header.d=employees.org
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 pXLfOZidThDp; Sun, 15 May 2016 11:06:49 -0700 (PDT)
Received: from cowbell.employees.org (cowbell.employees.org [IPv6:2001:1868:a000:17::142]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 26B5012D129; Sun, 15 May 2016 11:06:48 -0700 (PDT)
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id 455359CC7D; Sun, 15 May 2016 11:06:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; s=selector1; bh=EH/2uKbiZNT6T47Gz+Ug3EmXNlo=; b= OH/2lW0Ehmx9uFYF7OheObAb2QkAZFZJXKP9sNbWPEWZ9CD9vHK83KcCAhu6l/e5 V71Uld02Kh2f7YisUbYGMFeqhLNJi3ijdNxvuMqXsut1rSq0w32Myn4kZiHlOn/v 98hMaNmfjnkHnRN7W9nIptdhvvlrJKmYDXBqRKrPtYE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; q=dns; s=selector1; b=kuAA9yZhhGSM81Ca8wdWBKSfZ9 SW6ydx9Vh8Mx9YxWsx/3SKWOnu8JhnqX6rucmakVblHklGWd+ZSwm43yAJhfdc4C baAyG/i0eAR3+U7DaVrArjNNDB4a90oCztOkZs44D2VIzc0VagjB9gSfCFZyTl/n rMPtyHASkm7mOExfY=
Received: from h.hanazo.no (77.16.5.38.tmi.telenormobil.no [77.16.5.38]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id E3CBA9CC4E; Sun, 15 May 2016 11:06:46 -0700 (PDT)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id 23D84167E7B6; Sun, 15 May 2016 20:06:38 +0200 (CEST)
Subject: Re: [spring] L4 Checksum and draft-ietf-6man-segment-routing-header
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: multipart/signed; boundary="Apple-Mail=_C20840B7-3E4A-4D72-98CA-E1E30531A0D6"; protocol="application/pgp-signature"; micalg="pgp-sha512"
X-Pgp-Agent: GPGMail 2.6b2
From: otroan@employees.org
In-Reply-To: <eaf5cad817624c7a8758758aa058399b@IL-EXCH02.marvell.com>
Date: Sun, 15 May 2016 20:06:35 +0200
Message-Id: <AD825FC8-E5AB-437D-992B-F5900B67EFA7@employees.org>
References: <eaf5cad817624c7a8758758aa058399b@IL-EXCH02.marvell.com>
To: Tal Mizrahi <talmi@marvell.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/8HVImVsqkuKyGZ3Tpkchg18lTbQ>
Cc: "spring@ietf.org" <spring@ietf.org>, 6man WG <ipv6@ietf.org>, "draft-ietf-6man-segment-routing-header@tools.ietf.org" <draft-ietf-6man-segment-routing-header@tools.ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Sun, 15 May 2016 18:06:51 -0000

Tal,

> [Apologies if this issue has been discussed before.]
> 
> According to draft-ietf-6man-segment-routing-header, an ‘SR Segment Endpoint Node’ updates the Destination IP address.
> Therefore, it must also update the Layer 4 Checksum, right?
> 
> I wonder if there is an upper bound on the size of the SRH. Otherwise, the L4 Checksum may be located in a pretty deep location.
> Speaking from a chip vendor’s perspective this may be a problem.

From RFC2460, RH0:


      o  If the IPv6 packet contains a Routing header, the Destination
         Address used in the pseudo-header is that of the final
         destination.  At the originating node, that address will be in
         the last element of the Routing header; at the recipient(s),
         that address will be in the Destination Address field of the
         IPv6 header.

I would expect SR would work the same.

Cheers,
Ole

v2.23.0 | Report a Bug | By Email