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 ]
Max Tulyev
president at ukraine.su
Fri Dec 2 10:34:10 CET 2005
> You need a /28 and want "Provider Independence". I use a /28 at home. Hope you do not host thousands of websites at home ;) > Lets say that I want "PI" too, that would mean I am going to get, pay > for and maintain: > - Multiple Redundant Routers > - Multiple Redundant Links > - Multiple Redundant Transits > - Own 24/7 NOC (things will fail) > - and a lot more... > > You are willing to do and pay for all that, but don't want to become an > LIR? 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?). Also I need to be independent from carriers (especially when hosting grows up and I will ask for money for direct peering with me). But I do NOT need a lot of address space (thanks God and RFC, we have HTTP/1.1 this time). Look more. http://www.ripe.net/membership/benefits.html As a hosting provider, I do NOT want any of that services. So no reasons to be LIR, isn't it? It is only example for PI, but many other exists. -- WBR, Max Tulyev (MT6561-RIPE, 2:463/253 at FIDO)
- 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 ]