Re: [Idr] I-D Action: draft-ietf-idr-large-community-01.txt

[Robert Raszuk <[e-mail]>]

I believe Jeff was talking about intelligent cleanup with sufficient
information embedded into community itself such that forwarding BGP speaker
can decide what to pass and what to drop
... not an unconditional blind drop.

However as I see the folks here - some say do not send anything over eBGP
unless explicitely permitted (and sorry but "send-community all" knob is
not at that level of granularity needed), some say send everything
everywhere.

To me this is a bit a conflict of interests which I am really not going to
be in the middle of.

Some say that standardizing, deployment, education of large communities
will take years. And in fact they are very correct. It will take that much
indeed.

That is why I believe the delta to add few more lines of code which Jakob
refused should be smashed by IDR WG in the interest of BGP as protocol and
we should all together as a WG produce a solution which scales to the
current needs as well as leaves some room for future extensions. That would
mean that the overall effort which vastly exceeds few lines of C would gain
much more value.

Acee stating that may be even wide comms could be progressed in the future
is very interesting in the light of his BGP IOS team mate stating in the
other thread that he will never implement those :)

Kind regards,
R.

On Wed, Oct 12, 2016 at 11:56 PM, heasley <[e-mail]> wrote:

> Wed, Oct 12, 2016 at 09:45:52AM -0400, Jeffrey Haas:
> > Arguably this was one of the motivations for doing scoping of attributes
> or
> > communities themselves: If the effective operational behavior is almost
> > always going to be AS-non-transitive, it'd be nice if the cleanup just
> > happens automagically.  Unfortunately people are rather enamored with
> their
> > existing cleanup mechanisms.
>
> Please, no automatic clean-up.  A community may be 100% legitimately used
> to affect a decision 2 or 3 AS-hops away and it is extremely useful.
> Operators already know how to alter communities.
>
> _______________________________________________
> Idr mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/idr
>