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]/
[ipv6-wg] Re: Re: [address-policy-wg] Re: Andre's guide to fix IPv6
- Previous message (by thread): [ipv6-wg] Re: Re: [address-policy-wg] Re: Andre's guide to fix IPv6
- Next message (by thread): [ipv6-wg] Re: Re: [address-policy-wg] Re: Andre's guide to fix IPv6
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Per Heldal
heldal at eml.cc
Fri Dec 2 13:41:59 CET 2005
On Fri, 2 Dec 2005 12:34:10 +0300, "Max Tulyev" <president at ukraine.su> said: [snip] > > In this example I'm providing hosting and no more than hosting. No > telecoms, > no transit channels, no ADSL. May be domain registration. > > To make that business success I need to be multihomed (no objections at > this > point, I think?). Try a different angle; assume you can get decent (redundant) connectivity to one provider and thus almost as reliable as if you're sitting in their core network. If you still require multihoming, don't your arguments implicitly disqualify your upstream as a hosting-provider too (regardless of them being multihomed and/or peering at any tier)? Who can then be trusted to run hosting-operations? Only multihomed as'es with no downstreams? (*duck*) //per -- Per Heldal heldal at eml.cc
- Previous message (by thread): [ipv6-wg] Re: Re: [address-policy-wg] Re: Andre's guide to fix IPv6
- Next message (by thread): [ipv6-wg] Re: Re: [address-policy-wg] Re: Andre's guide to fix IPv6
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]