In message <u2j88ac5c711004251021q54694443l687b8f6aa78c42df@mail.gmail.com>, Richard Barnes writes:
Moreover, the general point stands that Mark's problem is one of bad ISP decisions, not anything different between IPv4/RFC1918 and IPv6.
Actually one needs to deploy a ULA or have PI addresses to handle external link down events that are long enough to cause any provider supplied addresses to expire. With address selection rules setup so that you prefer ULA over non-ULA for intra site it just works. For some services you only advertise a ULA address even if the host machine has both. I was disscussing how a CPE device should be advertising DNS severs in DHCP and decided that adverising ULA addresses for the DNS proxy/forewarding server was the best way to do this. Mark
On Sun, Apr 25, 2010 at 11:48 AM, Owen DeLong <owen@delong.com> wrote:
On Apr 25, 2010, at 8:17 AM, Tony Hoyle wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 25/04/2010 03:01, Mark Smith wrote:
I'm a typical, fairly near future residential customer. I have a NAS that I have movies stored on. My ISP delegates an IPv6 prefix to me wit=
h
a preferred lifetime of 60 minutes, and a valid lifetime of 90 minutes
What ISP would put a 'lifetime' on your ipv6 prefix? =A0That seems insan= e to me... they should give you a /48 and be done with it. =A0Even the fre= e tunnel brokers do that.
But then I never understood dynamic ipv4 either....
If they are using DHCP-PD, then, it comes with a lifetime whether it is static or not.
The reality is that unless they need to renumber you, you'll probably get a new RA with the 60/90 minute lifetimes specified each time RAs are sent and your counters will all get reset to 60/90 for the foreseeable future. =A0The preferred and valid lifetimes aren't limitations, they're minimums. =A0The prefix should be yours and should be functional for you for AT LEAST the valid lifetime.
Owen
-- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: marka@isc.org