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 ]
Nils Ketelsen
nils at druecke.strg-alt-entf.org
Fri Feb 25 19:12:26 CET 2005
On Fri, Feb 25, 2005 at 07:00:27PM +0100, Jeroen Massar wrote: > Also for the folks complaining about rootservers getting a /32 and those > not being available to ccTLD servers, why don't you move to the APNIC > region, there even the .jp root has a /32.... And now the next question: If a ccTLD NS gets a /32, why shouldn't a Authoratitative NS for a real big number of Domains (of a domain hoster, for example) get a /32? What is the difference between a ccTLD Nameserver and any other authoritative NS? I think the problem is not, that ccTLD Nameservers do not get a assignment, the problem is much more general: Addresses are assigned in the way that suits ISPs quite nicely but for sites is a major pain in the rear end. As long as this does not change IPv6 will stay what it is today: A nice platform for testing and playing without any business relevance. Nils -- Der Minister nimmt flüsternd den Bischof beim Arm: "Halt Du sie dumm - ich halt sie Arm" [Reinhard Mey, 'Sei Wachsam']
- 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 ]