- NZNOG - lists.nznog.org

NZRR Route Registry Update
by NZRR Database Notifications 02 Sep '08

02 Sep '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:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 202.53.176.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 202.160.116.0/22^22-29, 202.124.106.0/23^23-29, 202.160.114.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 198.32.71.0/24^24-29, 202.20.97.0/24^24-29, 202.36.33.0/24^24-29, 202.36.119.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.50.247.0/24^24-29, 202.55.105.0/24^24-29, 203.119.56.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: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080812 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 202.53.176.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 202.160.116.0/22^22-29, 202.124.106.0/23^23-29, 202.160.114.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 198.32.71.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.168.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.50.247.0/24^24-29, 202.55.105.0/24^24-29, 203.119.56.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: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080903 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 02 Sep '08

02 Sep '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: AS9560:RS-ROUTES:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 202.53.176.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 202.160.116.0/22^22-29, 202.124.106.0/23^23-29, 202.160.114.0/23^23-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 198.32.71.0/24^24-29, 202.20.97.0/24^24-29, 202.36.33.0/24^24-29, 202.36.119.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.50.247.0/24^24-29, 202.55.105.0/24^24-29, 203.119.56.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: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080812 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 166.65.0.0/16^16-29, 119.15.0.0/19^19-29, 202.14.32.0/19^19-29, 202.53.176.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 120.89.80.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.0/21^21-29, 202.49.0.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.37.48.0/22^22-29, 202.89.4.0/22^22-29, 202.160.116.0/22^22-29, 202.124.106.0/23^23-29, 202.160.114.0/23^23-29, 124.248.128.0/24^24-29, 124.248.132.0/24^24-29, 124.248.136.0/24^24-29, 124.248.140.0/24^24-29, 192.88.85.0/24^24-29, 192.122.171.0/24^24-29, 192.133.31.0/24^24-29, 192.195.219.0/24^24-29, 198.32.71.0/24^24-29, 202.20.97.0/24^24-29, 202.27.83.0/24^24-29, 202.36.33.0/24^24-29, 202.36.75.0/24^24-29, 202.36.119.0/24^24-29, 202.36.154.0/24^24-29, 202.36.162.0/24^24-29, 202.36.218.0/24^24-29, 202.37.168.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.50.247.0/24^24-29, 202.55.105.0/24^24-29, 203.119.56.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: peering(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080903 source: NZRR ------------------------------------------------------------

1 0

Air New Zealand / ECN
by Daniel Lawson 01 Sep '08

01 Sep '08

Hi, I'm seeing TCP ECN issues on the final hop to www.airnewzealand.co.nz. If there's someone from Air NZ on this list, you might want to look into it. I can provide traceroute / testing information if required. As an aside, I thought the "some routers break packets with ECN enabled" bug went away ages ago. Is anyone else seeing ECN related brokenness, or is it now SOP to disable ECN and leave it off? Daniel

3 3

DNS Cache Poisoning
by Andy Linton 01 Sep '08

01 Sep '08

At the APNIC meeting in Christchurch last week Sam Sargeant gave a nice talk on this. See http://www.apnic.net/meetings/26/program/apops/ for his slides. Leo Vegoda from ICANN pointed to this tool: http://recursive.iana.org/ which would be an interesting one for service providers to point out to their customers (unless of course they run the DNS for them and their servers are not right). A number of organisations in New Zealand have still not upgraded their software and many more are running servers that are recursive and authoritive at the same time. Time to get with the program!

1 0

The New Zealand Network Operators' Group
by Donald Neal 31 Aug '08

31 Aug '08

The New Zealand Network Operators' Group The New Zealand Network Operators' Group (NZNOG) has no king, president or formal membership. It consists of the subscribers to this mailing list. The group is intended to facilitate discussion among operators of networks in New Zealand on matters relevant to network operators as described in the list's Acceptable Use Policy. That policy appears later in this posting. Conference We hold New Zealand's only technical networking conference. Our next conference is to be hosted by FX Networks in Auckland on 28-30 January 2009. See http://www.nznog.org/?page_id=4 for details of conferences from 2004 to 2008. Other Meetings See http://thursdaynightcurry.com/ if you live in or near Auckland or Wellington (or Hamilton?) Operators' Contact List See http://www.nznog.org/?page_id=6 for operational contact details for most New Zealand ISP's. These are intended for use by other network operators, not by most customers. Internet Exchanges See http://www.nzix.net/ for details of exchanges in operation. About This Mailing List This list has between 900 and 1000 addresses subscribed. You may only post to the list from a subscribed address. A number of people subscribe addresses which do not receive email purely to allow posting from them. You may choose to receive postings as they come in, or just to receive daily "digests". See the bottom of the page http://list.waikato.ac.nz/mailman/listinfo/nznog/ to change the form in which you receive postings. The NZNOG mailing list is provided through a server at The University of Waikato, and is administered by employees of APN Online, Citylink, and The University of Waikato. None of these organisations, nor any administrator, is responsible for its content. NZNOG Mailing List Acceptable Use Policy The NZNOG mailing list exists to provide a forum for the exchange of technical information and the discussion of implementation issues that require cooperation among New Zealand network service providers. In order to continue to provide a useful forum for discussion of relevant technical issues, users of the list are asked to respect the following guidelines. 1. Discussion will focus on Internet operational and technical issues. 2. Discussion related to meetings of network service providers is appropriate. 3. Discussion unrelated to these topics is not appropriate. 4. Postings to multiple mailing lists are discouraged. 5. Postings that include foul language, character assassination, and lack of respect for other participants are unacceptable. 6. Blatant product or service marketing is unacceptable. 7. Postings of a political, philosophical or legal nature are discouraged. 8. Postings to the list should be in ASCII or MIME encoded as text/plain. Attachments should not be sent to the list. To present a document, a suitable URL may be referred to. For documents of general interest, the use of proprietary file formats is discouraged. 9. Breaches of list etiquette should be dealt with privately with the offending list user, and should not result in complaints being sent to the list. 10. A person repeatedly breaching list etiquette shall receive warnings from the list administrator. A further breach after the second such warning within thirty days shall result in the offender being unsubscribed from the list. Other action may also be taken to block postings to the list by the offender. Any such unsubscription is to be immediately announced to the list. Mailing List Archives A full archive is available at http://list.waikato.ac.nz/pipermail/nznog/ . Any message sent to the list will be archived and made available on the web automatically. Changes are not made to the archive on request, though the administrators remain happy to assist the Office of the Privacy Commissioner should any complaint be laid with that office. One way to search the archive is to use google and prefix your search with site:list.waikato.ac.nz . Subscribing to the List See http://list.waikato.ac.nz/mailman/listinfo/nznog to subscribe. Donald Neal NZNOG Mailing List Owner/Administrator/Muggins -- Donald Neal | "Careful design and strict discipline are Research Officer | necessary to prevent this sort of mess WAND | from escaping the development laboratory The University of Waikato | and infesting the production environment." | - D. Russell

1 0

NZRR Route Registry Update
by NZRR Database Notifications 31 Aug '08

31 Aug '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: AS9560:RS-ROUTES:AS38477 descr: Route set advertised to AS9560 by Unleash Connection 1 - AS38477 members: 116.90.128.0/21^21-29, 202.6.116.0/23^23-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: jasper(a)unleash.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080428 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS38477 descr: advertised to AS9560 by Unleash - AS38477 members: 116.90.128.0/21^21-29, 202.6.116.0/23^23-29, 192.88.99.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: jasper(a)unleash.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20080901 source: NZRR ------------------------------------------------------------

1 0

Xtra and port 110
by Don Stokes 31 Aug '08

31 Aug '08

We just had a customer on the phone unable to connect to our POP3 server from an Xtra DSL address; pop3s (995) and SMTP submission (587) worked fine, but no port 110 packets arrived at all. A quick squiz at the logs suggest that there has been rather less port 110 activity from Telecom DSL addresses than I would expect, but I don't have a lot of data. Is something going on? -- don

1 0

Intl transit providers
by Nathan Ward 30 Aug '08

30 Aug '08

This is not an RFP. Who transits packets over southern cross? - Asia Netcom - AS703 (I don't know what to call them, MCI/UUNet/Verizon/etc.) - Telecom NZ Global Gateway - Reach (?) - Sprint (?) Anyone else? Can someone confirm the last two? -- Nathan Ward

7 8

APNIC 26 Meeting Report
by Sunny 30 Aug '08

30 Aug '08

_______________________________________________________________________ APNIC 26 Meeting Report _______________________________________________________________________ 25-29 August 2008 Christchurch, New Zealand Thank you to everyone who attended or contributed to APNIC 26. APNIC 26 attendance statistics ------------------------------ Total number attending: 237 Economies represented: 33 APNIC member organisations represented: 70 APNIC 26 also staged two remote participation events where delegates in Hanoi and Manila could take part in the Policy SIG and APNIC Member Meeting via video conference. Number of Hanoi delegates: 25 Number of Manila delegates: 20 To read, watch or listen to archives from the meeting, go to: http://www.apnic.net/meetings/26/ Number Resource Organization (NRO) Number Council ------------------------------------------------- During the APNIC Member Meeting (AMM) in Christchurch on Friday, 29 August 2008, an election was held for a regional representative to the Number Resource Organization (NRO) Number Council (NC). Congratulations to the successful candidate Naresh Ajwani: Naresh Ajwani is President of Sify Technologies Limited, one of the pioneering leaders in the provision of eCommerce and Internet services in India. He is an Executive Council Member with ISPAI (Internet Service Providers Association of India) and brings over 25 years of core operational experience to this position. Election details are available at: http://www.apnic.net/meetings/26/election/ Meeting outcomes ---------------- Policy SIG Nine policy proposals were discussed in the Policy SIG. The following proposals reached consensus and were subsequently approved at the APNIC Member Meeting. These proposals are now subject to a 'last call' for comments: * prop-055: Global policy for the allocation of the remaining IPv4 address space * prop-061: Autonomous System Numbers (ASN) for documentation purposes * prop-062: Use of final /8 * prop-064: Change to assignment policy for AS numbers * prop-065: Format for delegation and recording of 4-byte AS numbers * prop-066: Ensuring efficient use of historical IPv4 resources The following proposal will be returned to the Policy SIG mailing list for further discussion: * prop-063: Reducing timeframe of IPv4 allocations from twelve to six months The following proposal will be returned to its author and mailing list for continued discussion: * prop-050: IPv4 resource transfers The following proposal will be revised by its author: * prop-060: Change in the criteria for the recognition of NIRs in the APNIC region APNIC Community Request for ICANN to Sign DNS Root The APNIC community considered ICANN's initiatives toward operational readiness for DNSSEC signing and informed ICANN that the Asia Pacific community supports efforts to sign the root of the DNS and called on ICANN to resolve these issues and to sign the root of the DNS as soon as is realistically possible. MoU (Memorandum of Understanding) APNIC signed two MoUs (Memorandum of Understanding). One with AusNOG, the other with NZNOG. These MoUs strengthened the relationship between the three organizations as they agreed to collectively work together, share information, and facilitate the development of the Internet in Australia and New Zealand. Meeting sponsors ---------------- APNIC offers its deepest thanks to the sponsors of APNIC 26, whose invaluable contributions allowed APNIC to offer a meeting program of a very high standard: http://www.apnic.net/meetings/26/sponsors/ Upcoming APNIC meetings ----------------------- APNIC 27 18-27 February 2009, Manila, Philippines APNIC 28 24-28 August 2009, Beijing, China APNIC 29 24 February - 5 March 2010, Kuala Lumpur, Malaysia Regards Sunny ____________________________________________________________________ Srinivas (Sunny) Chendi email: sunny(a)apnic.net External Relations Manager, APNIC sip: sunny(a)voip.apnic.net http://www.apnic.net ph/fx: +61 7 3858 3100/99

1 0

updated .nz graphs / stats
by Blair Harrison 29 Aug '08

29 Aug '08

Hi Folks, I've made a new set of graphs from the .nz statistics. xls and html versions are available at : http://jedi.school.nz/nzdg.html There seems to be an issue with viewing the html version in some versions of Firefox, so please try another browser or use the .xls if you can't open the html version. As usual, any feedback appreciated. Cheers, Blair

1 0