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] getting second IPv6 PA as a LIR
- Previous message (by thread): [address-policy-wg] getting second IPv6 PA as a LIR
- Next message (by thread): [address-policy-wg] getting second IPv6 PA as a LIR
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Martin Millnert
millnert at gmail.com
Sun May 1 22:46:59 CEST 2011
Immo, On Sun, May 1, 2011 at 2:16 PM, Immo 'FaUl' Wehrenberg <immo.ripe at be.free.de> wrote: >> IPv6 PI (PIv6) is nearly useless, by design: >> Only customer-less end-users can use PIv6 space today without stepping >> into a grey zone in the policy documents. I.e., these end-users can't >> have customers. I'm surprised that I had not realized that myself. IPv6-hosting ::= (bring-your-own-PIv6-prefix, @ 50EUR/year+registry fees | buy from a LIR) At 65536 /48s in a /32, that's a big source of revenue for RIPE right there. :) Current break-even seems to be around 50 customers (for when it's cheaper to be LIR). Which in other words means 50:1 prefixes in DFZ, before break-even. And I'm betting there's a significant long-tail of hosting providers who have less than 50 customers. Oh the joy of DFZ :) Regards, Martin
- Previous message (by thread): [address-policy-wg] getting second IPv6 PA as a LIR
- Next message (by thread): [address-policy-wg] getting second IPv6 PA as a LIR
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]