IETF Logo Mail Archive

Re: [MBONED] [Msr6] MSR6 BOF 3rd Issue Category: More details are requested about the large scale use cases, including issue 8-11

Dirk Trossen <dirk.trossen@huawei.com> Thu, 03 November 2022 07:53 UTC

Return-Path: <dirk.trossen@huawei.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0DB1DC14CF0C; Thu, 3 Nov 2022 00:53:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.907
X-Spam-Level:
X-Spam-Status: No, score=-6.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wG7WkzxKdD_Y; Thu, 3 Nov 2022 00:53:42 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E568FC14F739; Thu, 3 Nov 2022 00:53:41 -0700 (PDT)
Received: from fraeml742-chm.china.huawei.com (unknown [172.18.147.226]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4N2wvD6jXrz6HJVg; Thu, 3 Nov 2022 15:51:52 +0800 (CST)
Received: from lhrpeml100002.china.huawei.com (7.191.160.241) by fraeml742-chm.china.huawei.com (10.206.15.223) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.31; Thu, 3 Nov 2022 08:53:39 +0100
Received: from lhrpeml500003.china.huawei.com (7.191.162.67) by lhrpeml100002.china.huawei.com (7.191.160.241) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.31; Thu, 3 Nov 2022 07:53:39 +0000
Received: from lhrpeml500003.china.huawei.com ([7.191.162.67]) by lhrpeml500003.china.huawei.com ([7.191.162.67]) with mapi id 15.01.2375.031; Thu, 3 Nov 2022 07:53:39 +0000
From: Dirk Trossen <dirk.trossen@huawei.com>
To: Dino Farinacci <farinacci@gmail.com>, Toerless Eckert <tte@cs.fau.de>
CC: Jeffrey Zhang <zzhang@juniper.net>, "Xiejingrong (Jingrong)" <xiejingrong=40huawei.com@dmarc.ietf.org>, BIER WG <bier@ietf.org>, "msr6@ietf.org" <msr6@ietf.org>, "mboned@ietf.org" <mboned@ietf.org>, "pim@ietf.org" <pim@ietf.org>
Thread-Topic: [Msr6] MSR6 BOF 3rd Issue Category: More details are requested about the large scale use cases, including issue 8-11
Thread-Index: AQHY7m9JD3lrN7R9G0uzVxHA8OIhC64sM1GAgAChtGA=
Date: Thu, 03 Nov 2022 07:53:38 +0000
Message-ID: <22f67f393db049e0abcb018c1914c4d9@huawei.com>
References: <1A893DF5-816E-4D09-AAC6-065BBD1BD409@gmail.com> <Y1X2kvbLv0qXtD8z@faui48e.informatik.uni-erlangen.de> <DDD735E2-0930-4CB8-8992-E3E74C715D16@gmail.com> <Y1a8+EK9qA2kKDBF@faui48e.informatik.uni-erlangen.de> <03B2B681-FE16-4961-8932-1F3F29932837@gmail.com> <0d2e78fefe9e4cef87c52493b7fefc80@huawei.com> <BL0PR05MB56528FCEF7FDE262F633A24FD4329@BL0PR05MB5652.namprd05.prod.outlook.com> <C10FBD6A-E651-49BB-B2EC-0C04FC966C4A@gmail.com> <Y1/nUmnoYQhTn7OO@faui48e.informatik.uni-erlangen.de> <15F231E4-1D93-4531-AEA1-B4DC06F25A69@gmail.com> <Y2HqfVIOKKeDfdF0@faui48e.informatik.uni-erlangen.de> <5A79421D-7843-4F60-9165-0A077FF2695A@gmail.com>
In-Reply-To: <5A79421D-7843-4F60-9165-0A077FF2695A@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.220.96.241]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/11-Dv2y_gSD554JBQx4ceDl-O2M>
Subject: Re: [MBONED] [Msr6] MSR6 BOF 3rd Issue Category: More details are requested about the large scale use cases, including issue 8-11
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Nov 2022 07:53:46 -0000

-----Original Message-----
From: Msr6 <msr6-bounces@ietf.org> On Behalf Of Dino Farinacci
Sent: 02 November 2022 23:12
To: Toerless Eckert <tte@cs.fau.de>
Cc: Jeffrey Zhang <zzhang@juniper.net>; Xiejingrong (Jingrong) <xiejingrong=40huawei.com@dmarc.ietf.org>; BIER WG <bier@ietf.org>; msr6@ietf.org; mboned@ietf.org; pim@ietf.org
Subject: Re: [Msr6] MSR6 BOF 3rd Issue Category: More details are requested about the large scale use cases, including issue 8-11

[SNIP]

My point was that its "easier to DoS attack a data-plane then a control-plane". I didn't make any other assertions about control-plane security.

[SNIP]

No I am not. Its easier to get access to the data-plane by an ordinary user. So anyone can really attack the data-plane, and they might not even know it. I did not mention trust at all.
[DOT] In some previous project work of mine, resulting in some path-based forwarding approaches, collaborators of mine in this project looked into this issue (motivations included to set forwarding bits even accidentally to 'send all'). Some of their work can be found at http://repository.essex.ac.uk/14611/ Key to the approach was to protect the access to the data plane; in a way arguing for a control plane to do so. 

Dino

--
Msr6 mailing list
Msr6@ietf.org
https://www.ietf.org/mailman/listinfo/msr6

v2.23.0 | Report a Bug | By Email