Return-Path: X-Original-To: bess@ietfa.amsl.com Delivered-To: bess@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7DFDD1270FC for ; Thu, 21 Dec 2017 01:23:11 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.23 X-Spam-Level: X-Spam-Status: No, score=-4.23 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 XsUkzZkT44bm for ; Thu, 21 Dec 2017 01:23:09 -0800 (PST) Received: from huawei.com (lhrrgout.huawei.com [194.213.3.17]) (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 315BA1200FC for ; Thu, 21 Dec 2017 01:23:09 -0800 (PST) Received: from lhreml706-cah.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id E6AF72866BE0D for ; Thu, 21 Dec 2017 09:23:05 +0000 (GMT) Received: from NKGEML411-HUB.china.huawei.com (10.98.56.70) by lhreml706-cah.china.huawei.com (10.201.108.47) with Microsoft SMTP Server (TLS) id 14.3.361.1; Thu, 21 Dec 2017 09:23:07 +0000 Received: from NKGEML514-MBS.china.huawei.com ([169.254.3.248]) by nkgeml411-hub.china.huawei.com ([10.98.56.70]) with mapi id 14.03.0361.001; Thu, 21 Dec 2017 17:22:56 +0800 From: Xiejingrong To: "bess@ietf.org" CC: Xiejingrong Thread-Topic: [bess] Comments on draft-ietf-bess-mvpn-expl-track-03 Thread-Index: AdN6NEanDCpPv20UQYKcimcePljNRg== Date: Thu, 21 Dec 2017 09:22:56 +0000 Message-ID: <16253F7987E4F346823E305D08F9115A99A06375@nkgeml514-mbs.china.huawei.com> Accept-Language: zh-CN, en-US Content-Language: zh-CN X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.111.217.214] Content-Type: multipart/alternative; boundary="_000_16253F7987E4F346823E305D08F9115A99A06375nkgeml514mbschi_" MIME-Version: 1.0 X-CFilter-Loop: Reflected Archived-At: Subject: [bess] Comments on draft-ietf-bess-mvpn-expl-track-03 X-BeenThere: bess@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: BGP-Enabled ServiceS working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Dec 2017 09:23:11 -0000 --_000_16253F7987E4F346823E305D08F9115A99A06375nkgeml514mbschi_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I have a comment on draft-ietf-bess-mvpn-expl-track-03. The chap 5.3 of this document said: Furthermore, if the PTA specifies "no tunnel info", the LIR and LIR-pF flags in the PTA MUST be passed along unchanged. This will ensure that an egress ABR/ASBR only sends a Leaf A-D route in response to a "match for tracking" if it is on the path to an egress PE for the flow(s) identified in the corresponding S-PMSI A-D route. The issue is as follow: In a [IngressPE--EgressABR--EgressPE] topology, IngressPE send a Wildcard S= -PMSI(*,*) route with PTA(flag), whose NLRI is donated as SPMS= I(type<0/1/2>RD,*,*,IngressPE). This SPMSI route will be relayed by EgressA= BR to EgressPE with PTA flag untouched. Then EgressPE will generate ONE Lea= fAD route with NLRI(type<0/1/2>RD,*,*,IngressPE,EgressPE) and RT= and N(N>=3D0) LeafAD routes with NLRI(type<16/17/18>RD,S,G,IngressPE,Egres= sPE) and RT. All according to chap 5.2 of this document. Then according to chap 5.3 of this document: IngressABR will only send a Leaf A-D route, It should be the ONE of LeafAD(= type<0/1/2RD,*,*,IngressPE,EgressABR) with RT. Then how should IngressABR deal with the the N(N>=3D0) LeafAD routes with N= LRI(type<16/17/18>RD,S,G,IngressPE,EgressPE) and RT ? It is not clarified in RFC7524 either. See chap 7.1 of RFC7524, which only = clarify LeafAD route with type<0/1/2>RD. Should such LeafAD route with type<16/17/18>RD be accepted and installed by= EgressABR, and then 'relay' back to IngressPE, and thus enable IngressPE e= xplicit tracking inside the ingress "segmentation domain" ? Thanks. XieJingrong --_000_16253F7987E4F346823E305D08F9115A99A06375nkgeml514mbschi_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

 

I have a comment on draft-ietf-bess-mvpn-expl-= track-03.

 

The chap 5.3 of this document said:=

 

Furthermore, if the PTA specifies "no tunnel info&= quot;, the LIR and LIR-pF

flags in the PTA MUST be passed along unchanged.

 

   This will ensure that an egress A= BR/ASBR only sends a Leaf A-D route 

   in response to a "match for = tracking" if it is on the path to an

   egress PE for the flow(s) identif= ied in the corresponding S-PMSI A-D

   route.

 

The issue is as follow:

In a [IngressPE--EgressABR--EgressPE] topology= , IngressPE send a Wildcard S-PMSI(*,*) route with PTA(flag<LIR+LIR-= pF>), whose NLRI is donated as  SPMSI(type<0/1/2>RD,*,*,IngressPE). T= his SPMSI route will be relayed by EgressABR to EgressPE with PTA flag unto= uched. Then EgressPE will generate ONE LeafAD route with NLRI(type<0/1/2= >RD,*,*,IngressPE,EgressPE) and RT<EgressABR> and N(N>=3D0) LeafAD routes with NLRI(type<16/17/18>RD,S,G,Ingres= sPE,EgressPE) and RT<EgressABR>. All according to chap 5.2 of this do= cument.

 

Then according to chap 5.3  of this docum= ent:

IngressABR will only send a Leaf A-D route, It= should be the ONE of LeafAD(type<0/1/2RD,*,*,IngressPE,EgressABR) with RT<IngressABR>.

Then how should IngressABR deal with the the N= (N>=3D0) LeafAD routes with NLRI(type<16/17/18>RD,S,G,IngressPE,Eg= ressPE) and RT<EgressABR> ?

It is not clarified in RFC7524 either. See cha= p 7.1 of RFC7524, which only clarify LeafAD route with type<0/1/2>RD.

Should such LeafAD route with type<16/17/18= >RD be accepted and installed by EgressABR, and then ‘relay’ back to IngressPE, and thus enable IngressPE explicit tracking inside the = ingress “segmentation domain” ?

 

Thanks.

 

XieJingrong

 

 

 

--_000_16253F7987E4F346823E305D08F9115A99A06375nkgeml514mbschi_--