May 2008 - NZNOG - lists.nznog.org

List of NZ ISP MTA IP Addresses
by Barry Murphy 08 May '08

08 May '08

Hi, Does anyone have a list of most of the NZ ISP MTA's? I'd like to set a negative score on as many as possible to ensure legit email isn't classed as spam. Off-list replies appreciated, if there is a lot of requests for the same info, I shall collect aggregate and forward on. Thanks in advance. Barry Murphy

2 1

Dunedin city fibre
by Stu Fleming 07 May '08

07 May '08

Anyone got specifics on the new fibre network being rolled out by Delta Utilities in Dunedin? Timeframes? Topology? Costs?

2 1

Mott returns to Internet Industry
by Peter Mott 07 May '08

07 May '08

Good morning people, A quick heads up that we are back. A huge thank you to my contractors and the team at Citylink for helping kick off the new venture. We currently have kit in Kingston St and have connected to the APE (AS45181), but expect to roll out in other locations over the coming months. I've also managed to sign up to InternetNZ (clearly nobody remembered me) and we will be applying to join ISPANZ soon. We look forward to sharing our beer budget (fruit cocktails anybody?) with you at the next NZNOG conference. p.s This message is not intended to be a breach of policy 6 of the list AUP regards Peter Mott Swizzle | Wholesale Hosted Servers -/-

2 1

NZRR Route Registry Update
by NZRR Database Notifications 06 May '08

06 May '08

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:AS4770 descr: advertised to AS9439 by ICONZ - AS4770 members: 210.48.0.0/17^17-29, 210.185.0.0/18^18-29, 210.54.160.0/19^19-29, 202.55.96.0/20^20-29, 202.174.160.0/20^20-29, 210.56.32.0/20^20-29, 117.18.80.0/21^21-29, 202.12.248.0/21^21-29, 202.37.144.0/21^21-29, 202.37.224.0/21^21-29, 202.74.224.0/21^21-29, 202.78.240.0/21^21-29, 205.233.128.0/21^21-29, 202.36.36.0/22^22-29, 202.37.140.0/22^22-29, 202.37.200.0/22^22-29, 202.41.136.0/22^22-29, 203.80.60.0/22^22-29, 210.54.136.0/22^22-29, 210.55.24.0/22^22-29, 199.212.92.0/23^23-29, 202.21.136.0/23^23-29, 202.36.44.0/23^23-29, 202.36.76.0/23^23-29, 202.37.240.0/23^23-29, 202.37.252.0/23^23-29, 202.61.2.0/23^23-29, 202.174.6.0/23^23-29, 205.233.136.0/23^23-29, 192.88.85.0/24^24-29, 192.107.113.0/24^24-29, 198.32.66.0/24^24-29, 202.6.84.0/24^24-29, 202.12.70.0/24^24-29, 202.14.100.0/24^24-29, 202.20.6.0/24^24-29, 202.21.130.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.0/24^24-29, 202.37.57.0/24^24-29, 202.37.73.0/24^24-29, 202.37.76.0/24^24-29, 202.37.85.0/24^24-29, 202.37.163.0/24^24-29, 202.37.232.0/24^24-29, 202.46.190.0/24^24-29, 202.49.62.0/24^24-29, 202.49.89.0/24^24-29, 202.49.159.0/24^24-29, 202.49.249.0/24^24-29, 202.50.87.0/24^24-29, 202.50.139.0/24^24-29, 205.233.243.0/24^24-29, 210.54.140.0/24^24-29, 210.54.211.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: deon(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080318 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS4770 descr: advertised to AS9439 by ICONZ - AS4770 members: 210.48.0.0/17^17-29, 210.185.0.0/18^18-29, 210.54.160.0/19^19-29, 202.55.96.0/20^20-29, 202.174.160.0/20^20-29, 210.56.32.0/20^20-29, 117.18.80.0/21^21-29, 120.138.16.0/21^21-29, 202.12.248.0/21^21-29, 202.37.144.0/21^21-29, 202.37.224.0/21^21-29, 202.74.224.0/21^21-29, 202.78.240.0/21^21-29, 205.233.128.0/21^21-29, 202.36.36.0/22^22-29, 202.37.140.0/22^22-29, 202.37.200.0/22^22-29, 202.41.136.0/22^22-29, 203.80.60.0/22^22-29, 210.54.136.0/22^22-29, 210.55.24.0/22^22-29, 199.212.92.0/23^23-29, 202.21.136.0/23^23-29, 202.36.44.0/23^23-29, 202.36.76.0/23^23-29, 202.37.240.0/23^23-29, 202.37.252.0/23^23-29, 202.61.2.0/23^23-29, 202.174.6.0/23^23-29, 205.233.136.0/23^23-29, 192.88.85.0/24^24-29, 192.107.113.0/24^24-29, 198.32.66.0/24^24-29, 202.6.84.0/24^24-29, 202.12.70.0/24^24-29, 202.14.100.0/24^24-29, 202.20.6.0/24^24-29, 202.21.130.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.0/24^24-29, 202.37.57.0/24^24-29, 202.37.73.0/24^24-29, 202.37.76.0/24^24-29, 202.37.85.0/24^24-29, 202.37.163.0/24^24-29, 202.46.190.0/24^24-29, 202.49.62.0/24^24-29, 202.49.89.0/24^24-29, 202.49.159.0/24^24-29, 202.49.249.0/24^24-29, 202.50.87.0/24^24-29, 202.50.139.0/24^24-29, 205.233.243.0/24^24-29, 210.54.140.0/24^24-29, 210.54.211.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: deon(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080507 source: NZRR ------------------------------------------------------------

1 0

Tui update - please accept my routes and give me free transit. No really. Please?
by Nathan Ward 04 May '08

04 May '08

Hello all, A few weeks back we were loaned 2 x /24s[1] and 2 x ASNs by APNIC R&D, big thanks to Geoff Huston. One ASN and /24 lives on the Tui route- server at APE, and the others on the Tui route-server at WIX. They are: - APE: AS24021 203.147.108.0/24 - WIX: AS45163 203.147.109.0/24 These /24s are used for the unit's 6to4 address, which is used for 2 things: - BGP peer address for remote Tui boxes. - Next hop for v6 routes from native exchange peers. These routes are only given to remote Tui boxes that are on networks that are visible from APE/WIX. The first Tui route-server has been installed by Andy on WIX today, we're looking to get the APE one in next week. If you are on WIX, can you please accept 203.147.109.0/24 from the WIX v4 route-servers. If you prefer private peering on the exchange we can do that too, drop me an email - nward(a)braintrust.co.nz. Same for the APE /24 next week. Now, that gets these two /24s visible to networks that are visible at APE/WIX, however that doesn't get us to networks that aren't. If you can see these two /24s, please transit them - ie. advertise them to your peers and transit providers. That let's networks that don't peer (for whatever reason) still use Tui boxes in their networks. If you transit these /24s, the only data you'll see going across your network to/from these networks is BGP traffic in 6to4. You won't see any actual data, just BGP control messages. The routing policy only gives next hops in these /24s if the remote Tui box is in a network visible to the exchange (in which case you won't transit packets for that network) - if it's not, it only gets information about other Tui boxes, and that data goes direct between Tui boxes. I've been trying to figure out how to explain this clearly in words.. hopefully that makes sense. I'll follow up with a picture if needed. In short - please accept and re-advertise those two /24s to your peers, customers, and internationally to help out this Tui project, they are very low traffic and only carry control data, I promise. We're talking kilobits per second here, so it's really nothing. Also, if you do transit them, please tell me so I can tell people all about how awesome you are, and buy you beer when I next see you. Big thanks go to InternetNZ for hardware and support, APNIC for v4 and ASNs, and Citylink for exchange connectivity, hardware, etc. -- Nathan Ward Braintrust Ltd. nward(a)braintrust.co.nz +64-21-431675 [1] - No, the irony of burning 2 /24s to help encourage v6 adoption is not lost on me :-)

3 4

domain name nznog.org.nz
by Craig Whitmore 02 May '08

02 May '08

Hi there folks.. I've had "control" of the domain name nznog.org.nz for a quite a while ago after I retrieved it from the person who falsely registered it in 2003 (I'm not naming names but most of you know who it was). The question is.. at the moment it is not actually doing anything so does someone want it so they can use it with nznog as I'm thinking of just cancelling it at the moment. Thanks Craig

3 2

Request for Feedback: Industry Best Practice Programme
by Keith Davidson 01 May '08

01 May '08

Hello all, InternetNZ seeks input from NZNOG on a proposed Industry Best Practice Programme that would develop and document a range of local Internet operational and technical best practice standards. A brief overview of the Industry Best Practice Programme was given to NZNOG conference attendees in January, and we are looking for further feedback on the proposal via the NOG mailing list. InternetNZ Industry Best Practice Programme The proposed 'InternetNZ Industry Best Practice Programme' aims to create a community of technical practice in New Zealand by encouraging collaboration between network and service operators in defining best practice standards. Technical best practice documents would be developed by small working groups. These would form flexible codes of practice relating to the New Zealand Internet, allowing ISP's, content providers and other Internet service companies to select an overall best fit for their business. For instance, a DoS Response/Containment document would likely define and outline what steps would be taken in New Zealand should a large scale denial of service attack occur here. Other examples of best practice documents could include: - Routing Registry Practices - Use of BGP communities - Mail Server Operations - Peering Practices - Phishing Response/Containment - Emergency Response (Security) - Natural Disaster Response - Datacentre Standards and Classification Participants are more than welcome to suggest other best practice document topics. Development Process InternetNZ is looking to finalise a few areas of the proposed development process listed below: Best practice documents specifying New Zealand ICT industry-accepted technical practices and processes would be drafted by working groups comprising two to four technical/industry experts. Note: Working group members can be drawn from a range of NZ-based online communities and industry organisations such as NZNOG, e-Government, the TCF and ISPANZ. Draft documents, and subsequent iterations, would be floated on the NZNOG mailing list for open debate and discussion, to achieve broad consensus and approval. Following consensus, finalised drafts would be published by InternetNZ as a best practice document and filed on a public website. InternetNZ would promote and publish the finalised best practice documents, and provide administrative and secretarial support. Development Incentives To encourage development of best practice documents InternetNZ would provide a yearly travel grant, awarded to members of the top four successful working groups that have had documents published. Travel would be earmarked for international travel to technical conferences, with the published best practice document being presented and/or compared with similar best practices from other countries. The InternetNZ Technical Policy Committee will select which documents are subject to a development incentive. Your feedback on this proposal is most welcome. We are particularly interested in your views on how broad consensus would be achieved via the NZNOG list, and suggested approaches for defining the top four best practice working groups. Feel free to contact me off list also. Regards, Keith Davidson Executive Director - InternetNZ

1 0