IETF Logo Mail Archive

Re: [Sidrops] question on draft-ietf-sidrops-aspa-verification-04

"Guyunan (Yunan Gu, IP Technology Research Dept. NW)" <guyunan@huawei.com> Tue, 12 May 2020 07:12 UTC

Return-Path: <guyunan@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 436873A0C93 for <sidrops@ietfa.amsl.com>; Tue, 12 May 2020 00:12:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=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 1JN_BcDk0XRo for <sidrops@ietfa.amsl.com>; Tue, 12 May 2020 00:12:06 -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 CCDFC3A09FA for <sidrops@ietf.org>; Tue, 12 May 2020 00:12:05 -0700 (PDT)
Received: from lhreml701-chm.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 312C77C604D9EAB0FC8B for <sidrops@ietf.org>; Tue, 12 May 2020 08:12:04 +0100 (IST)
Received: from lhreml701-chm.china.huawei.com (10.201.108.50) by lhreml701-chm.china.huawei.com (10.201.108.50) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1913.5; Tue, 12 May 2020 08:12:03 +0100
Received: from DGGEML403-HUB.china.huawei.com (10.3.17.33) by lhreml701-chm.china.huawei.com (10.201.108.50) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256) id 15.1.1913.5 via Frontend Transport; Tue, 12 May 2020 08:12:03 +0100
Received: from DGGEML532-MBX.china.huawei.com ([169.254.8.202]) by DGGEML403-HUB.china.huawei.com ([fe80::74d9:c659:fbec:21fa%31]) with mapi id 14.03.0487.000; Tue, 12 May 2020 15:11:59 +0800
From: "Guyunan (Yunan Gu, IP Technology Research Dept. NW)" <guyunan@huawei.com>
To: Jay Borkenhagen <jayb@braeburn.org>
CC: SIDR Operations WG <sidrops@ietf.org>
Thread-Topic: [Sidrops] question on draft-ietf-sidrops-aspa-verification-04
Thread-Index: AdYdy08vebzctU/sRBSjzmRHyKjH2ACpL0yAALmBBzAA2L1MAAAdy1hgAArDfQAANA3jsA==
Date: Tue, 12 May 2020 07:11:58 +0000
Message-ID: <C01B0098369B2D4391851938DA6700B717A2CABA@DGGEML532-MBX.china.huawei.com>
References: <C01B0098369B2D4391851938DA6700B7179F9EAB@dggeml512-mbs.china.huawei.com> <CAEGSd=APMCnnd5mrnMKtti-QWy1m7r5JfJsf7HynZqyXWwsZHg@mail.gmail.com> <C01B0098369B2D4391851938DA6700B717A0C386@DGGEML532-MBX.china.huawei.com> <CAEGSd=Bk3Lgte1L0KKP_GU+ieDpETvLk1JTVTLZTv-Z5NrVUoQ@mail.gmail.com> <C01B0098369B2D4391851938DA6700B717A28020@DGGEML532-MBX.china.huawei.com> <24249.23930.126312.2484@oz.mt.att.com>
In-Reply-To: <24249.23930.126312.2484@oz.mt.att.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.108.203.151]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/Cb9Cs2SFm5XythPicRqWVScBnTM>
Subject: Re: [Sidrops] question on draft-ietf-sidrops-aspa-verification-04
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, 12 May 2020 07:12:07 -0000

Hi Jay,

"mutual transit" sounds like a proper term to me and to be used here!

BR,
Yunan

-----Original Message-----
From: Jay Borkenhagen [mailto:jayb@braeburn.org] 
Sent: Monday, May 11, 2020 10:13 PM
To: Guyunan (Yunan Gu, IP Technology Research Dept. NW) <guyunan@huawei.com>
Cc: SIDR Operations WG <sidrops@ietf.org>
Subject: Re: [Sidrops] question on draft-ietf-sidrops-aspa-verification-04

Guyunan (Yunan Gu, IP Technology Research Dept. NW) writes:

 > > And a final question about Section 7 Siblings (Complex Relations), regardless of the current description of what sibling relation is, do we think that sibling ASes are ASes that belong to the same operator? So any type of transition is free of charge?
 > Speaking about ASPA, we are speaking about peering relations, without any guess about the business between parties.
 > And from what I know - siblings are also spread among small networks, so this term is not strictly bound to the same administrative domain.
 >
 > Yunan: well, I’m trying to understand what it means by “sibling”. Your draft defines how ASPA records are created for “sibling” relations, but no precise definition is given (only examples). I understand It is a complex relation, as stated in the draft, but still, I’m confused of the actual peering relations when we talk about “sibling”. Can you maybe provide a more specific text definition?
 > 

Hi Yunan,

I also find the term 'siblings' to be confusing and potentially misleading in the ASPA context, since it implies common parentage.  I believe that there is one and only one such 'complex relation' to be called out in ASPA verification, and that would be accurately described as 'mutual transit': ASes mutually agreeing to send prefixes received from each other to their peers and upstreams.

Would your request for clarification be met by the draft replacing its use of the term 'siblings' with 'mutual transit'?

Thanks.

						Jay B.

v2.23.0 | Report a Bug | By Email