Re: [v6ops] WG Doc? draft-gont-v6ops-ipv6-ehs-packet-drops

Tom Herbert <tom@herbertland.com> Mon, 14 March 2016 18:12 UTC

Return-Path: <tom@herbertland.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D1BD12D671 for <v6ops@ietfa.amsl.com>; Mon, 14 Mar 2016 11:12:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=herbertland-com.20150623.gappssmtp.com
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 9tN7NwH1e-eR for <v6ops@ietfa.amsl.com>; Mon, 14 Mar 2016 11:12:17 -0700 (PDT)
Received: from mail-io0-x22f.google.com (mail-io0-x22f.google.com [IPv6:2607:f8b0:4001:c06::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 04AFA12D5DC for <v6ops@ietf.org>; Mon, 14 Mar 2016 11:12:17 -0700 (PDT)
Received: by mail-io0-x22f.google.com with SMTP id m184so232861495iof.1 for <v6ops@ietf.org>; Mon, 14 Mar 2016 11:12:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herbertland-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=+Y8VYFPw0MRKIIIi/A/K1Q9a4a7PpzAnNMCY5ZFLcHs=; b=rLmkbC/NdtKtdHlfJTVAQfu4pqwLR3TiLXEpwE6l7A5bTTpJ+v2EOHerjf1leODyTr AdyYPJmDm6q+ztbD5cSsauh2FB3cqa2FnlzZUZSh2ttnZLejkle8dnh8Bti/U7dWmrFI tzK5wcpHtMr8ZfRyIYhhjsUUeLtKfmCD9R8SrbzTUUHMwHqk0u4GG5EDCw53XOrmuCP5 PwFa9rYvxxDzLCf3a0wgcALcG+tIpK0CvDVIPqb8zz6C7Ic2cQRsLUIH1QRb3RQzM54Y bSLysCAhs5zoneCWWY/VUmWS/gWXu8fQGPQDO43JY709YZl7sBASDxMlcac3ZxlgxJIr pVAQ==
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; bh=+Y8VYFPw0MRKIIIi/A/K1Q9a4a7PpzAnNMCY5ZFLcHs=; b=HkqCNuWK7veX2kEWn4U0kJjS9F2znI4Ti02ybzmiXIwHWElx8nqCQKW11KDqQUX6kC L5SI+VSxGV/IxTDMbnDDIWHcazPrXjqyb4kOqd9GeStUpXmsxokiz7oxIzWE5O3V6JnC HijNKHz0Lg/MCWBs3Je3mX2JerCm+rUOICQVDe+tnXjDcn11QbpW+lIYwCdA7jBRzpFM WyAqg92LK9G7T7pqO8a9uZ+89lS1BN8rdtrJbYfUAfuWiJoc7xfaAN6kH6prtaydaKqQ nLo91r9R3ALxXkZPbbjp0FMnAxQck1P3pVi09wiFSko6wfN9MaFQmsbiGXepewsACNua syBw==
X-Gm-Message-State: AD7BkJKYRn4RkHFR2cXCFt2U8kdmOrEIjINTe4lHQbDLMztcGIEPWrCTGS8u116jlUK6pyQMOmVB/nRzhp4M+A==
MIME-Version: 1.0
X-Received: by 10.107.10.103 with SMTP id u100mr26092652ioi.50.1457979136393; Mon, 14 Mar 2016 11:12:16 -0700 (PDT)
Received: by 10.107.160.203 with HTTP; Mon, 14 Mar 2016 11:12:16 -0700 (PDT)
In-Reply-To: <56E6FC18.1060304@foobar.org>
References: <A277BE71-BD70-4AFE-97DA-F224D7DBBCB8@cisco.com> <BDA56C2D-788D-421C-B44A-1A29578F0F78@employees.org> <56E318C7.5020200@gmail.com> <F57DFD38-FC99-45AE-B41D-51B0565148B1@employees.org> <CALx6S37vNXk-g=W4n_Qvd2J=7xkgydvGEUwrhu8pRQig0hoqLg@mail.gmail.com> <1BB37194-0F5B-45C1-9DFA-87B1C28264D2@employees.org> <CALx6S37vfDcchTa5Tch+BS8rQAGgPP_EeYbVz19WBchSHTqExg@mail.gmail.com> <56E60B0D.6070600@gmail.com> <CALx6S36_Vi4XZfPvCNY42zpbXy9dXeXzwE8KedxYDhne371HHA@mail.gmail.com> <56E6326B.2090303@gmail.com> <CALx6S353ognNHWnjbNSdW5hb_e6Hv3LqLa_r+e9yEW4F=cjH=A@mail.gmail.com> <56E6FC18.1060304@foobar.org>
Date: Mon, 14 Mar 2016 11:12:16 -0700
Message-ID: <CALx6S35pcSj_LLnDWJ68KwSYiHeu6FwrXTaR4N2xE6aY7MRO1A@mail.gmail.com>
From: Tom Herbert <tom@herbertland.com>
To: Nick Hilliard <nick@foobar.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/7uoIMIHxUqz6SVaYQDAtK1aWIKE>
Cc: "v6ops@ietf.org" <v6ops@ietf.org>
Subject: Re: [v6ops] WG Doc? draft-gont-v6ops-ipv6-ehs-packet-drops
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Mar 2016 18:12:18 -0000

On Mon, Mar 14, 2016 at 10:59 AM, Nick Hilliard <nick@foobar.org> wrote:
> Tom Herbert wrote:
>> From that point of view, the IPv6 flow label "works best" for ECMP
>> and so the three tuple hash (addresses and flow label) should be the
>> recommended method for ECMP devices to implement.
>
> Tom,
>
> Everyone agrees with this.  The problem is that core and leaf operators
> are not in control of flow label generation at the edge, and many
> operating systems do not bother to set the flow label.  In other words,
> flow labels do not currently provide enough entropy to be useful for
> flow hash generation in most instances.
>
> Everyone understands that flow labels would help this problem.  This
> draft is about what happens when the flow label is zero, which is the
> case more often than not.
>

Nick,

iOS already sends non-zero IPv6 flow labels, we have changed Linux
default to use IPv6 flow label so once Android rebases the kernel the
majority of IPv6 end hosts should be sending non-zero flow labels. It
is far easier and shorter time to change the software stacks to send
them than upgrading all the HW in the paths to use them productively.
But compared the problem of HW being able to efficiently parse
arbitrarily long header chains, I still think this is a very solvable
problem.

Tom

> Nick