North American Network Operators Group|
Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical
Re: Operational Issues with 126.96.36.199/8...
On Fri, 6 Dec 2002, Rob Thomas wrote: > I (and Steve Gill) am more than happy to create such a list. Heck, you > don't even have to bug me! :) I've even pondered the idea of hosting > a WHOIS server that contains only bogon ranges. So many martian lists, so little authority. > whois -h whois.radb.net rs-martians route-set: rs-martians descr: Martian networks members: 0.0.0.0/0^32, 10.0.0.0/8^+, 192.168.0.0/16^+, 188.8.131.52/16^+, 192.0.0.0/24^+, 184.108.40.206/3^+, 127.0.0.0/8^+, 172.16.0.0/20^+, 192.0.2.0/24^+, 220.127.116.11/16^+, 18.104.22.168/24^+, 0.0.0.0/0^26-32 remarks: these networks and any more-specific networks are not remarks: accepted by eu-X across any peering points admin-c: EUX-RIPE tech-c: EUX-RIPE notify: [email protected] mnt-by: VASNET-MNT changed: [email protected] 20011020 source: RIPE route-set: RS-MARTIANS descr: The ff. routes should be denied by all border router members: 0.0.0.0/0, 127.0.0.0/8^+, 10.0.0.0/8^+, 172.16.0.0/20^+, 192.168.0.0/16^+, 192.0.2.0/24^+, 22.214.171.124/16^+, 126.96.36.199/16^+, 192.0.0.0/24^+, 188.8.131.52/24^+, 184.108.40.206/3^+, 0.0.0.0/0^26-32 remarks: These routes are usually blocked by ISPs. tech-c: AP16-AP admin-c: AP16-AP notify: [email protected] mnt-by: MAINT-AU-BLUETOOTH changed: [email protected] 20021111 source: APNIC route-set: rs-martians descr: Martian and IANA reserved networks members: 0.0.0.0/7, 220.127.116.11/8, 18.104.22.168/8, 10.0.0.0/8, 22.214.171.124/8, 126.96.36.199/8, 188.8.131.52/8, 184.108.40.206/7, 220.127.116.11/8, 18.104.22.168/8, 22.214.171.124/8, 126.96.36.199/7, 188.8.131.52/8, 184.108.40.206/7, 220.127.116.11/5, 18.104.22.168/8, 22.214.171.124/6, 126.96.36.199/5, 188.8.131.52/3, 127.0.0.0/8, 184.108.40.206/16, 220.127.116.11/16, 172.16.0.0/12, 18.104.22.168/16, 192.0.0.0/24, 192.0.2.0/24, 22.214.171.124/17, 126.96.36.199/24, 188.8.131.52/24, 184.108.40.206/24, 220.127.116.11/24, 18.104.22.168/21, 22.214.171.124/23, 126.96.36.199/24, 188.8.131.52/24, 192.168.0.0/16, 184.108.40.206/8, 220.127.116.11/24, 18.104.22.168/8, 22.214.171.124/7 remarks: these networks and any more-specific networks are not remarks: accepted by Level 3 across any peering points admin-c: LV3-LEVEL3 tech-c: LV3-LEVEL3 notify: [email protected] mnt-by: LEVEL3-MNT changed: [email protected] 20021125 source: LEVEL3 > The problem with all martian lists, going back to the very first one, is third-party maintainers eventually stop maintaining them after a few years while the lists themselves get embedded in many unexpected places. I'm sure Rob will do a great job for a few years, but no one does this forever. IANA is the source of the delegations, maintainer of the assignments, and is authoritative (i.e. if IANA gets it wrong, we're all screwed). The simpliest solution is when IANA delegates an IPv4/IPv6 block for something to post a message to the IETF-Announce, and the appropriate IANA and RIR list, much like the RFC-Editor does with RFCs.