Re: [Idr] Adoption and IPR call for draft-wang-idr-vpn-prefix-orf-03.txt (8/16 to 8/30)

王巍 <weiwang94@foxmail.com> Fri, 26 August 2022 01:45 UTC

Return-Path: <weiwang94@foxmail.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22D26C1522A4 for <idr@ietfa.amsl.com>; Thu, 25 Aug 2022 18:45:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.18
X-Spam-Level: *
X-Spam-Status: No, score=1.18 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HELO_DYNAMIC_IPADDR=1.951, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, NO_FM_NAME_IP_HOSTN=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RDNS_DYNAMIC=0.982, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=foxmail.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id brgrlXqR2gvF for <idr@ietfa.amsl.com>; Thu, 25 Aug 2022 18:44:56 -0700 (PDT)
Received: from out203-205-221-236.mail.qq.com (out203-205-221-236.mail.qq.com [203.205.221.236]) (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 6DAEEC14CE2D for <idr@ietf.org>; Thu, 25 Aug 2022 18:44:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=foxmail.com; s=s201512; t=1661478291; bh=cAn7R87WcLQ/oWWY9vJ11FBQsmiPnxN9ywF50Iu2+x8=; h=In-Reply-To:References:From:To:Subject:Date; b=tz/RTMFnj+di+buzFGKV88U/ivqE/okNz0hE9G7MJApYapYX1GM31xEyvUCt2kHB9 skqOAbAI/mv/j8I2vuYkpbvBWShB4d71JGJ0FYE+Xx8Nj4Xuqt9A8LZZFlhtZtxC6j 7MTJknubuiKfmpfkE4DjTLe2+GIcndR5KXhDm6v0=
X-QQ-FEAT: oHWrrGTW1dCGJEu1CuC8+nIWkvSYK6n9
X-QQ-SSF: 00000000000000F0000000000000
X-QQ-XMAILINFO: MJsm5enxOh0prIRLM67iK5KeWmGbIVFL34F5QLpJrpPB1m/Nmy+C9G1XM8RM+h Lsuu31lRdsa7vaBPcXRwK0tCIJmEoroshXNpHF8xzZwcIUWIwKP7tZZOf+ExalQkz3W3AUr2peM2j T4WJVWNMSjOOxffIpUpE3IYXFLFzjcnHmusIbQABCbjtAG38IapR6KfT8krRpzpnQvLEwVPJS5x/e 1w9q9+DFuCCRQ2+e9t8yaiWKsu0Ofi7fyHXZbIhZAW5jOj+gW5pkE7G7oEQP3o7KJtrc/p88SrGzI bhQeAygqpXqA/S8w7+ega0g+tCRfftA2SSkW4szedr9PARcegB3PWa4IOXaisrqlhgeVokDpD6G4i bA4xLFHhOktqYIx2PlqM6ueWGNOuH3ICc3RNWElmpBulJEHKdmjUsAFDEpBAohI7jcFEC3F/0y7rP qhOjOay9ewgcth/TGKTWnORvZDYsSRr3ldG0lYhWr9LkrPjRLXuJOS5NoWZbdIlMx4kEQFEak81u2 GxuKWcsVv6n5ZDGkRm7+eVIUoJHfUe4WQqQjkN8SHMq7cozWF76vOfC27KKC0bq7TadhYYn4h9LTc 265sDDOWK7zxYlZbaXiyTt01J6sQFfYh9fQRdCsEo3Z0SRcAzsmKfEtCJr6ZcViUX1q8NoloodXsJ RnsOQe47+lNIzW2/bq0sWO/C9YfdbBdG+XFXY38Jwan5X5cbkIMCuiD/lQTFwaGmYyfszjuhCVYgk ssTShkRzEVLzDPLgJG2ZUmnABgOesaZAfLPGGOvtQAn6vZjwTwQe3lM+GQzNIBTsSicOni3y5x66Z QxQ2/ZInRK5wvf56pvVbNHsSDLjVlLt8+3n/GX0tU0dKsITVm3t4jpG+oyFLS3KxUkmK12NoFsk/w aT0eOiOixHsp3c1jpkUUuiYv0uD6OOTvRbTbc8xM5yWRHltXiRMQYd2DQamu0CfkwY1PHkXmRk92X eJhTZ4XszyuDo1597jFrqdRlVsnw8ubIUT4/C5oWCwsxEf58Xw26ICCN5W1fXHeFcIw3cAnJJJfKi UP2XfoLzUFicC5PQ=
X-HAS-ATTACH: no
X-QQ-BUSINESS-ORIGIN: 2
X-Originating-IP: 219.142.230.39
In-Reply-To: <CO1PR13MB4920458A4769A45C51DAAB2D85729@CO1PR13MB4920.namprd13.prod.outlook.com>
References: <tencent_47E74EE633D90432AFA28EDB2ADAD3F46809@qq.com> <CO1PR13MB4920458A4769A45C51DAAB2D85729@CO1PR13MB4920.namprd13.prod.outlook.com>
X-QQ-STYLE:
X-QQ-mid: webmail812t1661478291t8581807
From: 王巍 <weiwang94@foxmail.com>
To: Linda Dunbar <linda.dunbar@futurewei.com>, Susan Hares <shares@ndzh.com>, idr <idr@ietf.org>
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_63082592_118485B0_7750AF1A"
Content-Transfer-Encoding: 8bit
Date: Fri, 26 Aug 2022 09:44:50 +0800
X-Priority: 3
Message-ID: <tencent_A8693E8C4D2713232ABB0DAD1D4F2F690E05@qq.com>
X-QQ-MIME: TCMime 1.0 by Tencent
X-Mailer: QQMail 2.x
X-QQ-Mailer: QQMail 2.x
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/n5I-thVYvixb9iECDjkbXyfnu_M>
Subject: Re: [Idr] Adoption and IPR call for draft-wang-idr-vpn-prefix-orf-03.txt (8/16 to 8/30)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Aug 2022 01:45:00 -0000

Hi Linda,



2.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Is the ORF message sent to all peers? Or just a selective peers?

“each of them makes a local judgement to determine whether it needs to send VPN Prefix ORF to its peers.”

[WW] Thanks for pointing out this typo, it should be changed to "each of them makes a local judgement to determine whether it needs to send VPN Prefix ORF to its&nbsp;upstream peer."

[Linda] For iBGP with RR distributing the UDPATE, how does the BGP speaker know who is its upstream peer?

[WW] In this case, RR is the upstream peer of the PE, it&nbsp;will do the filter work based on the received VPN Prefix ORF message for the request PE?



Best Regards,
Wei
------------------&nbsp;Original&nbsp;------------------
From:                                                                                                                        "Linda Dunbar"                                                                                    <linda.dunbar@futurewei.com&gt;;
Date:&nbsp;Fri, Aug 26, 2022 00:43 AM
To:&nbsp;"王巍"<weiwang94@foxmail.com&gt;;"Susan Hares"<shares@ndzh.com&gt;;"idr"<idr@ietf.org&gt;;

Subject:&nbsp;RE: [Idr] Adoption and IPR call for draft-wang-idr-vpn-prefix-orf-03.txt (8/16 to 8/30)



  
Wei, 
 
&nbsp;
 
Thank you for addressing my comments. 
 
&nbsp;
 
See my replies inserted below: 
 
&nbsp;
 
&nbsp;
  
From: 王巍 <weiwang94@foxmail.com&gt; 
 Sent: Tuesday, August 23, 2022 10:32 PM
 To: Linda Dunbar <linda.dunbar@futurewei.com&gt;; Susan Hares <shares@ndzh.com&gt;; idr <idr@ietf.org&gt;
 Subject: Re: [Idr] Adoption and IPR call for draft-wang-idr-vpn-prefix-orf-03.txt (8/16 to 8/30)
 
 
&nbsp;
  
Hi Linda,
 
  
&nbsp; &nbsp;Thanks for your comments, and please see my reply inline.
 
  
&nbsp;
 
   
Best Regards,
 
  
Wei
 
  
------------------ Original ------------------
 
   
From: "Linda Dunbar" <linda.dunbar@futurewei.com&gt;;
 
  
Date:&nbsp;Wed, Aug 24, 2022 02:26 AM
 
  
To:&nbsp;"Susan Hares"<shares@ndzh.com&gt;;"idr@ietf.org"<idr@ietf.org&gt;;
 
  
Subject:&nbsp;Re: [Idr] Adoption and IPR call for draft-wang-idr-vpn-prefix-orf-03.txt (8/16 to 8/30)
 
 
  
&nbsp;
 
  
Wei, Aijun, et al, 
 
&nbsp;
 
I forget to include the questions about draft at my last support message:
 
 1.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;  Page 3 says: 
 
&nbsp;if the "trashing routes" come from the interested VRF, filter on RTs will erase all prefixes from this VRF.
 
&nbsp;
 
why erase all prefixes even if the “trashing routes” only contain a subset of prefixes for the VRF?
 
&nbsp;[WW] RTC aims to tell the peer "I want to receive VPN routes with RTx", if the offending routes carry RTx, RTC can't tell the peer to stop sending these  routes unless withdraw the entry with RTx. 
 
How about the following updated sentence?
 
"RTC can only filter the VPN routes from the uninterested VRFs, if the "offending routes" come from the interested VRF, RFC mechanism can't filter them."
 
[Linda] that is much better. 
 
&nbsp;
 
 2.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;  Is the ORF message sent to all peers? Or just a selective peers?
 
“each of them makes a local judgement to determine whether it needs to send VPN Prefix ORF to its peers.”
 
[WW] Thanks for pointing out this typo, it should be changed to "each of them makes a local judgement to determine whether it needs to send VPN Prefix ORF to its upstream peer."
 
[Linda] For iBGP with RR distributing the UDPATE, how does the BGP speaker know who is its upstream peer? 
 
&nbsp;
 
NITs: 
 
Past 6: (you need to do a global change.)
 
past  à passed:
 
When routes associated with <RD31, PE3&gt; tuple past the quota but the prefix limit of VPN1 VRF is not exceeded,
 
[WW] Thanks, will correct this typo in next update.
 
&nbsp;
 
Linda Dunbar
 
&nbsp;
   
From: Linda Dunbar 
 Sent: Tuesday, August 23, 2022 11:03 AM
 To: Susan Hares <shares@ndzh.com&gt;;  idr@ietf.org
 Subject: RE: Adoption and IPR call for draft-wang-idr-vpn-prefix-orf-03.txt (8/16 to 8/30)
 
 
 
&nbsp;
 
&nbsp;
  
Hi Everyone,
 
  
&nbsp;
 
  
&nbsp; &nbsp; I read the draft and all the discussion on the mailing list. I think adopting to WG draft can further &nbsp;improve the draft with more WG &nbsp;discussions. Therefore I support its adoption.
 
  
&nbsp;
 
  
Best Regards,
 
  
Linda
 
&nbsp;
 
  
 
  
From: Idr <idr-bounces@ietf.org&gt; on behalf of Susan Hares <shares@ndzh.com&gt;
 Sent: Tuesday, August 16, 2022 11:55 AM
 To: idr@ietf.org <idr@ietf.org&gt;
 Subject: [Idr] Adoption and IPR call for draft-wang-idr-vpn-prefix-orf-03.txt (8/16 to 8/30) 
  
&nbsp;
 
 
   
This begins a 2 week WG Adoption call for draft-wang-idr-vpn-prefix-orf-03.txt
 
https://datatracker.ietf.org/doc/draft-wang-idr-vpn-prefix-orf/
 
&nbsp;
 
The authors believe that they have addressed the concerns raised in 
 
the previous 2 WG adoption calls.
 
&nbsp;
 
The WG should consider if:
 
&nbsp;
 
1) The revised text answers the previous concerns regarding 
 
the scope of this draft? 
 
&nbsp;
 
2) Does the revised text provide a useful function for  
 
networks? 
 
&nbsp;
 
3) Are there any additional concerns regarding the new text? 
 
&nbsp;
 
Each of the authors should send an IPR statement for 
 
this version of the draft. 
 
&nbsp;
 
The adoption call was moved to 8/29 to 8/30 to allow questions 
 
to be asked at the IDR interim meeting on 8/29/2022 (10am – 12pm EDT). 
 
&nbsp;
 
Cheers, Sue Hares &nbsp;