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-ROUTES6:AS9503
descr: Route set advertised to AS9560 by FX Networks - AS9503
mp-members: 2402:6000:0:0:0:0:0:0/32^32-64,
2404:3800:0:0:0:0:0:0/32^32-64,
2001:0dce:0:0:0:0:0:0/32^32-64,
2001:0dce:e000:0:0:0:0:0/48^48-64,
2001:0df0:004a:0:0:0:0:0/48^48-64,
2404:1800:0:0:0:0:0:0/32^32-64,
2001:4530:0:0:0:0:0:0/32^32-64,
2400:b400:0:0:0:0:0:0/32^32-64,
2404:0130:0:0:0:0:0:0/32^32-64
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: craig.wallace(a)fx.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20100427
source: NZRR
REPLACED BY:
route-set: AS9560:RS-ROUTES6:AS9503
descr: Route set advertised to AS9560 by FX Networks - AS9503
mp-members: 2402:6000:0:0:0:0:0:0/32^32-64,
2404:3800:0:0:0:0:0:0/32^32-64,
2001:DCE:0:0:0:0:0:0/32^32-64,
2001:DCE:E000:0:0:0:0:0/48^48-64,
2001:DF0:4A:0:0:0:0:0/48^48-64,
2404:1800:0:0:0:0:0:0/32^32-64,
2001:4530:0:0:0:0:0:0/32^32-64,
2400:B400:0:0:0:0:0:0/32^32-64,
2404:130:0:0:0:0:0:0/32^32-64,
2403:E00:0:0:0:0:0:0/32^32-64
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 20100712
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-ROUTES6:AS38477
descr: Route set advertised to AS9560 by Unleash Computers Ltd - AS38477
mp-members: 2401:F000:0:0:0:0:0:0/32^32-64
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: michael(a)unleash.co.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20100304
source: NZRR
REPLACED BY:
route-set: AS9560:RS-ROUTES6:AS38477
descr: Route set advertised to AS9560 by Unleash - AS38477
mp-members: 2401:F000:0:0:0:0:0:0/32^32-64,
2407:2400:0:0:0:0:0:0/32^32-64
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: noc(a)unleash.co.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20100712
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:AS17492
descr: advertised to AS9560 by Vector Communications Limited - AS17492
members: 202.126.192.0/20^20-29,
115.126.128.0/21^21-29,
123.108.144.0/21^21-29,
202.162.176.0/21^21-29,
180.210.208.0/22^22-29,
182.16.152.0/22^22-29,
202.0.151.0/24^24-29,
202.62.245.0/24^24-29,
203.30.174.0/24^24-29,
203.99.68.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: Tim.Harman(a)vector.co.nz
notify: Tony.Wicks(a)vector.co.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20100603
source: NZRR
REPLACED BY:
route-set: AS9560:RS-ROUTES:AS17492
descr: advertised to AS9560 by Vector Communications - AS17492
members: 116.199.208.0/20^20-29,
202.126.192.0/20^20-29,
115.126.128.0/21^21-29,
123.108.144.0/21^21-29,
182.23.176.0/21^21-29,
202.162.176.0/21^21-29,
180.210.208.0/22^22-29,
182.16.152.0/22^22-29,
202.0.151.0/24^24-29,
202.50.246.0/24^24-29,
202.62.245.0/24^24-29,
202.129.253.0/24^24-29,
203.30.174.0/24^24-29,
203.99.68.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: Tim.Harman(a)vector.co.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20100712
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,
180.189.192.0/19^19-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.136.0.0/21^21-29,
120.138.16.0/21^21-29,
202.36.16.0/21^21-29,
202.49.64.0/21^21-29,
210.54.56.0/21^21-29,
110.34.48.0/22^22-29,
113.21.224.0/22^22-29,
113.197.96.0/22^22-29,
202.36.24.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.14.217.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.37.179.0/24^24-29,
202.37.194.0/24^24-29,
202.46.189.0/24^24-29,
202.49.59.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.176.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 20100604
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,
143.96.0.0/16^16-29,
156.62.0.0/16^16-29,
180.189.192.0/19^19-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.136.0.0/21^21-29,
120.138.16.0/21^21-29,
202.36.16.0/21^21-29,
202.49.64.0/21^21-29,
210.54.56.0/21^21-29,
110.34.48.0/22^22-29,
113.21.224.0/22^22-29,
113.197.96.0/22^22-29,
202.36.24.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.88.190.0/24^24-29,
192.203.216.0/24^24-29,
202.0.151.0/24^24-29,
202.12.104.0/24^24-29,
202.14.217.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.36.198.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.179.0/24^24-29,
202.37.194.0/24^24-29,
202.46.189.0/24^24-29,
202.49.59.0/24^24-29,
202.49.140.0/24^24-29,
202.49.216.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.176.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 20100712
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: 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,
182.54.160.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.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.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.110.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.55.4.0/24^24-29,
210.55.7.0/24^24-29,
210.55.110.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 20100421
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,
182.54.160.0/20^20-29,
202.49.16.0/20^20-29,
203.86.192.0/20^20-29,
27.110.120.0/21^21-29,
202.174.112.0/21^21-29,
210.5.48.0/21^21-29,
110.92.16.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.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,
143.96.13.0/24^24-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.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.110.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.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 20100712
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:AS38477
descr: advertised to AS9560 by Unleash - AS38477
members: 116.90.128.0/20^20-29,
113.130.120.0/22^22-29,
131.203.134.0/23^23-29,
202.6.116.0/23^23-29,
131.203.133.0/24^24-29,
192.138.251.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)unleash.co.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20100504
source: NZRR
REPLACED BY:
route-set: AS9560:RS-ROUTES:AS38477
descr: advertised to AS9560 by Unleash - AS38477
members: 116.90.128.0/20^20-29,
113.130.120.0/22^22-29,
182.50.160.0/22^22-29,
202.6.116.0/23^23-29,
192.138.251.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)unleash.co.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20100712
source: NZRR
------------------------------------------------------------
Root Zone DNSSEC Deployment
Technical Status Update 2010-07-10
This is the tenth of a series of technical status updates intended
to inform a technical audience on progress in signing the root zone
of the DNS.
RESOURCES
Details of the project, including documentation published to date,
can be found at <http://www.root-dnssec.org/>.
We'd like to hear from you. If you have feedback for us, please
send it to rootsign(a)icann.org.
KSK CEREMONY 2
The second KSK ceremony for the root zone will take place in El
Segundo, CA, USA on Monday 2010-07-12. The ceremony is scheduled
to begin at 1300 local time (2000 UTC) and is expected to end by
1900 local time (0200 UTC).
Video from Ceremony 2 will be recorded for audit purposes, as with
Ceremony 1. Video and associated audit materials will be published
before the signed root enters full production on 2010-07-15. Details
will be circulated before that date.
ICANN will operate a separate camera whose video will not be retained
for audit purposes, but which will instead be streamed live in order
to provide remote observers an opportunity to watch the ceremony.
The live stream will be provided on a best-effort basis.
The live video stream will be available at:
http://dns.icann.org/ksk/stream/
FULL PRODUCTION SIGNED ROOT ZONE
The transition from Deliberately-Unvalidatable Root Zone (DURZ) to
production signed root zone will take place on 2010-07-15.
Trust anchor publication, according to draft-icann-dnssec-trust-anchor-00
will take place after the maintenance window closes, once a final
set of tests have been completed by ICANN and the results have been
found to be positive.
FTP ACCESS TO SIGNED ZONE FILES
Following the transition on 2010-07-15 the unsigned root and ARPA
zone files published at
ftp://rs.internic.net/domain/ftp://ftp.internic.net/domain/
will be replaced by signed zone files. That is, the zone files
retrieved from both FTP servers will contain DNSSEC data, and will
hence faithfully represent the zones being served by root servers.
PLANNED DEPLOYMENT SCHEDULE
Already completed:
2010-01-27: L starts to serve DURZ
2010-02-10: A starts to serve DURZ
2010-03-03: M, I start to serve DURZ
2010-03-24: D, K, E start to serve DURZ
2010-04-14: B, H, C, G, F start to serve DURZ
2010-05-05: J starts to serve DURZ
2010-06-16: First Key Signing Key (KSK) Ceremony
To come:
2010-07-12: Second Key Signing Key (KSK) Ceremony
2010-07-15: Distribution of validatable, production, signed root
zone; publication of root zone trust anchor
(Please note that this schedule is tentative and subject to change
based on testing results or other unforeseen factors.)
