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:AS23655
descr: advertised to AS9560 by SNAP Internet Ltd - AS23655
members: 130.195.0.0/16^16-29,
132.181.0.0/16^16-29,
138.75.0.0/16^16-29,
153.111.0.0/16^16-29,
165.84.0.0/16^16-29,
123.255.0.0/18^18-29,
202.124.96.0/19^19-29,
202.49.16.0/20^20-29,
203.86.192.0/20^20-29,
202.174.112.0/21^21-29,
210.5.48.0/21^21-29,
113.130.120.0/22^22-29,
202.49.72.0/22^22-29,
202.49.92.0/22^22-29,
202.50.104.0/22^22-29,
202.50.124.0/22^22-29,
202.164.28.0/22^22-29,
203.99.132.0/22^22-29,
202.27.186.0/23^23-29,
202.36.178.0/23^23-29,
202.36.220.0/23^23-29,
202.37.96.0/23^23-29,
202.37.100.0/23^23-29,
202.37.124.0/23^23-29,
202.49.90.0/23^23-29,
202.49.120.0/23^23-29,
203.147.108.0/23^23-29,
210.55.30.0/23^23-29,
210.55.206.0/23^23-29,
192.148.221.0/24^24-29,
192.156.225.0/24^24-29,
202.36.163.0/24^24-29,
202.36.170.0/24^24-29,
202.36.219.0/24^24-29,
202.37.114.0/24^24-29,
202.46.187.0/24^24-29,
202.49.115.0/24^24-29,
202.49.125.0/24^24-29,
202.49.187.0/24^24-29,
202.50.117.0/24^24-29,
202.50.169.0/24^24-29,
202.146.186.0/24^24-29,
203.96.112.0/24^24-29,
210.7.40.0/24^24-29,
210.54.15.0/24^24-29,
210.55.4.0/24^24-29,
210.55.7.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(a)snap.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20090608
source: NZRR
REPLACED BY:
route-set: AS9560:RS-ROUTES:AS23655
descr: advertised to AS9560 by SNAP Internet Ltd - AS23655
members: 111.69.0.0/16^16-29,
130.195.0.0/16^16-29,
132.181.0.0/16^16-29,
138.75.0.0/16^16-29,
153.111.0.0/16^16-29,
165.84.0.0/16^16-29,
123.255.0.0/18^18-29,
202.124.96.0/19^19-29,
111.65.224.0/20^20-29,
202.49.16.0/20^20-29,
203.86.192.0/20^20-29,
202.174.112.0/21^21-29,
210.5.48.0/21^21-29,
110.92.16.0/22^22-29,
113.130.120.0/22^22-29,
202.49.72.0/22^22-29,
202.49.92.0/22^22-29,
202.50.104.0/22^22-29,
202.50.124.0/22^22-29,
202.164.28.0/22^22-29,
203.99.132.0/22^22-29,
202.27.186.0/23^23-29,
202.36.178.0/23^23-29,
202.36.220.0/23^23-29,
202.37.96.0/23^23-29,
202.37.100.0/23^23-29,
202.37.124.0/23^23-29,
202.49.90.0/23^23-29,
202.49.120.0/23^23-29,
203.147.108.0/23^23-29,
210.55.30.0/23^23-29,
210.55.206.0/23^23-29,
192.148.221.0/24^24-29,
192.156.225.0/24^24-29,
202.36.163.0/24^24-29,
202.36.170.0/24^24-29,
202.36.219.0/24^24-29,
202.37.114.0/24^24-29,
202.46.187.0/24^24-29,
202.49.115.0/24^24-29,
202.49.125.0/24^24-29,
202.49.187.0/24^24-29,
202.50.117.0/24^24-29,
202.50.169.0/24^24-29,
202.146.186.0/24^24-29,
203.96.112.0/24^24-29,
210.7.40.0/24^24-29,
210.54.15.0/24^24-29,
210.55.4.0/24^24-29,
210.55.7.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(a)snap.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20090616
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:AS23655
descr: advertised to AS9439 by SNAP Internet Ltd - AS23655
members: 130.195.0.0/16^16-29,
132.181.0.0/16^16-29,
138.75.0.0/16^16-29,
153.111.0.0/16^16-29,
165.84.0.0/16^16-29,
123.255.0.0/18^18-29,
202.124.96.0/19^19-29,
202.49.16.0/20^20-29,
203.86.192.0/20^20-29,
202.174.112.0/21^21-29,
210.5.48.0/21^21-29,
110.92.16.0/22^22-29,
113.130.120.0/22^22-29,
202.49.72.0/22^22-29,
202.49.92.0/22^22-29,
202.50.104.0/22^22-29,
202.50.124.0/22^22-29,
202.164.28.0/22^22-29,
203.99.132.0/22^22-29,
202.27.186.0/23^23-29,
202.36.178.0/23^23-29,
202.36.220.0/23^23-29,
202.37.96.0/23^23-29,
202.37.100.0/23^23-29,
202.37.124.0/23^23-29,
202.49.90.0/23^23-29,
202.49.120.0/23^23-29,
203.147.108.0/23^23-29,
210.55.30.0/23^23-29,
210.55.206.0/23^23-29,
192.148.221.0/24^24-29,
192.156.225.0/24^24-29,
202.36.163.0/24^24-29,
202.36.170.0/24^24-29,
202.36.219.0/24^24-29,
202.37.114.0/24^24-29,
202.46.187.0/24^24-29,
202.49.115.0/24^24-29,
202.49.125.0/24^24-29,
202.49.187.0/24^24-29,
202.50.117.0/24^24-29,
202.50.169.0/24^24-29,
202.146.186.0/24^24-29,
203.96.112.0/24^24-29,
210.7.40.0/24^24-29,
210.54.15.0/24^24-29,
210.55.4.0/24^24-29,
210.55.7.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(a)snap.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20090515
source: NZRR
REPLACED BY:
route-set: AS9439:RS-ROUTES:AS23655
descr: advertised to AS9439 by Snap Internet Limited - AS23655
members: 111.69.0.0/16^16-29,
130.195.0.0/16^16-29,
132.181.0.0/16^16-29,
138.75.0.0/16^16-29,
153.111.0.0/16^16-29,
165.84.0.0/16^16-29,
123.255.0.0/18^18-29,
202.124.96.0/19^19-29,
202.49.16.0/20^20-29,
203.86.192.0/20^20-29,
202.174.112.0/21^21-29,
210.5.48.0/21^21-29,
110.92.16.0/22^22-29,
113.130.120.0/22^22-29,
202.49.72.0/22^22-29,
202.49.92.0/22^22-29,
202.50.104.0/22^22-29,
202.50.124.0/22^22-29,
202.164.28.0/22^22-29,
203.99.132.0/22^22-29,
202.27.186.0/23^23-29,
202.36.178.0/23^23-29,
202.36.220.0/23^23-29,
202.37.96.0/23^23-29,
202.37.100.0/23^23-29,
202.37.124.0/23^23-29,
202.49.90.0/23^23-29,
202.49.120.0/23^23-29,
203.147.108.0/23^23-29,
210.55.30.0/23^23-29,
210.55.206.0/23^23-29,
192.148.221.0/24^24-29,
192.156.225.0/24^24-29,
202.36.163.0/24^24-29,
202.36.170.0/24^24-29,
202.36.219.0/24^24-29,
202.37.114.0/24^24-29,
202.46.187.0/24^24-29,
202.49.115.0/24^24-29,
202.49.125.0/24^24-29,
202.49.187.0/24^24-29,
202.50.117.0/24^24-29,
202.50.169.0/24^24-29,
202.146.186.0/24^24-29,
203.96.112.0/24^24-29,
210.7.40.0/24^24-29,
210.54.15.0/24^24-29,
210.55.4.0/24^24-29,
210.55.7.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(a)snap.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20090614
source: NZRR
------------------------------------------------------------
With resolution 2009-02-03-04, the ICANN Board asked the Root
Server System Advisory Committee (RSSAC), the Security and
Stability Advisory Committee (SSAC), and the ICANN staff to study
the potential impact on the root zone stability that might arise
when IPv6 address records, IDN top level names, other new TLDs,
and new records to support DNS security are added to the root zone.
The Board has expressed interest in hearing of the impact of the
distinct changes, but also their aggregate effect on root zone
operations. The Board also asks that the study address the
technical and operational concerns regarding expanding the DNS
root zone that have been expressed on this topic.
A study team has been assembled and is composed of the following:
Jaap Akkerhuis
Lyman Chapin - Chair
Patrik FC$ltstrC6m
Glenn Kowack
Lars-Johan Liman
Bill Manning
The goal of the study is to construct a complete, definitive, and
authoritative model of the root server system (including all of
its provisioning and query components) that shows how the
different parts are related, and how changing the value of a
variable in one part would affect each of the other parts. It will
be as quantitative a model as possible given the relatively short
time frame of the study. The idea is not to try to identify all of
the bad things that might happen if (for example) the number of
TLDs in the root zone were to increase by several orders of
magnitude during the same time period in which new RRs were added
for DNSSEC (b^@^\how many entries in the root zone is too many?b^@^]), but
to construct a model that demonstrates what the effects would be
throughout the system of changing the value of one or more
variables either individually or in combination (e.g., the rate at
which new TLDs are added to the root, or the frequency of key
rollover events in a signed root). This model will provide an
unbiased factual and analyticalb^@^Trather than anecdotalb^@^Tbasis for
recognizing and evaluating concerns about root server system
security and stability as the root grows. As a tool for policy
makers, it will show the expected impact on the root server system
of policy decisions that would change various root zone parameters.
The study team has a couple of methods for collecting inputs and
encourages interested parties to provide the study team with their
concerns.
There is a public mailing list: root-scaling(a)icann.org
and
There is a comment site:
+http://www.icann.org/en/public-comment/public-comment-200907.html#root-scaling
If there are others whom you think would be interested in this work or
have opinions/ideas, please pass along this note.
Thanks
Good afternoon
If anyone has any recommendations (or advice on who to steer clear of)
on internet and/or fibre providers over in Melbourne can you please
contact me off-list? We're in Tullamarine if that helps.
Cheers
Thom
--
Thom Hooker
Director of Operations
SMX Ltd http://smx.co.nz
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: AS24388:RS-ROUTES:AS23655
descr: advertised to AS24388 by SNAP Internet Ltd - AS23655
members: 130.195.0.0/16^16-29,
132.181.0.0/16^16-29,
138.75.0.0/16^16-29,
153.111.0.0/16^16-29,
165.84.0.0/16^16-29,
123.255.0.0/18^18-29,
202.124.96.0/19^19-29,
202.49.16.0/20^20-29,
203.86.192.0/20^20-29,
202.174.112.0/21^21-29,
210.5.48.0/21^21-29,
110.92.16.0/22^22-29,
113.130.120.0/22^22-29,
202.49.72.0/22^22-29,
202.49.92.0/22^22-29,
202.50.104.0/22^22-29,
202.50.124.0/22^22-29,
202.164.28.0/22^22-29,
203.99.132.0/22^22-29,
202.27.186.0/23^23-29,
202.36.178.0/23^23-29,
202.36.220.0/23^23-29,
202.37.96.0/23^23-29,
202.37.100.0/23^23-29,
202.37.124.0/23^23-29,
202.49.90.0/23^23-29,
202.49.120.0/23^23-29,
203.147.108.0/23^23-29,
210.55.30.0/23^23-29,
210.55.206.0/23^23-29,
192.148.221.0/24^24-29,
192.156.225.0/24^24-29,
202.36.163.0/24^24-29,
202.36.170.0/24^24-29,
202.36.219.0/24^24-29,
202.37.114.0/24^24-29,
202.46.187.0/24^24-29,
202.49.115.0/24^24-29,
202.49.125.0/24^24-29,
202.49.187.0/24^24-29,
202.50.117.0/24^24-29,
202.50.169.0/24^24-29,
202.146.186.0/24^24-29,
203.96.112.0/24^24-29,
210.7.40.0/24^24-29,
210.54.15.0/24^24-29,
210.55.4.0/24^24-29,
210.55.7.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(a)snap.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20090515
source: NZRR
REPLACED BY:
route-set: AS24388:RS-ROUTES:AS23655
descr: advertised to AS24388 by Snap Internet Limited - AS23655
members: 111.69.0.0/16^16-29,
130.195.0.0/16^16-29,
132.181.0.0/16^16-29,
138.75.0.0/16^16-29,
153.111.0.0/16^16-29,
165.84.0.0/16^16-29,
123.255.0.0/18^18-29,
202.124.96.0/19^19-29,
202.49.16.0/20^20-29,
203.86.192.0/20^20-29,
202.174.112.0/21^21-29,
210.5.48.0/21^21-29,
110.92.16.0/22^22-29,
113.130.120.0/22^22-29,
202.49.72.0/22^22-29,
202.49.92.0/22^22-29,
202.50.104.0/22^22-29,
202.50.124.0/22^22-29,
202.164.28.0/22^22-29,
203.99.132.0/22^22-29,
202.27.186.0/23^23-29,
202.36.178.0/23^23-29,
202.36.220.0/23^23-29,
202.37.96.0/23^23-29,
202.37.100.0/23^23-29,
202.37.124.0/23^23-29,
202.49.90.0/23^23-29,
202.49.120.0/23^23-29,
203.147.108.0/23^23-29,
210.55.30.0/23^23-29,
210.55.206.0/23^23-29,
192.148.221.0/24^24-29,
192.156.225.0/24^24-29,
202.36.163.0/24^24-29,
202.36.170.0/24^24-29,
202.36.219.0/24^24-29,
202.37.114.0/24^24-29,
202.46.187.0/24^24-29,
202.49.115.0/24^24-29,
202.49.125.0/24^24-29,
202.49.187.0/24^24-29,
202.50.117.0/24^24-29,
202.50.169.0/24^24-29,
202.146.186.0/24^24-29,
203.96.112.0/24^24-29,
210.7.40.0/24^24-29,
210.54.15.0/24^24-29,
210.55.4.0/24^24-29,
210.55.7.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(a)snap.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20090612
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:AS23655
descr: advertised to AS9560 by SNAP Internet Ltd - AS23655
members: 130.195.0.0/16^16-29,
132.181.0.0/16^16-29,
138.75.0.0/16^16-29,
153.111.0.0/16^16-29,
165.84.0.0/16^16-29,
123.255.0.0/18^18-29,
202.124.96.0/19^19-29,
202.49.16.0/20^20-29,
203.86.192.0/20^20-29,
202.174.112.0/21^21-29,
210.5.48.0/21^21-29,
110.92.16.0/22^22-29,
113.130.120.0/22^22-29,
202.49.72.0/22^22-29,
202.49.92.0/22^22-29,
202.50.104.0/22^22-29,
202.50.124.0/22^22-29,
202.164.28.0/22^22-29,
203.99.132.0/22^22-29,
202.27.186.0/23^23-29,
202.36.178.0/23^23-29,
202.36.220.0/23^23-29,
202.37.96.0/23^23-29,
202.37.100.0/23^23-29,
202.37.124.0/23^23-29,
202.49.90.0/23^23-29,
202.49.120.0/23^23-29,
203.147.108.0/23^23-29,
210.55.30.0/23^23-29,
210.55.206.0/23^23-29,
192.148.221.0/24^24-29,
192.156.225.0/24^24-29,
202.36.163.0/24^24-29,
202.36.170.0/24^24-29,
202.36.219.0/24^24-29,
202.37.114.0/24^24-29,
202.46.187.0/24^24-29,
202.49.115.0/24^24-29,
202.49.125.0/24^24-29,
202.49.187.0/24^24-29,
202.50.117.0/24^24-29,
202.50.169.0/24^24-29,
202.146.186.0/24^24-29,
203.96.112.0/24^24-29,
210.7.40.0/24^24-29,
210.54.15.0/24^24-29,
210.55.4.0/24^24-29,
210.55.7.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(a)snap.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20090515
source: NZRR
REPLACED BY:
route-set: AS9560:RS-ROUTES:AS23655
descr: advertised to AS9560 by SNAP Internet Ltd - AS23655
members: 130.195.0.0/16^16-29,
132.181.0.0/16^16-29,
138.75.0.0/16^16-29,
153.111.0.0/16^16-29,
165.84.0.0/16^16-29,
123.255.0.0/18^18-29,
202.124.96.0/19^19-29,
202.49.16.0/20^20-29,
203.86.192.0/20^20-29,
202.174.112.0/21^21-29,
210.5.48.0/21^21-29,
113.130.120.0/22^22-29,
202.49.72.0/22^22-29,
202.49.92.0/22^22-29,
202.50.104.0/22^22-29,
202.50.124.0/22^22-29,
202.164.28.0/22^22-29,
203.99.132.0/22^22-29,
202.27.186.0/23^23-29,
202.36.178.0/23^23-29,
202.36.220.0/23^23-29,
202.37.96.0/23^23-29,
202.37.100.0/23^23-29,
202.37.124.0/23^23-29,
202.49.90.0/23^23-29,
202.49.120.0/23^23-29,
203.147.108.0/23^23-29,
210.55.30.0/23^23-29,
210.55.206.0/23^23-29,
192.148.221.0/24^24-29,
192.156.225.0/24^24-29,
202.36.163.0/24^24-29,
202.36.170.0/24^24-29,
202.36.219.0/24^24-29,
202.37.114.0/24^24-29,
202.46.187.0/24^24-29,
202.49.115.0/24^24-29,
202.49.125.0/24^24-29,
202.49.187.0/24^24-29,
202.50.117.0/24^24-29,
202.50.169.0/24^24-29,
202.146.186.0/24^24-29,
203.96.112.0/24^24-29,
210.7.40.0/24^24-29,
210.54.15.0/24^24-29,
210.55.4.0/24^24-29,
210.55.7.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(a)snap.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20090608
source: NZRR
------------------------------------------------------------
_______________________________________________________________________
APNIC 28 Early Bird Registration Now Open
_______________________________________________________________________
Hi NZNOG Community,
APNIC and CNNIC warmly invite you to join us for APNIC 28 at the Grand
Hyatt, Beijing, from 25 to 28 August 2009.
Hosted in one of the most dynamic cities in the region, attending APNIC
28 is an excellent opportunity to develop your networking skills and
build business relationships.
Early Bird Registration
-----------------------
Registration for APNIC 28 is opening soon with discounts for early
registration of up to 25 per cent. APNIC and CNNIC are also offering a
fantastic prize of a portable mini PC for early bird registrations.
Note, a convenient gateway is available for credit card payments.
http://meetings.apnic.net/28/register
Apply for your Visa
-------------------
Unless you are a national of Singapore, Brunei, and Japan, you will need
to apply for a visa to enter mainland China. Visas usually last for 30
days and must be used within 3 months of issue. Note, your passport must
be valid for at least six months after the date you intend to enter to
country.
http://meetings.apnic.net/28/beijing/visas
Speak at APNIC 28
-----------------
APNIC and CNNIC are looking for informational presentations with
interesting and topical operational content that will benefit the
larger Internet community. If you would like to contribute, here are
some potential topics for you to consider:
- Four-byte AS numbers
- IPv6 real world experiences
- ISP and carrier services such as:
- Fibre to the home (FTTH) and other 'all optical' deployments
- Large network deployments
- Next Generation telephony
Submit a brief summary of your proposal (two to four paragraphs) or a
set of presentation slides to policy(a)apnic.net by 31 July 2009.
Final Presentation slides are due on 14 August 2009.
How do I find out more about APNIC 28?
--------------------------------------
For more information about APNIC meetings, and how you can attend,
please see:
http://meetings.apnic.net
Kind regards,
Elly
------------------------------------------------------------------------
Elly Tawhai email: elly(a)apnic.net
Senior Internet Resource Analyst/ sip: elly(a)voip.apnic.net
Liaison Officer(Pacific), APNIC phone: +61 7 3858 3188
http://www.apnic.net fax: +61 7 3858 3199
------------------------------------------------------------------------
The New Zealand Network Operators' Group
The NZNOG mailing list exists to facilitate discussion among operators
of networks in New Zealand on matters relevant to network operators as
described in the list's Acceptable Use Policy. That policy appears later
in this posting.
The NZNOG Trust exists to provide the legal framework needed to do jobs
like operating the bank account which holds the money which allows our
annual conferences to happen. The Trust is not yet GST registered, but
work is under way to bring that about.
Conference
In the NZNOG conference, the people are represented by two separate yet
equally important groups. The trust, which is responsible for where the
money goes, and the organising committee who do most of the actual work.
See http://2009.nznog.org/ for details of this year's conference.
Discussions are under way between the organising committee and potential
hosts of the 2010 conference.
Other Meetings
See http://thursdaynightcurry.com/ if you live in or near Auckland or
Wellington.
Operators' Contact List
See http://www.nznog.org/?page_id=6 for operational contact details for
most New Zealand ISP's. These are intended for use by other network
operators, not by most customers.
Internet Exchanges
See http://www.nzix.net/ for details of exchanges in operation.
About This Mailing List
This list has around 1000 addresses subscribed. You may only post to the
list from a subscribed address. A number of people subscribe
addresses which do not receive email purely to allow posting from them.
You may choose to receive postings as they come in, or just to receive
daily "digests". See the bottom of the page
http://list.waikato.ac.nz/mailman/listinfo/nznog/ to change the form in
which you receive postings.
The NZNOG mailing list is provided through a server at The University of
Waikato, and is administered by employees of APN Online, Citylink, and
The University of Waikato. None of these organisations, nor any
administrator, is responsible for its content.
NZNOG Mailing List Acceptable Use Policy
The NZNOG mailing list exists to provide a forum for the exchange of
technical information and the discussion of implementation issues
that require cooperation among New Zealand network service providers.
In order to continue to provide a useful forum for discussion of
relevant technical issues, users of the list are asked to respect the
following guidelines.
1. Discussion will focus on Internet operational and technical
issues.
2. Discussion related to meetings of network service providers is
appropriate.
3. Discussion unrelated to these topics is not appropriate.
4. Postings to multiple mailing lists are discouraged.
5. Postings that include foul language, character assassination, and
lack of respect for other participants are unacceptable.
6. Blatant product or service marketing is unacceptable.
7. Postings of a political, philosophical or legal nature are
discouraged.
8. Postings to the list should be in ASCII or MIME encoded as
text/plain. Attachments should not be sent to the list. To
present a document, a suitable URL may be referred to. For
documents of general interest, the use of proprietary file
formats is discouraged.
9. Breaches of list etiquette should be dealt with privately with the
offending list user, and should not result in complaints being
sent to the list.
10. A person repeatedly breaching list etiquette shall receive warnings
from the list administrator. A further breach after the second such
warning within thirty days shall result in the offender being
unsubscribed from the list. Other action may also be taken to block
postings to the list by the offender. Any such unsubscription is to
be immediately announced to the list.
Mailing List Archives
A full archive is available at http://list.waikato.ac.nz/pipermail/nznog/ .
Any message sent to the list will be archived and made available on the
web automatically. Changes are not made to the archive on request,
though the administrators remain happy to assist the Office of the
Privacy Commissioner should any complaint be laid with that office.
One way to search the archive is to use google and prefix your search
with site:list.waikato.ac.nz .
Subscribing to the List
See http://list.waikato.ac.nz/mailman/listinfo/nznog to subscribe.
Donald Neal
NZNOG Mailing List Owner/Administrator/Muggins
--
Donald Neal | "Careful design and strict discipline are
Research Officer | necessary to prevent this sort of mess
WAND | from escaping the development laboratory
The University of Waikato | and infesting the production environment."
| - D. Russell
Thanks to everybody that replied. On a different note I would appreciate
the opinion of the list on :
What are the advantages and disadvantages of working in IT in NZ?
Thanks to Gary Benner for that.
Chris
