Re: [v6ops] Operational Implications of IPv6 Packets with Extension Headers - implications from new development for EHs

Gert Doering <gert@space.net> Wed, 29 July 2020 12:26 UTC

Return-Path: <gert@space.net>
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 5B3A33A0A2C for <v6ops@ietfa.amsl.com>; Wed, 29 Jul 2020 05:26:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, 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=space.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 i9S4aDEC8P4G for <v6ops@ietfa.amsl.com>; Wed, 29 Jul 2020 05:26:30 -0700 (PDT)
Received: from gatekeeper1-relay.space.net (gatekeeper1-relay.space.net [IPv6:2001:608:3:85::38]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 73B373A0A12 for <v6ops@ietf.org>; Wed, 29 Jul 2020 05:26:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=space.net; i=@space.net; q=dns/txt; s=esa; t=1596025590; x=1627561590; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=mVFugjLzr9OTFLXWQGtC0VwgAJ7lIxMKFSp/7MTKveA=; b=beh0x4Y8pdC8ME0ToqSYl6QTNFDW6qIRZgZyWIuFKfwa2c8i6l2WWjRB 6QLEdu2+iHRYuouXuhg9C+/L8oCBBqyCeJXRTW7dSTb7Sz104nSwGlXuH SpXsJxXM1jRh5sA7HMJ2J2oYIDkcL4hAW+La7ajTp6x/lIGaOy3SGdlCU 80gnIddecw90JWQb/H4LpIS68XRTJqIJJzjvuRqDgRnAaWbx6dhnLuBkA mNBJtLol2y0yHHSAv8kvOQbdyq8/efdK5JD6hU/af/Ft4W7OOpLzVeydv kIWWQeQvDqJ9QBJ5VgLIiwvDKmxK5c+aKoyoFAQKYfKARhySVwbNuKbXa g==;
IronPort-SDR: SU5FMPK1QhwYELi+UnyVAqIIO9lfIUmTPAiyl8MLC4CuPnpNMgyur099v3ERe2JWeTmoLBEBFQ Ge3p/UE36H8TKq2Lf5MfppKcmhzQ1LcNC5isBquprz+1bSI3k4AhBOc9YeuW1GIi3x+Q4chGhF jDZwZXDd5zu+Ud9ateypiungRStzZeOZdMTaPhIABBEVKjh/aFXg+tjKAfJBtCeTS7a2NKxvYe 8EEOjoqhdjkr8vvUE5tqUFN0/UoPGm7z2Pz5bVFYlHPCtH2xsGN9HzMG0/A7+G1TxM9HixuI9/ MQ0=
X-SpaceNet-SBRS: None
Received: from mobil.space.net ([195.30.115.67]) by gatekeeper1-relay.space.net with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 29 Jul 2020 14:26:28 +0200
X-Original-To: v6ops@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id E71B941C02 for <v6ops@ietf.org>; Wed, 29 Jul 2020 14:26:22 +0200 (CEST)
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
Received: from moebius4.space.net (moebius4.space.net [IPv6:2001:608:2:2::251]) by mobil.space.net (Postfix) with ESMTP id D56FC40CFB; Wed, 29 Jul 2020 14:26:22 +0200 (CEST)
Received: by moebius4.space.net (Postfix, from userid 1007) id D25CD15D9C; Wed, 29 Jul 2020 14:26:22 +0200 (CEST)
Date: Wed, 29 Jul 2020 14:26:22 +0200
From: Gert Doering <gert@space.net>
To: otroan@employees.org
Cc: Fernando Gont <fgont@si6networks.com>, Gert Doering <gert@space.net>, Vasilenko Eduard <vasilenko.eduard@huawei.com>, IPv6 Operations <v6ops@ietf.org>
Message-ID: <20200729122622.GT2485@Space.Net>
References: <d8d59ce07f7f4031a545ff6e24fdbb88@huawei.com> <20200729084351.GG2485@Space.Net> <32BAEAEA-7352-4BAE-ADA8-FDA2395D5732@employees.org> <a6ed89a8-c12e-b8d2-c720-5cc02e127a68@si6networks.com> <FCBD1043-A0B2-435A-9AB9-0FCE3566C769@employees.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="mWLiP9EtsNFnwsQG"
Content-Disposition: inline
In-Reply-To: <FCBD1043-A0B2-435A-9AB9-0FCE3566C769@employees.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/hvwbW0GL14PpeM8oVwcvpQzORw0>
Subject: Re: [v6ops] Operational Implications of IPv6 Packets with Extension Headers - implications from new development for EHs
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 29 Jul 2020 12:26:34 -0000

Hi,

On Wed, Jul 29, 2020 at 12:43:23PM +0200, otroan@employees.org wrote:
> >> Anyway I don't quite understand what this document adds to work describing ossification in general
> > Avoiding rehashing the same discussion everytime the issue of EHs comes up?
> 
> So you are proposing to fully embrace ossification and deprecate all EHs?

Can you see a way to make them work?

Gert Doering
        -- NetMaster
-- 
have you enabled IPv6 on something today...?

SpaceNet AG                      Vorstand: Sebastian v. Bomhard, Michael Emmer
Joseph-Dollinger-Bogen 14        Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                 HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444         USt-IdNr.: DE813185279