Re: [v6ops] I-D Action: draft-ietf-v6ops-ipv6-ehs-packet-drops-00 - Fragmentation

Vasilenko Eduard <vasilenko.eduard@huawei.com> Mon, 03 August 2020 13:12 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 DA0D43A091C for <v6ops@ietfa.amsl.com>; Mon, 3 Aug 2020 06:12:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.001
X-Spam-Level:
X-Spam-Status: No, score=-0.001 tagged_above=-999 required=5 tests=[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 rsmMZwgVsY7C for <v6ops@ietfa.amsl.com>; Mon, 3 Aug 2020 06:12:42 -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 542D73A0918 for <v6ops@ietf.org>; Mon, 3 Aug 2020 06:12:42 -0700 (PDT)
Received: from lhreml707-chm.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 032EE39A1A8A7BB6F465; Mon, 3 Aug 2020 14:12:41 +0100 (IST)
Received: from msceml702-chm.china.huawei.com (10.219.141.160) by lhreml707-chm.china.huawei.com (10.201.108.56) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1913.5; Mon, 3 Aug 2020 14:12:40 +0100
Received: from msceml703-chm.china.huawei.com (10.219.141.161) by msceml702-chm.china.huawei.com (10.219.141.160) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Mon, 3 Aug 2020 16:12:40 +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, 3 Aug 2020 16:12:39 +0300
From: Vasilenko Eduard <vasilenko.eduard@huawei.com>
To: Fernando Gont <fgont@si6networks.com>, "v6ops@ietf.org" <v6ops@ietf.org>
Thread-Topic: [v6ops] I-D Action: draft-ietf-v6ops-ipv6-ehs-packet-drops-00 - Fragmentation
Thread-Index: AdZoH5e3mvncP8aHS4+K7PyCnHbT4QBRYNMAAAyKHlA=
Date: Mon, 3 Aug 2020 13:12:39 +0000
Message-ID: <05cb4504285e407fbaacee5d3c067406@huawei.com>
References: <509253a95839479fbe9741be753ce8d5@huawei.com> <f81abb25-75b7-528c-05e1-26f73e4c22ae@si6networks.com>
In-Reply-To: <f81abb25-75b7-528c-05e1-26f73e4c22ae@si6networks.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.47.194.254]
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/ejy8DtSp-5rYMqy9kyPnp8PZnQY>
Subject: Re: [v6ops] I-D Action: draft-ietf-v6ops-ipv6-ehs-packet-drops-00 - Fragmentation
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, 03 Aug 2020 13:12:44 -0000

Hi Fernando,
I do not believe that the most basic EH (fragmentation) is dropper because "6.1. Inability to Find Layer-4 Information".
I suspect that it is because universal policy to drop all EHs, i.e. Political reason.
Hence, 6.1 is not the best place to squeeze fragmentation problem.

If WG would decide to tell something about "Admin Policy to drop everything", then fragmentation could be inside,
If not - then it is better to have separate bullet for fragmentation.

Many people (who have not seen you previous reports) do not expect that this basic thing does not work in the Internet.

Eduard
-----Original Message-----
From: Fernando Gont [mailto:fgont@si6networks.com] 
Sent: 3 августа 2020 г. 13:10
To: Vasilenko Eduard <vasilenko.eduard@huawei.com>om>; v6ops@ietf.org
Subject: Re: [v6ops] I-D Action: draft-ietf-v6ops-ipv6-ehs-packet-drops-00 - Fragmentation

Hello, Eduard,

On 1/8/20 13:45, Vasilenko Eduard wrote:
> There are many references to Fragmentation documents in "Previous 
> Work" section (and in real measurements too), But Fragmentation is no cited among drop reasons (section 4-6).
> IMHO: It deserves separate bullet in the Table of Contents.

I agree that we should probably say more about fragmentation. However, it would seem to me that this should be part of Section 6.1 (and maybe add a few more words to Section 6.4).

That is, fragmentation is one special case where it may be impossible for systems to find the upper-layer information -- so it would seem to fit in Section Section 6.1.

Thoughts?

Thanks,
--
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492