[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


To: Robert Elz <kre@munnari.OZ.AU>
cc: Keith Moore <moore@cs.utk.edu>, ngtrans@sunroof.eng.sun.com, namedroppers@ops.ietf.org, ipng@sunroof.eng.sun.com, dnsop@cafax.se
From: Keith Moore <moore@cs.utk.edu>
Date: Wed, 08 Aug 2001 13:25:59 -0400
In-reply-to: Your message of "Thu, 09 Aug 2001 00:17:09 +0700." <5403.997291029@brandenburg.cs.mu.OZ.AU>
Sender: owner-dnsop@cafax.se
Subject: Re: (ngtrans) Joint DNSEXT & NGTRANS summary

>   | it's even more realistic to say that TTL indicates the amount of time
>   | for which the DNS administrator is willing to accept that the services
>   | associated with the DNS name will be effectively unavailable, should
>   | he/she need to change the addresses.
> 
> That's not an unfair description of what often happens, mostly through
> ignorance of how things should be done though.  

sometimes ignorance, and sometimes a realistic assessment (based on 
knowledge of the users and applications affected) of the harm that 
will be done.

> Fortunately, with v6
> (whatever DNS RR format is chosen) having multiple addresses assigned to
> an interface is designed as a normal case, rather than an unusual one.

the stacks are designed to deal with this, yes.  whether ISPs and network
administrators and firewalls and applications will also deal with this is a 
separate question.

even so, renumbering for the purpose of new connections is a lot easier
than renumbering established connections.

Keith

Home | Date list | Subject list