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] Enabling Methods for Reallocation of IPv4 Resources
- Previous message (by thread): [address-policy-wg] Bogus Prefixes (was Enabling Methods ...)
- Next message (by thread): [address-policy-wg] Enabling Methods for Reallocation of IPv4 Resources
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Florian Weimer
fw at deneb.enyo.de
Tue Mar 25 20:02:38 CET 2008
>> Over here, a lease implies that it's RIPE NCC's job to make sure that >> the prefix is and remains in usable shape for its intended purpose >> (globally routeable, not blacklisted etc.). > > does RIPE NCC -really- provide assurance that a prefix > it hands out is globally routable? At least for PI space, they explicitly say they don't. (Of course, this doesn't completely rule out that an implied guarantee exists nevertheless.) > ` Or is that just an implied aspect of the term "lease", > which is not in use these days? Yes, it's a mandatory part of the contract, the leaser cannot abstain from that. You've got some wiggle room with regard to the scope of the contract. But a lease of something that provides no documented value (and the contract explicitly saying so!) will be a very difficult sell to various parties. It borders on breach of trust ("Untreue", embezzlement in extreme cases). The current model of industry self-governance does not seem to suffer from that.
- Previous message (by thread): [address-policy-wg] Bogus Prefixes (was Enabling Methods ...)
- Next message (by thread): [address-policy-wg] Enabling Methods for Reallocation of IPv4 Resources
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]