Pre-emptive top-post in case anyone mistakes the technique proposed: This will NOT be implemented via communities.
The proposal is for a NEW optional transitive attribute. If any operators can answer the original question, this will be very helpful. Thank you in advance to any and all operators. Reminder on optional+transitive logic - If the attribute is not understood/implemented/enabled, the attribute is passed unmodified. - If it is understood & implemented & enabled, behavior is subject to the applicable standards. - Thus, optional transitives are "opt-in", by definition. The proposal itself is an IDR WG I-D, and as such not finalized; input here is definitely helpful in reaching consensus, understanding requirements, etc. Brian On Tue, Mar 21, 2017 at 1:55 PM, Gert Doering <g...@space.net> wrote: > Hi, > > On Tue, Mar 21, 2017 at 06:00:36PM +0000, Sriram, Kotikalapudi (Fed) wrote: > > >>From an operator point of view, > > are you willing to place a piece of relationship info (as stated above) > > in the BGP update for the significant gain of a route leak solution > > that works well to detect/stop route leaks that do happen, > > and prevents single point of failures in incremental/partial > > deployment scenarios? > > I'm not sure it will do any good. > > Those ISPs that care about the garbage their customers try to inject > already do prefix/as-path filtering. > > Those ISPs that do not care today will not add bother to add a filter on > this well-known community value (... and most likely, the customer > router sending out unfiltered garbage won't have "send-community" > enabled either). > > Gert Doering > -- NetMaster > -- > have you enabled IPv6 on something today...? > > SpaceNet AG Vorstand: Sebastian v. Bomhard > Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann > D-80807 Muenchen HRB: 136055 (AG Muenchen) > Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279 >
_______________________________________________ GROW mailing list GROW@ietf.org https://www.ietf.org/mailman/listinfo/grow
