IETF Logo Mail Archive

Re: Header Insertion and TI-FA

Tom Herbert <tom@herbertland.com> Mon, 11 May 2020 15:05 UTC

Return-Path: <tom@herbertland.com>
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 37A453A0044 for <ipv6@ietfa.amsl.com>; Mon, 11 May 2020 08:05:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 KxqPl-oXz5lf for <ipv6@ietfa.amsl.com>; Mon, 11 May 2020 08:05:18 -0700 (PDT)
Received: from mail-ej1-x633.google.com (mail-ej1-x633.google.com [IPv6:2a00:1450:4864:20::633]) (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 05F6B3A005F for <6man@ietf.org>; Mon, 11 May 2020 08:05:17 -0700 (PDT)
Received: by mail-ej1-x633.google.com with SMTP id nv1so8210809ejb.0 for <6man@ietf.org>; Mon, 11 May 2020 08:05:17 -0700 (PDT)
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:content-transfer-encoding; bh=dRKqhmZ4156cI+PiDICNR8hUPPYZVHRECuWMymkEHVA=; b=YseVMP7dqS4+dbL8nKthbzh2y7rMr32mUXb9vKvNNjmkVhQhLCVPpAU0W2BpT9oaz5 GtIyEjGp9PzT1mlmGIyf5lEkVgTpFx+vEu+WufG6RVho7fW9Z6NhNnB5odOUuR+yz4LA bov552XxS9cKccVidKN5DFBdnkIp8tQ3eQENZmfN4MsqgjVKud1lyWtZPsRyfIsW7eSR DtFvGaez1DrRdsOLHAw3IgIaHZNhNILUKMDepS9okubXSHNfJiABin7kF1ZlNfRYrXMz nBsSLuI1yFDjcxYBfxfbeLcvaagm4TQ6Qytgj/3nZlwTkbuHW8RnF1FD4XXV5xDLWjpu UZFQ==
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:content-transfer-encoding; bh=dRKqhmZ4156cI+PiDICNR8hUPPYZVHRECuWMymkEHVA=; b=cZvO4XTJhlQ95ZMaYhEnwRuYazOus3b234fP6qwOpVnWx5EM8Jw2ALCLgDnAWE+ohu DW575dz56jxzCPeAf41hti+wRK4L42gcur3sO4TSAUCItyOGUYLBGGDVALp3G7erCorr 7m9pZDU9hcMp50L2eUDQ74iJDML1k7pwSwsBp8KUIqKas9bCSJSlzvpq9L5w0l37VNNP SgTBqw/e5gJ3K+DFN9wXQ4ghafro5vXt9KXH+/NCPOU6s3WRcOCBqrrOaSnTrp8JcM1q pb4KZ9L/vZ01xVH1UQD0kiFmvowUUS1OTVih0S7BvrrDzv4QYwy9qOao3Lo5THeXD3XA SYdw==
X-Gm-Message-State: AGi0PuZiLGps4ykk7qXjosYXGx9C0e60tXQyZLLo2xnUMoNvoUwqQgF+ 61OPm19mmACp8TCNys89W8zc1aBWfAIeo/8+/ciZzyaA
X-Google-Smtp-Source: APiQypIWTT8sdFNklIe9dINvTdD8J8V/Jmy15evCRZl/W9zGnPxGmDZTKaSgTlqrDvihqW8kwX0JeVarZkPbGVt/H7E=
X-Received: by 2002:a17:906:9450:: with SMTP id z16mr13297657ejx.166.1589209516057; Mon, 11 May 2020 08:05:16 -0700 (PDT)
MIME-Version: 1.0
References: <DM6PR05MB6348FA1FC00258ACE4FDE444AEA10@DM6PR05MB6348.namprd05.prod.outlook.com> <CABNhwV3-dMPg6SAAEz+uWre-rj6j5=1JgyyQyKyz_qn7f7mJwQ@mail.gmail.com> <DM6PR05MB634848D379A428372C166DD4AEA10@DM6PR05MB6348.namprd05.prod.outlook.com> <CAOj+MMEBVA+yK9cFXSe=GVUeH01ipi++nwCRQU_nQCxsKhyvRg@mail.gmail.com>
In-Reply-To: <CAOj+MMEBVA+yK9cFXSe=GVUeH01ipi++nwCRQU_nQCxsKhyvRg@mail.gmail.com>
From: Tom Herbert <tom@herbertland.com>
Date: Mon, 11 May 2020 08:05:04 -0700
Message-ID: <CALx6S34=zmydp59NLbjJgs4w+a2vTGygn42=BWCoihr3NPmHjA@mail.gmail.com>
Subject: Re: Header Insertion and TI-FA
To: Robert Raszuk <robert@raszuk.net>
Cc: Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>, 6man <6man@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/NvD5PyYAjPqTC8cHdAr0AeAd92o>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 11 May 2020 15:05:36 -0000

On Mon, May 11, 2020 at 7:42 AM Robert Raszuk <robert@raszuk.net> wrote:
>
> Hi Ron,
>
> > normalizing header insertion for the special case where the PLR is a segment endpoint
>
> When an operator is serious about good data plane protection with TI-LFA all nodes in the network will be enabled for SR. The less overhead required for the protection the better. You may just not have a room for adding additional 40 bytes to each packet at each potential PLR without fragmentation.

Robert,

Considering that SRH already carries a list of IPv6 addresses which
could create hundreds of bytes of overhead, the argument that an
additional forty byte header is the problem seems trite to me. Besides
that, it's not really an additional forty bytes being added to the
packet. The destination address in the encapsulating header saves one
address in the SID list, so that takes encapsulation down to
twenty-four bytes of additional overhead. If the address of the node
inserting the header is needed in inserted data, like for correct
handling of ICMP, that would be reflected in source address so the
overhead difference of encapsulation would only be eight bytes.

Tom

>
> Regarding all of your other TI-LFA related questions - I am sure Krzysztof will be happy to answer them for you internally :)  After all this is what your public demo was all about ....
>
> Best,
> Robert,
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

v2.23.0 | Report a Bug | By Email