Re: [Idr] I-D Action: draft-dong-idr-node-target-ext-comm-01.txt

[Robert Raszuk <[e-mail]>]

Dear authors,

Let me start by restating that using a p2mp protocol to distribute
information in a p2p fashion is a bad thing. Your proposal just further
encourages folks to do continue use of BGP along those lines which is not a
good thing.

Now few questions/observations:

* You are explicitly breaking RFC4456. The node which does your policy
enforcement - let's call it - BGP Policy based Update Replicator (BGP PUR)
- no longer follows RFC4456 recommendations of route propagation from
client to non-client and from non-client to client. Sure you may define
such new functional block in BGP but IMHO this is no longer a vanilla Route
Reflector with "just a little bit more filtering" :)

* Assume that in my 500 PEs IPv6 network I want to distribute some
information to 100 of them. Very conservative case. So with the current
draft I will need to send with each route BGP Extended Community Attribute
of the 2K size. Well assume that BGP Extended Message is not there at least
on one of the PEs the proposed scheme breaks. Did you ever consider to
actually define new attribute for this and support wildcard match/extended
community match length ?

* Can you describe the rational for keeping the Node Targets ext
communities still in the update when reflecting it to one of the targets on
the list ?

* Have you thought of using 4 octet BGP identifier instead of peering
address ? First you no longer need to struggle with IPv6 length, you no
longer worry about link-local peerings and you no longer need to touch all
senders when interface addresses get renumbered.

* RRs in general where designed and optimized to reflect all received
updates. RTC came and applied some outbound filters. Now your proposal
comes and applies new set of per peer dynamic filters. Putting
implementation details aside at min your proposal must define which filter
is more important RTC pushed from target or your Target RT pushed from
sources.

* How does your proposal works with RR hierarchy ? It seems pretty clear
that it only works with flat sender -- RR -- receiver architecture.

* How does your proposal work with confederations ?

* What happens when session to a peer goes down ? Would you now need to
remodify the list of Node Target Ext Comms and resend to other IBGP peers
including that node which you have lost IBGP to ?

Essentially what you are defining is to push dynamic filtering policy from
the src to the RRs hoping that RRs will honor it and apply proper outbound
filters. Moreover you are also adding new behaviour for RRs to modify
content of BGP attributes upon reflection. I think you are assuming that
all applicable implementations support dynamic update groups or are you
assuming that whenever such Node Target Ext Community arrive on the RR it
should switch for a given SAFI to per peer update generation ?

Best,
R.


> On Mon, Jul 8, 2019 at 1:13 PM <[e-mail]> wrote:

>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>
>
>         Title           : BGP Extended Community for Identifying the
> Target Node
>         Authors         : Jie Dong
>                           Shunwan Zhuang
>                           Gunter Van de Velde
>         Filename        : draft-dong-idr-node-target-ext-comm-01.txt
>         Pages           : 7
>         Date            : 2019-07-08
>
> Abstract:
>    BGP has been used to distribute different types of routing and policy
>    information in the network.  In some cases, the information
>    distributed may be only intended for one or several particular
>    receiving BGP nodes in the network.  However, BGP does not have a
>    general mechanism for designating the receiving node of the routing
>    information.  This document defines a new type of BGP extended
>    community called "Node Target".  The mechanism of using the Node
>    Target extended community to steer BGP route distribution to
>    particular BGP nodes is specified.
>
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-dong-idr-node-target-ext-comm/
>
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-dong-idr-node-target-ext-comm-01
>
> https://datatracker.ietf.org/doc/html/draft-dong-idr-node-target-ext-comm-01
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-dong-idr-node-target-ext-comm-01
>
>
> Please note that it may take a couple of minutes from the time of
> submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> I-D-Announce mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>