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 ]
Daniel Suchy
danny at danysek.cz
Wed May 4 12:21:31 CEST 2011
On 05/04/2011 11:55 AM, poty at iiat.ru wrote: > Why then you should apply for PI? In case of problems RIPE (for example) would speak with a single LIR, not with thousands of widespread customers. RIPE is always speaking with the LIR, in accordance to 2007-01 policy. All new PI users are always connected with some LIR. If you want obtain PI directly from RIPE, you'll pay additional money for the contract with RIPE, it's documented on the website. And generally, I don't prefer crapping PA space with such deaggregation caused just by the PI-blocking policy. If someone has good technical reason for provider-independent address usage, I don't see reason not to assign it from defined (dedicated-for-PI) range. Current typical IPv4 PI user has some reason for that and I'm not here for judging it. I trust RIPE employees in verification of request validity. I rather prefer controlled PI assignments by RIPE instead of some kind of LIR creativity here. There's known demand for for PI on the market. Daniel
- 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 ]