Re: [v6ops] Operational Implications of IPv6 Packets with Extension Headers

Vasilenko Eduard <vasilenko.eduard@huawei.com> Mon, 14 September 2020 11:55 UTC

Return-Path: <vasilenko.eduard@huawei.com>
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 7FF0A3A0930 for <v6ops@ietfa.amsl.com>; Mon, 14 Sep 2020 04:55:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 egI9QFXEITd6 for <v6ops@ietfa.amsl.com>; Mon, 14 Sep 2020 04:55:52 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 B38823A091B for <v6ops@ietf.org>; Mon, 14 Sep 2020 04:55:52 -0700 (PDT)
Received: from lhreml734-chm.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id C4210660383537CC3282; Mon, 14 Sep 2020 12:55:50 +0100 (IST)
Received: from msceml706-chm.china.huawei.com (10.219.141.145) by lhreml734-chm.china.huawei.com (10.201.108.85) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Mon, 14 Sep 2020 12:55:49 +0100
Received: from msceml703-chm.china.huawei.com (10.219.141.161) by msceml706-chm.china.huawei.com (10.219.141.145) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Mon, 14 Sep 2020 14:55:48 +0300
Received: from msceml703-chm.china.huawei.com ([10.219.141.161]) by msceml703-chm.china.huawei.com ([10.219.141.161]) with mapi id 15.01.1913.007; Mon, 14 Sep 2020 14:55:48 +0300
From: Vasilenko Eduard <vasilenko.eduard@huawei.com>
To: tom petch <ietfc@btconnect.com>, Fernando Gont <fgont@si6networks.com>
CC: IPv6 Operations <v6ops@ietf.org>
Thread-Topic: [v6ops] Operational Implications of IPv6 Packets with Extension Headers
Thread-Index: AQHWioRZW0go2gYqlEG0glGxz7yqdKloBGOg
Date: Mon, 14 Sep 2020 11:55:48 +0000
Message-ID: <c0d6803eaeed4888a71c36b1f2da96f8@huawei.com>
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> <4573db3f-ac8d-3103-1979-e803ae40f117@si6networks.com> <DEB1318E-0E5B-4093-A691-8E1FD35B9F50@strayalpha.com> <A197EF3A-1E1E-40F1-BB50-68469E3C8E63@delong.com> <44481FC7-6E3F-4D5A-A5A9-A338C1836EA1@strayalpha.com> <2ad804a2-e714-6256-3afa-4d4a92fd6d3c@si6networks.com>, <9c026e30-149b-172f-0953-456fb2d1e715@gmail.com> <AM7PR07MB6248A43FCBBB5D34AA2DA9AAA0230@AM7PR07MB6248.eurprd07.prod.outlook.com>
In-Reply-To: <AM7PR07MB6248A43FCBBB5D34AA2DA9AAA0230@AM7PR07MB6248.eurprd07.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.47.198.216]
Content-Type: text/plain; charset="koi8-r"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/pMY-0oQUpeqe0USu-71up_yvxJ8>
Subject: Re: [v6ops] Operational Implications of IPv6 Packets with Extension Headers
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: Mon, 14 Sep 2020 11:55:54 -0000

Hi all,
> And then there is the future; should more Extension Headers be allocated, should they be constrained to avoid the difficulties raised here?  The I-D, for me, lacks an ending, lacks a look forward.
I was discussing off-line with Fernando for long time about last Tom's comment. No success yet - no agreement to make any predictions or recommendations, Just "raise awareness".
I personally strongly suspect that a flood of new EH functionality that is in development now would greatly increase drop rate, because not all nodes would support everything needed at proper time.
Business is very restricted to something 7-10 years (depends on network layer) to refresh equipment, even if there is an EOS pressure.
Current EH innovation is much faster.
And additionally it overlays on slowdown of traffic growth (it was +50% just 2 years ago, 30% last year, 25% is probable this year) - would be more and more difficult to justify rip-and-replace.
Eduard
-----Original Message-----
From: v6ops [mailto:v6ops-bounces@ietf.org] On Behalf Of tom petch
Sent: 14 сентября 2020 г. 13:46
To: Fernando Gont <fgont@si6networks.com>
Cc: IPv6 Operations <v6ops@ietf.org>
Subject: [v6ops] Operational Implications of IPv6 Packets with Extension Headers

The problem that I have with this I-D is that I do not think that it will achieve its objectives.  It wants to raise awareness about the problems caused by Extension Headers so the target audience should be the world at large, especially those involved in setting up and operating IPv6 networks, but the style is, to me, rather academic, as if the audience was the sort of people who would be expected to be familiar with the literature and need little or no explanation.  I see this strongly in s.1, about Extension Headers, yet devoid of any reference, any explanation.  The first reference is RFC2460, which is Normative, so are readers expected to be familiar with the details therein?  One reaction might be 'So Extension Headers create problems so don't ever use them!'

The I-D lacks any explicit explanation of what an Extension Header is, what they were intended for, which bits have worked and which have failed so eg deprecating RHT0 is not very meaningful without some comment about RH something else.  Size matters as can be inferred from s.4 but there is no mention of the sizes involved of the IPv6 packet, with or without headers.  As I say, it seems that the reader is expected to know the literature.  There needs to be a page or two at the start giving the context within which the detail makes sense.

And then there is the future; should more Extension Headers be allocated, should they be constrained to avoid the difficulties raised here?  The I-D, for me, lacks an ending, lacks a look forward.

Tom Petch
_______________________________________________
v6ops mailing list
v6ops@ietf.org
https://www.ietf.org/mailman/listinfo/v6ops