[arin-discuss] use of 188.8.131.52/16 not clear
scottleibrand at gmail.com
Tue Sep 22 14:34:09 EDT 2009
Does anyone know the actual history of this block? All I see on a quick
whois + Google search is several copies of this message on
IETF/NANOG/etc, as well as some filter rules blocking 184.108.40.206/16.
However, it appears that most of the filters that block 128.66/16 also
block 2/8, for example. So without some additional history or
information on other types of filtering, I'm not sure that the
difficulty of getting 128.66/16 routed will be any higher than that of
getting any other previously unallocated block routed.
So I guess I'd favor the approach of returning it to the free pool, with
appropriate announcements and documentation, and then making allocations
from it once the rest of the "cleaner" /16s are used up.
Jason Schiller wrote:
> On behalf of Ron Bonica,
> The IETF has recently passed draft-iana-rfc3330bis-08. This draft
> documents the fact that the following address ranges have been reserved
> for documentation:
> - 192.0.2.0/24 (TEST-NET-1)
> - 198.51.100.0/24 (TEST-NET-2)
> - 203.0.113.0/24 (TEST-NET-3)
> In addition, some authors have used 220.127.116.11/16 (TEST-B) for example
> purposes. There is no RFC that talks about this block, but my
> understanding is that IANA/ARIN have marked it as reserved. If you
> search the Internet you will find at least some number of examples and
> firewall rule sets that use this block, but I have no good idea about
> how widespread such usage is.
> What should we do about this block? Some of the potential answers
> include documenting its role, marking it as reserved but deprecating its
> use in examples, and returning it to the free pool immediately (with a
> warning sign about possible filtering problems).
> You are receiving this message because you are subscribed to
> the ARIN Discussion Mailing List (ARIN-discuss at arin.net).
> Unsubscribe or manage your mailing list subscription at:
> Please contact info at arin.net if you experience any issues.
More information about the ARIN-discuss