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,
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.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.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.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 20090924
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.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,
121.79.224.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.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.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.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 20091022
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.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.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.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 20091007
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.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,
121.79.224.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.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.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.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 20091022
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:AS17705
descr: advertised to AS9439 by InspireNet - AS17705
members: 203.114.128.0/18^18-29,
121.79.192.0/19^19-29,
140.200.248.0/22^22-29,
192.138.251.0/24^24-29,
203.92.25.0/24^24-29,
203.174.26.0/24^24-29,
210.7.46.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: brenden(a)staff.inspire.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20080724
source: NZRR
REPLACED BY:
route-set: AS9439:RS-ROUTES:AS17705
descr: advertised to AS9439 by Inspire Net Ltd - AS17705
members: 203.114.128.0/18^18-29,
121.79.192.0/19^19-29,
121.79.224.0/21^21-29,
140.200.248.0/22^22-29,
192.138.251.0/24^24-29,
203.92.25.0/24^24-29,
203.174.26.0/24^24-29,
210.7.46.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: ops(a)inspire.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20091022
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.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.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.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 20091007
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.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,
121.79.224.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.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.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.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 20091022
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:AS17746
descr: advertised to AS9439 by Orcon Internet Limited - AS17746
members: 60.234.0.0/16^16-29,
121.98.0.0/16^16-29,
202.150.96.0/19^19-29,
203.99.0.0/19^19-29,
202.126.192.0/20^20-29,
202.191.32.0/20^20-29,
203.96.192.0/20^20-29,
219.88.128.0/20^20-29,
219.88.240.0/20^20-29,
210.54.56.0/21^21-29,
210.54.148.0/22^22-29,
210.55.12.0/22^22-29,
202.37.82.0/23^23-29,
202.0.151.0/24^24-29,
202.36.170.0/24^24-29,
202.37.19.0/24^24-29,
202.37.78.0/24^24-29,
202.37.173.0/24^24-29,
202.37.194.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.164.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 20090722
source: NZRR
REPLACED BY:
route-set: AS9439:RS-ROUTES:AS17746
descr: advertised to AS9439 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,
202.126.192.0/20^20-29,
202.191.32.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,
120.138.16.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,
110.34.48.0/22^22-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,
202.36.230.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.0.151.0/24^24-29,
202.12.104.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.174.0/24^24-29,
202.37.19.0/24^24-29,
202.37.78.0/24^24-29,
202.37.173.0/24^24-29,
202.46.189.0/24^24-29,
202.49.140.0/24^24-29,
202.49.233.0/24^24-29,
202.49.246.0/24^24-29,
202.50.164.0/24^24-29,
202.50.246.0/24^24-29,
202.62.245.0/24^24-29,
202.95.250.0/24^24-29,
202.129.253.0/24^24-29,
203.30.174.0/24^24-29,
210.54.12.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
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 20091019
source: NZRR
------------------------------------------------------------
I'm working on a new draft about ISP scenarios for IPv6, along
with Sheng Jiang of Huawei Research. We will soon be soliciting
input so that we can fill in the blanks in
http://tools.ietf.org/id/draft-carpenter-v6ops-isp-scenarios
One reason we're doing this is that translation scenarios seem
much more important now than they did a few years ago.
I'd love to hear (off list) from any provider willing to spend
some time filling in our (gulp, sorry) questionnaire.
In case there's any interest in beer related to this, I do plan
to be at NZNOG in January.
Brian Carpenter
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:AS131187
descr: Route set advertised to AS9439 by Teritary Education Commission aka Education Commons Network - AS131187
members: 203.217.140.0/23^23-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: andrew.frazer(a)thenetworks.co.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20090915
source: NZRR
REPLACED BY:
route-set: AS9439:RS-ROUTES:AS131187
descr: advertised to AS9439 by Tertiary Education Commission - AS131187
members: 203.217.142.0/23^23-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: dylan(a)citylink.co.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20091015
source: NZRR
------------------------------------------------------------
[Apologies for duplicates]
Asia Pacific Regional Internet Conference on Operational Technologies
(APRICOT)
23 February - 5 March 2010, Kuala Lumpur, Malaysia
http://www.apricot2010.net
CALL FOR PAPERS
===============
The APRICOT 2010 Programme Committee is now seeking contributions for
Presentations and Tutorials for APRICOT 2010.
We are looking for people and proposals that would:
- Offer a technical tutorial on an appropriate topic; and/or
- Participate in the technical conference sessions as a speaker; and/or
- Convene and chair a Birds of a Feather (BOF) session.
Please submit proposals on-line at
http://submission.apricot.net/paper/user/login.php?event=22
CONFERENCE MILESTONES
---------------------
Call for Papers Opens: 12 October 2009
First Deadline for Submissions: 30 November 2009
First Draft Programme Published: 7 December 2009
Final Deadline for Submissions: 14 February 2010
Final Programme Published: 15 February 2010
Final Slides Received: 19 February 2010
PROGRAM MATERIAL
----------------
The APRICOT Programme is organised in three parts, including
workshops, tutorials and the conference. The APNIC Policy SIG and
Annual Members Meeting will be held during the APRICOT conference.
Topics for tutorials and conference would include amongst others
relevant to Internet Operations and Technologies:
- IPv4 / IPv6 Routing and operations
- IPv4 address runout / IPv6 deployment and transition technologies
- Backbone operations
- ISP and Carrier services
- Network security issues (NSP-SEC, DDoS Anti-Spam, Anti-Malware)
- Peering / IXPs
- Internet policy (Security, Regulation, Content Management,
Addressing, etc)
- Access and Transport Technologies, including broadband deployment,
Cable/DSL, wireless, WiMax, metro ethernet, fiber network, MPLS
- Content & Service Delivery (Multicast, Voice, Video, "telepresence",
Gaming)
CFP SUBMISSION
--------------
Draft slides for both tutorials and conference sessions MUST be
provided with CfP submissions otherwise the Programme Committee will
be unable to review the submission. For work in progress, the most
current information available at time of submission is acceptable.
Final slides are to be provided by the specified deadline for
publication on the APRICOT website.
While the majority of speaking slots will be filled by the first
submission deadline, a limited number of slots may be available up to
the final submission deadline for presentations that are exceptionally
timely, important, or of critical operational importance.
Please submit on-line at
http://submission.apricot.net/paper/user/login.php?event=22
Any questions or concerns should be addressed to the Programme
Committee by e-mail.
We look forward to receiving your presentation proposals.
Jonny Martin & Philip Smith
Co-Chairs, APRICOT Programme Committee
program(a)apricot.net
