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] Re: [ipv6-wg] IPv6 micro allocation or something else?
- Previous message (by thread): [address-policy-wg] Re: [ipv6-wg] IPv6 micro allocation or something else?
- Next message (by thread): [address-policy-wg] Re: [ipv6-wg] IPv6 micro allocation or something else?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jørgen Hovland
jorgen at hovland.cx
Sun Nov 13 16:47:14 CET 2005
Hi, -----Original Message----- From: Kurt Erik Lindqvist [mailto:kurtis at kurtis.pp.se] Sent: 13. november 2005 15:32 >In the first scenario you are forced to the routing policies of ISP x >and only to the locations of ISP x. In the second example you can co- >locate, connect to and IXP and do your own routing decisions as well >as be present at locations you choose (without "vasting" or even >having to go to 11 servers). You will always be forced to obey the rules of whatever provider you are using, ISP or IXP. I get the impression that you believe ISP x's routing policies will always be insufficient for you. Nameservers are not the only anycast service so it would be tricky to discuss this in general. But you want your nameserver to be reachable, that I know. Both scenarios will accomplish that with the same amount of redundancy. What kind of routing policies do you mean? Do you want to restrict your reachability? Joergen Hovland
- Previous message (by thread): [address-policy-wg] Re: [ipv6-wg] IPv6 micro allocation or something else?
- Next message (by thread): [address-policy-wg] Re: [ipv6-wg] IPv6 micro allocation or something else?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]