Heya,
While drinking beer and playing with the routing table, i notice that mail
destined for Xtra:
xtra.co.nz. 799 IN MX 20 mx2.tnz.mail.yahoo.com.
xtra.co.nz. 799 IN MX 10 mx1.tnz.mail.yahoo.com.
Now goes via Vocus, a new operator selling international bandwidth in NZ:
root(a)accounting:/home/icepick# traceroute mx1.tnz.mail.yahoo.com
traceroute to mx1.tnz.mail.yahoo.com (124.108.96.67), 64 hops max, 40 byte
packets
1 FIREWALL (60.234.66.130) 0.433 ms 0.630 ms 0.389 ms
2 * * *
3 * * *
4 vocus.ape.net.nz (192.203.154.123) 2.029 ms 1.840 ms 3.055 ms
5 ip-42.192.31.114.vocusconnect.net.au (114.31.192.42) 25.294 ms 25.707
ms 26.766 ms
6 as17457-1.bdr02.syd01.nsw.vocusconnect.net.au (114.31.200.38) 26.161
ms 26.152 ms 26.022 ms
7 gi1-2.bas2.aue.yahoo.com (203.84.216.202) 26.164 ms
gi1-1.bas1.aue.yahoo.com (203.84.216.198) 26.283 ms 26.306 ms
I find it great that xtra bound MX traffic is now "Local" again as it
transits APE, but I find it funny that it's another operator supplying the
bandwidth rather than telecom.
I know this may not be news to everyone yet, and yes, it's not the first
time I've mentioned (1) vocus in the last week, but from what I can tell
they seem to be doing a good job for the NZ internet so far.
(1) I'm in no way affiliated to vocus.
Cheers
Barry
P.S. my views are mine only and not those of my employer, * insert rest of
disclaimer here *...
Is there anyone from xtra/yahoo who reads this list? I've run out of things that I can do to get your servers to accept my mail. This is what I get, and trying to follow up using the case number supplied just leads to another copy of the FAQ automatically sending to me. It's *always* mx2.tnz.mail.yahoo.com that does this to me, mx1 seems quite happy.
Dec 20 16:10:06 server sendmail[15781]: mBK3A4JE015618: to=<recipient(a)xtra.co.nz>, ctladdr=<steve(a)greengecko.co.nz> (1018/1018), delay=00:00:02, xdelay=00:00:01, mailer=esmtp, pri=128042, relay=mx2.tnz.mail.yahoo.com. [124.108.96.67], dsn=4.0.0, stat=Deferred: 421 Message from (210.5.53.81) temporarily deferred - 4.16.50. Please refer to http://help.yahoo.com/help/us/mail/defer/defer-06.html
All the recommendations - PTR, SPF, DKIM, no html, etc have been followed. I'm starting to believe that it's this server that is plain misconfigured.
Steve
--
Steve Holdoway <steve(a)greengecko.co.nz>
If you've registered for NZNOG 2009 (http://2009.nznog.org/register)
you will have seen that we are holding another network administrators
miniconf on the Wednesday tutorial day. We'd like to try a different
format this year and have a few BoF-style sessions on various ISP
systems/network management topics, each with a brief introductory talk
followed by an extended discussion period (10-30 minutes depending on
interest in the topic).
We would like suggestions for topics of interest to anyone planning
on coming to the miniconf. We would also welcome any offers to speak for
a few minutes (5-15 minutes) on a topic as a lead into discussion.
This is your opportunity to find out what your peers at other ISPs have
found does or does not work.
Some topics that have been mentioned in informal discussion, or happened
in previous years:
- system configuration automation (puppet, bcfg, cfengine, etc)
- system/network monitoring (nagios, etc, especially scalability)
- mail systems/spam filtering/webmail
But there are plenty of other possible topics so let us know what is
relevant to you at present.
Please send topic suggestions and offers to talk to:
<talks09(a)nznog.miniconf.org>
Simon Lyall and Ewen McNeill
Network Administrators Miniconf
Hi all. There are two conferences coming up early next year that have
a track on DNSSEC. Both NZNOG and APRICOT are looking to find people
who have experience and would be happy to share their thoughts.
My feeling is that actual use in .nz is small however I'd love to hear
from you if there's something you've done with DNSSEC. Ideally we'd
like people who are willing to talk in Manilla or Auckland but even
just a few shared thoughts are appreciated.
http://2009.nznog.org/http://apricot2009.net/
BTW, registrations are open for both. Register now! :)
Sam.
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: AS9281:RS-ROUTES:AS9503
descr: advertised to AS9281 by FX Networks - AS9503
members: 131.203.0.0/16^16-29,
161.29.0.0/16^16-29,
161.65.0.0/16^16-29,
166.65.0.0/16^16-29,
119.15.0.0/19^19-29,
202.14.32.0/19^19-29,
202.53.176.0/20^20-29,
202.160.48.0/20^20-29,
202.191.32.0/20^20-29,
210.48.160.0/20^20-29,
120.89.80.0/21^21-29,
192.173.16.0/21^21-29,
202.46.176.0/21^21-29,
202.49.0.0/21^21-29,
202.78.240.0/21^21-29,
202.160.112.0/21^21-29,
203.190.208.0/21^21-29,
113.197.64.0/22^22-29,
202.37.48.0/22^22-29,
202.89.4.0/22^22-29,
203.84.134.0/23^23-29,
124.248.128.0/24^24-29,
124.248.132.0/24^24-29,
124.248.136.0/24^24-29,
124.248.140.0/24^24-29,
192.88.85.0/24^24-29,
192.122.171.0/24^24-29,
192.133.31.0/24^24-29,
192.195.219.0/24^24-29,
202.12.91.0/24^24-29,
202.20.97.0/24^24-29,
202.27.83.0/24^24-29,
202.36.33.0/24^24-29,
202.36.75.0/24^24-29,
202.36.119.0/24^24-29,
202.36.154.0/24^24-29,
202.36.162.0/24^24-29,
202.36.218.0/24^24-29,
202.37.93.0/24^24-29,
202.37.168.0/24^24-29,
202.37.205.0/24^24-29,
202.46.188.0/24^24-29,
202.46.190.0/24^24-29,
202.49.106.0/24^24-29,
202.50.247.0/24^24-29,
202.55.99.0/24^24-29,
202.55.105.0/24^24-29,
202.55.107.0/24^24-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: peering(a)fx.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20081212
source: NZRR
REPLACED BY:
route-set: AS9281:RS-ROUTES:AS9503
descr: advertised to AS9281 by FX Networks - AS9503
members: 131.203.0.0/16^16-29,
161.29.0.0/16^16-29,
161.65.0.0/16^16-29,
166.65.0.0/16^16-29,
119.15.0.0/19^19-29,
202.14.32.0/19^19-29,
202.53.176.0/20^20-29,
202.86.96.0/20^20-29,
202.160.48.0/20^20-29,
202.191.32.0/20^20-29,
210.48.160.0/20^20-29,
120.89.80.0/21^21-29,
192.173.16.0/21^21-29,
202.46.176.0/21^21-29,
202.49.0.0/21^21-29,
202.78.240.0/21^21-29,
202.160.112.0/21^21-29,
203.190.208.0/21^21-29,
113.197.64.0/22^22-29,
202.37.48.0/22^22-29,
202.89.4.0/22^22-29,
203.84.134.0/23^23-29,
124.248.128.0/24^24-29,
124.248.132.0/24^24-29,
124.248.136.0/24^24-29,
124.248.140.0/24^24-29,
192.88.85.0/24^24-29,
192.122.171.0/24^24-29,
192.133.31.0/24^24-29,
192.195.219.0/24^24-29,
202.8.13.0/24^24-29,
202.12.0.0/24^24-29,
202.12.91.0/24^24-29,
202.20.97.0/24^24-29,
202.27.83.0/24^24-29,
202.36.33.0/24^24-29,
202.36.75.0/24^24-29,
202.36.119.0/24^24-29,
202.36.154.0/24^24-29,
202.36.162.0/24^24-29,
202.36.218.0/24^24-29,
202.37.93.0/24^24-29,
202.37.168.0/24^24-29,
202.37.205.0/24^24-29,
202.46.188.0/24^24-29,
202.46.190.0/24^24-29,
202.49.106.0/24^24-29,
202.50.247.0/24^24-29,
202.55.99.0/24^24-29,
202.55.105.0/24^24-29,
202.55.107.0/24^24-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: peering(a)fx.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20081219
source: NZRR
------------------------------------------------------------
Dear Colleague,
This is to notify you that one or more objects in which you are
designated for notification have been modified in the NZRR routing
registry database.
These objects are used to configure the various NZIX route servers
(http://nzix.net/) so you can expect the relevant servers to be reloaded
in the near future. The reloading of the servers is staggered over a
period of time so that if you are peering with both servers at an
exchange, you can maintain at least one BGP session at all times and
consequently a full set of routes.
Diagnostic output:
------------------------------------------------------------
---
PREVIOUS OBJECT:
route-set: AS9439:RS-ROUTES:AS9503
descr: advertised to AS9439 by FX Networks - AS9503
members: 131.203.0.0/16^16-29,
161.29.0.0/16^16-29,
161.65.0.0/16^16-29,
166.65.0.0/16^16-29,
119.15.0.0/19^19-29,
202.14.32.0/19^19-29,
202.53.176.0/20^20-29,
202.160.48.0/20^20-29,
202.191.32.0/20^20-29,
210.48.160.0/20^20-29,
120.89.80.0/21^21-29,
192.173.16.0/21^21-29,
202.46.176.0/21^21-29,
202.49.0.0/21^21-29,
202.78.240.0/21^21-29,
202.160.112.0/21^21-29,
203.190.208.0/21^21-29,
113.197.64.0/22^22-29,
202.37.48.0/22^22-29,
202.89.4.0/22^22-29,
203.84.134.0/23^23-29,
124.248.128.0/24^24-29,
124.248.132.0/24^24-29,
124.248.136.0/24^24-29,
124.248.140.0/24^24-29,
192.88.85.0/24^24-29,
192.122.171.0/24^24-29,
192.133.31.0/24^24-29,
192.195.219.0/24^24-29,
202.12.91.0/24^24-29,
202.20.97.0/24^24-29,
202.27.83.0/24^24-29,
202.36.33.0/24^24-29,
202.36.75.0/24^24-29,
202.36.119.0/24^24-29,
202.36.154.0/24^24-29,
202.36.162.0/24^24-29,
202.36.218.0/24^24-29,
202.37.93.0/24^24-29,
202.37.168.0/24^24-29,
202.37.205.0/24^24-29,
202.46.188.0/24^24-29,
202.46.190.0/24^24-29,
202.49.106.0/24^24-29,
202.50.247.0/24^24-29,
202.55.99.0/24^24-29,
202.55.105.0/24^24-29,
202.55.107.0/24^24-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: peering(a)fx.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20081212
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,
119.15.0.0/19^19-29,
202.14.32.0/19^19-29,
202.53.176.0/20^20-29,
202.86.96.0/20^20-29,
202.160.48.0/20^20-29,
202.191.32.0/20^20-29,
210.48.160.0/20^20-29,
120.89.80.0/21^21-29,
192.173.16.0/21^21-29,
202.46.176.0/21^21-29,
202.49.0.0/21^21-29,
202.78.240.0/21^21-29,
202.160.112.0/21^21-29,
203.190.208.0/21^21-29,
113.197.64.0/22^22-29,
202.37.48.0/22^22-29,
202.89.4.0/22^22-29,
203.84.134.0/23^23-29,
124.248.128.0/24^24-29,
124.248.132.0/24^24-29,
124.248.136.0/24^24-29,
124.248.140.0/24^24-29,
192.88.85.0/24^24-29,
192.122.171.0/24^24-29,
192.133.31.0/24^24-29,
192.195.219.0/24^24-29,
202.8.13.0/24^24-29,
202.12.0.0/24^24-29,
202.12.91.0/24^24-29,
202.20.97.0/24^24-29,
202.27.83.0/24^24-29,
202.36.33.0/24^24-29,
202.36.75.0/24^24-29,
202.36.119.0/24^24-29,
202.36.154.0/24^24-29,
202.36.162.0/24^24-29,
202.36.218.0/24^24-29,
202.37.93.0/24^24-29,
202.37.168.0/24^24-29,
202.37.205.0/24^24-29,
202.46.188.0/24^24-29,
202.46.190.0/24^24-29,
202.49.106.0/24^24-29,
202.50.247.0/24^24-29,
202.55.99.0/24^24-29,
202.55.105.0/24^24-29,
202.55.107.0/24^24-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: peering(a)fx.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20081219
source: NZRR
------------------------------------------------------------
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:AS24006
descr: advertised to AS9439 by Knossos Networks Ltd - AS24006
members: 202.160.48.0/20^20-29,
161.29.254.0/23^23-29,
202.53.189.0/28^28-29,
161.29.126.128/29,
161.29.192.160/29,
161.29.193.80/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)knossos.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20081118
source: NZRR
REPLACED BY:
route-set: AS9439:RS-ROUTES:AS24006
descr: advertised to AS9439 by Knossos Networks Ltd - AS24006
members: 202.160.48.0/20^20-29,
161.29.192.160/29,
161.29.193.80/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)knossos.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20081219
source: NZRR
------------------------------------------------------------
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:AS17746
descr: advertised to AS9560 by Orcon Internet Limited - AS17746
members: 60.234.0.0/16^16-29,
121.98.0.0/16^16-29,
156.62.0.0/16^16-29,
202.150.96.0/19^19-29,
203.99.0.0/19^19-29,
203.96.192.0/20^20-29,
219.88.128.0/20^20-29,
219.88.240.0/20^20-29,
116.193.144.0/21^21-29,
116.199.208.0/21^21-29,
210.54.56.0/21^21-29,
210.79.48.0/21^21-29,
113.21.224.0/22^22-29,
202.127.8.0/22^22-29,
210.54.148.0/22^22-29,
210.55.12.0/22^22-29,
120.138.22.0/23^23-29,
202.37.82.0/23^23-29,
202.175.142.0/23^23-29,
192.203.216.0/24^24-29,
202.27.8.0/24^24-29,
202.27.77.0/24^24-29,
202.36.12.0/24^24-29,
202.36.170.0/24^24-29,
202.37.19.0/24^24-29,
202.37.173.0/24^24-29,
202.37.194.0/24^24-29,
202.46.189.0/24^24-29,
202.49.187.0/24^24-29,
202.49.233.0/24^24-29,
202.49.246.0/24^24-29,
202.50.167.0/24^24-29,
202.50.246.0/24^24-29,
202.174.160.0/24^24-29,
203.86.200.0/24^24-29,
210.54.12.0/24^24-29,
210.55.1.0/24^24-29,
210.55.8.0/24^24-29,
210.55.199.0/24^24-29,
202.27.188.128/25^25-29,
210.55.0.0/25^25-29,
210.55.180.128/26^26-29,
210.55.193.64/27^27-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: benny.treefoot(a)team.orcon.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20081204
source: NZRR
REPLACED BY:
route-set: AS9560:RS-ROUTES:AS17746
descr: advertised to AS9560 by Orcon Internet Limited - AS17746
members: 60.234.0.0/16^16-29,
121.98.0.0/16^16-29,
156.62.0.0/16^16-29,
202.150.96.0/19^19-29,
203.99.0.0/19^19-29,
203.96.192.0/20^20-29,
219.88.128.0/20^20-29,
219.88.240.0/20^20-29,
116.193.144.0/21^21-29,
116.199.208.0/21^21-29,
202.49.64.0/21^21-29,
210.54.56.0/21^21-29,
210.79.48.0/21^21-29,
113.21.224.0/22^22-29,
202.127.8.0/22^22-29,
210.54.148.0/22^22-29,
210.55.12.0/22^22-29,
120.138.22.0/23^23-29,
202.37.82.0/23^23-29,
202.175.142.0/23^23-29,
192.203.216.0/24^24-29,
202.27.8.0/24^24-29,
202.27.77.0/24^24-29,
202.36.12.0/24^24-29,
202.36.170.0/24^24-29,
202.36.174.0/24^24-29,
202.37.19.0/24^24-29,
202.37.173.0/24^24-29,
202.37.194.0/24^24-29,
202.46.189.0/24^24-29,
202.49.140.0/24^24-29,
202.49.187.0/24^24-29,
202.49.233.0/24^24-29,
202.49.246.0/24^24-29,
202.50.167.0/24^24-29,
202.50.246.0/24^24-29,
202.129.253.0/24^24-29,
202.174.160.0/24^24-29,
203.86.200.0/24^24-29,
210.54.12.0/24^24-29,
210.55.1.0/24^24-29,
210.55.8.0/24^24-29,
210.55.199.0/24^24-29,
202.27.188.128/25^25-29,
210.55.0.0/25^25-29,
210.55.180.128/26^26-29,
210.55.193.64/27^27-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: benny.treefoot(a)team.orcon.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20081219
source: NZRR
------------------------------------------------------------
Dear Colleague,
This is to notify you that one or more objects in which you are
designated for notification have been modified in the NZRR routing
registry database.
These objects are used to configure the various NZIX route servers
(http://nzix.net/) so you can expect the relevant servers to be reloaded
in the near future. The reloading of the servers is staggered over a
period of time so that if you are peering with both servers at an
exchange, you can maintain at least one BGP session at all times and
consequently a full set of routes.
Diagnostic output:
------------------------------------------------------------
---
PREVIOUS OBJECT:
route-set: AS9560:RS-ROUTES:AS9503
descr: advertised to AS9560 by FX Networks - AS9503
members: 131.203.0.0/16^16-29,
161.29.0.0/16^16-29,
161.65.0.0/16^16-29,
166.65.0.0/16^16-29,
119.15.0.0/19^19-29,
202.14.32.0/19^19-29,
202.53.176.0/20^20-29,
202.160.48.0/20^20-29,
202.191.32.0/20^20-29,
210.48.160.0/20^20-29,
120.89.80.0/21^21-29,
192.173.16.0/21^21-29,
202.46.176.0/21^21-29,
202.49.0.0/21^21-29,
202.78.240.0/21^21-29,
202.160.112.0/21^21-29,
203.190.208.0/21^21-29,
113.197.64.0/22^22-29,
202.37.48.0/22^22-29,
202.89.4.0/22^22-29,
203.84.134.0/23^23-29,
124.248.128.0/24^24-29,
124.248.132.0/24^24-29,
124.248.136.0/24^24-29,
124.248.140.0/24^24-29,
192.88.85.0/24^24-29,
192.122.171.0/24^24-29,
192.133.31.0/24^24-29,
192.195.219.0/24^24-29,
202.12.91.0/24^24-29,
202.20.97.0/24^24-29,
202.27.83.0/24^24-29,
202.36.33.0/24^24-29,
202.36.75.0/24^24-29,
202.36.119.0/24^24-29,
202.36.154.0/24^24-29,
202.36.162.0/24^24-29,
202.36.218.0/24^24-29,
202.37.93.0/24^24-29,
202.37.168.0/24^24-29,
202.37.205.0/24^24-29,
202.46.188.0/24^24-29,
202.46.190.0/24^24-29,
202.49.106.0/24^24-29,
202.50.247.0/24^24-29,
202.55.99.0/24^24-29,
202.55.105.0/24^24-29,
202.55.107.0/24^24-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: peering(a)fx.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20081212
source: NZRR
REPLACED BY:
route-set: AS9560:RS-ROUTES:AS9503
descr: advertised to AS9560 by FX Networks - AS9503
members: 131.203.0.0/16^16-29,
161.29.0.0/16^16-29,
161.65.0.0/16^16-29,
166.65.0.0/16^16-29,
119.15.0.0/19^19-29,
202.14.32.0/19^19-29,
202.53.176.0/20^20-29,
202.86.96.0/20^20-29,
202.160.48.0/20^20-29,
202.191.32.0/20^20-29,
210.48.160.0/20^20-29,
120.89.80.0/21^21-29,
192.173.16.0/21^21-29,
202.46.176.0/21^21-29,
202.49.0.0/21^21-29,
202.78.240.0/21^21-29,
202.160.112.0/21^21-29,
203.190.208.0/21^21-29,
113.197.64.0/22^22-29,
202.37.48.0/22^22-29,
202.89.4.0/22^22-29,
203.84.134.0/23^23-29,
124.248.128.0/24^24-29,
124.248.132.0/24^24-29,
124.248.136.0/24^24-29,
124.248.140.0/24^24-29,
192.88.85.0/24^24-29,
192.122.171.0/24^24-29,
192.133.31.0/24^24-29,
192.195.219.0/24^24-29,
202.8.13.0/24^24-29,
202.12.0.0/24^24-29,
202.12.91.0/24^24-29,
202.20.97.0/24^24-29,
202.27.83.0/24^24-29,
202.36.33.0/24^24-29,
202.36.75.0/24^24-29,
202.36.119.0/24^24-29,
202.36.154.0/24^24-29,
202.36.162.0/24^24-29,
202.36.218.0/24^24-29,
202.37.93.0/24^24-29,
202.37.168.0/24^24-29,
202.37.205.0/24^24-29,
202.46.188.0/24^24-29,
202.46.190.0/24^24-29,
202.49.106.0/24^24-29,
202.50.247.0/24^24-29,
202.55.99.0/24^24-29,
202.55.105.0/24^24-29,
202.55.107.0/24^24-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: peering(a)fx.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20081219
source: NZRR
------------------------------------------------------------
A workshop at held at InternetNZ on the 28 November in Wellington
saw the formation of a New Zealand IPv6 Steering Group. This group includes
representatives from telecommunications carriers, internet service
providers, ICT
vendors, and industry and user associations. The members of this
steering group
consist of invited senior representatives from the following organisations:
InternetNZ
TUANZ
ISPANZ
Telecommunications Carriers Forum
Digital Development Forum
Telecom
TelstraClear
WorldXChange
Orcon
FX Networks
REANNZ
Canterbury Development Corporation
Kordia
Cisco
Vodafone
Juniper Networks
Alcatel Lucent
Braintrust
This steering group will primarily be concerned with high level discussion
regarding the deployment of IPv6 within New Zealand. The steering group
will not necessarily be a place where technical discussion takes place.
As with so many things these days, a combination of business and
technical expertise must be bought together to solve a given problem.
To this end at the same workshop a Technical Special Interest Group
(TechSIG) was also established.
The goals of this group are:
. To act as a central point for IPv6 technical discussion within the
New Zealand Internet community.
. To identify to the IPv6 Steering Group any business related barriers
to IPv6 deployment which have been identified by the SIG's
technical contributors.
. To comment and provide potential solutions to technical related barriers
identified by members of the IPv6 Steering Group.
. To stimulate the production of relevant technical documentation.
The co-conveners of this group are
Andy Linton
Nathan Ward
Brian Carpenter
Dean Pemberton
A mailing list has been created and membership is open to all interested
parties. Subscription details can be found at the link below;
http://listserver.internetnz.net.nz/mailman/listinfo/ipv6-techsig
I would encourage anyone who has an interest in the deployment and growth
of IPv6 to join and contribute to the list.
Please do not feel that this is a 'Networking Specialist Only' list. The
deployment of IPv6 (and depletion of IPv4) has just as significant an
impact on system administrators and content/application providers as it
does on
network administrators. I welcome all technical viewpoints onto the
list.
Thank you for your time.
Dean Pemberton
(Co-convener, IPv6 Steering Group Technical SIG)
