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] Update on ALLOCATED PI/UNSPECIFIED
- Previous message (by thread): [address-policy-wg] Update on ALLOCATED PI/UNSPECIFIED
- Next message (by thread): [address-policy-wg] Update on ALLOCATED PI/UNSPECIFIED
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Daniel Stolpe
stolpe at resilans.se
Thu Aug 4 17:58:26 CEST 2016
On Thu, 4 Aug 2016, Larisa Yurkina wrote: > Patrick Velder ????? 04.08.2016 11:12: > > Hi >> >> Hello Ingrid >> >> That means, if a resource holder (ASSIGNED PI within ALLOCATED PI) has an >> "Independent Assignment Request and Maintenance Agreement" with the LIR, >> like end users which got their assignment direct from RIPE NCC, this >> assignment will become an assignment which is managed directly by RIPE >> NCC? >> >> Best regards >> Patrick >> >> > My LIR have got ALLOCATED PI and ALLOCATED UNSPECIFIED blocks about 20 > years ago, according to those days policy. Some part of address space was not > aggregated and was used as "ASSIGNED PI within ALLOCATED PI", all of them > have agreement with the LIR, which also was within the policy, at least not > against. Why should we change anything here? Just because some LIRs lost > their control over 50% of the address space allocated to them? Perhaps there > are some other ways to restore it? Yes, if it aint broken, don't try to fix it. However Ingrid is right that "data accuracy must have the highest priority" and if the status tag causes confusion maybe something have to be done. The problem is that we aim for a very binary black and white world and forget that all of these labels were not there in the beginning. In our particular case we have been handling address space for three decades and the line between legacy in 1991 and the NCC era in 1992 was not very sharp. First none of the space had any status. Then (still in the 1990's) a colleague arbitrarily put the "ALLOCATED PI/ASSIGNED PI" status everywhere. Then (a couple of years ago) the NCC decided some blocks where LEGACY (assignments were made before 1992) and some not (assignments were made in 1992 or shortly afterwards), however all of the space have been treated both as LEGACY and PA earlier on. The use of PI was obviously based on a misunderstanding and the non-legacy blocks have been PA all the time so apparently you learn as long as you live. I think we can live with changing ASSIGNED PI to ASSIGNED PA if it makes the database more readable but I still agree with you Larisa that if we have been going on like this for decades, why the sudden urge to change it now? The end users will certainly be a bit worried by the sudden change. Cheers, Daniel _________________________________________________________________________________ Daniel Stolpe Tel: 08 - 688 11 81 stolpe at resilans.se Resilans AB Fax: 08 - 55 00 21 63 http://www.resilans.se/ Box 45 094 556741-1193 104 30 Stockholm
- Previous message (by thread): [address-policy-wg] Update on ALLOCATED PI/UNSPECIFIED
- Next message (by thread): [address-policy-wg] Update on ALLOCATED PI/UNSPECIFIED
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]