At 14:16 26/11/2004, Andy Linton wrote:
About a month ago Sid Jones and I had a conversation about one of his customers who has a /23 in this space. We raised the issue with APNIC and I attach the thread.
There's a clear implication in the mail below that APNIC expect Telecom NZ to cooperate on this issue which seems to be at odds with their behaviour over 202.49.252.0 - 202.49.255.255 as David Robb has noted.
I suggest a number of things here:
1) each ISP who routes portions of this block should encourage their customers to write to APNIC requesting that as this block was allocated via the University of Waikato which was operating as a proto NZNIC at the time then this address space should be deemed to be provider independent space which should be administered as other 'swamp' space.
For example, here's a record that's recently been obscured as part of this exercise:
inetnum: 202.36.137.0 - 202.36.137.255
netname: NZMFE descr: Ministry for the Environment descr: P.O. Box 10-362 descr: The Terrace descr: Wellington country: NZ admin-c: MB22-AP tech-c: MB22-AP notify: dbmon(a)apnic.net mnt-by: APNIC-HM changed: hostmaster(a)apnic.net 19931217 status: ALLOCATED PORTABLE changed: hm-changed(a)apnic.net 20031020 source: APNIC
This is clearly PORTABLE space and makes no reference to Telecom NZ and the admin-c and tech-c details were updated just over a year ago. Note that this address was allocated in 1993 long before Netway (a Telecom NZ subsidiary) entered the picture at all. Why are APNIC changing the goal posts?
Sorry for dredging up an old thread everyone, but I've noticed something that deserves a bit of scrutiny, and perhaps explanation - before all this APNIC debacle, as an example, the above record was listed as "ALLOCATED PORTABLE", before becomming invisible. Now that the suballocations are visible again I thought I'd see what it shows now: inetnum: 202.36.137.0 - 202.36.137.255 netname: NZMFE descr: Ministry for the Environment descr: P.O. Box 10-362 descr: The Terrace descr: Wellington country: NZ admin-c: http://www.apnic.net/apnic-bin/whois.pl?searchtext=MB22-AP&form_type=advancedMB22-AP tech-c: http://www.apnic.net/apnic-bin/whois.pl?searchtext=MB22-AP&form_type=advancedMB22-AP notify: dbmon(a)apnic.net mnt-by: http://www.apnic.net/apnic-bin/whois.pl?searchtext=APNIC-HM&form_type=advancedAPNIC-HM status: ASSIGNED NON-PORTABLE changed: hostmaster(a)apnic.net 19931217 changed: hm-changed(a)apnic.net 20031020 changed: hm-changed(a)apnic.net 20040927 source: APNIC Surprise surprise, in the interim its now suddenly changed to "ASSIGNED NON-PORTABLE". Post revisionism in action anyone ? What implication does this have for people who are suddenly now listed as NON-PORTABLE when they were not previously ? Is anybody with a range like this actually making use of the portability, and are you now listed as non portable ? Sure enough, checking apnic for our own range shows that it too is now listed as non portable when it was definately listed as portable earlier this year... Comments ? Regards, Simon