Hi Lu, > I have an policy question regarding Ripe policy before adoption of "no need" > policy.
I don't see the usefulness of second-guessing how obsolete policy would have been applied. Can you explain the relevance to current policy development? > We all know that before the no need policy, when Ripe makes an assignment, > while the "need" has changed, the assignment become invalid. RIPE NCC only would assign provider independent resources. To LIRs RIPE NCC would allocate resources and then verify policy requirements, such as need, when the LIR makes assignments from the allocation. > The question come to what the definition of need. Below I have few examples, > please provide your view: I am not going into the details of your examples as they are no longer relevant to current policy development. In general: assignments are quite specific. As an LIR you assign resources to your own infrastructure or a specific customer. Whenever any of that changes (i.e. customers changing, expansion of networks etc) it would be considered a new assignment which would require new justification (need etc). So the correct thing to do in the database (to keep things a bit relevant) would be to delete the old assignments and create new ones. That would keep the history nice and clean (old object would be for the old assignment, new object with new creation date would be for the new assignment). Cheers, Sander
