On 18 Mar 2010, at 6:02, Ingrid Wijte wrote: [...]
A new RIPE Policy Proposal has been made and is now available for discussion.
You can find the full proposal at:
I agree with James that by distinguishing between 16 and 32-bit AS Numbers in section 2, this text is inconsistent with the main ASN policy. I suspect that the RIPE NCC staff can reserve a couple of small AS Numbers for this purpose and there is such a large number of big AS Numbers that a reservation is probably not necessary. The proposed policy text does not state that these assignments are subject to a contract, presumably because that is specified in the text of the main policy. Am I right in thinking that requesters would need to sign a contract to get resources under this policy? While it is an implementation detail, it would be nice if the time frame was documented in the contract. Also, if I have read it correctly, this proposal text removes the publication requirement for assignments made to experiments and academic research. What is the reason for removing this requirement? Finally, in the rationale section a., I think the phrase "a negligible effect on the final RIPE NCC IANA-supplied IPv4 address pool depletion date" should be "a negligible effect on the IANA-supplied RIPE NCC address pool depletion date" to improve clarity. Regards, Leo Vegoda