Re: well-known Anycast prefixes

2019-03-19 Thread Frank Habicht
Hi, On 20/03/2019 00:03, Bill Woodcock wrote: > Ok, so, just trying to flesh out the idea to something that can be > usefully implemented… > > 1) People send an eBGP multi-hop feed of well-known-community routes > to a collector, or send them over normal peering sessions to > something that aggre

Re: Contacts wanted: OVH, DigitalOcean, and Microsoft (Deutschland)

2019-03-19 Thread David Hubbard
On 3/19/19, 8:23 PM, "NANOG on behalf of Ronald F. Guilmette" wrote: In message , Tom Beecher wrote: >Calling everyone an idiot in the midst of Endless Pontification isn't >really a recipe for success. I did not call "everyone" an idiot. I'm quite completel

Re: Contacts wanted: OVH, DigitalOcean, and Microsoft (Deutschland)

2019-03-19 Thread Ronald F. Guilmette
In message , Tom Beecher wrote: >Calling everyone an idiot in the midst of Endless Pontification isn't >really a recipe for success. I did not call "everyone" an idiot. I'm quite completely sure that there are innumerable people in all of the referenced companies who are consumate and hardw

Re: Contacts wanted: OVH, DigitalOcean, and Microsoft (Deutschland)

2019-03-19 Thread Ronald F. Guilmette
[[ I've just collected some new information about the length of time that this specific bincoin extortion spamming bad actor has been on Digital Ocean's network. For those who may only have an interest in that one detail, you can just skip down to the line of plus signs and start rea

Re: well-known Anycast prefixes

2019-03-19 Thread Bill Woodcock
> On Mar 19, 2019, at 1:55 PM, Frank Habicht wrote: > > Hi, > > On 19/03/2019 23:13, Bill Woodcock wrote: >> Generally, static lists like that are difficult to maintain when >> they’re tracking multiple routes from multiple parties. > > agreed. > and on the other extreme, communities are very

Re: well-known Anycast prefixes

2019-03-19 Thread Frank Habicht
Hi, On 19/03/2019 23:13, Bill Woodcock wrote: > Generally, static lists like that are difficult to maintain when > they’re tracking multiple routes from multiple parties. agreed. and on the other extreme, communities are very much prone to abuse. I guess I could set any community on a number of p

Re: well-known Anycast prefixes

2019-03-19 Thread Bill Woodcock
> On Mar 19, 2019, at 1:11 PM, Grzegorz Janoszka wrote: > > On 2019-03-19 21:04, Hansen, Christoffer wrote: >> https://github.com/netravnen/well-known-anycast-prefixes/blob/master/list.txt >> PR's and/or suggestions appreciated! (Can be turned into $lirDB friendly >> format->style RPSL) > > Mo

Re: well-known Anycast prefixes

2019-03-19 Thread Bill Woodcock
> On Mar 19, 2019, at 1:04 PM, Hansen, Christoffer > wrote: > > something like this? > > https://github.com/netravnen/well-known-anycast-prefixes/blob/master/list.txt > > PR's and/or suggestions appreciated! (Can be turned into $lirDB friendly > format->style RPSL) Generally, static lists l

Re: well-known Anycast prefixes

2019-03-19 Thread Grzegorz Janoszka
On 2019-03-19 21:04, Hansen, Christoffer wrote: https://github.com/netravnen/well-known-anycast-prefixes/blob/master/list.txt PR's and/or suggestions appreciated! (Can be turned into $lirDB friendly format->style RPSL) Most DNS root servers are anycasted. -- Grzegorz Janoszka

Re: well-known Anycast prefixes

2019-03-19 Thread Hansen, Christoffer
something like this? https://github.com/netravnen/well-known-anycast-prefixes/blob/master/list.txt PR's and/or suggestions appreciated! (Can be turned into $lirDB friendly format->style RPSL) On 19/03/2019 18:12, Fredy Kuenzler wrote: > I wonder whether anyone has ever compiled a list of well-kn

Re: well-known Anycast prefixes

2019-03-19 Thread Joe Provo
On Tue, Mar 19, 2019 at 11:52:19AM -0700, Damian Menscher via NANOG wrote: > Careful thought should be given into whether the BGP community means "this > is an anycast prefix" vs "please hot-potato to this prefix". > Latency-sensitive applications may prefer hot-potato to their network even > if it

Re: well-known Anycast prefixes

2019-03-19 Thread Damian Menscher via NANOG
Careful thought should be given into whether the BGP community means "this is an anycast prefix" vs "please hot-potato to this prefix". Latency-sensitive applications may prefer hot-potato to their network even if it's not technically an anycast range, as their private backbone may be faster (less

Re: well-known Anycast prefixes

2019-03-19 Thread Siyuan Miao
A Well-known BGP community will be better. You'll need to rewrite next hop or do something similar if AnyCast prefixes are learnt from a multi hop BGP feed, and it made the configuration more complicated and difficult to debug. On Wed, Mar 20, 2019, 01:48 Fredy Kuenzler wrote: > Am 19.03.19 um

Re: well-known Anycast prefixes

2019-03-19 Thread Fredy Kuenzler
Am 19.03.19 um 18:39 schrieb Bill Woodcock: >> On Mar 19, 2019, at 10:12 AM, Fredy Kuenzler >> wrote: I wonder whether anyone has ever compiled a list of >> well-known Anycast prefixes. > > I don’t know of one. > > It seems like a good idea. > > BGP-multi-hop might be a reasonable way to coll

RE: well-known Anycast prefixes

2019-03-19 Thread David Guo via NANOG
Hi Fredy, Our anycast prefixes for DNS resolver 185.222.222.0/24 2a09::/48 You can add them if someone will maintain a list. Regards, David -Original Message- From: NANOG On Behalf Of Fredy Kuenzler Sent: Wednesday, March 20, 2019 1:13 AM To: nanog@nanog.org Subject: well-known Anyca

Re: well-known Anycast prefixes

2019-03-19 Thread Bill Woodcock
> On Mar 19, 2019, at 10:12 AM, Fredy Kuenzler wrote: > > I wonder whether anyone has ever compiled a list of well-known Anycast > prefixes. I don’t know of one. It seems like a good idea. BGP-multi-hop might be a reasonable way to collect them. If others agree that it’s a good idea, and it

well-known Anycast prefixes

2019-03-19 Thread Fredy Kuenzler
I wonder whether anyone has ever compiled a list of well-known Anycast prefixes. Such as 1.1.1.0/24 8.8.8.0/24 9.9.9.0/24 ... Might be useful for a routing policy such as "always route hot-potato". PS. this mail is not intended to start a flame war of hot vs. cold potato routing. -- Fredy Kue

Re: Contacts wanted: OVH, DigitalOcean, and Microsoft (Deutschland)

2019-03-19 Thread niels=nanog
Apologies, it was in reply to a list mail. Just bad threading. * niels=na...@bakker.net (niels=na...@bakker.net) [Tue 19 Mar 2019, 16:51 CET]: Kind of bad netiquette to repost a private email to the list

Re: Contacts wanted: OVH, DigitalOcean, and Microsoft (Deutschland)

2019-03-19 Thread Eric Kuhnke
Absolutely unrelated to Ronald's original post, but it's ironic that the abuse@ address is itself heavily "abused", by commercial copyright enforcement companies which think it's a catch-all address for things which are not operationally related to the health of a network (BGP hijacks, DDoS, spam e

RE: Contacts wanted: OVH, DigitalOcean, and Microsoft (Deutschland)

2019-03-19 Thread Jack Barrett (Appia)
I agree it could have definitely been simplified, but I also found the “endless pontification” a little amusing this morning. What I do not find amusing is the social outrage and identity politics that has made it’s way into the sacred NANOG mailing list. From: NANOG On Behalf Of Tom Beecher

Re: Contacts wanted: OVH, DigitalOcean, and Microsoft (Deutschland)

2019-03-19 Thread niels=nanog
Kind of bad netiquette to repost a private email to the list -- Niels.

Re: Contacts wanted: OVH, DigitalOcean, and Microsoft (Deutschland)

2019-03-19 Thread Nikolas Geyer
Just to clarify, we are RFC 2142 section 4 compliant. I mention section 4 specifically as that is directly within my realm of control, the remaining sections I will check. Both methods, web form submission and abuse@ are integrated ultimately into the same workflow. Being transparent, as things

RE: Contacts wanted: OVH, DigitalOcean, and Microsoft (Deutschland)

2019-03-19 Thread Ray Orsini
I originally held back on a similar response. But I had the exact same opinion. It works against your argument when you start off with insults and condescension. Personally, I would not refer anyone to someone making a post like this. Regards, Ray Orsini – CEO Orsini IT, LLC – Technology Cons

Re: Contacts wanted: OVH, DigitalOcean, and Microsoft (Deutschland)

2019-03-19 Thread John Peach
On 3/19/19 10:49 AM, Rich Kulawiec wrote: On Tue, Mar 19, 2019 at 09:23:34AM -0400, Jeff McAdams wrote: We would prefer, but don't require, that you use the web form because that is integrated into the workflow of the groups that respond to those reports. Why isn't abuse@ integrated into the w

Re: Contacts wanted: OVH, DigitalOcean, and Microsoft (Deutschland)

2019-03-19 Thread Rich Kulawiec
On Tue, Mar 19, 2019 at 09:23:34AM -0400, Jeff McAdams wrote: > We would prefer, but don't require, that you use the web form because that > is integrated into the workflow of the groups that respond to those > reports. Why isn't abuse@ integrated into the workflow? It darn well should be, (a)

Re: Contacts wanted: OVH, DigitalOcean, and Microsoft (Deutschland)

2019-03-19 Thread Tom Beecher
This entire thread could easily have been simply : "Hey all! I'm having some challenges reaching a live person in the abuse groups for X, Y, and Z. Can anyone help with a contact, or if anyone from those companies sees this, can you contact me off-list?" Calling everyone an idiot in the midst of

Re: Webzilla

2019-03-19 Thread Denys Fedoryshchenko
On 2019-03-18 23:24, Ronald F. Guilmette wrote: In message , Eric Kuhnke wrote: Looking at the AS adjacencies for Webzilla, what would prevent them from disconnecting all of their US/Western Euro based peers and transits, and remaining online behind a mixed selection of the largest Russian A

Re: Contacts wanted: OVH, DigitalOcean, and Microsoft (Deutschland)

2019-03-19 Thread Jeff McAdams
(Disclosure: I, too, work for DigitalOcean as the Manager of Network Engineering. Nikolas does not work for me, nor I for him.) On Tue, March 19, 2019 02:17, Ronald F. Guilmette wrote: > > Nikolas Geyer wrote: >> I have passed your email on to the relevant team within DO to have a >> look at.