Re: [Idr] WG LC on draft-ietf-idr-rpd-05.txt (7/15 to 7/29/2020)

"duzongpeng@foxmail.com" <duzongpeng@foxmail.com> Tue, 28 July 2020 02:14 UTC

Return-Path: <duzongpeng@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 B4CA73A0ADA for <idr@ietfa.amsl.com>; Mon, 27 Jul 2020 19:14:36 -0700 (PDT)
X-Quarantine-ID: <y7J8WJBwZ1mI>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "Message-ID"
X-Spam-Flag: NO
X-Spam-Score: 0.495
X-Spam-Level:
X-Spam-Status: No, score=0.495 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_FROM=0.001, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_SORBS_WEB=1.5, RDNS_DYNAMIC=0.982, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y7J8WJBwZ1mI for <idr@ietfa.amsl.com>; Mon, 27 Jul 2020 19:14:32 -0700 (PDT)
Received: from qq.com (out203-205-221-143.mail.qq.com [203.205.221.143]) (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 6B48E3A0AD6 for <idr@ietf.org>; Mon, 27 Jul 2020 19:14:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=foxmail.com; s=s201512; t=1595902455; bh=lhaF4b0FdSWH0foerFrzZgc5lKbQ86E2v/vbAFvNcXg=; h=Date:From:To:Cc:Subject:References; b=bFBIuDcD0xIm6OKr3alhy9OWo5nj3cY4yJH34zLa8B6k0LUgBoKpQ6JbqL5iAAWd0 xqmiLCAXvpH+yoGucBYMXzW40qhYPqMulN9WxTnTI/MC7mB58DlNhBDPJXKPUjXaxl hgOmnzHcnDOOKeQSUf/9PnwjMYlHJPUM5kI8tHHY=
Received: from cmcc-PC ([221.130.253.135]) by newxmesmtplogicsvrszc9.qq.com (NewEsmtp) with SMTP id 38C920D7; Tue, 28 Jul 2020 10:14:12 +0800
X-QQ-mid: xmsmtpt1595902452tk5z7u1ki
Message-ID: <tencent_B4E58450E63EC4EC3A7C6B6D6D6AD7510408@qq.com>
X-QQ-XMAILINFO: Obc4w59CnLkmYFvBZFLzNCPHFwbxb+07oR5s7pB0oK/h4F3vwvmN1bVhXrtcXG GRc5H0G/qSAGJ25nQLjz+vp8x0PfFEo3jmByYNUwM2pRJzUudQi+fqyqoyvpZDMqBpTbJoP+FBHq GA0wfjLyKmqHRkXaOZPkeP5+hN0qLMRzrVtR+PjOgwW0OOzfC5+QYQnDgrQYPYo3fLzH+3zNBi9p lZgxygtg+nfa/w0tQMBwffDcAPM7+dqICtcbal+z0SzhVArwYtSCu7eqV2N8QDMJAvrTM2zuvWFA QbF4doXrTaUUlLuoF+K06vsjKP7rWOE4DR1os/wLW5gRT1nhpxMf1AT4wlA97b22syEhwGOydwBq McNGPpGicuSgIqckO8ALa89Ca71FhExhR3Rx5MOV45pnBC6Xs41xvYVntUL+GIZLMSBBo3oL9Thr nens0l41mwUFdTK58G3qu2ZvTvjM7p9T6bVrK5WeddBDfbspMyoghfFq+n06Q5tSwejGdslEw7tc le+9N+cCM/4sF/it+1lezrT/WL1BMUhh2tP9WyNdGbIWdMY5qHq0c0LuTzeHbpwSZYzXqza02T4u okz+fO4JgORfi3VIOM1gtmx5G7FhYh2+PEii//V0+xkFcAfVjhmOfo1R0ML9REouQpZ2FiAtqcd9 drmGdln63yKB8fFOBUTZFCnJGK4A1mNYNT2JBm2VSN56VOGIwoVrEk/JhmjGLpKYDpaEcWS1oVQ6 zxljGDZqIZfYI=
Date: Tue, 28 Jul 2020 10:16:22 +0800
From: "duzongpeng@foxmail.com" <duzongpeng@foxmail.com>
To: Zhuangshunwan <zhuangshunwan@huawei.com>, "Brendon H" <brendonholm@outlook.com>, "Robert Raszuk" <robert@raszuk.net>, "Huaimo Chen" <huaimo.chen@futurewei.com>
Cc: "idr@ietf. org" <idr@ietf.org>, "Ketan Talaulikar \(ketant\)" <ketant=40cisco.com@dmarc.ietf.org>, "Susan Hares" <shares@ndzh.com>
References: <003701d65aa9$689a64d0$39cf2e70$@ndzh.com>, <CAOj+MMGG6usHpQrn020LwWd7obt8PRPk9oii1drk0UPhyG5_gw@mail.gmail.com>, <MW3PR11MB457041054724225FB0DEB25DC1760@MW3PR11MB4570.namprd11.prod.outlook.com>, <MN2PR13MB3117CEF5726D2711D21C97BBF2720@MN2PR13MB3117.namprd13.prod.outlook.com>, <CAOj+MMGZPi16FUSwn4N4q23RLhDtCmYbSjm6_P0K5OJ3KnZinQ@mail.gmail.com>, <PS1PR06MB28075D03037399E557A93163A4720@PS1PR06MB2807.apcprd06.prod.outlook.com>, <c32cd36d681d48dbb008b69fcb544db2@huawei.com>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7.2.16.188[cn]
Mime-Version: 1.0
Message-ID: <202007281016211860184@foxmail.com>
Content-Type: multipart/alternative; boundary="----=_001_NextPart317575173378_=----"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/0JRErKf6TpP48C7vtHRhZLBDOhk>
Subject: Re: [Idr] WG LC on draft-ietf-idr-rpd-05.txt (7/15 to 7/29/2020)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 28 Jul 2020 02:14:37 -0000

Hi all,

    IMO, it is a valuable exploration to enable more convenient negotiation in the network. 
    Perhaps, multiple solutions exist here, and the authors should clarify the difference. 
    I support of pushing it forward. 

Best Regards
Zongpeng Du



duzongpeng@foxmail.com & duzongpeng@chinamobile.com
 
From: Zhuangshunwan
Date: 2020-07-28 08:13
To: Brendon H; Robert Raszuk; Huaimo Chen
CC: idr@ietf. org; Ketan Talaulikar \(ketant\); Susan Hares
Subject: Re: [Idr] WG LC on draft-ietf-idr-rpd-05.txt (7/15 to 7/29/2020)
Hi all,
 
Thanks for your review and comments!
 
If we believe that wide community is an acceptable solution, then we will realize that RPD is a good use case to push the wide community forward.
 
RPD = New SAFI + wide community, and it is implemented in one administrator domain.
RPD can implement dynamic routing policy management per peer, per node, and per administrator domain.
And it can apply some optimization operations on the existing network. When the optimization operations are canceled, the network can return to the original running status.
 
Best regards,
Shunwan
 
From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Brendon H
Sent: Tuesday, July 28, 2020 7:42 AM
To: Robert Raszuk <robert@raszuk.net>et>; Huaimo Chen <huaimo.chen@futurewei.com>
Cc: idr@ietf. org <idr@ietf.org>rg>; Ketan Talaulikar (ketant) <ketant=40cisco.com@dmarc.ietf.org>rg>; Susan Hares <shares@ndzh.com>
Subject: Re: [Idr] WG LC on draft-ietf-idr-rpd-05.txt (7/15 to 7/29/2020)
 
 
sorry i've come in late on this "hot" topic, but after reviewing all the information.
i too agree with Roberts answer.
 
With regard to the questions posed by Susan.
 
Ad 1) No.
Ad 2) No.
Ad 3) No.
Ad 4) No.
Ad 5) Yes.
 
 
kind regards,
 
Brendon
 
 
Sent from Outlook


From: Idr <idr-bounces@ietf.org> on behalf of Robert Raszuk <robert@raszuk.net>
Sent: 28 July 2020 08:02
To: Huaimo Chen <huaimo.chen@futurewei.com>
Cc: idr@ietf. org <idr@ietf.org>rg>; Ketan Talaulikar (ketant) <ketant=40cisco.com@dmarc.ietf.org>rg>; Susan Hares <shares@ndzh.com>
Subject: Re: [Idr] WG LC on draft-ietf-idr-rpd-05.txt (7/15 to 7/29/2020) 
 
 
> [HC]: Yang model seems mainly used in relatively static or stable configurations.  
 
Well that's a problem with the "user" or bad habits not with the YANG model itself. 
 
Nothing stops to use config push as dynamically as required to network elements.
 
Best,
Robert.
 
 
On Mon, Jul 27, 2020 at 10:57 PM Huaimo Chen <huaimo.chen@futurewei.com> wrote:
Hi Ketan,
 
    Thanks much for your comments.
    My answers/explanations are inline below with prefix [HC].
 
>Some more/other comments on why I believe this draft is not a good idea:
 
How does the controller or provisioning entity know the status of the Route Policy provisioning on the target router. Even that it was successfully propagated to it and installed on it?
[HC]:  It seems that BGP protocols guarantees the BGP UPDATE with the route policy reaches the target router. When a BGP speaker as a controller sends a BGP UPDATE to a peer, there is no need for the ack from the peer about whether it is received, processed, and installed. The controller is monitoring the traffic of the network almost in real time, and adjusting the traffic dynamically almost in real time... The former gets the status of the network regarding to the traffic.
Seems like one can have multiple policies advertised for a single peer/neighbor? How would they be handled?
[HC]: For multiple policies advertised to a single peer/neighbor, they are processed one by one by the peer/neighbor..
The draft has support for IPv4 and IPv6 prefix list and AS regex. What other route policy tools does the WG expect to extend in further drafts? Perhaps we end up with yet another boatload of extension drafts for BGP for RPD?
[HC]: It seems that the current draft defines a small set of extensions (6 sub TLVs), which is enough to support adjusting the traffic dynamically in the live networks. If there are some new requirements in the future, the extensions would be small too. 
 
We have Route Policy yang model defined at the IETF for provisioning of route policies that provide better and more comprehensive solution than the proposal in this document. That approach is also very robust from operational perspective. We don’t need to be putting this into BGP protocol.
[HC]: Yang model seems mainly used in relatively static or stable configurations. For frequently changing route policies, the solution proposed in the draft is more suitable. It makes the operations and maintenance on the network simpler. For example, in one metro area network without using the solution in the draft, planning and implementing an adjustment/redirection of a service traffic takes days. After the solution in the draft is deployed in the network with a controller NCE, this takes just minutes instead of days.
 
Best Regards,
Huaimo


From: Idr <idr-bounces@ietf.org> on behalf of Ketan Talaulikar (ketant) <ketant=40cisco.com@dmarc.ietf.org>
Sent: Thursday, July 23, 2020 6:02 AM
To: Robert Raszuk <robert@raszuk.net>et>; Susan Hares <shares@ndzh.com>
Cc: idr@ietf. org <idr@ietf.org>
Subject: Re: [Idr] WG LC on draft-ietf-idr-rpd-05.txt (7/15 to 7/29/2020) 
 
+1 and I also agree on Jakob’s comments/discussion on a parallel thread.
 
The individual version of this draft was called draft-li-idr-flowspec-rpd. When it came up for WG adoption, perhaps most people thought it was yet another Flowspec extension and did not have a close look at it.
 
The draft got adopted in Nov 2019 and since then, there has hardly been any change for it (other than IANA allocations update) : https://www.ietf.org/rfcdiff?url1=draft-ietf-idr-rpd-00&url2=draft-ietf-idr-rpd-05
 
I am not sure if this document has received sufficient review and inputs from the WG over the recent 9 months of its life as a WG document. Those provided by Robert previously seem not to have been incorporated?
 
Not sure if I missed implementation reports or some operator feedback on this.
 
Some more/other comments on why I believe this draft is not a good idea:
 
How does the controller or provisioning entity know the status of the Route Policy provisioning on the target router. Even that it was successfully propagated to it and installed on it?
Seems like one can have multiple policies advertised for a single peer/neighbor? How would they be handled?
The draft has support for IPv4 and IPv6 prefix list and AS regex. What other route policy tools does the WG expect to extend in further drafts? Perhaps we end up with yet another boatload of extension drafts for BGP for RPD?
 
We have Route Policy yang model defined at the IETF for provisioning of route policies that provide better and more comprehensive solution than the proposal in this document. That approach is also very robust from operational perspective. We don’t need to be putting this into BGP protocol.
 
In summary, my suggestion would also be not proceed further on this document.
 
Thanks,
Ketan
 
From: Idr <idr-bounces@ietf.org> On Behalf Of Robert Raszuk
Sent: 17 July 2020 18:38
To: Susan Hares <shares@ndzh.com>
Cc: idr@ietf. org <idr@ietf.org>
Subject: Re: [Idr] WG LC on draft-ietf-idr-rpd-05.txt (7/15 to 7/29/2020)
 
Dear IDR WG, 
 
As discussed previously on the list I strongly object to proceed with this draft any further. 
 
While I am as others quite sceptical about distributing more configuration over BGP this can be said to be debatable especially for p2mp applications. 
 
However including peer's IP address in the NLRI to which given policy applies goes completely AGAINST BGP spray principle of p2mp information distribution. Adding such extension to BGP can only deteriorate the protocol further. It is not a fit in p2mp protocol to by definition use it as p2p transport channel. 
 
The prefix 0 which is in the draft is not the solution to the above problem... 
 
Moreover wide community ATOM also can already contain that peer's address so placing it in the NLRI of MP_REACH is not needed at all. 
 
To the specific questions asked: 
 
Ad 1) No. 
Ad 2) No.
Ad 3) No.. 
Ad 4) No. 
Ad 5) Yes.
 
Kind regards,
R.
 
 
On Wed, Jul 15, 2020 at 3:11 PM Susan Hares <shares@ndzh.com> wrote:
This begins a 2 week WG LC on draft-ietf-idr-rpd 
from 7/15 to 7/29/2020.  You can obtain this draft at: 
https://datatracker.ietf.org/doc/draft-ietf-idr-rpd/
 
This draft defines a new AFI/SAFI and new atoms 
for the Wide Communities.  This WG LC has been delayed 
as I waited for a resubmission of the Wide Communities draft.  
I had hoped to do these 2 WG LC in parallel. 
 
I’ve not received the Wide Communities draft, but we will 
start this WGLC to provide feedback to the authors. 
We may have to run a short follow-up to this WG LC
If there are changes to the Wide Communities draft during 
Its WG LC. 
 
There is an IPR statement on this draft.
 
In your responses please answer the following questions: 
 
1) Do you feel this draft has an solution that is acceptable 
   With the IPR as a WG RFC?  
 
2) Do you feel this draft is ready to publish?
 
3) Do you know of implementations of this draft?  
 
4) Do you know of deployments of this draft?  
If so, is this feature useful in the deploy ments. 
 
5) Do you feel that Wide Communities is ready for 
Publication?  
 
Cheerily, Susan Hares   
_______________________________________________
Idr mailing list
Idr@ietf.org
https://www.ietf.org/mailman/listinfo/idr