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

Hi Robert,

I cannot see the absolute difference between the SR Policy and the RPD regarding the point you mentioned to look them as the config push.

Regarding your proposal, maybe we can. We also ever proposed the following draft.

https://tools.ietf.org/html/draft-dong-idr-node-target-ext-comm-02

But it seems a little conflicted about your viewpoints. Now such cases can be seen as the special cases of BGP. But if we define the general solutions,

it will go to change your claimed essence of p2mp for BGP you are defending :)

Best Regards,

Zhenbin (Robin)

________________________________
发件人: Idr [idr-bounces@ietf.org] 代表 Robert Raszuk [robert@raszuk.net]
发送时间: 2020年7月21日 17:12
收件人: Huaimo Chen
抄送: Jakob Heitz (jheitz); Susan Hares; idr@ietf.org
主题: Re: [Idr] WG LC on draft-ietf-idr-rpd-05.txt (7/15 to 7/29/2020)

SR policies propagation is a config push and should never be done in BGP. At least it is p2mp. Much better option here is https://tools.ietf..org/html/rfc5440<https://tools.ietf.org/html/rfc5440>

Your draft is p2p configuration push which is completely an NMS task. Please tell me why it can not be done with YANG models ?

Maybe instead of picking up one cherry at a time let's define a new AFI/SAFI - "BGP NMS AF" and stuff all of the p2p configuration there. At least when things melt it will be easy to recover by just disabling such AF and still allow for some routing info to go through ....

Thx,
R.

On Tue, Jul 21, 2020 at 6:00 AM Huaimo Chen <huaimo.chen@futurewei.com<mailto:huaimo.chen@futurewei.com>> wrote:
Hi Jakob,

    Thank you very much for your valuable comments.
    Our answers/explanations are inline below with prefix [HC].

Best Regards,
Huaimo on behalf of co-authors
________________________________
From: Idr <idr-bounces@ietf.org<mailto:idr-bounces@ietf.org>> on behalf of Jakob Heitz (jheitz) <jheitz=40cisco.com@dmarc.ietf.org<mailto:40cisco.com@dmarc.ietf.org>>
Sent: Thursday, July 16, 2020 9:01 PM
To: Susan Hares <shares@ndzh.com<mailto:shares@ndzh.com>>; idr@ietf.org<mailto:idr@ietf.org> <idr@ietf.org<mailto:idr@ietf.org>>
Subject: Re: [Idr] WG LC on draft-ietf-idr-rpd-05.txt (7/15 to 7/29/2020)

BGP seems the wrong way to distribute routing policy.

[HC]: It seems that BGP flow spec has been used widely to distribute policies for redirecting the traffic. It seems work well without some mechanisms in Netconf. BGP RPD should be similar to BGP flow spec.  BGP SR Policy is on the same train.

IETF has already defined a way to distribute configuration: Netconf.

Netconf provides needed features that BGP does not have:

- Atomic Transactions:

  If one configuration item fails, they all fail.

  They all either succeed or all fail. There is no partial success.

  Multiple configurations in one transaction are applied at the same time.

   . This avoids non-deterministic transient behavior between application of the first policy and the last.

- Feedback:

  BGP is "spray and pray".

  Netconf provides an acknowledgement that the config either failed or was applied,

  which then allows the controller to take the next steps with

  reliable information about what configuration exists in the network.

- Persistence:

  If the BGP session were to go down, all the configuration it sent will be implicitly withdrawn.

If another AS would not allow a foreign AS to configure it with netconf,

it would not allow it with RPD either.

There are already ways in BGP for an AS to signal preference across AS boundaries:

Med, AS-path length, communities.

[HC]: Netconf can be used to distribute configurations from a controller to the devices in a network. BGP RPD as an alternative option, may have some advantages in some cases. For example, in the case where BGP as a controller, BGP RPD seems more suitable. Using BGP RPD to control/redirect the traffic dynamically in real time may be more effective.

Regards,

Jakob.

From: Idr <idr-bounces@ietf.org<mailto:idr-bounces@ietf.org>> On Behalf Of Susan Hares
Sent: Wednesday, July 15, 2020 6:11 AM
To: idr@ietf.org<mailto:idr@ietf.org>
Subject: [Idr] WG LC on draft-ietf-idr-rpd-05.txt (7/15 to 7/29/2020)

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/<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-idr-rpd%2F&data=02%7C01%7Chuaimo.chen%40futurewei.com%7C12cf72daefe0446d5a7908d829ed0a36%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637305445341383523&sdata=3LvgG6xwElOv27jGetqpyk8ftRub%2B%2B4Ui31Yt8wN87A%3D&reserved=0>

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<mailto:Idr@ietf.org>
https://www.ietf.org/mailman/listinfo/idr