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

Vasilenko Eduard <vasilenko.eduard@huawei.com> Mon, 27 July 2020 10:01 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 6011B3A1831; Mon, 27 Jul 2020 03:01:09 -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 7tofbfcXr6Ap; Mon, 27 Jul 2020 03:01:08 -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 153B43A182E; Mon, 27 Jul 2020 03:01:08 -0700 (PDT)
Received: from lhreml713-chm.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id E085331265BD37E8BE08; Mon, 27 Jul 2020 11:01:04 +0100 (IST)
Received: from msceml704-chm.china.huawei.com (10.219.141.143) by lhreml713-chm.china.huawei.com (10.201.108.64) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Mon, 27 Jul 2020 11:01:04 +0100
Received: from msceml703-chm.china.huawei.com (10.219.141.161) by msceml704-chm.china.huawei.com (10.219.141.143) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Mon, 27 Jul 2020 13:01:04 +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, 27 Jul 2020 13:01:03 +0300
From: Vasilenko Eduard <vasilenko.eduard@huawei.com>
To: Fernando Gont <fgont@si6networks.com>, IPv6 Operations <v6ops@ietf.org>
CC: "draft-gont-v6ops-ipv6-ehs-packet-drops@ietf.org" <draft-gont-v6ops-ipv6-ehs-packet-drops@ietf.org>
Thread-Topic: Operational Implications of IPv6 Packets with Extension Headers - implementation-dependency
Thread-Index: AdZj9zFJtjveS0eYRluv5AthxXDk5f//0swA///H5tA=
Date: Mon, 27 Jul 2020 10:01:03 +0000
Message-ID: <b4c3f28a26d04d22b2d48e0240d10c9d@huawei.com>
References: <daa1c0efd47f47cfa9c2cffe4c917930@huawei.com> <3f135d04-7db1-39fa-07ea-2da190f2665d@si6networks.com>
In-Reply-To: <3f135d04-7db1-39fa-07ea-2da190f2665d@si6networks.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.47.200.156]
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/QR2G0qo0C5j8e0SRDf7XYlz8vZQ>
Subject: Re: [v6ops] Operational Implications of IPv6 Packets with Extension Headers - implementation-dependency
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, 27 Jul 2020 10:01:09 -0000

>> What would you expect us to cover in such section, other than what we already cover in Section 5.1.1. (Packet Forwarding Engine Constraints)?
It is better to move this story into separate section before security discussion.
Make this story visible.
It is relevant not just to security.
It is expenses - the biggest restriction in business.

-----Original Message-----
From: Fernando Gont [mailto:fgont@si6networks.com] 
Sent: 27 июля 2020 г. 12:39
To: Vasilenko Eduard <vasilenko.eduard@huawei.com>; IPv6 Operations <v6ops@ietf.org>
Cc: draft-gont-v6ops-ipv6-ehs-packet-drops@ietf.org
Subject: Re: Operational Implications of IPv6 Packets with Extension Headers - implementation-dependency

Hello, Eduard,

On 27/7/20 06:22, Vasilenko Eduard wrote:
> Hi Fernando, You did mention "implementation-dependent" in security 
> section. But majority of people would bypass security section on the 
> 1st pass of reading your draft. Except security people, others would 
> look to functionality 1st, them may be security (may be not:-().
> Hence, you almost ignore "implementation-dependency" in such a way 
> (putting it into security section).

Not sure what you mean...


> I propose to introduce additional
> 5.x, because (IMHO) "implementation-dependency" is the biggest problem 
> in this draft - it is related to money/expenses (especially to replace 
> hardware). It would be even bigger problem on next years with 
> proliferation of SRv6, iFit, iOAM, BIERv6 and other abuses of
> IPv6 headers extensibility. People need to check hardware (and
> software) capability far in advance, or else could be negative 
> surprise.

What would you expect us to cover in such section, other than what we already cover in Section 5.1.1. (Packet Forwarding Engine Constraints)?

Thanks!

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