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 ]
Jon Lawrence
jon at lawrence.org.uk
Fri Feb 25 01:23:40 CET 2005
On Thursday 24 February 2005 23:36, Iljitsch van Beijnum wrote: > On 25-feb-05, at 0:02, Elmar K. Bins wrote: > > The real problem is DNS deployment > > in v6. v4 has 11 (14 by June) of our servers, spread world-wide; I'd > > like to do the same with v6 servers, but I simply can't. > > > > Every f***ing registry on the planet has the special assignment policy > > (with very strict rules, mind you), except for the one they always > > send me back to ("sorry, not our business, you're in the RIPE region"). > > Well, there are more than a hundred TLDs and if they all want 11 IPv6 > prefixes that would inflate the v6 table by more than 150%. > > I think a reasonable proposal from a good portion of the TLD community > would go a long way, though. > > >> Of course the underlying question returns to "how to do IPv6 > >> multihoming > >> for A Special End Site". > > Everyone thinks they're special. That's how you get large routing > tables. yep - I'm special :). But the roots are more special. I want multihoming, until then v6 will NOT go mainstream. However, the roots really are a special case - There's no reason (at least none I can think of) why all the root's in the world couldn't be hosted out of a single /48, or rather a /48 for each region - which would avoid my nightmare of a single entity being able to control major internet resources. > (It's not _that_ long ago that the root servers got their addresses > from the organizations that hosted them.) and it's not that long ago that my laptop would have taken up your entire house - you point is ? > > Is everybody busy waiting for the IETF v6-multihoming group to come > > to a conclusion? > > In that case you won't have to wait much longer as this is going to > happen within a few weeks. However, the multi6 mechanisms (that still > have to be developed) aren't very suitable for multihoming DNS service. Be interesting to see what they come back with. How can multihoming be suitable to one kind of service and not another - I'll wait 'til they publish they're docs, you can explain then Iljitsch :) (unless we're talking locators again). As I said above, the roots are a special case - end of story - we cannot live without them (slight exaggeration). Why can't a /48 be set a side for the root servers in each region (or even a global /32). Jon
- 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 ]