Re: [Int-area] Comments on draft-ietf-intarea-frag-fragile-06

Tom Herbert <tom@herbertland.com> Wed, 30 January 2019 16:31 UTC

Return-Path: <tom@herbertland.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9970C131237 for <int-area@ietfa.amsl.com>; Wed, 30 Jan 2019 08:31:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.042
X-Spam-Level:
X-Spam-Status: No, score=-2.042 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.142, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001] 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 8zHewqySMdBA for <int-area@ietfa.amsl.com>; Wed, 30 Jan 2019 08:31:12 -0800 (PST)
Received: from mail-qt1-x834.google.com (mail-qt1-x834.google.com [IPv6:2607:f8b0:4864:20::834]) (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 4FD49131236 for <int-area@ietf.org>; Wed, 30 Jan 2019 08:31:12 -0800 (PST)
Received: by mail-qt1-x834.google.com with SMTP id n32so105008qte.11 for <int-area@ietf.org>; Wed, 30 Jan 2019 08:31:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herbertland-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=RN6AlUiEnML1iUTisYw32KKdnt4AvHsDMXkj06FntTE=; b=pxOdTKkpVPtJDoSFd5euI18AX5esrGn9gMZgAzJ36p2y9IlMdmpuPCQn5icahoIlYh nWJmddTpJ3MDTKMBJP9XiC7aufyKJH76Vh39huVojXp9EZV5OABQwk2Gpb8QVNOqeCT3 LqfwSz6LU+eZ2KXasYe2tO29fMukNanFdkm+tuOwXhtpJmBd31iJ5Yjcecprgy1M2A11 VDiyPW4+Mwmoz8+VT8mPKapsD8tYwOkgDXJyRBhQRLAl3E8bUiCpOkNXmTvwt0OJg2nf MbHRrZ8DT1ucpReRtei6pKProkXA8i5u469DNMlp3IT4c8vLeQSTE2KFgXd4b8gX1TR8 sYMw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=RN6AlUiEnML1iUTisYw32KKdnt4AvHsDMXkj06FntTE=; b=iPwZsU90huNtSwsNa78bpa5Nge6/qGoh9KAMgq3loby4qby+DZV87geM3uVuG4V3tM LzOwHDG384piy3E7Ar471/uHw+6IBTL6Lhl5kAwJORyEVwKzs6o/FP5FHlnfdk3sMVXX pVqQxTYdSfxeTZjI6EgCNFSAF7srWuIIMJDPWH2ik/KTRNTUfyOYNdCMrRJBXjvA3955 VCs9ePMtlF7UOesoZ1c0fWNKIz+RdbNNZs0MacikLdN6+jvkC4vR9GmCOoitxjiuBuQI tBGLYfVvf8JabxAzTXmxIhIJmVijGm2Hd4jSNCOuSQceEMroedc1Zkk/zmnuOU1c8GuC tXKg==
X-Gm-Message-State: AJcUukeUMlvzf/qdWnz3141aGjK3Upp85P9D6xJxMOEz0ZZy6d8w1Y9d wrRQlISqw0a35iJN0XLOmO7eXoXkpHofypR2hZ5W1Q==
X-Google-Smtp-Source: ALg8bN7it5AX2Qy1z4tktWf3v90v7RYHzyF4MsU3E8WTgFxUhCooWeRjADMObSRx7ikRLJvDZ25g7Ax36GGgSHotHlY=
X-Received: by 2002:a0c:b407:: with SMTP id u7mr27884156qve.179.1548865871024; Wed, 30 Jan 2019 08:31:11 -0800 (PST)
MIME-Version: 1.0
References: <CALx6S35kwvHL5iE4Ci10LQbPzun3k1C-T4m5B55yAyL+nP4sdQ@mail.gmail.com> <3B29EAA5-5989-4A8F-857B-3DEF63A7FEA7@gmail.com> <CALx6S35JNTS3KGyv5iJHv65KAmJube==d-aQs6a-uPv9W57VkA@mail.gmail.com> <4afecee1-0d1a-93a3-6041-a115651c773c@gmail.com>
In-Reply-To: <4afecee1-0d1a-93a3-6041-a115651c773c@gmail.com>
From: Tom Herbert <tom@herbertland.com>
Date: Wed, 30 Jan 2019 08:30:59 -0800
Message-ID: <CALx6S34cRU7pqQagQDEFrK4_YB7JOpD=dF_5BsKL=PWOrp3D2Q@mail.gmail.com>
To: Stewart Bryant <stewart.bryant@gmail.com>
Cc: Fred Baker <fredbaker.ietf@gmail.com>, int-area <int-area@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/AbrJKLMtEHP8LP5tioFMdRFBvxo>
Subject: Re: [Int-area] Comments on draft-ietf-intarea-frag-fragile-06
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Jan 2019 16:31:15 -0000

On Wed, Jan 30, 2019 at 6:17 AM Stewart Bryant <stewart.bryant@gmail.com> wrote:
>
>
> > That's true for IPv4,the only way to do stateless ECMP and have
> > fragments follow the same path as non-fragments is to hash over the IP
> > addresses only.
>
> There is not enough entropy in that.
>
> I remember the original ECMP studies, and if the designers could have
> got away with just SA/DA/Prot they would have. In those days we were
> using s/w forwarders and the ECMP "feature" cost headline PPS which in
> those days was the key metric.
>
>
> > For IPv6 we can do better. The flow label allows finer
> > grained per-flow routing, but still only requires inspection of IP
> > header so keeping fragments in order just works.
>
> If you can trust it.
>
Stewart,

I trust it more than I trust that vendors will ever go out of their
parse any transport layer protocols other than TCP or UDP to extract
port information, or that they'll happily skip over extension headers
or parse N levels of encapsulation to find anthe embedded transport
layer, or that they'll figure out a reasonable way to deal with
protocols that don't have enough information in plain text to discern
a five tuple.

Tom

> - Stewart
>