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/address-policy-wg@ripe.net/
[address-policy-wg] Just say *NO* to PI space -- or how to make it lessdestructive
- Previous message (by thread): [address-policy-wg] Just say *NO* to PI space -- or how to make it lessdestructive
- Next message (by thread): [address-policy-wg] Just say *NO* to PI space -- or how to make it lessdestructive
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Max Tulyev
president at ukraine.su
Mon Apr 24 12:56:59 CEST 2006
Hi, > Most (if not all) larger hosting providers I know are LIRs, so this > question really doesn't apply. And for smaller hosting providers, this can > be done - yes, it's painful, but the alternatives are also painful. In fact, no (especially, in .RU/.UA). But! Some of hosting providers are LIRs to have own IPs and AS, but many of them need no more than /24 (ok, /23 at the most), because of HTTP/1.1 nowdays is an industry standard. I also know many cases people get LIRs (and /20) because of they aware of potential (I think mostly imagined) PI problems, when they really need /24. What about conserving of address space? -- WBR, Max Tulyev (MT6561-RIPE, 2:463/253 at FIDO)
- Previous message (by thread): [address-policy-wg] Just say *NO* to PI space -- or how to make it lessdestructive
- Next message (by thread): [address-policy-wg] Just say *NO* to PI space -- or how to make it lessdestructive
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]