Re: [Sidrops] [routing-wg] misconceptions about ROV

Di Ma <madi@juicybun.cn> Tue, 22 February 2022 00:43 UTC

Return-Path: <madi@juicybun.cn>
X-Original-To: sidrops@ietfa.amsl.com
Delivered-To: sidrops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A08933A0EBD for <sidrops@ietfa.amsl.com>; Mon, 21 Feb 2022 16:43:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level:
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_NONE=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 kqCoWIZ_WHtu for <sidrops@ietfa.amsl.com>; Mon, 21 Feb 2022 16:43:38 -0800 (PST)
Received: from smtpbgau1.qq.com (smtpbgau1.qq.com [54.206.16.166]) (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 926C63A0EB7 for <sidrops@ietf.org>; Mon, 21 Feb 2022 16:43:36 -0800 (PST)
X-QQ-mid: bizesmtp65t1645490607t5cskiu0
Received: from smtpclient.apple (unknown [111.199.191.176]) by bizesmtp.qq.com (ESMTP) with id ; Tue, 22 Feb 2022 08:43:27 +0800 (CST)
X-QQ-SSF: 00100000000000D0W000B00A0000000
X-QQ-FEAT: F3yR32iATbgZf46s7riI7nYEVxYVD6dvJwATN6GgLrBIR1wbbyOlV92YDvrep xJtQ+2nO91+foKKN94+P/eEyl29mhdA1+hGS0RnYSjtowmeXSzH02D2kZZ6ui4Ij/oPyXkZ 8G4XH7Xo2F3RjRCqFIRbjlGtx780IMxQj3si4/VaORe9KDrwefpknv0dMJhAw3BabnI3hnF WfNLZwfv7kfGgFaRyAnHw/ro1F825zhspKMl2QJvuIH+CuP56ZPlpIMpM+Dwd9OgpVSCgsB UBbrnXKqjv4m7VXLEr+XV7IUw/UKhyJb6MP3M0O2/yw0ygyu31i2o3RnhN4GYxdKmGd0w5c ucz4Y1Z+DPqMeQWjwM=
X-QQ-GoodBg: 0
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.40.0.1.81\))
From: Di Ma <madi@juicybun.cn>
In-Reply-To: <m2h78roqbp.wl-randy@psg.com>
Date: Tue, 22 Feb 2022 08:43:26 +0800
Cc: SIDR Operations WG <sidrops@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <7FBC2063-2404-4BF9-836E-210629C4BA63@juicybun.cn>
References: <m2h78roqbp.wl-randy@psg.com>
To: Randy Bush <randy@psg.com>
X-Mailer: Apple Mail (2.3693.40.0.1.81)
X-QQ-SENDSIZE: 520
Feedback-ID: bizesmtp:juicybun.cn:qybgforeign:qybgforeign1
X-QQ-Bgrelay: 1
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/wj3dkGrx5DmPytMqgZCSC9QhQ0k>
Subject: Re: [Sidrops] [routing-wg] misconceptions about ROV
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: A list for the SIDR Operations WG <sidrops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidrops>, <mailto:sidrops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidrops/>
List-Post: <mailto:sidrops@ietf.org>
List-Help: <mailto:sidrops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidrops>, <mailto:sidrops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Feb 2022 00:43:43 -0000

Randy,

I don’t care the way we/they see ROV but the way we use it.

ROV is good as long as it can remedy accidental misconfigurations that bring about routing security problem/catastrophe.

If someone doesn't  think ROV is not a security mechanism from cryptography perspective, I settle for that.

Di

> 2022年2月22日 05:35,Randy Bush <randy@psg.com> 写道:
> 
> i should not have to say this, but ...
> 
> 
> From: Randy Bush <randy@psg.com>
> Subject: [routing-wg] misconceptions about ROV
> To: RIPE Routing WG <routing-wg@ripe.net>
> Date: Mon, 21 Feb 2022 13:13:00 -0800
> 
> lately, i am getting flak about ROV not providing protection from
> this or that malicious attack.  indeed it does not.
> 
> in the ROV design, we DELIBERATELY did NOT try to cover malicious
> attacks.  we also did not try to solve world hunger.
> 
> repeat 20 times: "ROV is not a security mechanism.  it is only meant
> to ameliorate accidental misconfigurations."
> 
> yes, a screwdriver sucks as a hammer.
> 
> we do seem to see that route mis-originations are propagating less
> widely; and presume this is due to ROV, especially in top tier
> providers.  this is good.
> 
> and once more for good luck: "ROV is not a security mechanism.  it
> is only meant to ameliorate accidental misconfigurations."
> 
> randy
> 
> _______________________________________________
> Sidrops mailing list
> Sidrops@ietf.org
> https://www.ietf.org/mailman/listinfo/sidrops
>