Re: Destination Preference Attribute for BGP

2023-08-31 Thread Robert Raszuk
Hi Michael, > two datacenters which user traffic can egress, and if one is used we want that traffic to return to the same > data center. It is a problem of asymmetry. It appears the only tools we have are AS_Path and MED, and so > I have been searching for another solution, that is when I came

Re: Destination Preference Attribute for BGP

2023-08-30 Thread Mark Tinka
On 8/30/23 18:56, michael brooks - ESC wrote: I, too, am looking for something sexy (explained below). But can you explain why you think AS_PATH is "useless," Mark? Because most network operators use LOCAL_PREF heavily, and no amount of AS_PATH prepending will be able fight that with any

Re: Destination Preference Attribute for BGP

2023-08-30 Thread michael brooks - ESC
>With AS-PATH prepend you have no control on the choice of which ASN should do what action on your advertisements. Robert- It is somewhat this problem we are trying to resolve. >I was imagining something sexier, especially given how pretty "useless" AS_PATH prepending is nowadays. I, too, am

Re: Destination Preference Attribute for BGP

2023-08-22 Thread Mark Tinka
On 8/22/23 16:46, Tom Beecher wrote: Again, as it was stated, the size of or number of BGP communities wasn't the problem anyway; it was hashing / memory storage. And you know what? Hashing / memory storage HAS been a problem with multiple vendors in many other contexts, not just BGP

Re: Destination Preference Attribute for BGP

2023-08-22 Thread Tom Beecher
> > What I am saying is that for those that have been fixed, unless someone > can offer up any additional evidence in 2023, the size of the number of BGP > communities attached to a path does not scream "danger" in 2023 hardware. > And the T1600 is a long time ago. > Again, as it was stated,

Re: Destination Preference Attribute for BGP

2023-08-21 Thread Mark Tinka
On 8/21/23 17:44, Tom Beecher wrote: So, while this all sounds good, without any specifics on vendor, box, code, code revision number, fix, year it happened, current status, e.t.c., I can't offer any meaningful engagement. If you clicked Matt's link to the Google search, you

Re: Destination Preference Attribute for BGP

2023-08-21 Thread Tom Beecher
> > So, while this all sounds good, without any specifics on vendor, box, > code, code revision number, fix, year it happened, current status, e.t.c., > I can't offer any meaningful engagement. > If you clicked Matt's link to the Google search, you could tell from the results what vendor , model,

Re: Destination Preference Attribute for BGP

2023-08-19 Thread Jon Lewis via NANOG
On Fri, 18 Aug 2023, Matthew Petach wrote: Hi Robert, Without naming any names, I will note that at some point in the not-too-distant past, I was part of a new-years-eve-holiday-escalation to $BACKBONE_ROUTER_PROVIDER when the global network I was involved with started seeing excessive

Re: Destination Preference Attribute for BGP

2023-08-18 Thread Mark Tinka
On 8/19/23 00:22, Matthew Petach wrote: Hi Mark, I know it's annoying that I won't mention specifics. Unfortunately, the last time I mentioned $vendor-specific information on NANOG, it was picked up by the press, and turned into a multimillion dollar kerfuffle with me at the center of the

Re: Destination Preference Attribute for BGP

2023-08-18 Thread Matthew Petach
On Fri, Aug 18, 2023 at 2:36 PM Mark Tinka wrote: > [...] > To be fair, you are talking about an arbitrary value of years back, on > boxes you don't name running code you won't mention. > > This really not saying much :-). > Hi Mark, I know it's annoying that I won't mention specifics.

Re: Destination Preference Attribute for BGP

2023-08-18 Thread Mark Tinka
On 8/18/23 22:40, Matthew Petach wrote: Hi Robert, Without naming any names, I will note that at some point in the not-too-distant past, I was part of a new-years-eve-holiday-escalation to $BACKBONE_ROUTER_PROVIDER when the global network I was involved with started seeing excessive

Re: Destination Preference Attribute for BGP

2023-08-18 Thread Mark Tinka
On 8/18/23 22:20, Jakob Heitz (jheitz) via NANOG wrote: We support platforms of various capacities. While we would all like to sell the large ones, people buy the cheap ones too. Even a bare bones x86 platform of some sort with at least 8GB of RAM would make the cheapest routers still,

Re: Destination Preference Attribute for BGP

2023-08-18 Thread Mark Tinka
On 8/18/23 19:38, Jakob Heitz (jheitz) via NANOG wrote: That's true Robert. However, communities and med only work with neighbors. Communities routinely get scrubbed because they cause increased memory usage and convergence time in routers. Really? We only scrub a specific string of

Re: Destination Preference Attribute for BGP

2023-08-18 Thread Mark Tinka
On 8/18/23 09:38, Robert Raszuk wrote: Jakob, With AS-PATH prepend you have no control on the choice of which ASN should do what action on your advertisements. My comprehension of DPA would have been more directed than the "spray & pray" approach AS_PATH prepending provides. However,

Re: Destination Preference Attribute for BGP

2023-08-18 Thread Mark Tinka
On 8/18/23 09:38, Robert Raszuk wrote: Jakob, With AS-PATH prepend you have no control on the choice of which ASN should do what action on your advertisements. My comprehension of DPA would have been more directed than the "spray & pray" approach AS_PATH prepending provides. However,

Re: Destination Preference Attribute for BGP

2023-08-18 Thread Robert Raszuk
> it's really about efficiently *parsing and updating* communities-- Absolutely correct. Inefficient implementations of how communities are used in inbound or outbound policies can do a lot of harm - no doubt about that - and as you say some surface in least convenient moments. But the point I

Re: Destination Preference Attribute for BGP

2023-08-18 Thread Jakob Heitz (jheitz) via NANOG
:20 PM To: Robert Raszuk Cc: nanog@nanog.org Subject: Re: Destination Preference Attribute for BGP We support platforms of various capacities. While we would all like to sell the large ones, people buy the cheap ones too. Kind Regards, Jakob From: Robert Raszuk Date: Friday, August 18, 2023

Re: Destination Preference Attribute for BGP

2023-08-18 Thread Jakob Heitz (jheitz) via NANOG
og.org> mailto:nanog@nanog.org>> Subject: Re: Destination Preference Attribute for BGP Hi Jakob, On Fri, Aug 18, 2023 at 7:41 PM Jakob Heitz (jheitz) via NANOG mailto:nanog@nanog.org>> wrote: That's true Robert. However, communities and med only work with neighbors. Commun

Re: Destination Preference Attribute for BGP

2023-08-18 Thread Robert Raszuk
k on code and with customer issues that escalate to code. > > > > Kind Regards, > > Jakob > > > > > > *From: *Robert Raszuk > *Date: *Friday, August 18, 2023 at 10:59 AM > *To: *Jakob Heitz (jheitz) > *Cc: *nanog@nanog.org > *Subject: *Re: Destination

Re: Destination Preference Attribute for BGP

2023-08-18 Thread Jakob Heitz (jheitz) via NANOG
Perhaps to you Robert. I work on code and with customer issues that escalate to code. Kind Regards, Jakob From: Robert Raszuk Date: Friday, August 18, 2023 at 10:59 AM To: Jakob Heitz (jheitz) Cc: nanog@nanog.org Subject: Re: Destination Preference Attribute for BGP Hi Jakob, On Fri, Aug 18

Re: Destination Preference Attribute for BGP

2023-08-18 Thread Robert Raszuk
; > Jakob > > > > > > *From: *Robert Raszuk > *Date: *Friday, August 18, 2023 at 12:38 AM > *To: *Jakob Heitz (jheitz) > *Cc: *nanog@nanog.org > *Subject: *Re: Destination Preference Attribute for BGP > > Jakob, > > > > With AS-PATH prepen

Re: Destination Preference Attribute for BGP

2023-08-18 Thread Jakob Heitz (jheitz) via NANOG
get dropped. route-policy testRP if as-path length ge 200 then drop endif end-policy Kind Regards, Jakob From: Robert Raszuk Date: Friday, August 18, 2023 at 12:38 AM To: Jakob Heitz (jheitz) Cc: nanog@nanog.org Subject: Re: Destination Preference Attribute for BGP Jakob

Re: Destination Preference Attribute for BGP

2023-08-18 Thread Robert Raszuk
Jakob, With AS-PATH prepend you have no control on the choice of which ASN should do what action on your advertisements. However, the practice of publishing communities by (some) ASNs along with their remote actions could be treated as an alternative to the DPA attribute. It could result in

Re: Destination Preference Attribute for BGP

2023-08-17 Thread Mark Tinka
On 8/17/23 21:43, Jakob Heitz (jheitz) via NANOG wrote: "prepend as-path" has taken its place. That pours water on my imaginary fire :-). I was imagining something sexier, especially given how pretty "useless" AS_PATH prepending is nowadays. Mark.

Re: Destination Preference Attribute for BGP

2023-08-17 Thread Jakob Heitz (jheitz) via NANOG
"prepend as-path" has taken its place. Kind Regards, Jakob Date: Wed, 16 Aug 2023 21:42:22 +0200 From: Mark Tinka On 8/16/23 16:16, michael brooks - ESC wrote: > Perhaps (probably) naively, it seems to me that DPA would have been a > useful BGP attribute. Can anyone shed light on why this

Re: Destination Preference Attribute for BGP

2023-08-16 Thread Mark Tinka
On 8/16/23 16:16, michael brooks - ESC wrote: Perhaps (probably) naively, it seems to me that DPA would have been a useful BGP attribute. Can anyone shed light on why this RFC never moved beyond draft status? I cannot find much information on this other than IETF's data tracker

Destination Preference Attribute for BGP

2023-08-16 Thread michael brooks - ESC
Perhaps (probably) naively, it seems to me that DPA would have been a useful BGP attribute. Can anyone shed light on why this RFC never moved beyond draft status? I cannot find much information on this other than IETF's data tracker ( https://datatracker.ietf.org/doc/draft-ietf-idr-bgp-dpa/) and