- NZNOG - lists.nznog.org

World IPv6 Day
by Pieter De Wit 06 Jun '12

06 Jun '12

Hi All, Not sure how many has seen this: http://www.worldipv6launch.org/participants/?q=2 Not a single NZ company ? Surely not... Cheers, Pieter

5 4

Fwd: DNCL Second Level Consultation and Submissions
by Andy Linton 05 Jun '12

05 Jun '12

Your views on this would be appreciated. -------- Original Message -------- Subject: DNCL Second Level Consultation and Submissions From: newsmail(a)dnc.org.nz To: asjl(a)lpnz.org CC: DNCL Second Level Consultation and Submissions The Domain Name Commission is proposing to extend the .nz domain name space by allowing anybody to register domain names at the ‘second level’. This has the potential to significantly alter New Zealand’s domain name space so it’s important we get your views. Key features of the .nz proposals include: Registration of .nz domain names could be at the second or third levels on an ongoing basis. Existing second level domains (such as .co.nz) will remain and continue to be supported. There will be no impact on any currently registered .nz domain names. Registrations at the second level will be on a “first come, first served” basis, except during the Sunrise Period and where there are currently multiple registrations of the same name in different second level domains. The Sunrise Period will be a designated window, where existing .nz domain name holders (registrants) can register their domain name/s at the second level if they are the only one that has that name at the third level. If two or more domain name holders have the same name at the third level, no-one will be able to register that name at the second level unless they obtain the consent of the other third level name holders. Alternatively, if all agree, it could become a second level domain instead. A temporary amendment to the Dispute Resolution Service Policy to cover sub-domains of generic domain names registered at the second level. The above list is a very brief overview of the proposals. The Consultation Paper at http://dnc.org.nz/content/Second_Level_Consultation_Paper.pdf and http://dnc.org.nz/content/Second_Level_Consultation_Paper.html provides more detail about what is proposed. It also includes marked up versions of the main policies affected so that people can get an indication of how it may be implemented. Each section of the Consultation Paper raises specific questions. Please respond to these questions or, more generally, to any of the issues raised through the online response from at https://www.research.net/s/dnc_consultation1. Submissions can also be made by email to policies(a)dnc.org.nz, by fax to (04) 495 2115, or by mail to P O Box 11881, Wellington. The closing date for submissions is midday on Thursday 27 September 2012. As submissions are received they will be published on this page. Related documents: Consultation notice and published submissions http://dnc.org.nz/second_level_proposal_c1 Consultation paper, with appendices http://dnc.org.nz/content/Second_Level_Consultation_Paper.pdf http://dnc.org.nz/content/Second_Level_Consultation_Paper.html Online submission form https://www.research.net/s/dnc_consultation1 FAQs http://dnc.org.nz/content/second_level_proposal_faq.pdf http://dnc.org.nz/content/second_level_proposal_faq.html Originally published 9am, Wednesday 30 May 2012 You have received this communication because you have subscribed to the DNC website at http://www.dnc.org.nz/ If you no longer wish to receive these emails, please send an email with 'Unsubscribe' in the subject line to unsubscribe(a)dnc.org.nz Or log into your account and turn off mail subscriptions

24 41

UFB services - CIR in contention
by Curtis Owings 04 Jun '12

04 Jun '12

RE: How CIR behaviour in contention works for bit stream 2 and 3 Bit streams 2 and 3 define a CIR component which is incremented in 2.5 meg chunks. The default value is 2.5 meg CIR. In order to use this high priority queue the RSP must tag their layer 2 frames with P-bit 4. All other p-bits are remarked to 0--as per the TCF requirement. If a services exceeds the allocated CIR, those frames delivered outside of the policy will be discarded. That is anything over the CIR is dumped. From a end-user perspective, if all traffic was tagged high priority, then any excess over 2.5 would be randomly dropped and the customer would never experience the advertised 10m up / 30m down (low priority). Bit stream 3a is being designed to allow some excess to be used where frames out of policy will be tagged discard eligible, but not immediately discarded. Remember that Chorus has created labs in Auckland and Wellington which are open to Retail Service Providers so that services parameters appropriate to the applications that RSPs want to sell can be developed. The feedback from these labs needs to get to the TCF and CFH so any new products can be ratified by the industry. Curtis Owings Principal Solution Architect T +64 4 498 9355 (extn 49355) M +64 27 655 5335 E Curtis.Owings(a)chorus.co.nz Level 3, Deloitte House, 10 Brandon Street P O Box 632, Wellington www.chorus.co.nz P Please consider the environment before printing this e-mail ________________________________ This communication, including any attachments, is confidential. If you are not the intended recipient, you should not read it - please contact me immediately, destroy it, and do not copy or use any part of this communication or disclose anything about it. Thank you. Please note that this communication does not designate an information system for the purposes of the Electronic Transactions Act 2002.

3 2

NZRR Route Registry Update
by NZRR Database Notifications 04 Jun '12

04 Jun '12

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS2687 descr: advertised to AS9439 by at&t - AS2687 members: 103.5.80.0/22^22-29, 202.36.192.0/22^22-29, 32.114.24.0/23^23-29, 122.248.172.0/23^23-29, 202.14.252.0/23^23-29, 202.36.68.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 32.234.81.0/24^24-29, 202.12.105.0/24^24-29, 202.14.254.0/24^24-29, 202.27.160.0/24^24-29, 202.36.80.0/24^24-29, 202.37.254.0/24^24-29, 202.135.38.0/24^24-29, 202.135.49.0/24^24-29, 202.135.64.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 203.163.68.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: dl-globalwork(a)att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20120531 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS2687 descr: advertised to AS9439 by AT&T - AS2687 members: 103.5.80.0/22^22-29, 202.36.192.0/22^22-29, 32.114.24.0/23^23-29, 122.248.172.0/23^23-29, 202.14.252.0/23^23-29, 202.36.68.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 32.234.81.0/24^24-29, 202.12.105.0/24^24-29, 202.14.254.0/24^24-29, 202.36.80.0/24^24-29, 202.37.254.0/24^24-29, 202.135.38.0/24^24-29, 202.135.49.0/24^24-29, 202.135.64.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 203.163.68.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: tim(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20120605 source: NZRR ------------------------------------------------------------

1 0

What just happened to APE ?
by Ian Batterbee 02 Jun '12

02 Jun '12

Anyone know if that was a power cut or was it scheduled work ?

2 2

Enabling DNSSEC for the .nz Second Level Domains
by Sebastian Castro 31 May '12

31 May '12

Dear Technical Community, The next step towards completing the DNSSEC deployment for .nz is to sign the second level domains, thus allowing registrants to enable DNSSEC for their domains. We have prepared a staggered deployment schedule for the unmoderated second level domains, which is available in full at http://nzrs.net.nz/dns/dnssec As a summary, geek.nz will be the first DNSSEC signed second level domain, closely followed by ac.nz, gen.nz, maori.nz and school.nz, all during June. In July, net.nz and org.nz will be signed, ending with co.nz during early August. As a reminder, the SRS has been able to receive DS records for domains under .nz since last year, and those records will be included in their respective zone when DNSSEC is fully enable for the second level domain. We advise against using any of the Second Level Domains DS records as a trust anchors. If you have any questions around this process, don't hesitate to contact us at support(a)nzrs.net.nz Kind Regards, -- Sebastian Castro DNS Specialist .nz Registry Services (New Zealand Domain Name Registry Limited) desk: +64 4 495 2337 mobile: +64 21 400535

10 18

APNIC proposal to remove multihoming requirement for IPv6 portable assignments - prop-101
by Dean Pemberton 31 May '12

31 May '12

Evening; Q: What now? A: At the APNIC meeing in New Delhi a proposal to remove the multihoming requirement for IPv6 portable assignments did not reach consensus. It's likely to come back again at the meeting in August and I'd like to explain a bit about it and get some feedback from the NZ community. Q: Ok what's this one all about? A; Right... Current APNIC policy only permits portable assignments of IPv6 addresses to be made if a member is currently multihomed or plans to be multihomed within three months. That can mean that people feel they can't apply for IPv6 space, or that they have to wait until they are multihomed in order to apply to APNIC for address space. Prop-101 looks to remove the requirement for multihoming and would let non-multihomed APNIC members apply for a portable IPv6 assignment. The full text is here: http://www.apnic.net/policy/proposals/prop-101/prop-101-v004.txt Q: What is a portable assignment and why would I want one anyway? A: A portable assignment of IPv6 addresses is independent of any particular ISP or network provider. It means that you can take those addresses and have them routed by anyone. Non-portable assignments are addresses which you might get from your ISP. Those addresses are taken from the ISPs block of IPv6 addresses and can only be used while you are their customer. If you were using non-portable addresses and wanted to move ISPs then you would have to renumber your network. Q: That sounds terrible! Why would anyone want anything else? A: Well for a lot of organisations they don't need anything else. Think about IPv4, most people operate with addresses given to them by their ISP just fine. Portable addresses are also only allocated by RIR organisations like APNIC. They don't come free, there is a yearly cost to be an APNIC member, and keep those addresses. Q: Are there any downsides? A: Objectors to this proposal suggest that if everyone was granted portable address space that the routing table would grow unnecessarily. Q: What does everyone else in the world do? A: APNIC is the only one for the 5 global registries which requires multihoming for portable IPv6 assignments. Q: So what do you want from me? A: If you have an opinion then let me know. If you think it's relevant to others then post it to the list. Don't hesitate to join the APNIC policy SIG list and have your say directly. Regards, Dean

2 1

New APNIC policy to increase transparency in IPv6 allocations
by Dean Pemberton 30 May '12

30 May '12

Evening all, Q: Why are you interrupting my evening? A; I just wanted to let everyone know about a new APNIC policy which has just passed through the Policy Development Process Q: Huh? A: The APNIC Executive council has just ratified a new policy called prop-102 which will increase transparency in IPv6 allocations. Q: Well what does it say then? A: Well prop-102 is a hellish boring name a new APNIC proposal which says that details of any sparse allocation algorithm used for the allocation by APNIC of IPv6 resources be published on their the website, and any revisions should be communicated back to the community. You can read the full text here: http://www.apnic.net/policy/proposals/prop-102/prop-102-v003.txt Q: Why do I care? A: When people are allocated IP addresses, they are sometimes under the impression that if they request more at a later date that they will get allocated a completly different area of the address space. That's not true. For some time now APNIC has been employing a system called 'Sparse Allocation' to try and make sure that when you came back, you stood a good chance of getting the IP address block just next-door. The problem up until now has been no one knew the details of this system. How soon did you have to come back? How large was the block they were reserving for you? If you wanted too long did they allocate it to someone else? All those details were hidden. Now they will be published. Q: What are you telling me this? A: I'm doing my bit to keep the community across what is happening at APNIC in a way that hopefully people can find accessible. I'll summarise some of the other policies shortly Q: What if I have more questions? A: Feel free to email me and I'll try and answer any APNIC policy related questions. Or feel free to participate in APNIC discussion directly via their Policy SIG (http://www.apnic.net/community/participate/join-discussions/sigs/policy-sig) Regards, Dean

1 0

NZRR Route Registry Update
by NZRR Database Notifications 30 May '12

30 May '12

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS23655 descr: advertised to AS9439 by Snap Internet - AS23655 members: 118.148.0.0/15^15-29, 111.69.0.0/16^16-29, 130.123.0.0/16^16-29, 130.195.0.0/16^16-29, 132.181.0.0/16^16-29, 138.75.0.0/16^16-29, 140.200.0.0/16^16-29, 150.206.0.0/16^16-29, 153.111.0.0/16^16-29, 159.117.0.0/16^16-29, 163.7.0.0/16^16-29, 165.84.0.0/16^16-29, 123.255.0.0/18^18-29, 14.1.32.0/19^19-29, 49.50.192.0/19^19-29, 180.189.192.0/19^19-29, 202.124.96.0/19^19-29, 202.154.128.0/19^19-29, 111.65.224.0/20^20-29, 182.54.160.0/20^20-29, 202.49.16.0/20^20-29, 202.56.32.0/20^20-29, 203.86.192.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 210.7.32.0/20^20-29, 27.110.120.0/21^21-29, 49.50.224.0/21^21-29, 120.136.0.0/21^21-29, 202.49.64.0/21^21-29, 202.49.152.0/21^21-29, 202.56.48.0/21^21-29, 202.137.240.0/21^21-29, 202.174.112.0/21^21-29, 210.5.48.0/21^21-29, 103.4.136.0/22^22-29, 103.4.152.0/22^22-29, 103.247.152.0/22^22-29, 110.92.16.0/22^22-29, 113.197.96.0/22^22-29, 202.49.72.0/22^22-29, 202.49.92.0/22^22-29, 202.50.104.0/22^22-29, 202.50.124.0/22^22-29, 202.164.28.0/22^22-29, 203.99.132.0/22^22-29, 103.22.234.0/23^23-29, 202.27.186.0/23^23-29, 202.36.178.0/23^23-29, 202.36.204.0/23^23-29, 202.36.220.0/23^23-29, 202.37.96.0/23^23-29, 202.37.100.0/23^23-29, 202.37.106.0/23^23-29, 202.49.80.0/23^23-29, 202.49.120.0/23^23-29, 210.55.30.0/23^23-29, 210.55.206.0/23^23-29, 103.10.233.0/24^24-29, 143.96.13.0/24^24-29, 192.100.53.0/24^24-29, 192.148.221.0/24^24-29, 192.156.225.0/24^24-29, 202.14.217.0/24^24-29, 202.36.29.0/24^24-29, 202.36.141.0/24^24-29, 202.36.163.0/24^24-29, 202.36.170.0/24^24-29, 202.36.174.0/24^24-29, 202.36.245.0/24^24-29, 202.37.114.0/24^24-29, 202.37.127.0/24^24-29, 202.37.179.0/24^24-29, 202.37.194.0/24^24-29, 202.37.220.0/24^24-29, 202.46.187.0/24^24-29, 202.49.59.0/24^24-29, 202.49.115.0/24^24-29, 202.49.125.0/24^24-29, 202.49.140.0/24^24-29, 202.49.187.0/24^24-29, 202.50.110.0/24^24-29, 202.50.117.0/24^24-29, 202.50.169.0/24^24-29, 202.50.176.0/24^24-29, 202.74.38.0/24^24-29, 203.6.246.0/24^24-29, 203.92.25.0/24^24-29, 203.96.112.0/24^24-29, 203.174.26.0/24^24-29, 203.191.7.0/24^24-29, 205.233.128.0/24^24-29, 210.55.4.0/24^24-29, 210.55.7.0/24^24-29, 210.55.110.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: tim(a)snap.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20120329 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS23655 descr: advertised to AS9439 by Snap Internet - AS23655 members: 118.148.0.0/15^15-29, 111.69.0.0/16^16-29, 130.123.0.0/16^16-29, 130.195.0.0/16^16-29, 132.181.0.0/16^16-29, 138.75.0.0/16^16-29, 140.200.0.0/16^16-29, 150.206.0.0/16^16-29, 153.111.0.0/16^16-29, 159.117.0.0/16^16-29, 163.7.0.0/16^16-29, 165.84.0.0/16^16-29, 123.255.0.0/18^18-29, 14.1.32.0/19^19-29, 49.50.192.0/19^19-29, 180.189.192.0/19^19-29, 202.124.96.0/19^19-29, 202.154.128.0/19^19-29, 111.65.224.0/20^20-29, 182.54.160.0/20^20-29, 202.49.16.0/20^20-29, 202.56.32.0/20^20-29, 203.86.192.0/20^20-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 210.7.32.0/20^20-29, 27.110.120.0/21^21-29, 49.50.224.0/21^21-29, 120.136.0.0/21^21-29, 202.49.64.0/21^21-29, 202.49.152.0/21^21-29, 202.50.144.0/21^21-29, 202.56.48.0/21^21-29, 202.137.240.0/21^21-29, 202.174.112.0/21^21-29, 210.5.48.0/21^21-29, 103.4.136.0/22^22-29, 103.4.152.0/22^22-29, 103.247.152.0/22^22-29, 110.92.16.0/22^22-29, 113.197.96.0/22^22-29, 202.49.72.0/22^22-29, 202.49.92.0/22^22-29, 202.50.104.0/22^22-29, 202.50.124.0/22^22-29, 202.164.28.0/22^22-29, 203.99.132.0/22^22-29, 103.22.234.0/23^23-29, 202.27.186.0/23^23-29, 202.36.178.0/23^23-29, 202.36.204.0/23^23-29, 202.36.220.0/23^23-29, 202.37.96.0/23^23-29, 202.37.100.0/23^23-29, 202.37.106.0/23^23-29, 202.49.80.0/23^23-29, 202.49.120.0/23^23-29, 210.55.30.0/23^23-29, 210.55.206.0/23^23-29, 103.10.233.0/24^24-29, 143.96.13.0/24^24-29, 159.172.204.0/24^24-29, 192.100.53.0/24^24-29, 192.148.221.0/24^24-29, 192.156.225.0/24^24-29, 202.14.217.0/24^24-29, 202.36.29.0/24^24-29, 202.36.141.0/24^24-29, 202.36.163.0/24^24-29, 202.36.170.0/24^24-29, 202.36.174.0/24^24-29, 202.36.245.0/24^24-29, 202.37.114.0/24^24-29, 202.37.127.0/24^24-29, 202.37.179.0/24^24-29, 202.37.194.0/24^24-29, 202.37.220.0/24^24-29, 202.46.187.0/24^24-29, 202.49.59.0/24^24-29, 202.49.115.0/24^24-29, 202.49.125.0/24^24-29, 202.49.140.0/24^24-29, 202.49.187.0/24^24-29, 202.50.110.0/24^24-29, 202.50.117.0/24^24-29, 202.50.169.0/24^24-29, 202.50.176.0/24^24-29, 202.74.38.0/24^24-29, 203.6.246.0/24^24-29, 203.92.25.0/24^24-29, 203.96.112.0/24^24-29, 203.174.26.0/24^24-29, 203.191.7.0/24^24-29, 205.233.128.0/24^24-29, 210.55.4.0/24^24-29, 210.55.7.0/24^24-29, 210.55.110.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: perrin(a)snap.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20120531 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 30 May '12

30 May '12

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS2687 descr: advertised to AS9439 by AT&T - AS2687 members: 103.5.80.0/22^22-29, 202.36.192.0/22^22-29, 32.114.24.0/23^23-29, 122.248.172.0/23^23-29, 202.14.252.0/23^23-29, 202.36.68.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 32.234.81.0/24^24-29, 202.12.105.0/24^24-29, 202.14.254.0/24^24-29, 202.36.29.0/24^24-29, 202.36.80.0/24^24-29, 202.37.254.0/24^24-29, 202.135.38.0/24^24-29, 202.135.49.0/24^24-29, 202.135.64.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 203.163.68.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: dl-globalwork(a)att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20120314 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS2687 descr: advertised to AS9439 by at&t - AS2687 members: 103.5.80.0/22^22-29, 202.36.192.0/22^22-29, 32.114.24.0/23^23-29, 122.248.172.0/23^23-29, 202.14.252.0/23^23-29, 202.36.68.0/23^23-29, 203.99.128.0/23^23-29, 203.163.70.0/23^23-29, 203.176.122.0/23^23-29, 32.234.81.0/24^24-29, 202.12.105.0/24^24-29, 202.14.254.0/24^24-29, 202.27.160.0/24^24-29, 202.36.80.0/24^24-29, 202.37.254.0/24^24-29, 202.135.38.0/24^24-29, 202.135.49.0/24^24-29, 202.135.64.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 203.163.68.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: dl-globalwork(a)att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20120531 source: NZRR ------------------------------------------------------------

1 0