Re: [nznog] TelstraVodaHug core lag

We already do this with the blackhole-*.iana.org addresses - we just announce the /32 routes into our internal routing table, just like any other internal service IP address. All I need to do is add 8.8.8.8 to my local forwarders, and they'll anycast the address to our downstreams. In the blackhole*.iana.org case we're doing something recommended to prevent bogus traffic from going outside our provider net, not hijacking another provider's service. That's the philosophical problem - it's not "can I do it without breaking the internet?", but "should I?", given that those using 8.8.8.8 probably don't understand that it's - in most cases - probably giving them a worse experience than asking locally. You could argue that it's "fixing the Internet" for the naive user. But Google DNS is not "standard" DNS. How non-standard it is isn't clear, but ... well, it's Google ... so providing something that behaves "differently" to Google DNS at the Google DNS address does strike me as rude. But is it actually bad? Note that I'm not proposing to do this on our infrastructure, because we have a customer base that for the most part either has clue, or punts clue to us. But other providers might think differently... -- don On 18/09/13 19:53, Tim Price wrote:

Well I guess if you want to get all technical ;). Blame the flu for the missing of the obvious, I know I will.

Cheers,

Tim

On 18/09/2013, at 7:51 PM, Nathan Ward wrote:

...

On 18/09/2013, at 7:46 PM, Tim Price wrote:

...

Apart from the obvious net neutrality rhetoric why would you have a stateful device in your forwarding path. And you'd better hope that google don't decide to do authoritive hosting on those servers now or in the future (although we all know they shouldn't) Yeah, why /would/ you have a stateful device in your forwarding path, in order to achieve Don's suggestion? :-)

Loopback/dummy interface + static route.

-- Nathan Ward