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/[email protected]/
[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 ]
Iljitsch van Beijnum
iljitsch at muada.com
Fri Feb 25 19:25:25 CET 2005
On 25-feb-05, at 19:12, Nils Ketelsen wrote: > 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? And if a big nameserver gets a /32, why doesn't a bank? I mean, most people value getting at their money more than getting at their homepage. But if the bank gets to multihome, then why not large etailers? And if the large ones get to, what about the medium-sized ones? > 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. ISPs know that keeping the routing infrastructure working is very important. End-users generally don't. > 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. And if we give everyone PI IPv6 will probably blow up even sooner than IPv4 so we can start again from scratch.
- 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 ]