- NZNOG - lists.nznog.org

Notification of NZRR Database changes
by NZRR Database Notifications 18 Oct '06

18 Oct '06

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:AS4770 descr: advertised to AS9439 by ICONZ - AS4770 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 210.48.0.0/17^17-29, 210.185.0.0/18^18-29, 210.54.160.0/19^19-29, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.55.96.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, 210.56.32.0/20^20-29, 192.173.16.0/21^21-29, 202.12.248.0/21^21-29, 202.37.144.0/21^21-29, 202.37.224.0/21^21-29, 202.46.176.0/21^21-29, 202.50.200.0/21^21-29, 202.74.224.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 203.190.208.0/21^21-29, 205.233.128.0/21^21-29, 202.36.36.0/22^22-29, 202.37.140.0/22^22-29, 202.37.200.0/22^22-29, 202.41.136.0/22^22-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 210.54.136.0/22^22-29, 210.55.24.0/22^22-29, 202.21.136.0/23^23-29, 202.36.44.0/23^23-29, 202.36.76.0/23^23-29, 202.37.86.0/23^23-29, 202.37.240.0/23^23-29, 202.37.252.0/23^23-29, 202.49.80.0/23^23-29, 202.50.246.0/23^23-29, 202.124.106.0/23^23-29, 205.233.136.0/23^23-29, 210.55.182.0/23^23-29, 192.88.85.0/24^24-29, 192.107.113.0/24^24-29, 192.133.31.0/24^24-29, 192.173.24.0/24^24-29, 198.32.66.0/24^24-29, 199.212.93.0/24^24-29, 202.6.84.0/24^24-29, 202.12.70.0/24^24-29, 202.14.100.0/24^24-29, 202.20.6.0/24^24-29, 202.20.97.0/24^24-29, 202.21.130.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.155.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.37.76.0/24^24-29, 202.37.85.0/24^24-29, 202.37.136.0/24^24-29, 202.37.163.0/24^24-29, 202.37.197.0/24^24-29, 202.37.232.0/24^24-29, 202.41.140.0/24^24-29, 202.46.190.0/24^24-29, 202.49.62.0/24^24-29, 202.49.89.0/24^24-29, 202.49.159.0/24^24-29, 202.49.249.0/24^24-29, 202.50.87.0/24^24-29, 203.97.5.0/24^24-29, 205.233.243.0/24^24-29, 210.54.140.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: deon(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060911 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS4770 descr: advertised to AS9439 by ICONZ - AS4770 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 210.48.0.0/17^17-29, 210.185.0.0/18^18-29, 210.54.160.0/19^19-29, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.55.96.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, 210.56.32.0/20^20-29, 192.173.16.0/21^21-29, 202.12.248.0/21^21-29, 202.37.144.0/21^21-29, 202.37.224.0/21^21-29, 202.46.176.0/21^21-29, 202.50.200.0/21^21-29, 202.74.224.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 203.190.208.0/21^21-29, 205.233.128.0/21^21-29, 202.36.36.0/22^22-29, 202.37.140.0/22^22-29, 202.37.200.0/22^22-29, 202.41.136.0/22^22-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 210.54.136.0/22^22-29, 210.55.24.0/22^22-29, 202.21.136.0/23^23-29, 202.36.44.0/23^23-29, 202.36.76.0/23^23-29, 202.37.86.0/23^23-29, 202.37.240.0/23^23-29, 202.37.252.0/23^23-29, 202.49.80.0/23^23-29, 202.50.246.0/23^23-29, 202.124.106.0/23^23-29, 205.233.136.0/23^23-29, 210.55.182.0/23^23-29, 192.88.85.0/24^24-29, 192.107.113.0/24^24-29, 192.133.31.0/24^24-29, 192.173.24.0/24^24-29, 198.32.66.0/24^24-29, 199.212.93.0/24^24-29, 202.6.84.0/24^24-29, 202.12.70.0/24^24-29, 202.14.100.0/24^24-29, 202.20.6.0/24^24-29, 202.20.97.0/24^24-29, 202.21.130.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.155.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.37.57.0/24^24-29, 202.37.76.0/24^24-29, 202.37.85.0/24^24-29, 202.37.136.0/24^24-29, 202.37.163.0/24^24-29, 202.37.197.0/24^24-29, 202.37.232.0/24^24-29, 202.41.140.0/24^24-29, 202.46.190.0/24^24-29, 202.49.62.0/24^24-29, 202.49.89.0/24^24-29, 202.49.159.0/24^24-29, 202.49.249.0/24^24-29, 202.50.87.0/24^24-29, 203.97.5.0/24^24-29, 205.233.243.0/24^24-29, 210.54.140.0/24^24-29, 210.54.211.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: deon(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20061019 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 18 Oct '06

18 Oct '06

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:AS4770 descr: advertised to AS9560 by ICONZ - AS4770 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 210.48.0.0/17^17-29, 210.185.0.0/18^18-29, 210.54.160.0/19^19-29, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.55.96.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, 210.56.32.0/20^20-29, 192.173.16.0/21^21-29, 202.12.248.0/21^21-29, 202.37.144.0/21^21-29, 202.37.224.0/21^21-29, 202.46.176.0/21^21-29, 202.50.200.0/21^21-29, 202.74.224.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 203.190.208.0/21^21-29, 205.233.128.0/21^21-29, 202.36.36.0/22^22-29, 202.37.140.0/22^22-29, 202.37.200.0/22^22-29, 202.41.136.0/22^22-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 210.54.136.0/22^22-29, 210.55.24.0/22^22-29, 202.21.136.0/23^23-29, 202.36.44.0/23^23-29, 202.36.76.0/23^23-29, 202.37.86.0/23^23-29, 202.37.240.0/23^23-29, 202.37.252.0/23^23-29, 202.49.80.0/23^23-29, 202.50.246.0/23^23-29, 202.124.106.0/23^23-29, 205.233.136.0/23^23-29, 210.55.182.0/23^23-29, 192.88.85.0/24^24-29, 192.107.113.0/24^24-29, 192.133.31.0/24^24-29, 192.173.24.0/24^24-29, 198.32.66.0/24^24-29, 199.212.93.0/24^24-29, 202.6.84.0/24^24-29, 202.12.70.0/24^24-29, 202.14.100.0/24^24-29, 202.20.6.0/24^24-29, 202.20.97.0/24^24-29, 202.21.130.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.155.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.37.76.0/24^24-29, 202.37.85.0/24^24-29, 202.37.136.0/24^24-29, 202.37.163.0/24^24-29, 202.37.197.0/24^24-29, 202.37.232.0/24^24-29, 202.41.140.0/24^24-29, 202.46.190.0/24^24-29, 202.49.62.0/24^24-29, 202.49.89.0/24^24-29, 202.49.159.0/24^24-29, 202.49.249.0/24^24-29, 202.50.87.0/24^24-29, 203.97.5.0/24^24-29, 205.233.243.0/24^24-29, 210.54.140.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: deon(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060911 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS4770 descr: advertised to AS9560 by ICONZ - AS4770 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 210.48.0.0/17^17-29, 210.185.0.0/18^18-29, 210.54.160.0/19^19-29, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.55.96.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, 210.56.32.0/20^20-29, 192.173.16.0/21^21-29, 202.12.248.0/21^21-29, 202.37.144.0/21^21-29, 202.37.224.0/21^21-29, 202.46.176.0/21^21-29, 202.50.200.0/21^21-29, 202.74.224.0/21^21-29, 202.78.240.0/21^21-29, 202.126.80.0/21^21-29, 203.190.208.0/21^21-29, 205.233.128.0/21^21-29, 202.36.36.0/22^22-29, 202.37.140.0/22^22-29, 202.37.200.0/22^22-29, 202.41.136.0/22^22-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 210.54.136.0/22^22-29, 210.55.24.0/22^22-29, 202.21.136.0/23^23-29, 202.36.44.0/23^23-29, 202.36.76.0/23^23-29, 202.37.86.0/23^23-29, 202.37.240.0/23^23-29, 202.37.252.0/23^23-29, 202.49.80.0/23^23-29, 202.50.246.0/23^23-29, 202.124.106.0/23^23-29, 205.233.136.0/23^23-29, 210.55.182.0/23^23-29, 192.88.85.0/24^24-29, 192.107.113.0/24^24-29, 192.133.31.0/24^24-29, 192.173.24.0/24^24-29, 198.32.66.0/24^24-29, 199.212.93.0/24^24-29, 202.6.84.0/24^24-29, 202.12.70.0/24^24-29, 202.14.100.0/24^24-29, 202.20.6.0/24^24-29, 202.20.97.0/24^24-29, 202.21.130.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.155.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.37.57.0/24^24-29, 202.37.76.0/24^24-29, 202.37.85.0/24^24-29, 202.37.136.0/24^24-29, 202.37.163.0/24^24-29, 202.37.197.0/24^24-29, 202.37.232.0/24^24-29, 202.41.140.0/24^24-29, 202.46.190.0/24^24-29, 202.49.62.0/24^24-29, 202.49.89.0/24^24-29, 202.49.159.0/24^24-29, 202.49.249.0/24^24-29, 202.50.87.0/24^24-29, 203.97.5.0/24^24-29, 205.233.243.0/24^24-29, 210.54.140.0/24^24-29, 210.54.211.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: deon(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20061019 source: NZRR

1 0

New IPv6 block allocated to RIPE NCC
by leo vegoda 17 Oct '06

17 Oct '06

[Apologies for duplicate mails] Dear Colleagues, The RIPE NCC received the IPv6 address range 2a00::/12 from the IANA in October 2006. This allocation expands two previous allocations. We will begin allocating from this new space in the near future. The minimum allocation size for this /12 has been set at /32. You may wish to adjust any filters you have in place accordingly. More information on the IP space administered by the RIPE NCC can be found on our web site at: https://www.ripe.net/ripe/docs/ripe-ncc-managed-address-space.html Regards, -- leo vegoda Registration Services Manager RIPE NCC

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 17 Oct '06

17 Oct '06

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:AS24324 descr: advertised to AS9560 by BCL - AS24324 members: 124.157.64.0/19^19-29, 202.49.128.0/21^21-29, 218.185.24.0/21^21-29, 202.27.83.0/24^24-29, 202.36.75.0/24^24-29, 202.36.154.0/24^24-29, 202.37.168.0/24^24-29, 202.49.183.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: leon.chang(a)bclnz.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060911 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS24324 descr: advertised to AS9560 by - AS24324 members: 124.157.64.0/19^19-29, 202.49.128.0/21^21-29, 218.185.224.0/21^21-29, 202.27.83.0/24^24-29, 202.36.75.0/24^24-29, 202.36.154.0/24^24-29, 202.37.168.0/24^24-29, 202.49.183.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: smc(a)bclnz.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20061018 source: NZRR

1 0

Trogan site and spam run using nuclear tests of North Korea as a hook (AUSCERT#2006ba825)
by matthew＠auscert.org.au 16 Oct '06

16 Oct '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Greetings, Not sure if anyone else has seen this but here it is again if so. First seen discussed per SANS http://isc.sans.org/diary.php?date=2006-10-14 * h t t p://cnnwarnews(dot)com/ uses an iframe to go to * h t t p://www.theaustralian.news.com.au/index/0,,5002460,00.html which is a legit Australian news site but also uses another iframe to open * h t t p://zagevqsoii(dot)biz/dl/adv433_.php and this opens: * h t t p://zagevqsoii(dot)biz/dl/loadadv433.exe If you google for usage of the domain you can see that it has been seeding web forums with supposed "news" stories about North Korea that entice victims to get infected as above: * h t t p://www.google.com/search?q=www(dot)cnnwarnews(dot)com * h t t p://www.google.com/search?q=au(dot)cnnwarnews(dot)com eg: h t t p://sv.wikipedia.org/wiki/The_Forum h t t p://www.kaigai-wedding.com/cgi-bin/wforum3/wforum.cgi?mode=new_sort h t t p://www.depdiknas.go.id/RPP/modules.php?name=Forums&file=posting&mode=topicreview&t=1331 The articles being seeded or spammed around usually look like this: Subject: North Korea vs Australia - nuclear stress Prime minister of Australia John Govard claimed that "..nuclear tests of North Korea was confirmed by seismological data", Associated Press. In connection with increase of probability of nuclear attack from the direction of North Korea Minister of Defence of Australia along with Ministers of Defence of China, South Korea and Russia signed a memorandum on infliction? h t t p://au(dot)cnnwarnews(dot)com/topnews/ The infection process is/was the same as above. Still accessible to the spammed material via: wget --header="Host: au(dot)cnnwarnews(dot)com" h t t p://203.116.50.253/topnews/ The original infector file, loadadv433.exe, is detected as Harnig which grabs: * h t t p://zbobivgcso(dot)biz/dl/loadadv455.exe And this then grabs: * h t t p://zagevqsoii(dot)biz/progs_exe/tdynqspzoa/ffkzyu * h t t p://zagevqsoii(dot)biz/progs_exe/tdynqspzoa/oswzvfcm * h t t p://zagevqsoii(dot)biz/progs_exe/tdynqspzoa/tkshrolhx.php * h t t p://zagevqsoii(dot)biz/progs_exe/tdynqspzoa/plgrx.php * h t t p://zagevqsoii(dot)biz/progs_exe/tdynqspzoa/rsamiscm * h t t p://zagevqsoii(dot)biz/progs_exe/tdynqspzoa/djrhd.php * h t t p://zagevqsoii(dot)biz/progs_exe/tdynqspzoa/gwrkgq.php * h t t p://zagevqsoii(dot)biz/progs_exe/tdynqspzoa/mhghnoxhnv.php * h t t p://zagevqsoii(dot)biz/progs_exe/tdynqspzoa/wipfrokuw.php * h t t p://zagevqsoii(dot)biz/progs_exe/tdynqspzoa/idlgmwf.php We have submitted all of these binaries to AV and sent shutdown requests for the four key domains above. We haven't seen much discussion of this but maybe the spam run hasn't really taken off yet. The subject of the upcoming spam run will probably look like "North Korea vs Australia - nuclear stress" and have the same text at the forum spams above. Credit to F-Secure for some of their analysis on this. Hope this is of some use. 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.5 (FreeBSD) Comment: http://www.auscert.org.au/render.html?it=1967 Comment: http://www.auscert.org.au/render.html?it=1967 iQCVAwUBRTSTYCh9+71yA2DNAQIZDwP/SZQYu/hzHAutGUa+6pkQqCRAczlMoqYw rjiCm71mfX++HCEup7IXo9NzW4rTPhCxNfM5q+qhukUZlWLd4QFah2eRk+fFtopT Sf1POAOuWM0knjwBRWPG156bA4jytLIu+UU+M9P8hoFt4MovvQYqPljOsIpSBADe eAgPsGrny8k= =guYP -----END PGP SIGNATURE-----

1 0

Re: [nznog] NZNOG 07 - Call for Participation and Papers
by Simon Lyall 15 Oct '06

15 Oct '06

A reminder that submissions for NZNOG 07 close in 4 days on Friday the 20th. Please contact talks(a)nznog.org if you are interested in holding a SIG or presenting at the main conference. On Tue, 5 Sep 2006, Simon Lyall wrote: > > NZNOG 07 - Call for Participation and Papers > > The next conference of the New Zealand Network Operators' Group is to be held > in Palmerston North, New Zealand between 31 January and 2 February 2007. Our > host is Inspire.net and the venue is to be at Massey University's campus. > > 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 2007 will consist of one day Special Interest Group ( SIG ) Meetings > 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: 5 September 2006 > Deadline for speaker submissions: 20 October 2006 > Responses to speaker submissions: 27 October 2006 > Draft program published: 1 November 2006 > Final program published: 18 December 2006 > NZNOG 2007 Conference: 31 January - 2 February 2007 > > SIG Meetings > ------------ > > The first day of the conference is arranged as parallel tracks to > cover subject material which is of interest to particular groups of > attendees. Proposals are requested for workshops, tutorials and other > appropriate special-interest meetings of interest to Network Operators. > > Topics which have been successful in the past, or have been requested > for this year are: > > * Advanced BGP gubbins > * IPV6 implementation > * Service Provider wireless networking > * VoIP > * BIND and DNSSEC > * MPLS and high performance IP backbone routing > * Systems Administration. > > The program committee will consider proposals for tutorials in any of these > or new areas. There is a single day of SIGs with up to five running > concurrently. > > If you have an idea for a tutorial subject that is not listed, please feel > free to submit it to us. > > > Conference Presentations > ------------------------ > > The main conference program for 2007 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 > > If you are interested in submitting a talk please fill out the questions > at then end of this document and email them to talks(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 22 January 2007. > > Note: While the majority of speaking slots will be submitted by 20 October > 2006, 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'07 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 > > * www.nznog.org > > General Enquiries > > * info(a)nznog.org > > Talks and Papers > > * talks(a)nznog.org > > > Talk Proposals > -------------- > > Please send all talk proposals (including lightning talks) to talks(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: > > > > -- Simon J. Lyall | Very Busy | Web: http://www.darkmere.gen.nz/ "To stay awake all night adds a day to your life" - Stilgar | eMT.

1 0

Radio New Zealand Podcasts
by Richard Hulse 15 Oct '06

15 Oct '06

Operators may wish to know that as from today all our podcasts have been increased from 48 to 64 kbs. This is in repsonse to requests from consumers for an improvement in audio quality. Given the current number of downloads being requested, some operators may notice an increase in traffic. regards, Richard Hulse

1 0

NZNOG '06 videos
by Jeremy Naylor 11 Oct '06

11 Oct '06

Hey guys, Just a quick note to let you know that the videos for the talks at NZNOG '06 are now available. Sorry for the delay with them. They're at: http://www.r2.co.nz/20060323 Thanks, -- Jeremy Naylor p: +64 4 978 7371 p: +64 21 374 689 e: jeremy.naylor(a)r2.co.nz w: http://www.r2.co.nz/~jeremy w: http://e-living.wellington.net.nz -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.408 / Virus Database: 268.13.2/472 - Release Date: 11/10/2006

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 10 Oct '06

10 Oct '06

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:AS9889 descr: advertised to AS9439 by Maxnet - AS9889 members: 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 192.138.251.0/24^24-29, 202.6.5.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.181.0/24^24-29, 202.49.141.0/24^24-29, 202.150.102.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: david.fox(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051125 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS9889 descr: advertised to AS9439 by Maxnet - 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, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 192.138.251.0/24^24-29, 202.6.5.0/24^24-29, 202.6.116.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.181.0/24^24-29, 202.49.141.0/24^24-29, 202.150.102.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: simon.allard(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20061011 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 10 Oct '06

10 Oct '06

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:AS9889 descr: advertised to AS9560 by Maximum Internet Ltd - AS9889 members: 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 202.55.96.0/20^20-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 192.138.251.0/24^24-29, 202.6.5.0/24^24-29, 202.6.116.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.181.0/24^24-29, 202.49.141.0/24^24-29, 202.150.102.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 notify: simon.allard(a)staff.maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060915 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9889 descr: advertised to AS9560 by Maxnet - 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, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 192.138.251.0/24^24-29, 202.6.5.0/24^24-29, 202.6.116.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.181.0/24^24-29, 202.49.141.0/24^24-29, 202.150.102.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: simon.allard(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20061011 source: NZRR

1 0