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/[email protected]/
[address-policy-wg] Enabling Methods for Reallocation of IPv4 Resources
- Previous message (by thread): [address-policy-wg] Enabling Methods for Reallocation of IPv4 Resources
- Next message (by thread): [address-policy-wg] Bogus Prefixes (was Enabling Methods ...)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
bmanning at vacation.karoshi.com
bmanning at vacation.karoshi.com
Tue Mar 25 19:19:03 CET 2008
On Tue, Mar 25, 2008 at 04:34:31PM +0100, Florian Weimer wrote: > * Nick Hilliard: > > > Hank Nussbacher wrote: > >> Unfortunately, RIPE has never used the word "lease" after 2001. The > >> word "lease" was removed when the doc became policy: > > > > In countries whose legal system is derived from the british legal > > code, the word "lease" can attract the attention of the tax > > authorities who like to feel that all leases should be officially > > stamped and should therefore incur a stamp duty of several per cent of > > the lease cost. > > 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? ` Or is that just an implied aspect of the term "lease", which is not in use these days? --bill
- Previous message (by thread): [address-policy-wg] Enabling Methods for Reallocation of IPv4 Resources
- Next message (by thread): [address-policy-wg] Bogus Prefixes (was Enabling Methods ...)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]