November 2007 - NZNOG - lists.nznog.org

NZRR Route Registry Update
by NZRR Database Notifications 12 Nov '07

12 Nov '07

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:AS9889 descr: advertised to AS9560 by Maximum Internet Ltd - AS9889 members: 123.100.64.0/18^18-29, 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 202.55.96.0/20^20-29, 202.189.160.0/21^21-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 117.53.150.0/24^24-29, 192.138.251.0/24^24-29, 202.6.5.0/24^24-29, 202.27.8.0/24^24-29, 202.27.204.0/24^24-29, 202.36.70.0/24^24-29, 202.36.227.0/24^24-29, 202.37.72.0/24^24-29, 202.37.162.0/24^24-29, 202.37.181.0/24^24-29, 202.49.141.0/24^24-29, 202.150.102.0/24^24-29, 203.12.15.0/24^24-29, 203.97.42.0/24^24-29, 210.54.13.0/24^24-29, 210.54.142.0/24^24-29, 210.55.169.0/24^24-29, 210.55.214.0/24^24-29, 210.55.230.0/24^24-29, 203.167.219.56/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20071004 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9889 descr: advertised to AS9560 by Maximum Internet Ltd - AS9889 members: 123.100.64.0/18^18-29, 124.198.128.0/18^18-29, 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 202.55.96.0/20^20-29, 202.189.160.0/21^21-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 117.53.150.0/24^24-29, 192.138.251.0/24^24-29, 202.6.5.0/24^24-29, 202.27.8.0/24^24-29, 202.27.204.0/24^24-29, 202.36.70.0/24^24-29, 202.36.227.0/24^24-29, 202.37.72.0/24^24-29, 202.37.162.0/24^24-29, 202.37.181.0/24^24-29, 202.49.141.0/24^24-29, 202.150.102.0/24^24-29, 203.12.15.0/24^24-29, 203.97.42.0/24^24-29, 210.54.13.0/24^24-29, 210.54.142.0/24^24-29, 210.55.169.0/24^24-29, 210.55.214.0/24^24-29, 210.55.230.0/24^24-29, 203.167.219.56/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20071113 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 07 Nov '07

07 Nov '07

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, 202.53.176.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 116.90.128.0/21^21-29, 123.108.144.0/21^21-29, 202.46.176.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.59.4.0/22^22-29, 202.6.116.0/23^23-29, 202.124.106.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, 202.20.97.0/24^24-29, 202.36.119.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 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20071024 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, 202.53.176.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 116.90.128.0/21^21-29, 123.108.144.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.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.59.4.0/22^22-29, 202.89.4.0/22^22-29, 202.6.116.0/23^23-29, 202.124.106.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, 202.20.97.0/24^24-29, 202.36.33.0/24^24-29, 202.36.119.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 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20071108 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 07 Nov '07

07 Nov '07

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, 202.53.176.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 116.90.128.0/21^21-29, 123.108.144.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.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.59.4.0/22^22-29, 202.6.116.0/23^23-29, 202.124.106.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, 202.20.97.0/24^24-29, 202.36.119.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 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20071024 source: NZRR REPLACED BY: 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, 202.53.176.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 116.90.128.0/21^21-29, 123.108.144.0/21^21-29, 192.173.16.0/21^21-29, 202.46.176.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.59.4.0/22^22-29, 202.89.4.0/22^22-29, 202.6.116.0/23^23-29, 202.124.106.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, 202.20.97.0/24^24-29, 202.36.33.0/24^24-29, 202.36.119.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 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20071108 source: NZRR ------------------------------------------------------------

1 0

InternetNZ launches public consultation on Internet peering
by Dean Pemberton 07 Nov '07

07 Nov '07

Hi all. InternetNZ is asking for public consultation on Internet Peering. There are a number of interesting things in this email, my apologies for its length. The first is the InternetNZ Peering Report which can be downloaded at http://peering.internetnz.net.nz/wp-content/uploads/2007/11/issues-regardin… And the second are the 8 questions which InternetNZ is asking for submissions on. People are welcome to send in their own submissions, and if the discussion is within the AUP then feel free to voice them here too. I look forward to the discussion. =) I've included the original RTF document as text below inline with the list rules. Dean -------- Original Message -------- InternetNZ launches public consultation on Internet peering For immediate release 7 November 2007 InternetNZ (the Internet Society of New Zealand Inc) today launches a public consultation on Internet peering, a subject that relates to the performance and reliability of the Internet. This follows the release of a report commissioned by the Society entitled “Issues regarding Internet peering and interconnection in New Zealand”. Some key issues identified in the report include conflicting interpretations of the term peering, cost of transit, lack of reliable internet traffic data and statistics and the challenges faced by content providers InternetNZ invites comments on any issues presented in the report and what further steps should be considered in progressing peering and data interconnection issues in New Zealand. A consultation document is attached and submissions have been invited either by email in response to that document, or at the website http://peering.internetnz.net.nz, where comments can be attached to the individual questions. The mission of InternetNZ is to protect and promote the Internet in New Zealand. InternetNZ is a public policy advocate for Internet and telecommunications issues that further an open and uncaptureable Internet. InternetNZ promotes neutral peering and neutral peering exchanges on the basis that it provides diversity for the Internet network and assists in improving network performance. For further information contact: Richard Wood Communications and Research Officer InternetNZ richard(a)internetnz.net.nz 0274 974 837 ----------Attachment------- InternetNZ Invites Comment on Peering Consultation Document - 7 November 2007 ------------------------------------------------- InternetNZ (the Internet Society of New Zealand Inc) has commissioned a report "Issues regarding Internet peering and interconnection in New Zealand", which examines the state of peering and related issues in New Zealand. The report can be found here: http://peering.internetnz.net.nz/wp-content/uploads/2007/11/issues- regarding-internet-peering-and-interconnection-in-new-zealand-099.pdf InternetNZ invites comments on any issues presented in the report and what further steps should be considered in progressing peering and data interconnection issues in New Zealand. Submissions must be received by 5pm, Friday 7 December. InternetNZ is also inviting comments and discussion online at the website http://peering.internetnz.net.nz Background --------------- The mission of InternetNZ is to protect and promote the Internet in New Zealand. InternetNZ is a public policy advocate for Internet and telecommunications issues that further an open and uncaptureable Internet. InternetNZ promotes neutral peering and neutral peering exchanges on the basis that it provides diversity for the Internet network and assists in improving network performance. In March 2008 InternetNZ commissioned an external working group chaired by Dr Murray Milner to undertake a wide ranging industry consultation on peering and related issues. The terms of reference were as follows; • To facilitate industry discussion on issues relating to Internet peering in New Zealand inclusive of all interested and affected stakeholders and in a collaborative fashion. • To establish policies and principles that will expedite an industry-wide agreement on peering and local interconnection of data. The findings and recommendations contained in "Issues regarding Internet peering and interconnection in New Zealand" do not represent InternetNZ policy but are designed to provide a framework for a wider industry debate on peering and data connection issues. Following the public consultation process, InternetNZ will publish a final report that will incorporate feedback from public submissions To assist the feedback process, outlined below are a list of specific questions based on the findings and recommendations raised in the report Questions ------------ 1. Peering: Interpretation and Definition The term peering is open to many interpretations. The report identifies the differences in what is meant by the word "peering" and says that emotive responses flowing from historical events can be overcome by defining as far as possible what peering means. Do you agree with definition of peering that is proposed in the report. If not, what would be more appropriate? 2. Cost of Transit International benchmarking suggests the cost of transit is relatively high in New Zealand. Do you agree? Specifically, is there a market failure or evidence of SMP (significant market power) with regard to the cost of transit? Should government conduct an investigation regarding the price of transit? And finally should Government regulate the price of transit? 3. The state of networking - lack of reliable data The report highlights the difficulty in having any informed debate about the state of networking in relation to local, national and international data interconnection in New Zealand, without access to reliable Internet traffic data and statistics. Do you support the need for an initiative that would collect and make available on an aggregated basis, New Zealand Internet traffic flows and volumes? If so who should collect that data? Specifically; the Telecommunication Carrier's Forum, Commerce Commission, Ministry of Economic Development, InternetNZ, or other? 4. Rich Media Content Distribution The report identifies the challenges faced by content providers, particularly the distribution of audio and video files. What initiatives with regards to peering and data interconnection would assist the growth and viability of the NZ digital content industry? 5. Consumer Pricing Strategies The report suggests consumer pricing strategies that differentiate between national and international traffic might encourage a greater take-up of New Zealand-sourced content. Do you agree? 6. Telecom Local Peering Proposal The report has noted a significant industry development with regards to Telecom's Local Peering Proposal, which has been the subject of industry discussions since April 2007. Do you support the proposals put forward in Telecom's local peering initiative? 7. Peering Code of Practice The report is neutral at this time on whether a Peering Code of Practice could be a useful mechanism to progress industry cooperation on peering and data connection issues. Do you support the need for a specific self regulatory industry initiative such as a Code of Practice to manage and develop consensus on peering and data connection issues? Failing that, should Government consider some form of regulation? 8. Other Please comment on any other issues in the report that you feel are not covered by the above questions. ------------ Please forward submissions to richard(a)internetnz.net.nz. InternetNZ will publish all submissions on its website at www.internetnz.net.nz and considers you have consented to this by filing your submission

1 0

Spam & NZ Anti Spam law issues.
by Skip Parker 05 Nov '07

05 Nov '07

Hi, I hope this email is not too far off List Topic, however i have a question that I would like some feedback for from NZ ISP's. (I believe its been raised before) A number of my customers run Email List Services which sends out various messages to a subscribed customer base (compliant with the NZ Anti Spam Laws etc). The issue we have is that while we have done ALL we can to adhere to good internet etiquette, we seem to be loosing the battle to send legitimate emails to our customers. In the last month ive been discussing these issues with many ISP's and the range of responses are "Sure heres how you can make it work" to "Go Away we dont want to deal with this". What I'm wondering is this. If we setup a whitelist service that had a set of guidelines, would ISP's look at adopting it in their Firewall/Spam filtering services. Some guidelines for such a service would be: - New Zealand Based List Servers Only - New Zealand Anti Spam law compliant - Correct DNS and Fixed IP Address configured - Agreed Email Delivery Speeds (i.e x number of messages per hour) - Agreed Email Volumes (i.e x number of bulk message sent per day) - Server/Service Administrator Details registered for contacting etc - Security Compliance etc.. Keen to hear any feedback and suggestions. I think i speak for a number of content providers when i say that we want to work with ISP's and provide a service that works for both our Customers and you guys as ISP's. Skip Parker skip(a)ignition.net.nz

9 11

BBBZZZZZTTTT: Where did all the lights go?
by Dean Pemberton 04 Nov '07

04 Nov '07

Anyone get effected by the Telecom power outage? Dean

8 9

[Apnic-announce] APNIC additional IPv4 address blocks
by Elly Tawhai 01 Nov '07

01 Nov '07

Dear colleagues The information in this announcement is to enable the Internet community to update network configurations, such as routing filters, where required. APNIC received the following IPv4 address blocks from IANA in October 2007 and will be making allocations from these ranges in the near future: 114/8 115/8 Reachability and routability testing of new prefixes will commence soon. The daily report will be published at the usual URL: http://www.ris.ripe.net/debogon For more information on the resources administered by APNIC, please see: http://www.apnic.net/db/ranges.html For information on the minimum allocation sizes within address ranges administered by APNIC, please see: http://www.apnic.net/db/min-alloc.html Kind regards, Elly ________________________________________________________________________ Elly Tawhai email: hostmaster(a)apnic.net Internet Resource Analyst/ Liaison (Australasia), APNIC sip: helpdesk(a)voip.apnic.net http://www.apnic.net/helpdesk phone: +61 7 3858 3188 fax: +61 7 3858 3199 ________________________________________________________________________

1 0

Re: [nznog] The day the routers died
by Scott Weeks 01 Nov '07

01 Nov '07

Once, back when I was working on a global network, myself, some folks from Europe and some folks from your part of the world were all working on a big problem together and I kept hearing the guys from your part of the world snicker every time the Europe guys said 'rooter'. Being from Hawaii, I didn't get it. Later, it was explained to me. Now every time I hear the Europe guys say 'rooter' I laugh and everyone now looks at me strangely. ;-) scott --- danclarknz(a)gmail.com wrote: haha the 'Rooter' ;-) --------------------------------- On 11/1/07, Philip D'Ath <pid(a)ifm.net.nz> wrote: > > Not on topic, I know, but this is very entertaining and will appeal to > people on this group. > > http://www.youtube.com/watch?v=_y36fG2Oba0

1 0