[155532] in North American Network Operators' Group
Re: DNS Changer items
daemon@ATHENA.MIT.EDU (Leo Bicknell)
Wed Aug 15 09:56:39 2012
Date: Wed, 15 Aug 2012 06:55:52 -0700
From: Leo Bicknell <bicknell@ufp.org>
To: NANOG <nanog@nanog.org>
Mail-Followup-To: NANOG <nanog@nanog.org>
In-Reply-To: <CANB6qChF4hTYkP8K39q8==Au7jZTqwoyROhSGHvELwV64gOcDw@mail.gmail.com>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
--W/nzBZO5zC0uMSeA
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
In a message written on Wed, Aug 15, 2012 at 10:46:52AM +0100, Stephen Wilc=
ox wrote:
> https://www.ripe.net/internet-coordination/news/clarification-on-realloca=
ted-ipv4-address-space-related-to-dutch-police-order
=46rom the article:
] The address space was quarantined for six weeks before being returned to
] the RIPE NCC's available pool of IPv4 address space. It was then
] randomly reallocated to a new resource holder according to normal
] allocation procedures.
]=20
] As the RIPE NCC nears IPv4 exhaustion, it will reduce the quarantine
] period of returned address space accordingly to ensure that there is no
] more IPv4 address space available before the last /8 is reached. The
] RIPE NCC recognises that this shortened quarantine could lead to
] routability problems and offers its members assistance to reduce this.
While I understand that in the face of IPv4 exhaustion long quarantine
periods are probably no longer a good idea, I think 6 weeks is
shockingly short. I also think to blanket apply the quarantine is
a little short sighted, there are cases that need a longer cooling
off period, and this may be one of them.
I think the RIPE membership, and indeed the policy making bodies
of all RIR's should look at their re-allocation policies with this
case in mind and see if a corner case like this doesn't present a
surprising result.
--=20
Leo Bicknell - bicknell@ufp.org - CCIE 3440
PGP keys at http://www.ufp.org/~bicknell/
--W/nzBZO5zC0uMSeA
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (FreeBSD)
iQIVAwUBUCuqaLN3O8aJIdTMAQJtXBAAu1nt2X8x5/GOw8VRLjH75RtRZGtOfaJx
ec3Ic8vApDJC8udJlgnGenHkznZ4/4bKLjK/5TEZ+cxJsdNL8rPcTDtGNXQSRO1L
+udhVS1AxWUhzA+DHZ2rZKNyReuszVHV7/6Z+ikUhEMmtOS2aTbBM1gnqIEKXY1P
S2S1v+adzouQgJcpVWnnnGoD2paXJynhC4xKtoc8q3w+WrOg3UQIp1058L5rsAmg
wQeTTK/c1bbnnex3aLB6iSPq+GmPjxrCjiQ6UxvInMC80stCZTvLE9z/7/tiMK3J
JF+W0RBcaslkQfUsH0Zaoded6qbIuKcblU1bw92np7mhHz0l7rPTssbw2rzsdW1K
BbMs1UlpeXulySaTFnj12Bp7y1RupWhEO0a8bjlSkgEUWC5HS1l2H6IzQbExcX4V
9YARx8UI9ULmRusxxFitrmgdTSM+O60gqRxrtGR2stNlDvSM+9SaKSRgrnZ5vEKT
oZkiNMbp46GEmL4zAufX+xiLnDefQFfbs4P1kgdJBqjpUOm6I7x94JAqPftYdfoa
alGc8wT/e1wNRwyZcfmg1agyTc4TEatpng8rL3mBvnRU0G0wlPLCQrUKpSKtdI0v
Zv1uhPOynDNBPlhfmHtiXvzj9jaMpSrVVPHSyBDTJIPWQ+dbgJYkj7ZDx4kEVre4
ZMegRzAcY64=
=Byx9
-----END PGP SIGNATURE-----
--W/nzBZO5zC0uMSeA--
