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] Guidance Requested: Changing the Status of PI Address Space
- Previous message (by thread): [address-policy-wg] 2013-03: Summary of amendments for version 3.0
- Next message (by thread): [address-policy-wg] Guidance Requested: Changing the Status of PI Address Space
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Tomasz Śląski GMAIL
tomasz.slaski at gmail.com
Wed Aug 7 23:49:36 CEST 2013
W dniu 2013-07-31 13:50, Erik Bais pisze: > Hi Carsten, > > I'm in favor of LIR's being able to change the PI status to PA for their own assigned PI space. (Infrastructure) > > I think that the whole PI and PA discussion itself will take some time to complete, but this particular change should be fairly easy to implement imho. > > Regards, > Erik Bais I think that is very simple, requiring only a decision which no one yet wants to take. Do we have any new ideas on this subject? Personally, I think that: 1. If an organization wants to become LIR status and declares, that alerady has the PI resources equal or more than /22, it should no longer receive the "initial" allocation of the /22 from the lat /8, but should be able to convert all, what was received before becoming the LIR status. 2. Existing LIRs should be able to convert his PI resources to PA regardless of the block size. All the best Tomasz
- Previous message (by thread): [address-policy-wg] 2013-03: Summary of amendments for version 3.0
- Next message (by thread): [address-policy-wg] Guidance Requested: Changing the Status of PI Address Space
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]