This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/address-policy-wg@ripe.net/
[address-policy-wg] IPv6 access to K-root
- Previous message (by thread): [address-policy-wg] IPv6 access to K-root
- Next message (by thread): [address-policy-wg] IPv6 access to K-root
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Elmar K. Bins
elmi at 4ever.de
Mon Feb 28 10:11:27 CET 2005
kurtis at kurtis.pp.se (Kurt Erik Lindqvist) wrote: > > Contrast this with eleven/fifteen v4 sets on five unicast (provider PA) > > and one anycast v4 (PI) address. > > So what you are _really_ arguing (or should be) is that you can get PA > IPv4 but does not qualify for PA IPv6. That is something completely We're a LIR, so naturally (!) we have our v4 PA. Funny enough, a v6 PA seems out of the question. Were this an ordinary end-site, I'd have no problem with it; unfortunately, I have to overcome a few things which includes rolling out a heap of name servers. As Iljitsch said, DNS has built-in redundancy. Unfortunately, it's still limited. The biggest obstacle is the 510-byte answer packet that can only be circumvented by anycasting the stuff (which of course is impossible with a PA assignment). The next biggest obstacle, of course, is that some people simply refuse to listen. -- "Begehe nur nicht den Fehler, Meinung durch Sachverstand zu substituieren." (PLemken, <bu6o7e$e6v0p$2 at ID-31.news.uni-berlin.de>) --------------------------------------------------------------[ ELMI-RIPE ]---
- Previous message (by thread): [address-policy-wg] IPv6 access to K-root
- Next message (by thread): [address-policy-wg] IPv6 access to K-root
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]