I-D Action:draft-azinger-scalable-addressing-00.txt

[Michael K. Smith - Adhost]

> -----Original Message-----
> From: Tony Li [mailto:tony.li at tony.li]
> Sent: Wednesday, September 29, 2010 12:18 PM
> To: Michael K. Smith - Adhost
> Cc: ipv6-ops at lists.cluenet.de
> Subject: Re: I-D Action:draft-azinger-scalable-addressing-00.txt
> 
> 
> >>> However this is leaking network topology into the DNS plane which
> > means
> >> when a network problem occurs and an upstream is flaky or down the
> > sysops
> >> need to update DNS to kill that mapping. Otherwise we get outages
> > similar to
> >> what happens now when a  site goes down on a dns balanced service.
> >>
> >>
> >> This is something that could be reasonably automated.
> >
> > <snip>
> >
> > My Google Fu is failing me.  Can someone point me to the RFC(s) that
> > reference the DNS plane for routing updates?
> 
> 
> Try looking for dynamic DNSSEC.
> 
> Tony

Thanks.  I'm assuming that all of these fast-flux routing updates are
going to be handled by everyones existing DNS infrastructure.  Has
anyone addressed the issue with providers, some quite large, that don't
honor TTL's?  I'm imagining waiting 72 hours for a routing update.

Regards,

Mike