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] RE: Private address space in IPv4 and IPv6 [was something irrelevantly titled]
- Previous message (by thread): [address-policy-wg] RE: Private address space in IPv4 and IPv6 [was something irrelevantly titled]
- Next message (by thread): [address-policy-wg] RE: Private address space in IPv4 and IPv6 [was something irrelevantly titled]
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Andy Davidson
andy at nosignal.org
Sun May 31 13:39:19 CEST 2009
On 31 May 2009, at 11:28, Olivier MJ Crepin-Leblond wrote: > "Andy Davidson" <andy at nosignal.org> wrote: > >> IP networks can't function properly (or at least, as intended) when >> consumers of addresses start using addresses that are already >> assigned to others already. >> >> We shall see this be a problem for networks who ignore this warning >> as the last v4 /8s start to be assigned. > > Actually who is mandated to act as a policeman when this happens? > Is it IANA? Is it the RIRs? Is it informal routing agreements > outside the realm of these organizations? Nobody - just as nobody can guarantee reach-ability. Andy
- Previous message (by thread): [address-policy-wg] RE: Private address space in IPv4 and IPv6 [was something irrelevantly titled]
- Next message (by thread): [address-policy-wg] RE: Private address space in IPv4 and IPv6 [was something irrelevantly titled]
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]