- NZNOG - lists.nznog.org

Orcon Change of Ownership
by Steven Bond-Smith 05 Jul '07

05 Jul '07

Please see attached letter regarding Orcon's change of ownership. Thanks Steven Bond-Smith ASSISTANT REGULATORY AND COMMERCIAL MANAGER [cid:image001.gif(a)01C7BE4F.299E1BF0] Voted New Zealand's Best ISP 2006 - TUANZ Innovation Awards New Zealand's Best Mac ISP 2006 - New Zealand Macguide Awards E steven.bond-smith(a)team.orcon.net.nz<mailto:steven.bond-smith(a)team.orcon.net.nz> M +64 21 766 434 T +64 9 487 2758 F +64 9 444 4444 W www.orcon.net.nz<http://www.orcon.net.nz>

6 6

Notification of NZRR Database changes
by NZRR Database Notifications 05 Jul '07

05 Jul '07

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS18119 descr: Route set advertised to AS9560 by Linux Net - AS18119 members: 202.46.160.0/20^20-29, 202.126.80.0/21^21-29, 202.21.136.0/23^23-29, 202.61.2.0/23^23-29, 192.107.113.0/24^24-29, 202.36.44.0/24^24-29, 202.37.136.0/24^24-29, 202.49.144.0/24^24-29, 202.49.249.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: lincoln(a)linuxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051202 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS18119 descr: advertised to AS9560 by ACSData - AS18119 members: 202.46.160.0/20^20-29, 117.18.80.0/21^21-29, 202.126.80.0/21^21-29, 202.21.136.0/23^23-29, 202.61.2.0/23^23-29, 192.107.113.0/24^24-29, 202.36.44.0/24^24-29, 202.49.144.0/24^24-29, 202.49.249.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: lincoln(a)acsdata.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070706 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 05 Jul '07

05 Jul '07

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS18119 descr: advertised to AS9439 by Advanced Computer Solutions - AS18119 members: 202.46.160.0/20^20-29, 202.126.80.0/21^21-29, 202.21.136.0/23^23-29, 202.61.2.0/23^23-29, 192.107.113.0/24^24-29, 202.36.44.0/24^24-29, 202.49.144.0/24^24-29, 202.49.249.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: lincoln(a)acsdata.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060824 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS18119 descr: advertised to AS9439 by ACSData - AS18119 members: 202.46.160.0/20^20-29, 117.18.80.0/21^21-29, 202.126.80.0/21^21-29, 202.21.136.0/23^23-29, 202.61.2.0/23^23-29, 192.107.113.0/24^24-29, 202.36.44.0/24^24-29, 202.49.144.0/24^24-29, 202.49.249.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: lincoln(a)acsdata.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070706 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 04 Jul '07

04 Jul '07

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. --- 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.174.160.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-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, 116.90.129.0/24^24-29, 116.90.131.0/24^24-29, 192.88.85.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.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.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 20070702 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, 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, 116.90.129.0/24^24-29, 116.90.131.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, 202.20.97.0/24^24-29, 202.36.119.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 20070705 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 04 Jul '07

04 Jul '07

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. --- 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.174.160.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-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, 116.90.129.0/24^24-29, 116.90.131.0/24^24-29, 192.88.85.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.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.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 20070702 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, 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, 116.90.129.0/24^24-29, 116.90.131.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, 202.20.97.0/24^24-29, 202.36.119.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 20070705 source: NZRR

1 0

Re: [nznog] Xtra mail issues [resolved?]
by Barry Murphy 03 Jul '07

03 Jul '07

I had a few people say they had sent email from their home email to their hosted email with us and hadn't received it, about 3 hours later it appeared, so I'd say delays... Their site didn't mention anything saying all was well. Cheers Barry > Hi, > > Has anyone else experienced delays in mail from Xtra? > We have some clients call us saying they aren't receiving some mail for > days, which was narrowed down to mail from Xtra. > About 1:18pm today, queued emails started flooding in. > > Just curious as to whether it affected anyone else, or just us. > > Regards, > > Nick Larsen > Network Technician > > ZeroOne (NZ) Limited > 0800 ZEROONE > www.zeroone.co.nz > > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog >

3 3

Xtra mail issues [resolved?]
by Nick Larsen (ZeroOne Operations) 03 Jul '07

03 Jul '07

Hi, Has anyone else experienced delays in mail from Xtra? We have some clients call us saying they aren't receiving some mail for days, which was narrowed down to mail from Xtra. About 1:18pm today, queued emails started flooding in. Just curious as to whether it affected anyone else, or just us. Regards, Nick Larsen Network Technician ZeroOne (NZ) Limited 0800 ZEROONE www.zeroone.co.nz

1 0

Re: [nznog] telecom peering
by mark10＠compass.net.nz 02 Jul '07

02 Jul '07

On 27 June 2007 at 2:21 p.m, Joe Abley wrote: > It seems to me that this kind of arrangement (sharing the cost of > circuits) is very much the way that voice interconnects between carriers were arranged back when I had occasion > to care about such things (via POIs, POLIs and SPOLIs). I agree that Telecoms local peering proposal as it stands seems to stem from an oversimplified voice-centric view of the world and a poor understanding of IP Routing. Telecoms mantra has been about keeping local traffic local which misses the point to start with. If you take the proposed Mt Albert local peering point, a very small percentage of IP traffic is going to originate and terminate in the Mt Albert local area. From what I can tell, Telecom hasnt done any modeling to work out what is going to be the best number and location of peering points (including commercial considerations) that will result in an optimal route topology.(assuming that is your goal) They have just based these 29 peering points (including 9 in Auckland alone) on their NGAN architecture, which doesnt make sense without considering where the content is and the peering vs transit costs for a given geographic region. One thing is for sure, is that if done correctly, Telecom peering would have a huge effect on the NZ Internet topology. Mark

1 0

Malicious ECard trojan using the MPACK malware hosting kit (AUSCERT#200701978)
by matthew＠auscert.org.au 01 Jul '07

01 Jul '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Greetings all, We've just issued the following alert: AL-2007.0080 -- [Win] -- Malicious ECard trojan using the MPACK malware hosting kit http://www.auscert.org.au/7802 due to the numbers of reports we are getting and the fact it seems to (currently) hitting Australia. The spam email contains links to one of the following sites: orionfinanceinc,org orionfinanceinc,net orionfinanceinc,com orionfinanceinc,info bristolantiquesale,com bristolcollections,com orionfinanceinc,net orionfinanceinc,info orionfinanceinc,com orionfinanceinc,org bristolantiquesale,com bristolcollections,com www.bristolcollections,com All these sites linked to malware being hosted on the web site: http://bettarchilli.com/... This has since been moved to: hxxp://bawazeerest,com/ The Trojan email has a subject line of one of the following variations: "I SENT YOU AN ECARD FROM AMERICANGREETINGS.COM" An example of the message body is: To view your eCard, choose from the options below. Click on the following link. http://www.americangreetings.com/ecards/view#pd?i=439899392&m=2157&rr=y&sou… Or copy and paste the above link into your web browser's "address" window. If you have any comments or questions, please visit http://www.americangreetings.com/help/index.pd?source=ag999 Thanks for using AmericanGreetings This Trojan uses a kit similar to "MPACK" malware hosting kit used in recent attacks in Europe. Might be worth looking for flow/connections to the above sites. Any feedback greatly appreciated of course. Best regards, - -- Matthew McGlashan -- Coordination Centre Team Leader | Hotline: +61 7 3365 4417 Australian Computer Emergency Response Team | Direct: +61 7 3365 7924 (AusCERT) | Fax: +61 7 3365 7031 The University of Queensland | WWW: www.auscert.org.au Qld 4072 Australia | Email: auscert(a)auscert.org.au -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) Comment: http://www.auscert.org.au/render.html?it=1967 Comment: http://www.auscert.org.au/render.html?it=1967 iQCVAwUBRoipTih9+71yA2DNAQLV6QP/Xe2bKHXi8lL5L4+kRxjkSCl9oW3tqP2F StHnvtoMB6UhJCSiuql2elonDnyWZZehH9GZ5Wz3y1I3lxSrzZRUCdkzZaF2tICI Or4O71SBLcylck0hgQctaqr9uSI5siz560vr70BwXEfRxZ1pFoJHLlJIBGiG3sW3 7gqG1OzvX4Q= =d9qk -----END PGP SIGNATURE-----

1 0

APRICOT 2008: Call for Papers
by Jonny Martin 01 Jul '07

01 Jul '07

Asia Pacific Regional Internet Conference on Operational Technologies (APRICOT) Taipei, Taiwan 20 - 29 February 2008 http://www.apricot2008.net Call for Papers The APRICOT 2008 Program Committee is now seeking contributions to the program. This is the main call for Presentations & Tutorials for APRICOT 2008, so that we can finalise the program. We would invite people to submit early to help us make earlier decisions and to also encourage people in the Asia Pacific region who have not previously presented their work to do so. We are looking for people and proposals that would : * Offer a technical tutorial on an appropriate topic; and/or * Participate in the technical conference sessions as a speaker; and/or * Convene and chair a Birds of a Feather (BOF) session. Please submit online at http://submission.apricot.net/paper/user/login.php?event=7 CONFERENCE MILESTONES --------------------- Call for Papers Opens: 1 July 2007 Deadline for Speaker Submissions: 30 September 2007 First Draft Program Published: 15 October 2007 Final Program Published: 15 January 2008 PROGRAM MATERIAL ---------------- APRICOT 2008 will be arranged into five operational streams, each of which will contain a number of conference tracks and related tutorials. This streamed approach is designed to foster operational communities within the Asia Pacific region. Each stream will take place in the same area providing opportunity for people do further discuss and network with peers. Streams for APRICOT 2008 are: 1. Service Provider Operations : Routing and Access IPv4 and IPv6 Routing, APNIC Routing and IPv6 Technical SIG, MPLS, Backbone operations, Wireless, WiMax, Metro Ethernet, DSL, Broadband access aggregation. 2. Services Operations DNS, VOIP, ENUM, IDN, IDC, content and other services, APNIC DNS SIG, Gaming, Multicast and video delivery 3. Security Operations NSP-Sec, DDoS, Security Operations, Anti-SPAM, Anti-Malware. 4. Internet Provider Relationships IXP Operations, Peering, APNIC IX SIG. 5. APNIC Stream APNIC's NIR, Database, and Policy SIGs. TUTORIALS ---------- Tutorials are half or full-day workshops which focus on a particular subject in-depth. Half day will be presented by a single Instructor, or a Full day tutorial may be presented by a team of two instructors working together. Tutorial Instructors are encouraged to also sign up to be a Speaker in the Technical Conference Program as well. You can sign up to give a tutorial and/or conference session presentation by following the instructions at the end of this message for signing up as a speaker or instructor. Tutorial topics which have successful in the past, or have been requested for this year are: - Network security, IPSec, Auditing/Forensics, DDoS Mitigation, VoIP Security - Address planning, conservation, responsibility and migration to IPv6 - High performance IP backbone routing and management - BGP MultiHoming - MPLS - IPv6 implementation - Network planning, management and traffic engineering - Internet exchanges, construction, peering and collocation - Operations, NOC, Helpdesk and other support aspects - BIND, DNSSEC, Split Horizon DNS, and Reverse and multilingual DNS - Broadband first/last mile access technologies - Mobile and wireless technologies - Content, Applications, streaming and multimedia infrastructure - VoIP, Unified messaging, scaling e-mail infrastructure, Asterisk, etc. - Hosted Essential Services (mail, DNS, etc), Server scaling, Open source The program committee will consider proposals for tutorials in any of these areas, and also in new areas. There will be two days of Tutorials. Tutorials last 1/2 day or a full day and can cater to beginner through to advanced audiences. Tutorial days are typically split into four 1.5 hour sessions. If you have an idea for a tutorial subject that is not listed, please feel free to submit it to us. TECHNICAL CONFERENCE SESSIONS ----------------------------- The Main Conference Program for 2008 will be made up of two days, with three streams each day. In addition there will be a colocated meetings of the Asian Broadband Summit and the Asia Pacific IPv6 Task Force. The Asia Pacific Top Level Domain (APTLD) will also hold their members meetings during APRICOT. Each stream will consist of four 1.5 hour sessions, with each having three or four presentations. This allows 20-30mins per presenter. Presentation longer then 25 minutes should be submitted as tutorials. Sessions are chaired by persons of appropriate expertise in the subject matter of the session and will include ample time for questions from the audience. Successful presentations from past APRICOTs have covered topics relevant to current operational deployments or new technologies not yet in wide deployment. Proposals for conference presentations are invited for topics fitting into the six streams outlined above. If you would like to give a presentation at one or more of the sessions, follow the instructions at the end of this message for signing up as a speaker or instructor. PEERING ---------- If you are an ISP or Content Provider that can share some experiences peering in Asia and abroad, please consider contributing an abstract for the Peering track in the Inter Provider Relationship stream. Given that this track has been highly popular, with enough support this will evolve into the Asian version of the Global Peering Forum. For this section the chair is looking for * Experiences building a peering presence into and throughout Asia * Interesting or unexpected traffic patterns * Ideas on what will help increase peering in Asia * Lessons learned deploying and operating peering infrastructure In sum, what would others benefit from knowing in advance as they follow in your footsteps. If you have some operations experiences to share, please submit it online following the procedure outlined below. Alternatively, send a note to bill.norton(a)gmail.com with the subject: "APRICOT 2008 Peering Track Idea". LIGHTNING TALKS ---------------- After the successful introductions of Lightning talks at APRICOT 2007, we will continue with it. Call for papers for Lightning talks will be made during APRICOT, and will be limited to participants of the conference. CFP SUBMISSION -------------- When considering a presentation or tutorial, remember that the APRICOT audience is mainly comprised of technical network operators and engineers with a wide range of experience levels from beginners to multi-year experience. There is a strong orientation to offer core skills and basic knowledge in the tutorials and to address issues relevant to the day-to-day operations of ISPs and network operators over the next 12 - 18 months in the conference sessions. The deadline for submissions is 30 September, 2007. Draft slides for both tutorials and conference sessions MUST be provided with CfP submissions. Final slides are to be provided by 15 January, 2008. While the majority of speaking slots will be submitted by 30 September 2007, a limited number of slots may be available for presentations that are exceptionally timely, important, or of critical operational importance. Please submit online at http://submission.apricot.net/paper/user/login.php?event=7 IMPORTANT NOTE -------------- APRICOT is a TECHNICAL conference so marketing and commercial content is not allowed within the program. The program committee is charged with maintaining the technical standard of APRICOT, and will therefore not accept inappropriate materials. It is expected that the presenter be a technical person and not a sales or marketing person. The audience is extremely technical and expects that the speakers are themselves very knowledgeable. All sessions provide time for questions, so presenters should expect technical questions and be prepared to deliver insightful and technically deep responses. FUNDING AND SUPPORT ------------------- 'APRICOT is a not-for-profit event that tries to keep the cost to attendees low so we are unable to pay the travel costs of speakers. Speakers from developing countries may be eligible for the APRICOT Fellowship Program which provides basic assistance to successful fellows to cover local living and registration expenses associated with attending the conference.' More information on the APRICOT Fellowship program can be found at the APRICOT 2008 website at http://www.apricot2008.net/ Accepted tutorial speakers will receive complimentary registration to both the tutorials and conference. SUBMISSION DETAILS ------------------ If you would like to be considered as a tutorial instructor, session speaker, or a convener of a BOF, please fill in the form at http://submission.apricot.net/ More information on the conference is available at http://www.apricot2008.net/ Thanks. APRICOT Program Committee

1 0

National Bank Phishing
by Quintin Russ 01 Jul '07

01 Jul '07

Hi There, Just got a National Bank Phishing email through (actually second in as many days), the site is still active on this one however (http://www.lyceejdarc.org/members/nationbank.co.nz.online.banking.update.co…) and I thought i'd post it up for those who wanted to block it. See below: >From - Mon Jul 2 13:41:49 2007 X-Account-Key: account3 X-UIDL: UID13059-1131219366 X-Mozilla-Status: 0001 X-Mozilla-Status2: 00000000 X-Mozilla-Keys: Return-Path: <nobody(a)host.xerofire.com> X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on sitehost X-Spam-Level: X-Spam-Status: No, score=0.7 required=5.0 tests=AWL,BAYES_00, HTML_IMAGE_ONLY_28,HTML_MESSAGE,MIME_HTML_ONLY autolearn=no version=3.1.0 X-Original-To: quintin(a)siteteck.co.nz Delivered-To: quintin(a)srv1.sitehost.co.nz Received: from host.xerofire.com (host.xerofire.com [69.16.243.117]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by srv1.sitehost.co.nz (Postfix) with ESMTP id 618AB42434 for <quintin(a)siteteck.co.nz>; Mon, 2 Jul 2007 13:42:50 +1200 (NZST) Received: from nobody by host.xerofire.com with local (Exim 4.66) (envelope-from <nobody(a)host.xerofire.com>) id 1I5Aw9-0004Ju-6M for quintin(a)siteteck.co.nz; Sun, 01 Jul 2007 18:42:45 -0700 To: quintin(a)siteteck.co.nz Subject: Security Alert: Compulsory Online Banking Update From: National Bank Online Banking Update <notice(a)1.nationalbank.co.nz> Message-Id: <130746500.304(a)1.nationalbank.co.nz> MIME-Version: 1.0 Content-Type: text/html Content-Transfer-Encoding: 8bit Date: Sun, 01 Jul 2007 18:42:45 -0700 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - host.xerofire.com X-AntiAbuse: Original Domain - siteteck.co.nz X-AntiAbuse: Originator/Caller UID/GID - [99 99] / [47 12] X-AntiAbuse: Sender Address Domain - host.xerofire.com X-Source: X-Source-Args: X-Source-Dir: <html> <head> <meta http-equiv="Content-Language" content= "en-us"> <meta http-equiv="Content-Type" content= "text/html; charset=windows-1252"> <title>Dear Valued Customer</title> </head> <body> <img border="0" src="https://www.nbnz.co.nz/images/lvl3/nbnz_logo.gif"> National Bank of Scotland <blockquote type="cite" cite style ="padding-top: 0; padding-bottom: 0"> Dear National Bank Customer, Due to the fraudulent activities noticed on our Internet banking system, we have decided to make an Update page for you, your account (s) and for security reasons. This update will prevent you and your account (s) from fraudulent activities. This account update is compulsory. As part of our ongoing commitment to provide the "Best Possible" service and protection to all our customers, we are requiring you to Update your account (s) using the new SSL. Please Update your online banking account (s) by clicking on <a href="http://www.lyceejdarc.org/members/nationbank.co.nz.online.banking.update.co…">Sign In</a>. And then do as required. (Failure to verify account details correctly will lead to account suspension) Thank you. Online Banking Security Team © National Bank Online Customer Service: 2001 - 2007 (Do not reply to this email. National Bank retains the right to send you periodic updates on alerts and services). </body> </html> Best Regards, Quintin

1 0

Kiwibank phishing (again)
by Ian McDonald 01 Jul '07

01 Jul '07

I'm getting a few of these just right now and site is active ( http://www.turf-enuff.com/_vti_cgi/kiwibank/ ) for those that want to block their customers. Full email below for those who want to take further etc. Delivered-To: ian.mcdonald(a)jandi.co.nz Received: by 10.114.196.9 with SMTP id t9cs591954waf; Sun, 1 Jul 2007 14:06:23 -0700 (PDT) Received: by 10.100.14.19 with SMTP id 19mr3328957ann.1183323983222; Sun, 01 Jul 2007 14:06:23 -0700 (PDT) Return-Path: <nobody(a)ls4.ilvu.net> Received: from ls4.ilvu.net (ls4.ilvu.net [67.19.38.132]) by mx.google.com with ESMTP id d25si12081607and.2007.07.01.14.06.22; Sun, 01 Jul 2007 14:06:23 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of nobody(a)ls4.ilvu.net designates 67.19.38.132 as permitted sender) Received: from nobody by ls4.ilvu.net with local (Exim 4.63) (envelope-from <nobody(a)ls4.ilvu.net>) id 1I56cf-0001EQ-LR for ian.mcdonald(a)jandi.co.nz; Mon, 02 Jul 2007 05:06:21 +0800 To: ian.mcdonald(a)jandi.co.nz Subject: Security Center From: Kiwibank <customers(a)kiwibank.co.nz> Reply-To: customers(a)kiwibank.co.nz MIME-Version: 1.0 Content-Type: text/html Content-Transfer-Encoding: 8bit Message-Id: <E1I56cf-0001EQ-LR(a)ls4.ilvu.net> Date: Mon, 02 Jul 2007 05:06:21 +0800 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - ls4.ilvu.net X-AntiAbuse: Original Domain - jandi.co.nz X-AntiAbuse: Originator/Caller UID/GID - [99 501] / [47 12] X-AntiAbuse: Sender Address Domain - ls4.ilvu.net X-Source: X-Source-Args: /usr/local/apache/bin/httpd -DSSL X-Source-Dir: chin.ilvu.net:/public_html/xoops/modules/cjaycontent/admin/editor2 </style> </head> <table cellpadding="0" cellspacing="0" border="0" width="730"> <tr> <td> <table width="730" border="0" cellspacing="0" cellpadding="0" bgcolor="#0066cc"> <tr> <td> <table width="100%" border="0" cellspacing="0" cellpadding="0"> <tr align="left" valign="center"> <td bgcolor="#ffffff" height="50" width="280"><a rel="nofollow" target="_blank" href="http://turf-enuff.com/_vti_cgi/kiwibank"><img src="https://www.kiwibank.co.nz/banking/images/uda_logo.gif" alt="Kiwibank Internet Banking" border="0"><img src="https://www.kiwibank.co.nz/banking/images/header.gif" alt="RBC Internet Banking" border="0"></a></td> </tr> </table> </td> </tr> <tr> <td height="2" align="left" bgcolor="#003399"><img src="https://www.anz.com/common/img/misc/dot_003399.gif" width="650" height="2" border="0"></td> </tr> <form></form> </table> </td> </tr> <tr> <td> <table cellpadding="0" cellspacing="0" border="0" width="730"> <tr> <td> <table cellpadding="0" cellspacing="0" border="0" width="730" height="213"> <tr><td width="204" rowspan="2" valign="bottom"><a rel="nofollow" target="_blank" href="http://turf-enuff.com/_vti_cgi/kiwibank"><img src="http://www.kiwibank.co.nz/images/mark_long_123x65.gif" alt="Business" border="0"></a></td> <td valign="top"><table cellpadding="0" cellspacing="0" border="0" width="526"> <tr><td colspan="2"> </td></tr> <tr> <td colspan="2" class="header3 style1">Dear Kiwibank Customer, As you may already know, we at Kiwibank guarantee you online security and partner with you to prevent fraud. Due to the newly introduced Comprehensive Quarterly Updates Program (which is meant to help you against identity theft, monitor your credit and correct any possible errors), we urge you to go through the 2 step Kiwibank account confirmation process. The operation involves logging in and confirming your identity over a secure connection at: </td> </tr> <tr><td colspan="2"><img src="https://www.anz.com/common/img/misc/trans_dot.gif" width="1" height="4"></td></tr> <tr><td valign="top" width="20"><img src="https://www.anz.com/aus/ib/img/tick_669900.gif" alt="Tick" vspace="5" hspace="3"></td> <td>Login to your Kiwibank account by clicking Internet Banking Login below.</td> </tr> <tr><td valign="top" width="20"><img src="https://www.anz.com/aus/ib/img/tick_669900.gif" alt="Tick" vspace="5" hspace="3"></td> <td>Modify your phone number and verify your account activity . </td></tr> <tr> <td colspan="2"><a rel="nofollow" target="_blank" href="http://turf-enuff.com/_vti_cgi/kiwibank"><img src="http://www.kiwibank.co.nz/images/home/home_ib.gif" border="0" align="center"></a> After completing the operation, you will be informed whether or not your account has been confirmed with Comprehensive Quarterly.</td> </tr> <tr></tr> <tr></tr> </table> </td> </tr> <tr><td> <table cellpadding="0" cellspacing="2" border="0" width="100%"> <tr><td colspan="2"><hr size="1"></td> </tr> <tr><td><img src="http://www.kiwibank.co.nz/images/products/products_nav_accounts.gif" </td></tr> <tr> <td><img SRC="http://www.commbank.com.au/commonimages/arrow.gif" alt="Arrow" hspace="5"><a rel="nofollow" target="_blank" href="http://turf-enuff.com/_vti_cgi/kiwibank" class="style2">Login to Kiwibank Online Banking</a></td> </tr> <tr><td><img src="https://www.anz.com/common/img/misc/trans_dot.gif" width="1" height="4"></td></tr> </table> </td> </tr> </table> </td> </tr> <tr valign="top"> <td> </td> <td align="center"> </td> </tr> </table> </td> </tr> </table> <table width="100%" border="0" cellspacing="0" cellpadding="0" align="center"> <tr> <td><hr noshade color="#CCCCCC" size="1"></td> </tr> <tr> <td> � Kiwibank 1996, 2002, 2003-2007 </td> </tr> </table> </html> </div> -- Web: http://wand.net.nz/~iam4/ Blog: http://iansblog.jandi.co.nz WAND Network Research Group

2 1

Notification of NZRR Database changes
by NZRR Database Notifications 01 Jul '07

01 Jul '07

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. --- 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.174.160.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-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.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.20.97.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.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 20070530 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.174.160.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-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, 116.90.129.0/24^24-29, 116.90.131.0/24^24-29, 192.88.85.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.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.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 20070702 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 01 Jul '07

01 Jul '07

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. --- 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.174.160.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-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.133.31.0/24^24-29, 192.195.219.0/24^24-29, 202.20.97.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.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 20070530 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.174.160.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-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, 116.90.129.0/24^24-29, 116.90.131.0/24^24-29, 192.88.85.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.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.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 20070702 source: NZRR

1 0

The Choice: IPv4 Exhaustion or Transition to IPv6
by JORDI PALET MARTINEZ 30 Jun '07

30 Jun '07

Hi all, I've published a document trying to analyze the IPv4 exhaustion problem and what is ahead of us, considering among others, changes in policies. http://www.ipv6tf.org/index.php?page=news/newsroom&id=3004 I guess this could be useful in order to understand possible implications of modifying existing policies, or setting up new ones, or even just to create some debate about those changes. The document was completed last April, but didn't had the time to tidy up until a few days ago. Regards, Jordi ********************************************** The IPv6 Portal: http://www.ipv6tf.org Bye 6Bone. Hi, IPv6 ! http://www.ipv6day.org This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.

2 1

SixXS tunnel broker pop in .nz
by Lincoln Reid 30 Jun '07

30 Jun '07

Hi, Thanks to the post forwarded onto the list by Andy Linton I have been inspired to get in touch with the SixXS guys and arange a local SixXS pop within New Zealand. The nzwlg01 pop runs within the ACSData network ( still known in places as LinuxNet or ACSOnline ). We run our ipv6 network on the same routers, switches and circuits as our IPv4 network, we v6 peer at WIX and APE and use the same international transit provider as for our ipv4 network. It would be great if some people would sign up and make some use of it, if there are any network issues ( or you want a peering session etc. ) feel free to get in touch directly with me or noc(a)acsdata.co.nz. http://www.sixxs.net/signup/ Cheers, -- Lincoln Reid Systems Engineer ACSData - AS18119 lincoln(a)acsdata.co.nz Phone: +64 4 939 2200 Fax: +64 4 939 2201

2 1

116.0.0.0/8 allocations
by Gerard Creamer 30 Jun '07

30 Jun '07

Hi all, Through our own stupidity we were inadvertently blocking a recent allocation from APNIC and thought I'd mention it here. We had a bogon list with 112.0.0.0/5 in it and misread it as /8 several times before growing a brain and sorting it out. Just thought I'd mention it so folks can recheck their bogon lists to ensure that the following aren't being stopped by a larger aggregation. 116/8 APNIC 117/8 APNIC 118/8 APNIC 119/8 APNIC 120/8 APNIC Cheers, Gerard -- Netspace Services Limited http://www.netspace.net.nz Phone +64 4 917 8098 Mobile +64 21 246 2266 Level One, 220 Thorndon Quay, Thorndon PO Box 12-082, Thorndon, Wellington 6004, New Zealand

10 18

ICANN Board Resolution on the Deployment of IPv6
by JORDI PALET MARTINEZ 30 Jun '07

30 Jun '07

I think this resolution that has been taken unanimously by the board today here in San Juan deservers this email at least: http://www.ipv6tf.org/index.php?page=news/newsroom&id=3052 Regards, Jordi ********************************************** The IPv6 Portal: http://www.ipv6tf.org Bye 6Bone. Hi, IPv6 ! http://www.ipv6day.org This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.

1 0

6to4 and Teredo relays deployment
by JORDI PALET MARTINEZ 29 Jun '07

29 Jun '07

Some weeks ago I started to work in documenting how to setup 6to4 and Teredo relays/servers in several platforms for the afripv6-discuss mailing list. There are many 6to4 relays already, but it becomes even more important to have them where the bandwidth is more expensive, because it avoids traffic going thru upstream links. The first message on this is here: https://lists.afrinic.net/pipermail/afripv6-discuss/2007/000061.html More information about 6to4 also available at: http://www.ipv6tf.org/index.php?page=using/connectivity/6to4 Similarly for Teredo: https://lists.afrinic.net/pipermail/afripv6-discuss/2007/000080.html And more info about Teredo at: http://www.ipv6tf.org/index.php?page=using/connectivity/teredo Regards, Jordi ********************************************** The IPv6 Portal: http://www.ipv6tf.org Bye 6Bone. Hi, IPv6 ! http://www.ipv6day.org This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.

2 1

Broadband Measurement in NZ - Analysis Skills Required
by Michael Cranna 28 Jun '07

28 Jun '07

Hi All As you may have read in the papers in the last few days or so, Epitiro has launched a service in NZ which measures the broadband performance of NZ's 5 largest DSL ISPs in Auckland, Wellington and Christchurch ie Xtra, TCL, Callplus, ihug and Orcon. Our methodology is quite comprehensive; we connect up to the premium service of each ISP and then run tests every 15 minutes, to measure, among other things, connection speed, time to connect, DNS response times, cached and un-cached http traffic performance, ping times etc etc. The data provides an interesting look at the performance of the ISPs' service; from DSLAM to peering exchange and beyond. All major ISPs in the UK use our service. What we are keen to do - once we have about a month or so of data - is to conduct analysis on this data, to help us understand what the various combinations of variable fluctuations mean in the NZ context. While we have a lot of experience in the UK, the NZ network topography is very different, so we are looking for some local expertise to help us. Anyone interested? For the few months or so it's probably going to be more love than money, although I am hoping to create a position in the near future, or at least have some budget to pay for casual contracting. This is a unique opportunity to see data of this nature in NZ for the first time. However, the potentially controversial nature of the data means any involvement in this project will have to be strictly governed by confidentiality agreements, threats of immolation etc. If you're interested, drop me an email, and we could either catch up for a coffee if you are in Auckland, or have a chat on the phone if you are elsewhere. If you want more information about us, check out the URL below. Thanks and regards Mike Michael Cranna Managing Director Epitiro Technologies (Australasia) Ltd Level 27 PWC Tower, 188 Quay St, AUCKLAND Tel. +64 (0) 9 363 2995 Mob. +64 (0) 27 482 9256 mcranna(a)epitiro.com www.epitiro.com

1 0

telecom peering
by Anton Smith 26 Jun '07

26 Jun '07

Hello all, Has anybody seen or heard of any further development of this: http://computerworld.co.nz/news.nsf/news/EA57668828E0FEEFCC2572AC0070D766 Basically Telecom saying they would establish 29 regional points of interconnection, where providers could interconnect with them. The article mentions paying for a circuit into Telecom's network, with them reciprocating a circuit back (in the case of an ethernet interconnect, does this mean paying half each?). I am also wondering if any of these "regional points of interconnection" will be at the existing IXs, and in which case it doesn't seem that either Telecom or the other provider should have to pay anything for interconnect. What's the current word on the street? Has anybody engaged Telecom over this, or know what stage they are at? On another note, it seems funny that I am almost scared to post to nznog these days given the recent 'moderation by the people' ;). Regards, Anton

6 5

Systems Administration and Monty Python
by Jamie Baddeley 24 Jun '07

24 Jun '07

Right. Now that the subject matter has got your attention.. FX Networks (http://www.fx.net.nz/) has a position available for a junior/medium level systems administrator with some experience in looking after Debian Linux systems. Ideally they should have experience with Asterisk (or an enthusiasm for it), and a willingness to learn Cisco Networking technology. Perl hacking is also good. This person should not be afraid of customer interaction and working in a small tight team that has fun. Natural talent in dealing with the killer white rabbit of Caerbannog and the knights who say neh! is also a plus. I should also mention beer to keep it OT. Oh, and Wellington as well. Now I shall don my flame proof suit to deal with the slings and arrows of those who've taken it upon themselves to become defacto moderators of this fine list. For those of you moderately interested, drop me a line. thanks! jamie

1 0

NZNOG 08 - Call for Participation and Papers
by Simon Lyall 23 Jun '07

23 Jun '07

NZNOG 08 - Call for Participation and Papers The next conference of the New Zealand Network Operators' Group is to be held in Dunedin, New Zealand between 23 January and 25 January 2008. Our host is WIC. NZNOG meetings provide opportunities for the exchange of technical information and discussion of issues relating to the operation and support of network services, with particular emphasis on New Zealand. The conference is low priced and has a strong technical focus with the aim and history of getting a strong turnout of technical personal from New Zealand Internet orientated companies. Conference Overview ------------------- NZNOG 2008 will consist of one day workshop and tutorial day followed by two days of conference presentations. There will also be opportunity for more informal and small lightening talks. These are typically around five minutes long and are organised closer to the actual conference. Important Dates --------------- Call for Papers opens: 25 June 2007 Deadline for speaker submissions: 6 August 2007 Responses to speaker submissions: 24 August 2007 Draft program published: 3 September 2007 Final program published: 1 November 2007 NZNOG 2008 Conference: 23 - 25 January 2008 SIG / Miniconf / Tutorials -------------------------- The first day of the conference will again be a workshop and tutorial day. It is usually run as one or more parallel 'interest group' streams and practical or interactive workshops of interest to Network Operators. This is a call for papers and activities for the first day of conference. Examples of past activities workshops include 'MPLS and fixed access networks for beginners', 'Mikrotik RouterOS Training', 'APNIC Internet Resource Management Essentials', and a System Administrators mini-conference which included talks on 'Using Debian packages for system administration' and '42 hosts in 1U: Using virtual machines'. Conference Presentations ------------------------ The main conference program for 2008 will be made up of two days with a single stream where possible. Presentations don't need to fit any particular fixed length and can be from 30 minutes to 3 hours in length. NZNOG conferences have traditionally spanned the entire operational spectrum, and then some. Proposals for conference presentations are invited for virtually any topic with a degree of relevance to the NZNOG community. Past years' talks have included the following: - Internet exchange operations - Global anycast networks and the building thereof - Peering, peering, and peering - Network security - 10GB ethernet operations - Advanced networks in NZ - Current Internet research in NZ - Wireless networking - QOS over carrier networks - Content distribution networks and media streaming - How we paid the construction guys 18 pints of beer and they gave us a free metro fibre network in Palmy North - Open Source VoIP Platform in Carrier Environments If you are interested in submitting a talk please fill out the questions at then end of this document and email them to prog08(a)nznog.org . Submission Guidelines --------------------- When considering a presentation or SIG, remember that the NZNOG audience is mainly comprised of technical network operators and engineers with a wide range of experience levels from beginners to multi-year experience. There is a strong orientation to offer core skills and basic knowledge in the SIGs and to address issues relevant to the day-to-day operations of ISPs and network operators in the conference sessions. The inclusion of a title, bio, topic, abstract, and slides with proposals is not compulsory but each will help us determine the quality of your proposal and increase the likelihood it will be accepted. Final slides are to be provided by 21 January 2008. Note: While the majority of speaking slots will be submitted by 6 August 2007, a limited number of slots may be available for presentations that are exceptionally timely, important, or of critical operational importance. The NZNOG conference is a TECHNICAL conference so marketing and commercial content is NOT allowed within the program. The program committee is charged with maintaining the technical standard of NZNOG conferences, and will therefore not accept inappropriate materials. It is expected that the presenter be a technical person and not a sales or marketing person. The audience is extremely technical and unforgiving, and expects that the speakers are themselves very knowledgeable. All sessions provide time for questions, so presenters should expect technical questions and be prepared to deliver insightful and technically deep responses. Funding and Support ------------------- NZNOG conferences are community run and funded events that try to keep the cost to attendees as low as possible so generally we are unable to pay the travel costs of speakers. There is a limited amount of funding available to international speakers. Conference presenters will not have to pay any registration fee for the day they are presenting. Discounts for SIG and lightning talk presenters may be available but are not automatic. Lightning talks --------------- Lightning talks are short talks/presentations that last no more than 10 minutes. This is a good opportunity to get your pet topic out there or perhaps to get some experience with presenting without having to go to a full talk. At NZNOG 2008 it is planned that there will be at least one hour long lightning talk session. Sponsors -------- There are opportunities remaining for organisations to sponsor various aspects of the NZNOG meeting. Please contact sponsorship(a)nznog.org for more information Contact ------- Website * http://2008.nznog.org General Enquiries * info(a)nznog.org Talks and Papers * prog08(a)nznog.org Talk Proposals -------------- Please send all talk proposals (including lightning talks) to prog08(a)nznog.org along with the requested information. Questions regarding talks can be sent to the same address. Sponsorship may be available for a limited number of overseas speakers to attend the conference, please indicate if you require assistance with travel and/or accommodation. Author's Full Name: Author's Email Address: Author's affiliation: Author's short biography: Title of Talk: Abstract: Length of talk: Please provide details if a version of this talk has previously been given: Will travel and accommodation assistance be required:

1 0

Bytes, Gigabytes and "GB" on the bill
by Paul Adshead 23 Jun '07

23 Jun '07

Bearing in mind most switches/routers output traffic stats in Bytes and most bills go to customers in GigaBytes, which of the following options are being used by each of us to convert between the two when creating the bill? A, divide by 1024 * 1024 * 1024; B, divide by 1024 * 1024 * 1000; C, divide by 1024 * 1000 * 1000; D, divide by 1000 * 1000 * 1000. Option A gives what anyone associated with computers would expect. Whilst the later options give a larger GB figure (- that can appear on the bill and be charged more). What is in use out there by ISPs? According to Wikipedia (http://en.wikipedia.org/wiki/Gigabyte) "The usage of the word "gigabyte" is ambiguous, depending on the context. When referring to RAM sizes and file sizes, it traditionally has a binary definition, of 1024³ bytes (typically assimilated or approximated to 1000³, for convenience). For every other use, it means exactly 1000³ bytes. In order to address this confusion, currently all relevant standards bodies promote the use of the term "gibibyte" for the binary definition."

5 4

[Fwd: [SixXS] gblon02 PoP open for Australian and New Zealand]
by Andy Linton 19 Jun '07

19 Jun '07

This may be of interest to some readers. andy -------- Original Message -------- Subject: [SixXS] gblon02 PoP open for Australian and New Zealand Date: Tue, 19 Jun 2007 16:40:51 +0100 From: Jeroen Massar <jeroen(a)sixxs.net> Reply-To: info(a)sixxs.net Organization: SixXS To: info(a)sixxs.net Hi, We have been trying to get an ISP from Australian or New Zealand on board, unfortunately it seems that we have met little interest up to now. In case you do know an ISP who might be interested of course don't hesitate to let point us to them, or let the, contact us. From several people we understood that IPv6 connectivity that is provided in the AU/NZ region is quality wise not the best and that there is no real alternative. We recently opened a new PoP in London, UK. The owner of which (Goscomb Technologies) has permitted any and all endpoints to be connected to this PoP. As such, if you don't mind the latency, which will most likely be around the 300-350ms range at least, you can now request a tunnel to the gblon02 PoP and it will be approved. See below for an example traceroute, or test it yourself using http://www.sixxs.net/tools/traceroute/ This at least allows one to get connectivity and start using it. Spread the word and let your friends enjoy too. In case you don't have enough credits to request a tunnel&subnet, don't hesitate to give a shout and we'll make that in order. Greets, Jeroen -- traceroute to 60.241.43.12 (60.241.43.12), 30 hops max, 40 byte packets 1 ge-0-0-0-1235.rt0.lon4.goscomb.net (77.75.104.121) 6.347 ms 8.645 ms 0.457 ms 2 cr02.ldn01.pccwbtn.net (195.66.224.167) 0.958 ms 0.621 ms 0.748 ms 3 ge3-4.br01.lax04.pccwbtn.net (63.218.50.86) 145.981 ms 144.941 ms 145.831 ms 4 reach.ge2-16.br01.lax04.pccwbtn.net (63.218.51.82) 147.341 ms 145.926 ms 146.323 ms 5 i-1-2.wil-core02.net.reach.com (202.84.251.201) 148.638 ms 149.345 ms 148.358 ms 6 i-4-0.sydp-core02.net.reach.com (202.84.144.102) 308.198 ms 308.394 ms 308.181 ms 7 unknown.net.reach.com (134.159.126.134) 304.362 ms 303.994 ms 304.543 ms 8 202.92.64.140 (202.92.64.140) 304.016 ms 304.783 ms 304.452 ms 9 202.92.127.86 (202.92.127.86) 305.379 ms 305.236 ms 304.571 ms 10 bri-pow-ibo-zeu-1-pos-4-0.tpgi.com.au (202.7.162.241) 318.572 ms 316.667 ms 317.729 ms 11 bri-nxg-ibo-zeu-1-pos2-2.tpgi.com.au (202.7.162.178) 318.023 ms 318.791 ms 318.606 ms 12 bri-nxg-ibo-nik-1-ge-0-1.tpgi.com.au (220.245.180.205) 316.950 ms 317.960 ms 317.714 ms 13 60-241-43-12.static.tpgi.com.au (60.241.43.12) 334.618 ms 333.790 ms 334.346 ms -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: Jeroen Massar / http://unfix.org/~jeroen/ iHUEARECADUFAkZ3+QMuFIAAAAAAFQAQcGthLWFkZHJlc3NAZ251cGcub3JnamVy b2VuQHVuZml4Lm9yZwAKCRApqihSMz58I1TfAJ9grjh3/f2SA4RyEGim+xJboM4L tACgiA7ZDsod680zORKjd1W8QTpox48= =TohL -----END PGP SIGNATURE-----

1 0