North American Network Operators Group|
Date Prev | Date Next |
Date Index |
Thread Index |
Author Index |
- From: Stephen J. Wilcox
- Date: Sat Feb 22 08:39:33 2003
I can imagine there is some reason why this was originally reserved thats
probably not valid any more..
However seems like a lot of effort to change documents and policies for a single
On Thu, 20 Feb 2003 email@example.com wrote:
> 126.96.36.199/24 has historically been designated as a special-use network
> as it is the numerically highest Class C network. It is listed in
> RFC3330 as Reserved but open for possible future allocation.
> Now that 222/7 has been allocated to APNIC, the question comes up as to
> whether it is retaining the Reserved designation, or whether APNIC will
> keep it as reserved. I note that the APNIC whois servers do not denote
> it as Reserved.
> I bring this up since many bogon filters include this network for both
> routing and packet filtering.
> I have queries out to both APNIC and IANA as to the present status of
> that network, but I expect IANA will likely defer to APNIC.
> If it is no longer reserved, I've suggested that RFC3330 be updated
> to reflect its present status (such as prior-special-use networks
> are listed).
> In any event, pending confirmation from APNIC, I suggest folks look over
> their own bogon filtering. A quick check of Rob's list doesn't have
> this network specified. I believe that Juniper has a prebuilt bogon
> list, but I don't recall whether this network is on it or not.
> I've suggested APNIC send out email to the operations community, but
> if they don't, I'll send an update with whatever they send me.