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

Robert Raszuk <robert@raszuk.net> Tue, 12 May 2020 14:55 UTC

Return-Path: <robert@raszuk.net>
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 E76623A0BAC for <ipv6@ietfa.amsl.com>; Tue, 12 May 2020 07:55:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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=raszuk.net
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 FoXh5jugRYN3 for <ipv6@ietfa.amsl.com>; Tue, 12 May 2020 07:55:21 -0700 (PDT)
Received: from mail-ed1-x52a.google.com (mail-ed1-x52a.google.com [IPv6:2a00:1450:4864:20::52a]) (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 110F63A0A9A for <6man@ietf.org>; Tue, 12 May 2020 07:55:20 -0700 (PDT)
Received: by mail-ed1-x52a.google.com with SMTP id g9so6830928edw.10 for <6man@ietf.org>; Tue, 12 May 2020 07:55:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=raszuk.net; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=tGgGKSsqBlnzmt3YC+c6s7tHS7Wwz8aA7ZeLkheOpn8=; b=LubNFefOujL8j5CQHa1WPSnK6XKZ8j+Y5tZhQRvx1CxxLat8wpQ2PAh4vB5m3uBAgK wMSon8E32ojLZCPnfRBefkwuMFPhlqk+eIGWXW4eLCPYY9ZATWwTxAh8zS0RFXnWeVtd Kg8mAugfxzl5l0Y14upYh6qRJdwLBnsfUfyja40Pm+GZg2iy8SDB41wJZ2Fa/Dgz1bgr esEvmYb2C9zb6ejVozaBB3u701Vf2X6M+KcCWeKnHXmOy7A5f/wWCwErgTkqqU5j8lJk 9pET81olF5B3qnUeG3RaLVba+rIA24sNXv25yDrbIz5wnHKFJldvC1C5lz1weLZmC1+U PGBA==
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=tGgGKSsqBlnzmt3YC+c6s7tHS7Wwz8aA7ZeLkheOpn8=; b=kd3ImINzjr7CGU7vH+KiWe926YzvmsdYX2mB0STQRvH5SKoDtssyLX3TsrKbyEpgDL CZNmJsTvh3cr9/4Ymt35VCglKqci0mbmew00iD6y4BZkX1+/5YTlRGJKnHcFn8UQXalO JwIK5VKdjAGA+y4bOi76F3DZ5Nz2597EEJCD/lAPOBsx62Zjd7rY+UdZJiZ6b9UIXBYX z/l1O1152bjZaZGoy4dGHXZHHR8KE0rz0qEN1rT2DCm7QqXUkI8x4Hpg/MqrhEndEmkV WFOd/RdtAREjlZlfSFE6JKo/5hppW8NuhjDBtS3QnQE5jot8h/pVQP8tbotZT+s6M0d4 S9UA==
X-Gm-Message-State: AOAM530f7gi6XmDSyWssRctPganOHdQGC1++BhKSnEad7Ca3OBdEJgLq HUFJ3NsXUvPCxZOznMo8CRzBD8fVGava+kk771l5sQ==
X-Google-Smtp-Source: ABdhPJz2Q3+RY/sNkqpqMz7NN+OOSs/0BNslWMBVhtW0blCsu+fbDYODkCUktmxaL/seBcmZp+eKqxvrz87o9n9IWlA=
X-Received: by 2002:a05:6402:3092:: with SMTP id de18mr3246236edb.109.1589295319313; Tue, 12 May 2020 07:55:19 -0700 (PDT)
MIME-Version: 1.0
References: <DM6PR05MB6348FA1FC00258ACE4FDE444AEA10@DM6PR05MB6348.namprd05.prod.outlook.com> <CALx6S35EncqhfBCP0aZHqBQ2MBT1VSxpRUB59dOTBpP4wwFsjg@mail.gmail.com> <41a5a637-7b77-e9b8-180a-9a0d0958edfd@gmail.com> <CAOj+MMEu5SgQEFSSxNiZnthm=jMAMQE301PGycdteitqk2d27A@mail.gmail.com> <DM6PR05MB634828DFCB535CA7E7CEA3FAAEBE0@DM6PR05MB6348.namprd05.prod.outlook.com>
In-Reply-To: <DM6PR05MB634828DFCB535CA7E7CEA3FAAEBE0@DM6PR05MB6348.namprd05.prod.outlook.com>
From: Robert Raszuk <robert@raszuk.net>
Date: Tue, 12 May 2020 16:55:06 +0200
Message-ID: <CAOj+MME=p=14DEdWK5XtZbj2YOMDMN0hE=EFuJ74B-mV3buCSQ@mail.gmail.com>
Subject: Re: Other use cases for header insertion (was Re: Header Insertion and TI-FA)
To: Ron Bonica <rbonica@juniper.net>
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>, Tom Herbert <tom@herbertland.com>, 6man <6man@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000f3853c05a574a61a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/pQimo-RLtxl27sr9Q41LRXFf5bM>
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: Tue, 12 May 2020 14:55:23 -0000

Hey Ron,

Well it was half joke / half serious suggestion. Your SRv6+ was an
inspiration for IPv6+ - no doubt !

But to your point ...

* Yes it would be much easier to contain any new significant protocol
extension if you apply new ethertype to it

* As sent in the note over weekend I think that this "packets leaking" or
"escaping" fear is a nonsense - packets are not mosquitoes flying where
they want to go - packets are forwarded based on the control plane
directions. If there is more work on controlled leaking IGP to BGP we
should work on that in LSR WG and IDR WG.

* If you force that SRv6 must only be legal in new ethertype then I can no
longer legally send SRv6 packet between my sites over Internet which breaks
completely my #1 application and main interest in/for SRv6.

Cheers,
Robert.


On Tue, May 12, 2020 at 4:45 PM Ron Bonica <rbonica@juniper.net> wrote:

> Robert,
>
>
>
> I realize that you are joking, but it might actually be a good idea for
> SRv6 to move onto another protocol number. This would solve the following
> problems:
>
>
>
>    - SRv6 could do whatever it wanted, without regard for RFC 4291,  RFC
>    8200, or anything else that 6man produces
>    - 6man could evolve IPv6 as it sees fit, without having to consider
>    the sensitivities of SRv6
>
>
>
> It would only mean changing the first four bits of every SRv6 packet. That
> would probably take much less time than converging the SRv6 and IPv6
> architectures.
>
>
>
>                                                          Ron
>
>
>
>
>
>
>
> Juniper Business Use Only
>
> *From:* Robert Raszuk <robert@raszuk.net>
> *Sent:* Monday, May 11, 2020 4:43 PM
> *To:* Brian E Carpenter <brian.e.carpenter@gmail.com>
> *Cc:* Tom Herbert <tom@herbertland.com>; Ron Bonica <rbonica@juniper.net>;
> 6man <6man@ietf.org>
> *Subject:* Re: Other use cases for header insertion (was Re: Header
> Insertion and TI-FA)
>
>
>
> *[External Email. Be cautious of content]*
>
>
>
>
>
> I'm not sure this is feasible without changing the IP version number.
>
>
>
> How about IPv6+ ?
>
>
>
> Thx,
>
> R.
>
>
>