Re: [v6ops] Operational Implications of IPv6 Packets with Extension Headers - Security as Functionality

Vasilenko Eduard <vasilenko.eduard@huawei.com> Mon, 27 July 2020 09:43 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 E22BA3A180E; Mon, 27 Jul 2020 02:43:16 -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 H1WDzCuXDs8g; Mon, 27 Jul 2020 02:43:15 -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 128E33A180B; Mon, 27 Jul 2020 02:43:15 -0700 (PDT)
Received: from lhreml724-chm.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 1C50C29AD50D114B401A; Mon, 27 Jul 2020 10:43:12 +0100 (IST)
Received: from msceml705-chm.china.huawei.com (10.219.141.144) by lhreml724-chm.china.huawei.com (10.201.108.75) 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 10:43:11 +0100
Received: from msceml703-chm.china.huawei.com (10.219.141.161) by msceml705-chm.china.huawei.com (10.219.141.144) 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 12:43:10 +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 12:43:10 +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 - Security as Functionality
Thread-Index: AdZj8y0cpQvjOWzVQImqu+eAb68F0P//1v2A///IybA=
Date: Mon, 27 Jul 2020 09:43:10 +0000
Message-ID: <48214ae519994396ae77e73c9b2b8d57@huawei.com>
References: <ee0bbb4d1f844ee8aef70dff0986685f@huawei.com> <be491036-fe49-1d37-df1f-f68e33f23d12@si6networks.com>
In-Reply-To: <be491036-fe49-1d37-df1f-f68e33f23d12@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/2hKE3yB3qWCWhJ9JahrnN9gj5Z8>
Subject: Re: [v6ops] Operational Implications of IPv6 Packets with Extension Headers - Security as Functionality
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 09:43:17 -0000

There is no any restriction in the name of this draft that "Enterprises should not read this draft".
Put this restriction, then I would agree that FW is out.

Something like "Operational Implications of IPv6 Packets with Extension Headers in Telco environment".

-----Original Message-----
From: Fernando Gont [mailto:fgont@si6networks.com] 
Sent: 27 июля 2020 г. 12:25
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 - Security as Functionality

Hello, Edward,

On 27/7/20 05:57, Vasilenko Eduard wrote:
> Hi Fernando,
> Security is sometimes functionality, not vulnerability or attack vector. The good example is Firewall. Firewall needs to parse all headers to be useful.
> Hence, I believe it is in the logic of this draft to have section 
> 5.1.5: one additional "use case" when parsing of ALL headers are 
> mandatory. FW, IDPS

It's indeed normally necessary for a firewall to parse all headers, and certainly this might be a motivation to drop packets at the edge of the network.

However, I'm not sure if it would make sense to cover IDPS/FW in this I-D, since we're mostly discussing the reasons for operators (as opposed to say, sys admins or security administrators) to drop them.

What do folks think?

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