Hi everyone,
I would just like to thank you all for your help and suggestions for
the entertainment for next Thursday night, it was really helpful!
Taking all offers into consideration we have come to a decision.
After the dinner, Vocus' buses will take us all to the casino where
we'll have gambling (with fake money ;) and drinks.
Looking forward to seeing you all there.
Kind Regards,
Corinne Cowlishaw
Administration Assistant
Level 1, 189 Miller St
North Sydney, NSW 2060
T: +61 2 8999 8999
E: corinne(a)vocus.com.au
W: www.vocus.com.au
_______________________________________________________________________
Less than 10% of IPv4 Addresses Remain Unallocated, says Number Resource
Organization
_______________________________________________________________________
Hi NZNOG Community,
Deploying IPv6 - the next generation of the Internet Protocol - is vital
to the continued development of the Internet
AMSTERDAM - The Number Resource Organization (NRO), the official
representative of the five Regional Internet Registries (RIRs) that
oversee the allocation of all Internet number resources, announced today
that less than 10 percent of available IPv4 addresses remain
unallocated. This small pool of existing IP addresses marks a critical
moment in IPv4 address exhaustion, ultimately impacting the future
network operations of all businesses and organizations around the globe.
"This is a key milestone in the growth and development of the global
Internet," noted Axel Pawlik, Chairman of the NRO. "With less than 10
percent of the entire IPv4 address range still available for allocation
to RIRs, it is vital that the Internet community take considered and
determined action to ensure the global adoption of IPv6. The limited
IPv4 addresses will not allow us enough resources to achieve the
ambitions we all hold for global Internet access. The deployment of IPv6
is a key infrastructure development that will enable the network to
support the billions of people and devices that will connect in the
coming years," added Pawlik.
Internet Protocol is a set of technical rules that defines how devices
communicate over a network. There are currently two versions of IP, IPv4
and IPv6. IPv6 includes a modern numbering system that provides a much
larger address pool than IPv4. With so few IPv4 addresses remaining, the
NRO is urging all Internet stakeholders to take immediate action by
planning for the necessary investments required to deploy IPv6.
The NRO, alongside each individual RIR, has actively promoted IPv6
deployment for several years through grassroots outreach, speaking
engagements, conferences and media outreach. To date, their combined
efforts have yielded positive results in the call to action for the
adoption of IPv6. Given the less than 10 percent milestone, the NRO is
continuing its call for Internet stakeholders, including governments,
vendors, enterprises, telecoms operators, and end users, to fulfill
their roles in IPv6 adoption, specifically encouraging the following
actions: The business sector should provide IPv6-capable services
and platforms, including web hosting and equipment, ensuring
accessibility for IPv6 users. Software and hardware vendors should
implement IPv6 support in their products to guarantee they are available
at production standard when needed. Governments should lead the way
by making their own content and services available over IPv6 and
encouraging IPv6 deployment efforts in their countries. IPv6
requirements in government procurement policies are critical at this
time. Civil society, including organizations and end users, should
request that all services they receive from their ISPs and vendors are
IPv6-ready, to build demand and ensure competitive availability of IPv6
services in coming years.
The NRO's campaign to promote the next generation of Internet Protocol
continues to positively impact the Internet community. IPv6 allocations
increased by nearly 30% in 2009, as community members continued to
recognize the benefits of IPv6.
"Many decision makers don't realize how many devices require IP
addresses - mobile phones, laptops, servers, routers, the list goes on,"
said Raul Echeberria, Secretary of the NRO. "The number of available
IPv4 addresses is shrinking rapidly, and if the global Internet
community fails to recognize this, it will face grave consequences in
the very near future. As such, the NRO is working to educate everyone,
from network operators to top executives and government representatives,
about the importance of IPv6 adoption," added Echeberria.
IP addresses are allocated by the Internet Assigned Numbers Authority
(IANA), a contract operated by the Internet Corporation for Assigned
Names and Numbers (ICANN). IANA distributes IP addresses to RIRs, who in
turn issue them to users in their respective regions. "This is the time
for the Internet community to act," said Rod Beckstrom, ICANN's
President and Chief Executive Officer. "For the global Internet to grow
and prosper without limitation, we need to encourage the rapid
widespread adoption of the IPv6 protocol."
________________________________________________________________________
APNIC Secretariat secretariat(a)apnic.net
Asia Pacific Network Information Centre (APNIC) Tel: 61 7 3858 3100
PO Box 2131 Milton, QLD 4064 Australia Fax: 61 7 3858 3199
Level 1, 33 Park Road, Milton, QLD http://www.apnic.net
________________________________________________________________________
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:AS9503
descr: Route set advertised to AS24388 by FX Networks - AS9503
members: 202.89.43.0/25^25-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: service(a)fx.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20100120
source: NZRR
REPLACED BY:
route-set: AS24388:RS-ROUTES:AS9503
descr: advertised to AS24388 by FX Networks - AS9503
members: 130.123.0.0/16^16-29,
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,
112.109.64.0/20^20-29,
114.134.160.0/20^20-29,
119.47.112.0/20^20-29,
124.248.128.0/20^20-29,
202.53.176.0/20^20-29,
202.86.96.0/20^20-29,
202.160.48.0/20^20-29,
210.48.160.0/20^20-29,
112.109.80.0/21^21-29,
117.18.80.0/21^21-29,
120.89.80.0/21^21-29,
192.173.16.0/21^21-29,
202.37.32.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,
110.232.144.0/22^22-29,
113.197.64.0/22^22-29,
175.111.100.0/22^22-29,
192.206.152.0/22^22-29,
202.37.48.0/22^22-29,
202.89.4.0/22^22-29,
203.99.132.0/22^22-29,
192.206.156.0/23^23-29,
202.36.218.0/23^23-29,
202.46.190.0/23^23-29,
202.49.164.0/23^23-29,
203.84.134.0/23^23-29,
203.217.142.0/23^23-29,
192.88.85.0/24^24-29,
192.88.99.0/24^24-29,
192.105.10.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.221.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.49.106.0/24^24-29,
202.49.168.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,
202.89.57.0/24^24-29,
203.89.178.0/24^24-29,
203.89.181.0/24^24-29,
203.89.187.0/24^24-29,
202.89.43.0/25^25-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: tim(a)fx.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20100120
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: AS45279:RS-ROUTES:AS9503
descr: advertised to AS45279 by FX Networks - AS9503
members: 130.123.0.0/16^16-29,
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,
112.109.64.0/20^20-29,
114.134.160.0/20^20-29,
119.47.112.0/20^20-29,
124.248.128.0/20^20-29,
202.46.160.0/20^20-29,
202.53.176.0/20^20-29,
202.86.96.0/20^20-29,
202.160.48.0/20^20-29,
210.48.160.0/20^20-29,
112.109.80.0/21^21-29,
117.18.80.0/21^21-29,
120.89.80.0/21^21-29,
192.173.16.0/21^21-29,
202.37.32.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.126.80.0/21^21-29,
202.160.112.0/21^21-29,
203.190.208.0/21^21-29,
110.232.144.0/22^22-29,
113.197.64.0/22^22-29,
202.37.48.0/22^22-29,
202.89.4.0/22^22-29,
203.99.132.0/22^22-29,
202.36.218.0/23^23-29,
202.46.190.0/23^23-29,
202.49.164.0/23^23-29,
203.84.134.0/23^23-29,
203.217.142.0/23^23-29,
192.88.85.0/24^24-29,
192.88.99.0/24^24-29,
192.105.10.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.221.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.49.106.0/24^24-29,
202.49.144.0/24^24-29,
202.49.168.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,
202.89.57.0/24^24-29,
203.89.178.0/24^24-29,
203.89.181.0/24^24-29,
203.89.187.0/24^24-29,
202.89.43.0/25^25-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 20091208
source: NZRR
REPLACED BY:
route-set: AS45279:RS-ROUTES:AS9503
descr: advertised to AS45279 by FX Networks - AS9503
members: 130.123.0.0/16^16-29,
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,
112.109.64.0/20^20-29,
114.134.160.0/20^20-29,
119.47.112.0/20^20-29,
124.248.128.0/20^20-29,
202.53.176.0/20^20-29,
202.86.96.0/20^20-29,
202.160.48.0/20^20-29,
210.48.160.0/20^20-29,
112.109.80.0/21^21-29,
117.18.80.0/21^21-29,
120.89.80.0/21^21-29,
192.173.16.0/21^21-29,
202.37.32.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,
110.232.144.0/22^22-29,
113.197.64.0/22^22-29,
175.111.100.0/22^22-29,
192.206.152.0/22^22-29,
202.37.48.0/22^22-29,
202.89.4.0/22^22-29,
203.99.132.0/22^22-29,
192.206.156.0/23^23-29,
202.36.218.0/23^23-29,
202.46.190.0/23^23-29,
202.49.164.0/23^23-29,
203.84.134.0/23^23-29,
203.217.142.0/23^23-29,
192.88.85.0/24^24-29,
192.88.99.0/24^24-29,
192.105.10.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.221.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.49.106.0/24^24-29,
202.49.168.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,
202.89.57.0/24^24-29,
203.89.178.0/24^24-29,
203.89.181.0/24^24-29,
203.89.187.0/24^24-29,
202.89.43.0/25^25-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: tim(a)fx.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20100120
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: 130.123.0.0/16^16-29,
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,
112.109.64.0/20^20-29,
114.134.160.0/20^20-29,
119.47.112.0/20^20-29,
124.248.128.0/20^20-29,
202.46.160.0/20^20-29,
202.53.176.0/20^20-29,
202.86.96.0/20^20-29,
202.160.48.0/20^20-29,
210.48.160.0/20^20-29,
112.109.80.0/21^21-29,
117.18.80.0/21^21-29,
120.89.80.0/21^21-29,
192.173.16.0/21^21-29,
202.37.32.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.126.80.0/21^21-29,
202.160.112.0/21^21-29,
203.190.208.0/21^21-29,
110.232.144.0/22^22-29,
113.197.64.0/22^22-29,
202.37.48.0/22^22-29,
202.89.4.0/22^22-29,
203.99.132.0/22^22-29,
202.36.218.0/23^23-29,
202.46.190.0/23^23-29,
202.49.164.0/23^23-29,
203.84.134.0/23^23-29,
203.217.142.0/23^23-29,
192.88.85.0/24^24-29,
192.88.99.0/24^24-29,
192.105.10.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.221.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.49.106.0/24^24-29,
202.49.144.0/24^24-29,
202.49.168.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,
202.89.57.0/24^24-29,
203.89.178.0/24^24-29,
203.89.181.0/24^24-29,
203.89.187.0/24^24-29,
202.89.43.0/25^25-29,
123.100.117.192/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: peering(a)fx.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20091106
source: NZRR
REPLACED BY:
route-set: AS9439:RS-ROUTES:AS9503
descr: advertised to AS9439 by FX Networks - AS9503
members: 130.123.0.0/16^16-29,
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,
112.109.64.0/20^20-29,
114.134.160.0/20^20-29,
119.47.112.0/20^20-29,
124.248.128.0/20^20-29,
202.53.176.0/20^20-29,
202.86.96.0/20^20-29,
202.160.48.0/20^20-29,
210.48.160.0/20^20-29,
112.109.80.0/21^21-29,
117.18.80.0/21^21-29,
120.89.80.0/21^21-29,
192.173.16.0/21^21-29,
202.37.32.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,
110.232.144.0/22^22-29,
113.197.64.0/22^22-29,
175.111.100.0/22^22-29,
192.206.152.0/22^22-29,
202.37.48.0/22^22-29,
202.89.4.0/22^22-29,
203.99.132.0/22^22-29,
192.206.156.0/23^23-29,
202.36.218.0/23^23-29,
202.46.190.0/23^23-29,
202.49.164.0/23^23-29,
203.84.134.0/23^23-29,
203.217.142.0/23^23-29,
192.88.85.0/24^24-29,
192.88.99.0/24^24-29,
192.105.10.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.221.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.49.106.0/24^24-29,
202.49.168.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,
202.89.57.0/24^24-29,
203.89.178.0/24^24-29,
203.89.181.0/24^24-29,
203.89.187.0/24^24-29,
202.89.43.0/25^25-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: tim(a)fx.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20100120
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: 130.123.0.0/16^16-29,
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,
112.109.64.0/20^20-29,
114.134.160.0/20^20-29,
119.47.112.0/20^20-29,
124.248.128.0/20^20-29,
202.46.160.0/20^20-29,
202.53.176.0/20^20-29,
202.86.96.0/20^20-29,
202.160.48.0/20^20-29,
210.48.160.0/20^20-29,
112.109.80.0/21^21-29,
117.18.80.0/21^21-29,
120.89.80.0/21^21-29,
192.173.16.0/21^21-29,
202.37.32.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.126.80.0/21^21-29,
202.160.112.0/21^21-29,
203.190.208.0/21^21-29,
110.232.144.0/22^22-29,
113.197.64.0/22^22-29,
202.37.48.0/22^22-29,
202.89.4.0/22^22-29,
203.99.132.0/22^22-29,
202.36.218.0/23^23-29,
202.46.190.0/23^23-29,
202.49.164.0/23^23-29,
203.84.134.0/23^23-29,
203.217.142.0/23^23-29,
192.88.85.0/24^24-29,
192.88.99.0/24^24-29,
192.105.10.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.221.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.49.106.0/24^24-29,
202.49.144.0/24^24-29,
202.49.168.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,
202.89.57.0/24^24-29,
203.89.178.0/24^24-29,
203.89.181.0/24^24-29,
203.89.187.0/24^24-29,
202.89.43.0/25^25-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 20091208
source: NZRR
REPLACED BY:
route-set: AS9560:RS-ROUTES:AS9503
descr: advertised to AS9560 by FX Networks - AS9503
members: 130.123.0.0/16^16-29,
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,
112.109.64.0/20^20-29,
114.134.160.0/20^20-29,
119.47.112.0/20^20-29,
124.248.128.0/20^20-29,
202.53.176.0/20^20-29,
202.86.96.0/20^20-29,
202.160.48.0/20^20-29,
210.48.160.0/20^20-29,
112.109.80.0/21^21-29,
117.18.80.0/21^21-29,
120.89.80.0/21^21-29,
192.173.16.0/21^21-29,
202.37.32.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,
110.232.144.0/22^22-29,
113.197.64.0/22^22-29,
192.206.152.0/22^22-29,
202.37.48.0/22^22-29,
202.89.4.0/22^22-29,
203.99.132.0/22^22-29,
192.206.156.0/23^23-29,
202.36.218.0/23^23-29,
202.46.190.0/23^23-29,
202.49.164.0/23^23-29,
203.84.134.0/23^23-29,
203.217.142.0/23^23-29,
192.88.85.0/24^24-29,
192.88.99.0/24^24-29,
192.105.10.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.221.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.49.106.0/24^24-29,
202.49.168.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,
202.89.57.0/24^24-29,
203.89.178.0/24^24-29,
203.89.181.0/24^24-29,
203.89.187.0/24^24-29,
202.89.43.0/25^25-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: tim(a)fx.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20100120
source: NZRR
------------------------------------------------------------
Good afternoon everyone.
The National Library of New Zealand is planning a second New Zealand Web Harvest in April 2010.
We received a lot of feedback from NZNOG (and others) during and after New Zealand Web Harvest 2008. Following that harvest, Dean helped arrange up a meeting of interested stakeholders at the Library to discuss the various issues that were raised, and reported back to the list here:
http://list.waikato.ac.nz/pipermail/nznog/2008-November/014763.html
You may also recall that I spoke at the 2009 NZNOG conference about our experience with the first harvest. I will speak at the 2010 conference out our plans for the second.
During the 2008 Web Harvest, members of the New Zealand internet community raised several concerns, specifically relating to:
-- the notification period
-- the robots policy
-- the location of the harvester.
For the 2010 harvest we have developed an Options Paper, detailing approaches the Library could take to address these concerns. We are circulating this Options Paper to stakeholder groups in the networking and technical communities. The feedback we receive will be built into the planning of the harvest, its public notification, and its operation.
Please note that the options paper is NOT a general notification of the 2010 harvest. We will notify the wider New Zealand internet community closer to the date of the harvest when more details are known.
You can find a copy of the Options Paper on the National Library website: http://bit.ly/nlnzwebharvest
Submissions on the Options Paper close at 9am on Monday 8 February 2010, or you can talk to me in person at NZNOG 2010. I'll be giving a short presentation on Thursday morning, and staying on to talk to people until Friday afternoon.
See you in sunny Hamilton!
And by way of providing a useful service to conference attendees, and illustrating the value of web archiving, may I refer you to one of the first substantive websites about Hamilton, written by myself and my flatmates when I was at University, offering valuable advice on the city, where to eat, the University, architecture, and so on, and preserved for your benefit by the Internet Archive:
If you're planning on visiting Hamilton in 1998, it's a must-read: http://web.archive.org/web/20070515122721rn_1/www.paynter.info/miscellania/…
Thanks,
Gordon
--
Gordon Paynter
Programme Manager Digitisation
National Digital Library
National Library of New Zealand
Hi everyone,
Would those attending have a preference for entertainment for after
dinner on Thursday 28th?
Also are there any particular bars that anyone could recommend in
Hamilton in the city centre or near the conference?
Thanks,
Kind Regards,
Corinne Cowlishaw
Administration Assistant
Level 1, 189 Miller St
North Sydney, NSW 2060
T: +61 2 8999 8999
E: corinne(a)vocus.com.au
W: www.vocus.com.au
NZNOG is just a week away now. There are limited slots left in the
Routing Workshop and Security Tutorial. If you want to get into these
then you'll need to register on up mighty fast.
Accommodation on campus needs to be finalised soon also, so same deal
- register soon. Note that the registration system allows you to book
just accommodation so if you've previously registered for the
conference you can add another order for accommodation only should you
want that.
http://2010.nznog.org/register
Additionally Renaissance and Brocade will be providing a Brocade
(Foundry) switch/router course on the Wednesday. As a bonus they'll
also be providing attendees with a complimentary exam voucher allowing
for a Brocade qualification to be achieved.
http://2010.nznog.org/tutorials#brocade
Once more, the org team would like to thank our generous sponsors for
making each and every NZNOG a reality.
http://2010.nznog.org/sponsors
See you in Hamilton!
Jonny.
Hi NZNOG Community,
On 10 February 2009, APNIC will implement three policy proposals that
reached consensus during APNIC 28 in Beijing, China in August
2009. The APNIC Executive Council (EC) endorsed the proposals during
their November 2009 meeting. The three policy changes are:
- Removing policy restrictions on the transfer of registration of
IPv4 address allocations and IPv4 portable address assignments
between current APNIC account holders.
This change aims to ensure that the APNIC registry reflects
the true status of IPv4 resource holdings, reducing risks to the
routing and addressing infrastructure integrity of the network
and providing a stronger incentive for unused IPv4 address space
to return to active use during the IPv6 transition.
- Providing alternative simplified criteria that allows a Member
with existing IPv4 space to qualify for an appropriately sized
IPv6 block under the matching IPv6 policy and request that
IPv6 block through a simple online form.
This change aims to encourage greater uptake of IPv6 addresses
amongst APNIC Members who have IPv4 space.
- Adding the ability to recover unused historical AS numbers for
eventual reassignment to other APNIC account holders.
This change aims to release unused AS numbers back into the
unassigned pool.
To view the history of these policy proposals, see:
prop-050: IPv4 address transfers
http://www.apnic.net/policy/proposals/prop-050
prop-073: Simplifying allocation/assignment of IPv6 to APNIC
members with existing IPv4 addresses
http://www.apnic.net/policy/proposals/prop-073
prop-075: Ensuring efficient use of historical AS numbers
http://www.apnic.net/policy/proposals/prop-075
APNIC policies are developed by the Membership and broader Internet
community. It's easy to participate in APNIC policy development. If
you can't attend APNIC meetings, you can join the discussions online
via the Policy SIG mailing list. To join, go to:
http://www.apnic.net/community/participate/join-discussions
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
------------------------------------------------------------------------
