<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Jun 13, 2019, at 8:24 AM, Job Snijders <<a href="mailto:job@instituut.net" class="">job@instituut.net</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">On Thu, Jun 13, 2019 at 11:18 Warren Kumari <<a href="mailto:warren@kumari.net" class="">warren@kumari.net</a>> wrote:<br class=""></div><div class=""><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Thu, Jun 13, 2019 at 9:59 AM Joe Abley <<a href="mailto:jabley@hopcount.ca" target="_blank" class="">jabley@hopcount.ca</a>> wrote:<br class="">
><br class="">
> Hey Joe,<br class="">
><br class="">
> On 12 Jun 2019, at 12:37, Joe Provo <<a href="mailto:nanog-post@rsuc.gweep.net" target="_blank" class="">nanog-post@rsuc.gweep.net</a>> wrote:<br class="">
><br class="">
> > On Wed, Jun 12, 2019 at 04:10:00PM +0000, David Guo via NANOG wrote:<br class="">
> >> Send abuse complaint to the upstreams<br class="">
> ><br class="">
> > ...and then name & shame publicly. AS-path forgery "for TE" was<br class="">
> > never a good idea. Sharing the affected prefix[es]/path[s] would<br class="">
> > be good.<br class="">
><br class="">
> I realise lots of people dislike AS_PATH stuffing with other peoples' AS numbers and treat it as a form of hijacking.<br class="">
><br class="">
<br class="">
Actually, I've been meaning to start a thread on this for a while.<br class="">
<br class="">
I have an anycast prefix - at one location I'm a customer of a<br class="">
customer of ISP_X & ISP_Y & ISP_Z. Because ISP_X prefers customer<br class="">
routes, any time a packet touches ISP_X, it goes to this location,<br class="">
even though it is (severely) suboptimal -- things would be better if<br class="">
ISP_X didn't accept this route in this location.<br class="">
<br class="">
Now, the obvious answer of "well, just ask your provider in this<br class="">
location to not announce it to ISP_X. That's what communities / the<br class="">
telephone were invented for!" doesn't work for various (entirely<br class="">
non-technical) reasons...<br class="">
<br class="">
Other than doing path-poisoning can anyone think of a way to<br class="">
accomplish what I want? (modulo the "just become a direct customer<br class="">
instead of being a customer of a customer" or "disable that site", or<br class="">
"convince the AS upstream of you to deploy communities / filters").<br class="">
While icky, sometimes stuffing other people's AS in the path seems to<br class="">
be the only solution...</blockquote><div dir="auto" class=""><br class=""></div><div dir="auto" class=""><br class=""></div><div dir="auto" class="">Given the prevalence of peerlock-style filters at the transit-free club, poisoning the path may result in a large outage for your prefix rather than a clever optimization. Poisoning paths is bad for all parties involved.</div><div dir="auto" class=""><br class=""></div><div dir="auto" class="">Kind regards,</div><div dir="auto" class=""><br class=""></div><div dir="auto" class="">Job</div></div></div>
</div></blockquote></div><br class=""><div class="">Job,</div><div class=""><br class=""></div><div class="">Permit me to apply some reflective listening to your statement:</div><div class=""><br class=""></div><div class="">What I heard you say is: “I’m not going to offer a solution to your problem, but you shouldn’t use the one you have that currently works because some things my friends and I are doing react poorly to it and you may suffer some consequences as a result.”</div><div class=""><br class=""></div><div class="">Owen</div><div class=""><br class=""></div></body></html>