IRR listing of IANA-reserved, a question..
First, standard disclaimers.. 1. This is a technical email. 2. I'm not speaking for any organization, other than ME. In the last 72 hours I've seen over 3GB of data hit a network I play with with source IP's of IANA-RESERVED space. Various people have reported seeing IANA-RSERVED get announced via BGP at different parts of the net. Various people maintain lists of IANA-RESERVED space and other such "special use or reserved" prefixes. These lists are used by others to generate filters, ACL's and the like. When IANA allocates a new prefix to a RIR, these lists have to be updated manually. Sometime after the space has been put into service and someone complains. Give the above, would it make sense for: A) The IANA to maintain a IRR/RADB type database that would allow for the auto generation of filters and ACL's based *purely* on RESERVED IANA space. No other prefixs would be listed. or B) For one or more of the RIR's (APNIC, ARIN, LACNIC, RIPE, etc) to maintain such a database, again only IANA-RSERVED space. or C) One of the existing well known IRR/RADB's to maintain the db ? If such a database was available, would YOU use it ? Would it help your network operations? Would it be of a possitive or negative nature to your network? Lets try to stay away from the obvious potential flames and other religous statements. Thank you. John Brown Speaking a single person
Wouldn't the easiest (at least short term) thing be for IANA (or someone else authoritative-like) to put up a text file (not that I'm really sure how many blocks this entails) available via http or ftp for people to periodically wget, etc. Surely IANA, ARIN, or someone else has some type of up-to date database that they could script, etc to generate this file? On Tue, Sep 03, 2002 at 06:36:04PM -0700, John M. Brown wrote:
First, standard disclaimers.. 1. This is a technical email. 2. I'm not speaking for any organization, other than ME.
In the last 72 hours I've seen over 3GB of data hit a network I play with with source IP's of IANA-RESERVED space.
Various people have reported seeing IANA-RSERVED get announced via BGP at different parts of the net.
Various people maintain lists of IANA-RESERVED space and other such "special use or reserved" prefixes.
These lists are used by others to generate filters, ACL's and the like.
When IANA allocates a new prefix to a RIR, these lists have to be updated manually. Sometime after the space has been put into service and someone complains.
Give the above, would it make sense for:
A) The IANA to maintain a IRR/RADB type database that would allow for the auto generation of filters and ACL's based *purely* on RESERVED IANA space. No other prefixs would be listed.
or
B) For one or more of the RIR's (APNIC, ARIN, LACNIC, RIPE, etc) to maintain such a database, again only IANA-RSERVED space.
or
C) One of the existing well known IRR/RADB's to maintain the db ?
If such a database was available, would YOU use it ?
Would it help your network operations?
Would it be of a possitive or negative nature to your network?
Lets try to stay away from the obvious potential flames and other religous statements.
Thank you.
John Brown Speaking a single person
http://www.iana.org/assignments/ipv4-address-space If folks want me to split it to show 256 lines (one per /8) I can have that happen. Don't want to have multiple sources of the data, so for now that's probably easiest. I'll watch this discussion with interest. If people think something is useful at the IANA level I'll do my best to make it happen. _________________________________________ John Crain Manager of Technical Operations ICANN crain@icann.org 1AF4 F638 4B2D 3EF2 F9BA 99E4 8D85 69A7 _________________________________________
-----Original Message----- From: owner-nanog@merit.edu [mailto:owner-nanog@merit.edu] On Behalf Of Jeffrey Meltzer Sent: Tuesday, September 03, 2002 11:54 PM To: nanog@merit.edu Subject: Re: IRR listing of IANA-reserved, a question..
Wouldn't the easiest (at least short term) thing be for IANA (or someone else authoritative-like) to put up a text file (not that I'm really sure how many blocks this entails) available via http or ftp for people to periodically wget, etc.
Surely IANA, ARIN, or someone else has some type of up-to date database that they could script, etc to generate this file?
On Tue, Sep 03, 2002 at 06:36:04PM -0700, John M. Brown wrote:
First, standard disclaimers.. 1. This is a technical email. 2. I'm not speaking for any organization, other than ME.
In the last 72 hours I've seen over 3GB of data hit a
network I play
with with source IP's of IANA-RESERVED space.
Various people have reported seeing IANA-RSERVED get announced via BGP at different parts of the net.
Various people maintain lists of IANA-RESERVED space and other such "special use or reserved" prefixes.
These lists are used by others to generate filters, ACL's and the like.
When IANA allocates a new prefix to a RIR, these lists have to be updated manually. Sometime after the space has been put into service and someone complains.
Give the above, would it make sense for:
A) The IANA to maintain a IRR/RADB type database that would allow for the auto generation of filters and ACL's based *purely* on RESERVED IANA space. No other prefixs would be listed.
or
B) For one or more of the RIR's (APNIC, ARIN, LACNIC, RIPE, etc) to maintain such a database, again only IANA-RSERVED space.
or
C) One of the existing well known IRR/RADB's to maintain the db ?
If such a database was available, would YOU use it ?
Would it help your network operations?
Would it be of a possitive or negative nature to your network?
Lets try to stay away from the obvious potential flames and other religous statements.
Thank you.
John Brown Speaking a single person
Yes. 256 lines is probably better, just to make it easily portable. Also I'd like to see the list of how the ips are split between reginal registries for whois purposes. For example blocks like 3.0.0.0/8 or 4.0.0.0/8 have records in ARIN. I think therefore they should be listed as ARIN blocks even if they are used entirely by one company. What I'd like to see if format like this: block registry date of allocation comment (purpose) And additional list which has list of all "ip registries" and contact info for each one include website, whois server, etc. I also would like to see ICANN can put all /8 (its only 256 records) in its whois server and have this information available there as well. On Wed, 4 Sep 2002, John Crain wrote:
http://www.iana.org/assignments/ipv4-address-space
If folks want me to split it to show 256 lines (one per /8) I can have that happen. Don't want to have multiple sources of the data, so for now that's probably easiest.
I'll watch this discussion with interest. If people think something is useful at the IANA level I'll do my best to make it happen.
_________________________________________ John Crain Manager of Technical Operations ICANN
crain@icann.org 1AF4 F638 4B2D 3EF2 F9BA 99E4 8D85 69A7 _________________________________________
-----Original Message----- From: owner-nanog@merit.edu [mailto:owner-nanog@merit.edu] On Behalf Of Jeffrey Meltzer Sent: Tuesday, September 03, 2002 11:54 PM To: nanog@merit.edu Subject: Re: IRR listing of IANA-reserved, a question..
Wouldn't the easiest (at least short term) thing be for IANA (or someone else authoritative-like) to put up a text file (not that I'm really sure how many blocks this entails) available via http or ftp for people to periodically wget, etc.
Surely IANA, ARIN, or someone else has some type of up-to date database that they could script, etc to generate this file?
On Tue, Sep 03, 2002 at 06:36:04PM -0700, John M. Brown wrote:
First, standard disclaimers.. 1. This is a technical email. 2. I'm not speaking for any organization, other than ME.
In the last 72 hours I've seen over 3GB of data hit a
network I play
with with source IP's of IANA-RESERVED space.
Various people have reported seeing IANA-RSERVED get announced via BGP at different parts of the net.
Various people maintain lists of IANA-RESERVED space and other such "special use or reserved" prefixes.
These lists are used by others to generate filters, ACL's and the like.
When IANA allocates a new prefix to a RIR, these lists have to be updated manually. Sometime after the space has been put into service and someone complains.
Give the above, would it make sense for:
A) The IANA to maintain a IRR/RADB type database that would allow for the auto generation of filters and ACL's based *purely* on RESERVED IANA space. No other prefixs would be listed.
or
B) For one or more of the RIR's (APNIC, ARIN, LACNIC, RIPE, etc) to maintain such a database, again only IANA-RSERVED space.
or
C) One of the existing well known IRR/RADB's to maintain the db ?
If such a database was available, would YOU use it ?
Would it help your network operations?
Would it be of a possitive or negative nature to your network?
Lets try to stay away from the obvious potential flames and other religous statements.
Thank you.
John Brown Speaking a single person
-- William Leibzon Elan Communications Inc.
Actually let me correct myself... The format I think would be better is: block date-of-current-allocation registry comment/purpose I don't want to see separate lines below like "(Formerly Stanford University - Apr 93)". This should be part of the comment on the same line and date should always be the last change, i.e. 049/8 Joint Technical Command May 94 Returned to IANA Mar 98 should actually be: 049/8 Mar98 IANA Formerly Joint Technical Command (May 94 - Mar 98) On Wed, 4 Sep 2002 william@elan.net wrote:
Yes. 256 lines is probably better, just to make it easily portable.
Also I'd like to see the list of how the ips are split between reginal registries for whois purposes. For example blocks like 3.0.0.0/8 or 4.0.0.0/8 have records in ARIN. I think therefore they should be listed as ARIN blocks even if they are used entirely by one company.
What I'd like to see if format like this: block registry date of allocation comment (purpose)
And additional list which has list of all "ip registries" and contact info for each one include website, whois server, etc.
I also would like to see ICANN can put all /8 (its only 256 records) in its whois server and have this information available there as well.
On Wed, 4 Sep 2002, John Crain wrote:
http://www.iana.org/assignments/ipv4-address-space
If folks want me to split it to show 256 lines (one per /8) I can have that happen. Don't want to have multiple sources of the data, so for now that's probably easiest.
I'll watch this discussion with interest. If people think something is useful at the IANA level I'll do my best to make it happen.
_________________________________________ John Crain Manager of Technical Operations ICANN
crain@icann.org 1AF4 F638 4B2D 3EF2 F9BA 99E4 8D85 69A7 _________________________________________
-----Original Message----- From: owner-nanog@merit.edu [mailto:owner-nanog@merit.edu] On Behalf Of Jeffrey Meltzer Sent: Tuesday, September 03, 2002 11:54 PM To: nanog@merit.edu Subject: Re: IRR listing of IANA-reserved, a question..
Wouldn't the easiest (at least short term) thing be for IANA (or someone else authoritative-like) to put up a text file (not that I'm really sure how many blocks this entails) available via http or ftp for people to periodically wget, etc.
Surely IANA, ARIN, or someone else has some type of up-to date database that they could script, etc to generate this file?
On Tue, Sep 03, 2002 at 06:36:04PM -0700, John M. Brown wrote:
First, standard disclaimers.. 1. This is a technical email. 2. I'm not speaking for any organization, other than ME.
In the last 72 hours I've seen over 3GB of data hit a
network I play
with with source IP's of IANA-RESERVED space.
Various people have reported seeing IANA-RSERVED get announced via BGP at different parts of the net.
Various people maintain lists of IANA-RESERVED space and other such "special use or reserved" prefixes.
These lists are used by others to generate filters, ACL's and the like.
When IANA allocates a new prefix to a RIR, these lists have to be updated manually. Sometime after the space has been put into service and someone complains.
Give the above, would it make sense for:
A) The IANA to maintain a IRR/RADB type database that would allow for the auto generation of filters and ACL's based *purely* on RESERVED IANA space. No other prefixs would be listed.
or
B) For one or more of the RIR's (APNIC, ARIN, LACNIC, RIPE, etc) to maintain such a database, again only IANA-RSERVED space.
or
C) One of the existing well known IRR/RADB's to maintain the db ?
If such a database was available, would YOU use it ?
Would it help your network operations?
Would it be of a possitive or negative nature to your network?
Lets try to stay away from the obvious potential flames and other religous statements.
Thank you.
John Brown Speaking a single person
List the 128-191/8 allocations first. Getting this information from the RIR's has been tedious. After that, details on each /8 for all 256 lines would be useful. It is a stepping stone to some of other suggestions that are bound to come out of this thread. Rob Thomas and I have been playing around with a more stricter ingress prefix filter template to help ISPs get out of the "I only filter RFC1918" rut. You can check out the drafts at: http://www.cisco.com/public/con/isp/security/ The big question was a consensus on how to handle a template recommendation for the old B space and C.
-----Original Message----- From: owner-nanog@merit.edu [mailto:owner-nanog@merit.edu]On Behalf Of John Crain Sent: Wednesday, September 04, 2002 1:04 AM To: 'Jeffrey Meltzer'; nanog@merit.edu Subject: RE: IRR listing of IANA-reserved, a question..
http://www.iana.org/assignments/ipv4-address-space
If folks want me to split it to show 256 lines (one per /8) I can have that happen. Don't want to have multiple sources of the data, so for now that's probably easiest.
I'll watch this discussion with interest. If people think something is useful at the IANA level I'll do my best to make it happen.
_________________________________________ John Crain Manager of Technical Operations ICANN
crain@icann.org 1AF4 F638 4B2D 3EF2 F9BA 99E4 8D85 69A7 _________________________________________
-----Original Message----- From: owner-nanog@merit.edu [mailto:owner-nanog@merit.edu] On Behalf Of Jeffrey Meltzer Sent: Tuesday, September 03, 2002 11:54 PM To: nanog@merit.edu Subject: Re: IRR listing of IANA-reserved, a question..
Wouldn't the easiest (at least short term) thing be for IANA (or someone else authoritative-like) to put up a text file (not that I'm really sure how many blocks this entails) available via http or ftp for people to periodically wget, etc.
Surely IANA, ARIN, or someone else has some type of up-to date database that they could script, etc to generate this file?
On Tue, Sep 03, 2002 at 06:36:04PM -0700, John M. Brown wrote:
First, standard disclaimers.. 1. This is a technical email. 2. I'm not speaking for any organization, other than ME.
In the last 72 hours I've seen over 3GB of data hit a
network I play
with with source IP's of IANA-RESERVED space.
Various people have reported seeing IANA-RSERVED get announced via BGP at different parts of the net.
Various people maintain lists of IANA-RESERVED space and other such "special use or reserved" prefixes.
These lists are used by others to generate filters, ACL's and the like.
When IANA allocates a new prefix to a RIR, these lists have to be updated manually. Sometime after the space has been put into service and someone complains.
Give the above, would it make sense for:
A) The IANA to maintain a IRR/RADB type database that would allow for the auto generation of filters and ACL's based *purely* on RESERVED IANA space. No other prefixs would be listed.
or
B) For one or more of the RIR's (APNIC, ARIN, LACNIC, RIPE, etc) to maintain such a database, again only IANA-RSERVED space.
or
C) One of the existing well known IRR/RADB's to maintain the db ?
If such a database was available, would YOU use it ?
Would it help your network operations?
Would it be of a possitive or negative nature to your network?
Lets try to stay away from the obvious potential flames and other religous statements.
Thank you.
John Brown Speaking a single person
List the 128-191/8 allocations first. Getting this information from the RIR's has been tedious. Unless IANA was responsible for those initial allocations, it should not be IANA's task to make this list. And if IANA makes such a list I think it should be separate from the /8 list presented at http://www.iana.org/assignments/ipv4-address-space
I'd much rather have regional registries list information for customers for all blocks for companies that are located in their territory. And that means information for initial allocations made prior to APNIC/RIPE should be moved to those registraries with link available from ARIN. All those /8 which IANA currently lists as having multiple registries are in reality in ARIN's database currently so we might as well consider ARIN to be responsible registry, however in case where majority of allocations in that block are going to custoers in other region, IANA should consider having another RIR be made reponsible for that /8 block. My opinion is that we have chosen right approach by having a heirchy of responsibilities for ip allocations, i.e. IANA->RIR->ISP->customer. We should try to keep to this strategy and for old records have the information transfered to approriate authority. IANA should only keep records for entire /8 in the end.
After that, details on each /8 for all 256 lines would be useful. It is a stepping stone to some of other suggestions that are bound to come out of this thread.
Rob Thomas and I have been playing around with a more stricter ingress prefix filter template to help ISPs get out of the "I only filter RFC1918" rut. You can check out the drafts at:
http://www.cisco.com/public/con/isp/security/
The big question was a consensus on how to handle a template recommendation for the old B space and C.
-----Original Message----- From: owner-nanog@merit.edu [mailto:owner-nanog@merit.edu]On Behalf Of John Crain Sent: Wednesday, September 04, 2002 1:04 AM To: 'Jeffrey Meltzer'; nanog@merit.edu Subject: RE: IRR listing of IANA-reserved, a question..
http://www.iana.org/assignments/ipv4-address-space
If folks want me to split it to show 256 lines (one per /8) I can have that happen. Don't want to have multiple sources of the data, so for now that's probably easiest.
I'll watch this discussion with interest. If people think something is useful at the IANA level I'll do my best to make it happen.
_________________________________________ John Crain Manager of Technical Operations ICANN
crain@icann.org 1AF4 F638 4B2D 3EF2 F9BA 99E4 8D85 69A7 _________________________________________
-----Original Message----- From: owner-nanog@merit.edu [mailto:owner-nanog@merit.edu] On Behalf Of Jeffrey Meltzer Sent: Tuesday, September 03, 2002 11:54 PM To: nanog@merit.edu Subject: Re: IRR listing of IANA-reserved, a question..
Wouldn't the easiest (at least short term) thing be for IANA (or someone else authoritative-like) to put up a text file (not that I'm really sure how many blocks this entails) available via http or ftp for people to periodically wget, etc.
Surely IANA, ARIN, or someone else has some type of up-to date database that they could script, etc to generate this file?
On Tue, Sep 03, 2002 at 06:36:04PM -0700, John M. Brown wrote:
First, standard disclaimers.. 1. This is a technical email. 2. I'm not speaking for any organization, other than ME.
In the last 72 hours I've seen over 3GB of data hit a
network I play
with with source IP's of IANA-RESERVED space.
Various people have reported seeing IANA-RSERVED get announced via BGP at different parts of the net.
Various people maintain lists of IANA-RESERVED space and other such "special use or reserved" prefixes.
These lists are used by others to generate filters, ACL's and the like.
When IANA allocates a new prefix to a RIR, these lists have to be updated manually. Sometime after the space has been put into service and someone complains.
Give the above, would it make sense for:
A) The IANA to maintain a IRR/RADB type database that would allow for the auto generation of filters and ACL's based *purely* on RESERVED IANA space. No other prefixs would be listed.
or
B) For one or more of the RIR's (APNIC, ARIN, LACNIC, RIPE, etc) to maintain such a database, again only IANA-RSERVED space.
or
C) One of the existing well known IRR/RADB's to maintain the db ?
If such a database was available, would YOU use it ?
Would it help your network operations?
Would it be of a possitive or negative nature to your network?
Lets try to stay away from the obvious potential flames and other religous statements.
Thank you.
John Brown Speaking a single person
On Wed, 4 Sep 2002 william@elan.net wrote:
List the 128-191/8 allocations first. Getting this information from the RIR's has been tedious. Unless IANA was responsible for those initial allocations, it should not be IANA's task to make this list. And if IANA makes such a list I think it should be separate from the /8 list presented at http://www.iana.org/assignments/ipv4-address-space
Originally IANA (Postel) allocated all the numbers. So if its old enough, or special enough like the Cable net 24, it originally came from IANA. But who really cares if it originally was allocated by IANA? Over the years, parts of blocks have been allocated by different groups. In some cases part of the allocations in a network range were originally done by one group, and part way throug the range the maintenance was transfered to a different organization (e.g. maintenance of the 24 block was transfered to ARIN). At the simiplest, figuring out who did what when is still a mess. But we do NOT need to answer that question. If an address block has NOT been allocated by IANA, it should NEVER appear in the global Internet routing table exchanged between ISPs. To make that a positive statement, according to IANA has block X been allocated for unicast routing purposes? We don't need to know who, where, when, why. Just what. Net/8 Allocated for unicast routing on Internet 0/8 N 1/8 N 2/8 N 3/8 Y 4/8 Y ... 10/8 N ... 127/8 N ... 224/8 N ... 255/8 N I know, what about multicast, what about Class E addresses, what about addresses allocated by IANA but not by the RIR, ... All great questions. People want this information so they can filter their BGP routing tables. What addresses are "legal" (following the liberal in what you accept, conservative in what you send motto) for the global Internet BGP routing table. As a first cut let's document, preferably in a machine readable form for easy updating, what are the network blocks allocated for use.
I used the list posted at iana and created the list in the what I think is better for use by own whois server. Its likely to be of use to others. Also based on suggestion by Sean Donelan column has been added if /8 block is or should be routable or not (my own opinion). The list is available at http://www.completewhois.com/iana-ipv4-addresses I'm also posting it here below (you're free to modify or not and use it for whatever purposes you desire): Address Globally Last Change RIR whois Responsibe RIR Comments Block Routable Date server for allocation (Purpose) ------- --------- ---------- -------------- ---------------- ----------------------- 000/8 N Sep-81 none IANA IANA - Reserved 001/8 N Sep-81 none IANA IANA - Reserved 002/8 N Sep-81 none IANA IANA - Reserved 003/8 Y May-94 whois.arin.net IANA General Electric Company 004/8 Y Dec-92 whois.arin.net IANA Genuity/BBN (IANA INFO: Bolt Beranek and Newman Inc.) 005/8 N Jul-95 none IANA IANA - Reserved 006/8 Y Feb-94 whois.arin.net US-DOD Army Information Systems Center 007/8 N Apr-95 none IANA IANA - Reserved 008/8 Y Aug-92 whois.arin.net IANA Genuity/BBN (IANA INFO: Bolt Beranek and Newman Inc.) 009/8 Y Aug-92 whois.arin.net IANA IBM 010/8 N Jun-95 none-rfc1918 IANA IANA - Private Use. See RFC 1918 011/8 Y May-93 whois.arin.net US-DOD DoD Intel Information Systems 012/8 Y Jun-95 whois.arin.net IANA AT&T Bell Laboratories 013/8 Y Sep-91 whois.arin.net IANA Xerox Corporation 014/8 N Jun-91 none-14 IANA IANA - Public Data Network 015/8 Y Jul-94 whois.arin.net IANA Hewlett-Packard Company 016/8 Y Nov-94 whois.arin.net IANA Digital Equipment Corporation 017/8 Y Jul-92 whois.arin.net IANA Apple Computer Inc. 018/8 Y Jan-94 whois.arin.net IANA MIT 019/8 Y May-95 whois.arin.net IANA Ford Motor Company 020/8 Y Oct-94 whois.arin.net IANA Computer Sciences Corporation 021/8 Y Jul-91 whois.arin.net US-DOD DDN-RVN 022/8 Y May-93 whois.arin.net US-DOD Defense Information Systems Agency 023/8 N Jul-95 none IANA IANA - Reserved 024/8 Y May-01 whois.arin.net ARIN ARIN - Cable Block (Formerly IANA - Jul 95) 025/8 Y Jan-95 whois.arin.net IANA Royal Signals and Radar Establishment (insnet.net route block; EU territory should be in RIPE database) 026/8 Y May-95 whois.arin.net US-DOD Defense Information Systems Agency 027/8 N Apr-95 none IANA IANA - Reserved 028/8 Y Jul-92 whois.arin.net US-DOD DSI-North 029/8 Y Jul-91 whois.arin.net US-DOD Defense Information Systems Agency 030/8 Y Jul-91 whois.arin.net US-DOD Defense Information Systems Agency 031/8 N Apr-99 none IANA IANA - Reserved 032/8 Y Jun-94 whois.arin.net IANA AT&T (IANA INFO: Norsk Informasjonsteknologi) 033/8 Y Jan-91 whois.arin.net US-DOD DLA Systems Automation Center 034/8 Y Mar-93 whois.arin.net IANA Halliburton Company 035/8 Y Apr-94 whois.arin.net IANA MERIT Computer Network 036/8 N Jul-00 none IANA IANA - Reserved (Formerly Stanford University - Apr 93 to Jul 00) 037/8 N Apr-95 none IANA IANA - Reserved 038/8 Y Sep-94 whois.arin.net IANA COGENT/PSI (IANA INFO: Performance Systems International) 039/8 N Apr-95 none IANA IANA - Reserved 040/8 Y Jun-94 whois.arin.net IANA Eli Lily and Company 041/8 N May-95 none IANA IANA - Reserved 042/8 N Jul-95 none IANA IANA - Reserved 043/8 Y Jan-91 whois.arin.net IANA V6NIC.NET (IANA INFO: Japan Inet. ; Japan territory should be in APNIC database) 044/8 Y Jul-92 whois.arin.net IANA Amateur Radio Digital Communications 045/8 Y Jan-95 whois.arin.net IANA Interop Show Network 046/8 Y Dec-92 whois.arin.net IANA Genuity/BBN (IANA INFO: Bolt Beranek and Newman Inc.) 047/8 Y Jan-91 whois.arin.net IANA Nortel (IANA INFO: Bell-Northern Research) 048/8 Y May-95 whois.arin.net IANA Prudential Securities Inc. 049/8 N Mar-98 none IANA IANA (Formerly DoD - Joint Technical Command. Used: May 94 - Mar 98) 050/8 N Mar-98 none IANA IANA (Formerly DoD - Joint Technical Command. Used: May 94 - Mar 98) 051/8 Y Dec-91 whois.arin.net IANA Deparment of Social Security of UK (EU territory should be in RIPE database) 052/8 Y Dec-91 whois.arin.net IANA E.I. duPont de Nemours and Co., Inc. 053/8 Y Oct-93 whois.arin.net IANA Cap Debis CCS (EU territory should be in RIPE database) 054/8 Y Mar-92 whois.arin.net IANA Merck and Co., Inc. 055/8 Y Apr-95 whois.arin.net US-DOD Naval Ocean Systems Center (IANA INFO: Boeing Computer Services) 056/8 Y Jun-94 whois.arin.net IANA U.S. Postal Service Jun 94 057/8 Y May-95 whois.arin.net IANA SITA (Equant.Net routable. EU territory should be in RIPE database) 058/8 N Sep-81 none IANA IANA - Reserved 059/8 N Sep-81 none IANA IANA - Reserved 060/8 N Sep-81 none IANA IANA - Reserved 061/8 Y Apr-97 whois.apnic.net APNIC APNIC - Pacific Rim Apr 97 062/8 Y Apr-97 whois.ripe.net RIPE RIPE NCC - Europe 063/8 Y Apr-97 whois.arin.net ARIN ARIN 064/8 Y Jul-99 whois.arin.net ARIN ARIN 065/8 Y Jul-00 whois.arin.net ARIN ARIN 066/8 Y Jul-00 whois.arin.net ARIN ARIN 067/8 Y May-01 whois.arin.net ARIN ARIN 068/8 Y Jun-01 whois.arin.net ARIN ARIN 069/8 Y Aug-02 whois.arin.net ARIN ARIN 070/8 N Sep-81 none IANA IANA - Reserved 071/8 N Sep-81 none IANA IANA - Reserved 072/8 N Sep-81 none IANA IANA - Reserved 073/8 N Sep-81 none IANA IANA - Reserved 074/8 N Sep-81 none IANA IANA - Reserved 075/8 N Sep-81 none IANA IANA - Reserved 076/8 N Sep-81 none IANA IANA - Reserved 077/8 N Sep-81 none IANA IANA - Reserved 078/8 N Sep-81 none IANA IANA - Reserved 079/8 N Sep-81 none IANA IANA - Reserved 080/8 Y Apr-01 whois.ripe.net RIPE RIPE NC 081/8 Y Apr-01 whois.ripe.net RIPE RIPE NC 082/8 N Sep-81 none IANA IANA - Reserved 083/8 N Sep-81 none IANA IANA - Reserved 084/8 N Sep-81 none IANA IANA - Reserved 085/8 N Sep-81 none IANA IANA - Reserved 086/8 N Sep-81 none IANA IANA - Reserved 087/8 N Sep-81 none IANA IANA - Reserved 088/8 N Sep-81 none IANA IANA - Reserved 089/8 N Sep-81 none IANA IANA - Reserved 090/8 N Sep-81 none IANA IANA - Reserved 091/8 N Sep-81 none IANA IANA - Reserved 092/8 N Sep-81 none IANA IANA - Reserved 093/8 N Sep-81 none IANA IANA - Reserved 094/8 N Sep-81 none IANA IANA - Reserved 095/8 N Sep-81 none IANA IANA - Reserved 096/8 N Sep-81 none IANA IANA - Reserved 097/8 N Sep-81 none IANA IANA - Reserved 098/8 N Sep-81 none IANA IANA - Reserved 099/8 N Sep-81 none IANA IANA - Reserved 100/8 N Sep-81 none IANA IANA - Reserved 101/8 N Sep-81 none IANA IANA - Reserved 102/8 N Sep-81 none IANA IANA - Reserved 103/8 N Sep-81 none IANA IANA - Reserved 104/8 N Sep-81 none IANA IANA - Reserved 105/8 N Sep-81 none IANA IANA - Reserved 106/8 N Sep-81 none IANA IANA - Reserved 107/8 N Sep-81 none IANA IANA - Reserved 108/8 N Sep-81 none IANA IANA - Reserved 109/8 N Sep-81 none IANA IANA - Reserved 110/8 N Sep-81 none IANA IANA - Reserved 111/8 N Sep-81 none IANA IANA - Reserved 112/8 N Sep-81 none IANA IANA - Reserved 113/8 N Sep-81 none IANA IANA - Reserved 114/8 N Sep-81 none IANA IANA - Reserved 115/8 N Sep-81 none IANA IANA - Reserved 116/8 N Sep-81 none IANA IANA - Reserved 117/8 N Sep-81 none IANA IANA - Reserved 118/8 N Sep-81 none IANA IANA - Reserved 119/8 N Sep-81 none IANA IANA - Reserved 120/8 N Sep-81 none IANA IANA - Reserved 121/8 N Sep-81 none IANA IANA - Reserved 122/8 N Sep-81 none IANA IANA - Reserved 123/8 N Sep-81 none IANA IANA - Reserved 124/8 N Sep-81 none IANA IANA - Reserved 125/8 N Sep-81 none IANA IANA - Reserved 126/8 N Sep-81 none IANA IANA - Reserved 127/8 N Sep-81 none IANA IANA - Reserved 128/8 Y May-93 whois.arin.net IANA Various Registries - Early Internic Registrations 129/8 Y May-93 whois.arin.net IANA Various Registries - Early Internic Registrations 130/8 Y May-93 whois.arin.net IANA Various Registries - Early Internic Registrations 131/8 Y May-93 whois.arin.net IANA Various Registries - Early Internic Registrations 132/8 Y May-93 whois.arin.net IANA Various Registries - Early Internic Registrations 133/8 Y May-93 whois.arin.net IANA Various Registries - Early Internic Registrations 134/8 Y May-93 whois.arin.net IANA Various Registries - Early Internic Registrations 135/8 Y May-93 whois.arin.net IANA Various Registries - Early Internic Registrations 136/8 Y May-93 whois.arin.net IANA Various Registries - Early Internic Registrations 137/8 Y May-93 whois.arin.net IANA Various Registries - Early Internic Registrations 138/8 Y May-93 whois.arin.net IANA Various Registries - Early Internic Registrations 139/8 Y May-93 whois.arin.net IANA Various Registries - Early Internic Registrations 140/8 Y May-93 whois.arin.net IANA Various Registries - Early Internic Registrations 141/8 Y May-93 whois.arin.net IANA Various Registries - Early Internic Registrations 142/8 Y May-93 whois.arin.net IANA Various Registries - Early Internic Registrations 143/8 Y May-93 whois.arin.net IANA Various Registries - Early Internic Registrations 144/8 Y May-93 whois.arin.net IANA Various Registries - Early Internic Registrations 145/8 Y May-93 whois.arin.net IANA Various Registries - Early Internic Registrations 146/8 Y May-93 whois.arin.net IANA Various Registries - Early Internic Registrations 147/8 Y May-93 whois.arin.net IANA Various Registries - Early Internic Registrations 148/8 Y May-93 whois.arin.net IANA Various Registries - Early Internic Registrations 149/8 Y May-93 whois.arin.net IANA Various Registries - Early Internic Registrations 150/8 Y May-93 whois.arin.net IANA Various Registries - Early Internic Registrations 151/8 Y May-93 whois.arin.net IANA Various Registries - Early Internic Registrations 152/8 Y May-93 whois.arin.net IANA Various Registries - Early Internic Registrations 153/8 Y May-93 whois.arin.net IANA Various Registries - Early Internic Registrations 154/8 Y May-93 whois.arin.net IANA Various Registries - Early Internic Registrations 155/8 Y May-93 whois.arin.net IANA Various Registries - Early Internic Registrations 156/8 Y May-93 whois.arin.net IANA Various Registries - Early Internic Registrations 157/8 Y May-93 whois.arin.net IANA Various Registries - Early Internic Registrations 158/8 Y May-93 whois.arin.net IANA Various Registries - Early Internic Registrations 159/8 Y May-93 whois.arin.net IANA Various Registries - Early Internic Registrations 160/8 Y May-93 whois.arin.net IANA Various Registries - Early Internic Registrations 161/8 Y May-93 whois.arin.net IANA Various Registries - Early Internic Registrations 162/8 Y May-93 whois.arin.net IANA Various Registries - Early Internic Registrations 163/8 Y May-93 whois.arin.net IANA Various Registries - Early Internic Registrations 164/8 Y May-93 whois.arin.net IANA Various Registries - Early Internic Registrations 165/8 Y May-93 whois.arin.net IANA Various Registries - Early Internic Registrations 166/8 Y May-93 whois.arin.net IANA Various Registries - Early Internic Registrations 167/8 Y May-93 whois.arin.net IANA Various Registries - Early Internic Registrations 168/8 Y May-93 whois.arin.net IANA Various Registries - Early Internic Registrations 169/8 Y May-93 whois.arin.net IANA Various Registries - Early Internic Registrations 170/8 Y May-93 whois.arin.net IANA Various Registries - Early Internic Registrations 171/8 Y May-93 whois.arin.net IANA Various Registries - Early Internic Registrations 172/8 Y May-93 whois.arin.net IANA Various Registries - Early Internic Registrations 173/8 Y May-93 whois.arin.net IANA Various Registries - Early Internic Registrations 174/8 Y May-93 whois.arin.net IANA Various Registries - Early Internic Registrations 175/8 Y May-93 whois.arin.net IANA Various Registries - Early Internic Registrations 176/8 Y May-93 whois.arin.net IANA Various Registries - Early Internic Registrations 177/8 Y May-93 whois.arin.net IANA Various Registries - Early Internic Registrations 178/8 Y May-93 whois.arin.net IANA Various Registries - Early Internic Registrations 179/8 Y May-93 whois.arin.net IANA Various Registries - Early Internic Registrations 180/8 Y May-93 whois.arin.net IANA Various Registries - Early Internic Registrations 181/8 Y May-93 whois.arin.net IANA Various Registries - Early Internic Registrations 182/8 Y May-93 whois.arin.net IANA Various Registries - Early Internic Registrations 183/8 Y May-93 whois.arin.net IANA Various Registries - Early Internic Registrations 184/8 Y May-93 whois.arin.net IANA Various Registries - Early Internic Registrations 185/8 Y May-93 whois.arin.net IANA Various Registries - Early Internic Registrations 186/8 Y May-93 whois.arin.net IANA Various Registries - Early Internic Registrations 187/8 Y May-93 whois.arin.net IANA Various Registries - Early Internic Registrations 188/8 Y May-93 whois.arin.net IANA Various Registries - Early Internic Registrations 189/8 Y May-93 whois.arin.net IANA Various Registries - Early Internic Registrations 190/8 Y May-93 whois.arin.net IANA Various Registries - Early Internic Registrations 191/8 Y May-93 whois.arin.net IANA Various Registries - Early Internic Registrations 192/8 Y May-93 whois.arin.net IANA Various Registries MultiRegional - Early Registrations 193/8 Y May-93 whois.ripe.net RIPE RIPE NCC - Europe 194/8 Y May-93 whois.ripe.net RIPE RIPE NCC - Europe 195/8 Y May-93 whois.ripe.net RIPE RIPE NCC - Europe 196/8 Y May-93 whois.arin.net IANA Various Registries - Early Internic Registrations 197/8 N May-93 none IANA IANA - Reserved 198/8 Y May-93 whois.arin.net IANA Various Registries - Early Internic Registrations 199/8 Y May-93 whois.arin.net ARIN ARIN - North America 200/8 Y May-93 whois.lacnic.net LACNIC LACNIC - Transfered from ARIN (IANA INFO: ARIN - Central and South America) 201/8 Y May-93 whois.lacnic.net LACNIC LACNIC - New Assignments - 2002 (IANA INFO: Reserved - Central and South America) 202/8 Y May-93 whois.apnic.net APNIC APNIC - Pacific Rim 203/8 Y May-93 whois.apnic.net APNIC APNIC - Pacific Rim 204/8 Y Mar-94 whois.arin.net ARIN ARIN - North America 205/8 Y Mar-94 whois.arin.net ARIN ARIN - North America 206/8 Y Apr-95 whois.arin.net ARIN ARIN - North America 207/8 Y Nov-95 whois.arin.net ARIN ARIN - North America 208/8 Y Apr-96 whois.arin.net ARIN ARIN - North America 209/8 Y Jun-96 whois.arin.net ARIN ARIN - North America 210/8 Y Jun-96 whois.apnic.net APNIC APNIC - Pacific Rim 211/8 Y Jun-96 whois.apnic.net APNIC APNIC - Pacific Rim 212/8 Y Oct-97 whois.ripe.net RIPE RIPE NCC - Europe 213/8 Y Mar-99 whois.ripe.net RIPE RIPE NCC - Europe 214/8 Y Mar-98 whois.arin.net US-DOD US Department of Defense 215/8 Y Mar-98 whois.arin.net US-DOD US Department of Defense 216/8 Y Apr-98 whois.arin.net ARIN ARIN - North America 217/8 Y Jun-00 whois.ripe.net RIPE RIPE NCC - Europe 218/8 Y Dec-00 whois.apnic.net APNIC APNIC - Pacific Rim 219/8 Y Sep-01 whois.apnic.net APNIC APNIC 220/8 Y Dec-01 whois.apnic.net APNIC APNIC 221/8 Y Jul-02 whois.apnic.net APNIC APNIC 222/8 N Sep-81 none IANA IANA - Reserved 223/8 N Sep-81 none IANA IANA - Reserved 224/8 N Sep-81 none-rfc3171 IANA IANA - Multicast. See RFC 3171 225/8 N Sep-81 none-rfc3171 IANA IANA - Multicast. See RFC 3171 226/8 N Sep-81 none-rfc3171 IANA IANA - Multicast. See RFC 3171 227/8 N Sep-81 none-rfc3171 IANA IANA - Multicast. See RFC 3171 228/8 N Sep-81 none-rfc3171 IANA IANA - Multicast. See RFC 3171 229/8 N Sep-81 none-rfc3171 IANA IANA - Multicast. See RFC 3171 230/8 N Sep-81 none-rfc3171 IANA IANA - Multicast. See RFC 3171 231/8 N Sep-81 none-rfc3171 IANA IANA - Multicast. See RFC 3171 232/8 N Sep-81 none-rfc3171 IANA IANA - Multicast. See RFC 3171 233/8 N Sep-81 none-rfc3171 IANA IANA - Multicast. See RFC 3171 234/8 N Sep-81 none-rfc3171 IANA IANA - Multicast. See RFC 3171 235/8 N Sep-81 none-rfc3171 IANA IANA - Multicast. See RFC 3171 236/8 N Sep-81 none-rfc3171 IANA IANA - Multicast. See RFC 3171 237/8 N Sep-81 none-rfc3171 IANA IANA - Multicast. See RFC 3171 238/8 N Sep-81 none-rfc3171 IANA IANA - Multicast. See RFC 3171 239/8 N Sep-81 none-rfc3171 IANA IANA - Multicast. See RFC 3171 240/8 N Sep-81 none IANA IANA - Reserved 241/8 N Sep-81 none IANA IANA - Reserved 242/8 N Sep-81 none IANA IANA - Reserved 243/8 N Sep-81 none IANA IANA - Reserved 244/8 N Sep-81 none IANA IANA - Reserved 245/8 N Sep-81 none IANA IANA - Reserved 246/8 N Sep-81 none IANA IANA - Reserved 247/8 N Sep-81 none IANA IANA - Reserved 248/8 N Sep-81 none IANA IANA - Reserved 249/8 N Sep-81 none IANA IANA - Reserved 250/8 N Sep-81 none IANA IANA - Reserved 251/8 N Sep-81 none IANA IANA - Reserved 252/8 N Sep-81 none IANA IANA - Reserved 253/8 N Sep-81 none IANA IANA - Reserved 254/8 N Sep-81 none IANA IANA - Reserved 255/8 N Sep-81 none IANA IANA - Reserved
On Wed, 4 Sep 2002 william@elan.net wrote:
I used the list posted at iana and created the list in the what I think is better for use by own whois server. Its likely to be of use to others.
Also based on suggestion by Sean Donelan column has been added if /8 block is or should be routable or not (my own opinion).
The list is available at http://www.completewhois.com/iana-ipv4-addresses
I'm also posting it here below (you're free to modify or not and use it for whatever purposes you desire):
92 /8s reserved... Since the start of 1999, ARIN has grown by 6 /8s, APNIC and RIPE by 4 each, for a total of 14 /8s in almost 4 years. Call it an even /4 per 4 years, for an average of a /6 per year. Now, assume some acceleration in growth...say global assignment increases to /7 per year starting next year, which I think is unreasonable but illustrative for the sake of the point. That would still provide space for the next 10+ years. And looking at the list, there are still several companies who have unreasonable allocations. You have weird things like Eli Lilly and Company, Ford, US Postal Service, Prudential Securities, Interop Show Network, Halliburton Company, Apple, Xerox, Computer Sciences Corporation, etc. I'm sure these companies have legitimate needs for large amounts of address space, but they most likely don't even need a /8 combined. Surely the US-DOD (with 10 /8s to their name) would like to renumber into rfc1918 space for a myriad of reasons. If not, one would think that can be reduced considerably. This is all ignoring the considerable amount of dead space in 128/2. Does anybody keep statistics about what percentage of useable space is announced? So...my question is, without a marketable product, and without a need for the considerable future, will IPv6 remain a barely supported protocol for too long to be implemented? Will IPv6 be surpassed by a superior protocol before it becomes neccessary to be implemented? 10 years is a long time... Andy xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx Andy Dills 301-682-9972 Xecunet, LLC www.xecu.net xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx Dialup * Webhosting * E-Commerce * High-Speed Access
On Thu, 5 Sep 2002, Andy Dills wrote:
This is all ignoring the considerable amount of dead space in 128/2. Does anybody keep statistics about what percentage of useable space is announced?
See the CAIDA web site (www.caida.org). It is chock full of interesting statistics about the Internet.
Whoops that should be http://www.cisco.com/public/cons/isp/security/
-----Original Message----- From: owner-nanog@merit.edu [mailto:owner-nanog@merit.edu]On Behalf Of Barry Raveendran Greene Sent: Wednesday, September 04, 2002 1:29 PM To: John Crain; 'Jeffrey Meltzer'; nanog@merit.edu Subject: RE: IRR listing of IANA-reserved, a question..
List the 128-191/8 allocations first. Getting this information from the RIR's has been tedious. After that, details on each /8 for all 256 lines would be useful. It is a stepping stone to some of other suggestions that are bound to come out of this thread.
Rob Thomas and I have been playing around with a more stricter ingress prefix filter template to help ISPs get out of the "I only filter RFC1918" rut. You can check out the drafts at:
http://www.cisco.com/public/con/isp/security/
The big question was a consensus on how to handle a template recommendation for the old B space and C.
-----Original Message----- From: owner-nanog@merit.edu [mailto:owner-nanog@merit.edu]On Behalf Of John Crain Sent: Wednesday, September 04, 2002 1:04 AM To: 'Jeffrey Meltzer'; nanog@merit.edu Subject: RE: IRR listing of IANA-reserved, a question..
http://www.iana.org/assignments/ipv4-address-space
If folks want me to split it to show 256 lines (one per /8) I can have that happen. Don't want to have multiple sources of the data, so for now that's probably easiest.
I'll watch this discussion with interest. If people think something is useful at the IANA level I'll do my best to make it happen.
_________________________________________ John Crain Manager of Technical Operations ICANN
crain@icann.org 1AF4 F638 4B2D 3EF2 F9BA 99E4 8D85 69A7 _________________________________________
-----Original Message----- From: owner-nanog@merit.edu [mailto:owner-nanog@merit.edu] On Behalf Of Jeffrey Meltzer Sent: Tuesday, September 03, 2002 11:54 PM To: nanog@merit.edu Subject: Re: IRR listing of IANA-reserved, a question..
Wouldn't the easiest (at least short term) thing be for IANA (or someone else authoritative-like) to put up a text file (not that I'm really sure how many blocks this entails) available via http or ftp for people to periodically wget, etc.
Surely IANA, ARIN, or someone else has some type of up-to date database that they could script, etc to generate this file?
On Tue, Sep 03, 2002 at 06:36:04PM -0700, John M. Brown wrote:
First, standard disclaimers.. 1. This is a technical email. 2. I'm not speaking for any organization, other than ME.
In the last 72 hours I've seen over 3GB of data hit a
network I play
with with source IP's of IANA-RESERVED space.
Various people have reported seeing IANA-RSERVED get announced via BGP at different parts of the net.
Various people maintain lists of IANA-RESERVED space and other such "special use or reserved" prefixes.
These lists are used by others to generate filters, ACL's and the like.
When IANA allocates a new prefix to a RIR, these lists have to be updated manually. Sometime after the space has been put into service and someone complains.
Give the above, would it make sense for:
A) The IANA to maintain a IRR/RADB type database that would allow for the auto generation of filters and ACL's based *purely* on RESERVED IANA space. No other prefixs would be listed.
or
B) For one or more of the RIR's (APNIC, ARIN, LACNIC, RIPE, etc) to maintain such a database, again only IANA-RSERVED space.
or
C) One of the existing well known IRR/RADB's to maintain the db ?
If such a database was available, would YOU use it ?
Would it help your network operations?
Would it be of a possitive or negative nature to your network?
Lets try to stay away from the obvious potential flames and other religous statements.
Thank you.
John Brown Speaking a single person
Speaking for myself too: I have been wanting an *authoritative* *single* listing of unallocated address space for at least 6 years. Note that this is at a finer granularity than the IANA allocations list and it would have much more frequent changes than the IANA list as address space is allocated to local registries. However it could include a more coarse data set that changes less frequently for those that do not want or need the higher granularity. The only way to make this happen is for the RIRs to collect this data among themselves and publish it regularly. Because of the possible ramifications of errors in this list it is not as simple to do that reliably as it may seem at first glance; but it should be done. I know that the RIRs have efforts underway to publish such authoritative lists. I do not know the exact status of this work. But I fully agree with your requirement for a *single* *authoritative* list. Of course I would use it in the routers I operate. However these are not significant to many peoiple these days. Daniel PS: I do not care at all about the format as long as it is readily machine parseable. Daniel
Daniel, Daniel Karrenberg wrote:
Speaking for myself too: [...]
I know that the RIRs have efforts underway to publish such authoritative lists. I do not know the exact status of this work. But I fully agree with your requirement for a *single* *authoritative* list.
Yes, we at the RIPE NCC are working on such list. However the task, as you said, is not as easy as it seems to be. We have to be confident in the data we publish and this requires some work especially regarding early registrations. There are also efforts by the RIRs to make allocation records more accurate and appearing in the right RIR, the ERX project for instance http://www.arin.net/registration/erx/index.html.
Of course I would use it in the routers I operate. However these are not significant to many peoiple these days.
Daniel
PS: I do not care at all about the format as long as it is readily machine parseable.
Daniel
Regards, Andrei Robachevsky DB Group Manager RIPE NCC
We need to be careful, at the RIR level, that data being published doesn't get mucked up. If a RIR publishes a netblock as "unallocated" and that happens to knock people off the net, then the RIR's need to be willing to solve that problem 7x24x365. Having the IANA, or other entity publishing a list of blocks that have not been allocated to any RIR is much less of a risk, and much less likely to cause operational outage issues. At the RIR level, it would be far more useful to have accurate data on who the registrant / user of the space it. I know the RIR's are working very hard at getting the legacy data in better condition. john brown as a person, and nothing else On Wed, Sep 04, 2002 at 12:46:13PM +0200, Daniel Karrenberg wrote:
Speaking for myself too:
I have been wanting an *authoritative* *single* listing of unallocated address space for at least 6 years. Note that this is at a finer granularity than the IANA allocations list and it would have much more frequent changes than the IANA list as address space is allocated to local registries.
However it could include a more coarse data set that changes less frequently for those that do not want or need the higher granularity.
The only way to make this happen is for the RIRs to collect this data among themselves and publish it regularly. Because of the possible ramifications of errors in this list it is not as simple to do that reliably as it may seem at first glance; but it should be done.
I know that the RIRs have efforts underway to publish such authoritative lists. I do not know the exact status of this work. But I fully agree with your requirement for a *single* *authoritative* list.
Of course I would use it in the routers I operate. However these are not significant to many peoiple these days.
Daniel
PS: I do not care at all about the format as long as it is readily machine parseable.
Daniel
John M. Brown wrote:
In the last 72 hours I've seen over 3GB of data hit a network I play with with source IP's of IANA-RESERVED space.
Just out of curiosity, do you know that these are bogus source addresses? Some of the IANA-RESERVED block is actually valid and is used by IANA's computers. My company was blocking all of the IANA-RESERVED space for a while, until we discovered that the IANA web server is using an address in that space. Note: $dig www.iana.org a ; <<>> DiG 2.0 <<>> www.iana.org a ;; ->>HEADER<<- opcode: QUERY , status: NOERROR, id: 6 ;; flags: qr rd ra ; Ques: 1, Ans: 1, Auth: 6, Addit: 6 ;; QUESTIONS: ;; www.iana.org, type = A, class = IN ;; ANSWERS: www.iana.org. 68055 A 192.0.34.69 ... and: $whois -h whois.arin.net 192.0.34.69 IANA RESERVED-192 (NET-192-0-0-0-1) 192.0.0.0 - 192.0.127.255 ICANN c/o Internet Assigned Numbers Authority ICANN (NET-192-0-32-0-1) 192.0.32.0 - 192.0.47.255
Various people have reported seeing IANA-RSERVED get announced via BGP at different parts of the net.
Again, bogus addresses or legitimate IANA servers? Not everything in IANA-RESERVED is bogus. -- David
On Wed, 04 Sep 2002 10:08:00 -0400 David Charlap <David.Charlap@marconi.com> wrote:
John M. Brown wrote:
In the last 72 hours I've seen over 3GB of data hit a network I play with with source IP's of IANA-RESERVED space.
Just out of curiosity, do you know that these are bogus source addresses? Some of the IANA-RESERVED block is actually valid and is used by IANA's computers.
My company was blocking all of the IANA-RESERVED space for a while, until we discovered that the IANA web server is using an address in that space.
This seems like an unwise overlaying of the IANA-RESERVED space to me. Why can't IANA allocate itself a /20 (or whatever it needs) and keep IANA-RESERVED space for unallocated addresses (plus maybe experimental uses that can and should be filtered at every border). Regards Marshall Eubanks that
Note: $dig www.iana.org a
; <<>> DiG 2.0 <<>> www.iana.org a ;; ->>HEADER<<- opcode: QUERY , status: NOERROR, id: 6 ;; flags: qr rd ra ; Ques: 1, Ans: 1, Auth: 6, Addit: 6 ;; QUESTIONS: ;; www.iana.org, type = A, class = IN
;; ANSWERS: www.iana.org. 68055 A 192.0.34.69 ...
and: $whois -h whois.arin.net 192.0.34.69 IANA RESERVED-192 (NET-192-0-0-0-1) 192.0.0.0 - 192.0.127.255 ICANN c/o Internet Assigned Numbers Authority ICANN (NET-192-0-32-0-1) 192.0.32.0 - 192.0.47.255
Various people have reported seeing IANA-RSERVED get announced via BGP at different parts of the net.
Again, bogus addresses or legitimate IANA servers? Not everything in IANA-RESERVED is bogus.
-- David
They are not bogus, hence the sub-deligation, and hence a good reason to have a more detailed source of information. I would suspect that this block should be "chopped" a bit to reflect the IANA/ICANN usage. This block was first routed on the internet via AS 226 around late summer early fall 1999. On Wed, Sep 04, 2002 at 10:08:00AM -0400, David Charlap wrote:
John M. Brown wrote:
In the last 72 hours I've seen over 3GB of data hit a network I play with with source IP's of IANA-RESERVED space.
Just out of curiosity, do you know that these are bogus source addresses? Some of the IANA-RESERVED block is actually valid and is used by IANA's computers.
My company was blocking all of the IANA-RESERVED space for a while, until we discovered that the IANA web server is using an address in that space.
Note: $dig www.iana.org a
; <<>> DiG 2.0 <<>> www.iana.org a ;; ->>HEADER<<- opcode: QUERY , status: NOERROR, id: 6 ;; flags: qr rd ra ; Ques: 1, Ans: 1, Auth: 6, Addit: 6 ;; QUESTIONS: ;; www.iana.org, type = A, class = IN
;; ANSWERS: www.iana.org. 68055 A 192.0.34.69 ...
and: $whois -h whois.arin.net 192.0.34.69 IANA RESERVED-192 (NET-192-0-0-0-1) 192.0.0.0 - 192.0.127.255 ICANN c/o Internet Assigned Numbers Authority ICANN (NET-192-0-32-0-1) 192.0.32.0 - 192.0.47.255
Various people have reported seeing IANA-RSERVED get announced via BGP at different parts of the net.
Again, bogus addresses or legitimate IANA servers? Not everything in IANA-RESERVED is bogus.
-- David
participants (11)
-
Andrei Robachevsky -
Andy Dills -
Barry Raveendran Greene -
Daniel Karrenberg -
David Charlap -
Jeffrey Meltzer -
John Crain -
John M. Brown -
Marshall Eubanks -
Sean Donelan -
william＠elan.net