Other use cases for header insertion (was Re: Header Insertion and TI-FA)

Tom Herbert <tom@herbertland.com> Mon, 11 May 2020 14:49 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 C27743A0BAC for <ipv6@ietfa.amsl.com>; Mon, 11 May 2020 07:49:08 -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=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 mRq2U2CLo3IQ for <ipv6@ietfa.amsl.com>; Mon, 11 May 2020 07:48:51 -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 206563A0B91 for <6man@ietf.org>; Mon, 11 May 2020 07:48:50 -0700 (PDT)
Received: by mail-ej1-x633.google.com with SMTP id s21so25385ejd.2 for <6man@ietf.org>; Mon, 11 May 2020 07:48:49 -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; bh=YxAlN0rJj0AKKU5qsODAGwL/725ZPZga8o0XuoovrMc=; b=xQ2CXpyQmRAdoK2h2/oZZ66YseYtoLGAcO4VXWjvYkBjer1u4X2uYzc2/80YvDfU1b VahSU+DcJfkXdRRdeY+00iF9pL1Bpq2tF5ChGOZVBnL63H9bE8RNRQ3AFa+4u5iJ+Wdo fM47tE8KfjWBz2vjHw9KW9H1AMyri6IGp+rd7EqjZ9ktXMBujZC8bS6DurKGdzBwQksA yHQL3D6JFcS/mCg0W9EikafuNH1Xk0Jo294ZBYNfsq3DQeYMRf4G7eAG5ld9HLJJMmth fZWlUWnIeYPN/PyLH0f20nRz8KeS2fuinxA1wJripnrIzazdXsDYkyCXUGtLTDa+IZoj j5dQ==
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=YxAlN0rJj0AKKU5qsODAGwL/725ZPZga8o0XuoovrMc=; b=V1Nr9BbeLmp4fJbcy0nl2ZB74DL+S4TmblrIo/gwFa3q9thLBaptIXKf7Uj7dF2Wqp QtG2gmtPWa0geqyXEUv7r4R2jNqw7j2jewe1zVGZ72jOdCpSybl+O+48yFkJHIlhOFxj KXIhjpArFfZxi10ZA5KMxNbr0CyWmpaRzEcyVsFhljPkwx32n4pDzJSW+5gtBhwZxMym 80sNC4kRjWqLHpua89Tp0afAHns/TdisIUjkJEGMjDm/3y/dpRNPMFvhDBoXHiZkXmgD 9gIMgdTXThZCoXUmF9VnkvuctXCNjYO1MsI3T8Q+9ecqJ6A+uuVRiqLRQqUxO/yGMt6B FhbA==
X-Gm-Message-State: AGi0Puau6sqAQ8SmK0kXv5gscDYxSydTuTm0aXCcDYGWDEQpzTR5z2Sv PR3Kj4sYU570/0yw4mqR6AireBF6D8j7Fzpb9FeIcQ==
X-Google-Smtp-Source: APiQypJITltF2JFh8sdZNLpbcSciu6iNelNvMpyMeefrxWUwOvYicyui/Xb3hDSQryxfeRvufFIMkY6t56cOD3SfxEY=
X-Received: by 2002:a17:907:7210:: with SMTP id dr16mr13389371ejc.197.1589208527910; Mon, 11 May 2020 07:48:47 -0700 (PDT)
MIME-Version: 1.0
References: <DM6PR05MB6348FA1FC00258ACE4FDE444AEA10@DM6PR05MB6348.namprd05.prod.outlook.com>
In-Reply-To: <DM6PR05MB6348FA1FC00258ACE4FDE444AEA10@DM6PR05MB6348.namprd05.prod.outlook.com>
From: Tom Herbert <tom@herbertland.com>
Date: Mon, 11 May 2020 07:48:36 -0700
Message-ID: <CALx6S35EncqhfBCP0aZHqBQ2MBT1VSxpRUB59dOTBpP4wwFsjg@mail.gmail.com>
Subject: Other use cases for header insertion (was Re: Header Insertion and TI-FA)
To: Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>
Cc: 6man <6man@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/8h1v8_INazBAd1BuQULdyHWrOg8>
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 14:49:13 -0000

On Mon, May 11, 2020 at 5:58 AM Ron Bonica
<rbonica=40juniper.net@dmarc.ietf.org> wrote:
>
> Folks,
>
>
>
> Happy Monday!
>
>
>
> As I was painting this weekend, I remembered that the use-case for IPv6 Header insertion is TI-LFA. This made the following questions come to mind:
>

Ron,

There is at least one other use case for IPv6 Header insertion, that
being IOAM. For example, an operator may wish to collect per packet
statistics as packets traverse its network. An ingress router would
insert headers containing IOAM, routers would annotate the
information, and the egress router is expected to consume and remove
the headers. The big difference between this use case and SR is that
there's no source routing involved so the ingress router doesn't
necessarily know what the egress router is, hence the ingress router
wouldn't know the right destination address to use in encapsulation.

I believe that this is currently being developed and maybe even being
deployed, but not under the auspices of IETF. Frankly, figuring out
how to do header insertion in a sensible and standard way would be a
step up from some of the methods being proposed. The most egregious
proposal I've seen was one in which the ingress router would place the
IOAM information in the TCP payload and then use diff serv bits to
indicate the TCP payload is modified. Of course the day a network
fails to remove the inserted information this completely breaks TCP!

This use case makes me think the WG should consider how to make header
insertion safe and viable.

Tom
>
>
> How does TI-LFA work when the original packet already contains a routing header? Will it insert a second, so that the packet has two routing headers?
> How does TI-LFA work when the node directly upstream of the link (i.e., the PLR) is not a segment endpoint? Will it insert an routing header? Is that consistent with 8200?
>
>
>
>                                                                                                                         Ron
>
>
>
>
>
>
> Juniper Business Use Only
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------