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] 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 ]
Marcin Kuczera
marcin at leon.pl
Sun May 1 23:12:55 CEST 2011
> > I don't really see why suddenly a lot of organizations should come > up wanting PIv6. I think the need of PIv6 would be quite compareable > to PIv4, and at least nowadays, the PI-Prefixes aren't really that > problem as far as I see. And, as pointed out before, the current > PIv6 policy can even be interpreted as source of much more > v6-routes in the DFZ anyways. That is not so simple in post-communist countries. As I know, there are around 200 ISPs in Germany. In Poland, we have - 2000-3000 of ISPs.. however they are very little sometimes - i.e. serving 300 or 700 customers. let's say - 10 euro /month per customer (+ VAT) * 700 = 7000 euro of a budget. Pay taxes, pay salaries, pay lawyers, office, investments, upstreams, infrastructure... I's just a little for the owner if you compare it to large ISPs. So, if there is no possibility to use IPv6 PI for own customers (/128 for customer) any more, the only way is to use other LIR's part of PA space. There is NO WAY that they will pay for beeing LIR. Regards, Marcin
- 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 ]