IETF Logo Mail Archive

Re: [savnet] A variation of DSAV as a BGP extension

Zhuangshunwan <zhuangshunwan@huawei.com> Tue, 22 March 2022 06:43 UTC

Return-Path: <zhuangshunwan@huawei.com>
X-Original-To: savnet@ietfa.amsl.com
Delivered-To: savnet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 53A313A0932 for <savnet@ietfa.amsl.com>; Mon, 21 Mar 2022 23:43:55 -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_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=unavailable 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 TKookwmrpKom for <savnet@ietfa.amsl.com>; Mon, 21 Mar 2022 23:43:51 -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 608403A0933 for <savnet@ietf.org>; Mon, 21 Mar 2022 23:43:51 -0700 (PDT)
Received: from fraeml705-chm.china.huawei.com (unknown [172.18.147.200]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4KN2331nZJz67rcd for <savnet@ietf.org>; Tue, 22 Mar 2022 14:42:07 +0800 (CST)
Received: from kwepeml500002.china.huawei.com (7.221.188.128) by fraeml705-chm.china.huawei.com (10.206.15.54) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2375.24; Tue, 22 Mar 2022 07:43:47 +0100
Received: from kwepeml500004.china.huawei.com (7.221.188.141) by kwepeml500002.china.huawei.com (7.221.188.128) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2308.21; Tue, 22 Mar 2022 14:43:46 +0800
Received: from kwepeml500004.china.huawei.com ([7.221.188.141]) by kwepeml500004.china.huawei.com ([7.221.188.141]) with mapi id 15.01.2308.021; Tue, 22 Mar 2022 14:43:46 +0800
From: Zhuangshunwan <zhuangshunwan@huawei.com>
To: "Lubashev, Igor" <ilubashe=40akamai.com@dmarc.ietf.org>, "savnet@ietf.org" <savnet@ietf.org>
Thread-Topic: A variation of DSAV as a BGP extension
Thread-Index: Adg9nfAO1hcZ2EGeTFq3J3oLqYsPuwAGdakA
Date: Tue, 22 Mar 2022 06:43:46 +0000
Message-ID: <df5f92221b7f4f95a8c354cfd97e8879@huawei.com>
References: <dcf252ce9dd04cb58fba15d5e5e228dd@ustx2ex-dag1mb5.msg.corp.akamai.com>
In-Reply-To: <dcf252ce9dd04cb58fba15d5e5e228dd@ustx2ex-dag1mb5.msg.corp.akamai.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.108.152.178]
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/savnet/Bkk5QXYOM29U1jj90zeZIp4NNfU>
Subject: Re: [savnet] A variation of DSAV as a BGP extension
X-BeenThere: savnet@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <savnet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/savnet>, <mailto:savnet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/savnet/>
List-Post: <mailto:savnet@ietf.org>
List-Help: <mailto:savnet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/savnet>, <mailto:savnet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Mar 2022 06:43:56 -0000

Hi Igor,

Thank you for sharing the useful information! 
Do you have a relevant draft for this new BGP SAFI?

Kind Regards,
Shunwan

> -----Original Message-----
> From: savnet [mailto:savnet-bounces@ietf.org] On Behalf Of Lubashev, Igor
> Sent: Tuesday, March 22, 2022 12:15 PM
> To: savnet@ietf.org
> Subject: [savnet] A variation of DSAV as a BGP extension
> 
> I am glad to see some renewed attention paid to SAV.
> 
> Here is a quick proposal I've made on the topic @ IETF-101.
> https://datatracker.ietf.org/meeting/101/materials/slides-101-rtgwg-sessb-i
> ngress-filtering-for-asymmetric-routing-01
> 
> The quick summary of the above:
> 
> 1. We have a problem today, because we use the same BGP reachability
> advertisements for two separate purposes: advertising reachability and SAV.
> 
> 2. The proposal is a creation of a new "SAV Allow" SAFI. Advertisements with
> "SAV Allow" SAFI are never used for forwarding and can only be used for SAV.
> 2a. The advertisements are secured against spoofing by all the usual means
> that BGP advertisements are secured.
> 2b. "SAV Allow" SAFI advertisements are transitive, unless a route (a regular
> or "SAV Allow") with the same or a shorter prefix is advertised to a peer. This
> is because the advertised route already serves "SAV Allow" purpose.
> 2c. Only routers that support "SAV Allow" SAFI get these advertisements.
> 
> 3. The upside is that this seems like it would solve SAV problem and use just
> a simple BGP extension for it. The downside is that incremental deployment
> can only start with the routers that are originating the routes -- upgrading an
> intermediary router does no good, unless all routers between the path
> originator and itself have been upgraded.
> 3a. Compared to RFC8704, RFC8704 does not solve SAV completely, but it
> allows for a much looser increment deployment to be useful.
> 
> Happy to discuss this more, of course.
> 
> - Igor
> 
> --
> savnet mailing list
> savnet@ietf.org
> https://www.ietf.org/mailman/listinfo/savnet

v2.8.7 | Report a Bug | By Email