IETF Logo Mail Archive

Re: [Sidrops] [GROW] IXP Route Server question

Zhuangshunwan <zhuangshunwan@huawei.com> Mon, 14 March 2022 01:45 UTC

Return-Path: <zhuangshunwan@huawei.com>
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 5F7BE3A18A7; Sun, 13 Mar 2022 18:45:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level:
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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=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 urRvZJxVAhgR; Sun, 13 Mar 2022 18:45:26 -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 EF3A93A0C66; Sun, 13 Mar 2022 18:45:25 -0700 (PDT)
Received: from fraeml702-chm.china.huawei.com (unknown [172.18.147.206]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4KGzqZ4xNfz67ts3; Mon, 14 Mar 2022 09:44:42 +0800 (CST)
Received: from kwepeml100001.china.huawei.com (7.221.188.249) by fraeml702-chm.china.huawei.com (10.206.15.51) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2375.24; Mon, 14 Mar 2022 02:45:22 +0100
Received: from kwepeml500004.china.huawei.com (7.221.188.141) by kwepeml100001.china.huawei.com (7.221.188.249) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2308.21; Mon, 14 Mar 2022 09:45:21 +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; Mon, 14 Mar 2022 09:45:21 +0800
From: Zhuangshunwan <zhuangshunwan@huawei.com>
To: "Sriram, Kotikalapudi (Fed)" <kotikalapudi.sriram@nist.gov>
CC: "grow@ietf.org" <grow@ietf.org>, "sidrops@ietf.org" <sidrops@ietf.org>
Thread-Topic: [GROW] IXP Route Server question
Thread-Index: AdgzI9AeBV4234ykpkmw38R5LhMrNQAD5f2AAD5dAsAAYRU1MABRQkygABOGoeA=
Date: Mon, 14 Mar 2022 01:45:20 +0000
Message-ID: <2ad9d317fdf9441aa207628d4bfd6098@huawei.com>
References: <SA1PR09MB8142093BE50A27A7EED132D884099@SA1PR09MB8142.namprd09.prod.outlook.com> <0db7749f-66fd-5def-a8bb-3ee316cf2ca1@foobar.org> <SA1PR09MB81421BCBA7FB59615A7638A5840B9@SA1PR09MB8142.namprd09.prod.outlook.com> <82b678f2254b42fabe3bfbcef4b8d28c@huawei.com> <SA1PR09MB81423C2B4C924D886C030365840E9@SA1PR09MB8142.namprd09.prod.outlook.com>
In-Reply-To: <SA1PR09MB81423C2B4C924D886C030365840E9@SA1PR09MB8142.namprd09.prod.outlook.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/sidrops/Vty8cHmKqgC4r3FLJm6gAswTvNk>
Subject: Re: [Sidrops] [GROW] IXP Route Server question
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: Mon, 14 Mar 2022 01:45:31 -0000

Hi Sriram,

Thanks for your pointers! I will read them carefully.

Best regards,
Shunwan

> -----Original Message-----
> From: Sriram, Kotikalapudi (Fed) [mailto:kotikalapudi.sriram@nist.gov]
> Sent: Monday, March 14, 2022 12:45 AM
> To: Zhuangshunwan <zhuangshunwan@huawei.com>
> Cc: grow@ietf.org; sidrops@ietf.org
> Subject: RE: [GROW] IXP Route Server question
> 
> Hi Shunwan,
> 
> >> The ASPA verification draft treats the relationship of RS to
> >> RS-client as similar to that of Provider to Customer. Seems
> >> reasonable? The AS of an RS client includes the RS's AS in its ASPA as a
> "Provider".
> 
> >IMO, the ASPA verification draft regards the relationship between RS
> >and RS-client as "peer-to-peer",
> 
> That is not correct.
> 
> >maybe my understanding is wrong, I will read the ASPA verification draft
> again.
> 
> OK. Just FYI... the draft needs a revision. It does not contain yet the enhanced
> ASPA upstream/downstream verification algorithms/procedures. Not sure if
> you've followed sidrops discussions on the algorithms since January 2021.
> Some pointers:
> https://datatracker.ietf.org/meeting/110/materials/slides-110-sidrops-srira
> m-aspa-alg-accuracy-01
> https://mailarchive.ietf.org/arch/msg/sidrops/C6Ethp2aC9sJsxDtBrLQDjmCq
> k4/
> 
> Thanks.
> 
> Sriram
> 
> 
> 
> 
> 
>

v2.8.7 | Report a Bug | By Email