Hi, On Tue, May 10, 2011 at 01:25:21PM -0400, Martin Millnert wrote:
"I permit 195.30.0.0/16 to be announced by AS5539" "I permit 80.81.192.0/22 to be announced by AS5539"
[and needing some sort of document from RIPE NCC to say which one is true]
Yes, this is indeed the key issue. I'd like to single out the registry function you mention above, and separate it from that authority also having the power to lease out resources under some kind of notion that they can be called back.
Well, that's the IP resource assignment framework we have today: numbers are given out as long as they are needed, and given back when they are no longer needed (or under special circumstances, e.g. fraud involved). If you change that model to something where number blocks are actually traded ("Sold by the NCC to entity A, which can do then with the numbers whatever it want, e.g. sell to entity B without registering with the RIPE NCC"), the model would look different - and a trade could, for example, be done in your model by adding an "eternal signature" to the hand-over XML blob. So, assuming we want to keep the existing model of number resource allocations from the RIRs (and giving them *back* to the RIRs eventually), what can we do to have that reflected in whatever attestation system? It should be pointed out that the nice folks over at the anti-abuse WG would scream bloody murder if they hear about the notion of resources being given to spammers, scammers, phishers and whatnot, with no way to take them back... (and that's not "LEA type" anti-abuse folks, but "netizen" anti-abuse folks). Gert Doering -- did you enable IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (89) 32356-444 USt-IdNr.: DE813185279