I imagine that the “description” of each entry in the list should include a
machine-readable field indicating the use.
There was a question about the use-case... I’m sure a lot of people in the ops
community have their own reasons related to routing and filtering and so forth,
but there’s
On 3/21/19 11:52 AM, Ross Tajvar wrote:
Not all any-casted prefixes are DNS resolvers and not all DNS resolvers
are anycasted. It sounds like you would be better served by a list of
well-known DNS resolvers.
True on both counts, and that's why I said "help".
On Thu, Mar 21, 2019 at 12:35
Not all any-casted prefixes are DNS resolvers and not all DNS resolvers are
anycasted. It sounds like you would be better served by a list of
well-known DNS resolvers.
On Thu, Mar 21, 2019 at 12:35 PM Bryan Holloway wrote:
>
> On 3/21/19 10:59 AM, Frank Habicht wrote:
> > Hi James,
> >
> > On
On 3/21/19 10:59 AM, Frank Habicht wrote:
Hi James,
On 20/03/2019 21:05, James Shank wrote:
I'm not clear on the use cases, though. What are the imagined use cases?
It might make sense to solve 'a method to request hot potato routing'
as a separate problem. (Along the lines of Damian's
On Thu, Mar 21, 2019 at 06:59:18PM +0300, Frank Habicht wrote:
> On 20/03/2019 21:05, James Shank wrote:
> > I'm not clear on the use cases, though. What are the imagined use cases?
> >
> > It might make sense to solve 'a method to request hot potato routing'
> > as a separate problem. (Along
Hi James,
On 20/03/2019 21:05, James Shank wrote:
> I'm not clear on the use cases, though. What are the imagined use cases?
>
> It might make sense to solve 'a method to request hot potato routing'
> as a separate problem. (Along the lines of Damian's point.)
my personal reason/motivation is
On 3/19/19 5:03 PM, Bill Woodcock wrote:
>
>
>> 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.
>>
>>
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
> 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
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
> 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)
>
>
> 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
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
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
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
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
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
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
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
> 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
20 matches
Mail list logo
