Dear Colleague,
This is to notify you that one or more objects in which you are
designated for notification have been modified in the NZRR routing
registry database.
These objects are used to configure the various NZIX route servers
(http://nzix.net/) so you can expect the relevant servers to be reloaded
in the near future. The reloading of the servers is staggered over a
period of time so that if you are peering with both servers at an
exchange, you can maintain at least one BGP session at all times and
consequently a full set of routes.
Diagnostic output:
------------------------------------------------------------
---
PREVIOUS OBJECT:
route-set: AS9560:RS-ROUTES:AS9503
descr: advertised to AS9560 by FX Networks - AS9503
members: 131.203.0.0/16^16-29,
161.29.0.0/16^16-29,
161.65.0.0/16^16-29,
166.65.0.0/16^16-29,
119.15.0.0/19^19-29,
202.14.32.0/19^19-29,
202.53.176.0/20^20-29,
202.191.32.0/20^20-29,
210.48.160.0/20^20-29,
120.89.80.0/21^21-29,
192.173.16.0/21^21-29,
202.46.176.0/21^21-29,
202.49.0.0/21^21-29,
202.78.240.0/21^21-29,
203.190.208.0/21^21-29,
202.37.48.0/22^22-29,
202.89.4.0/22^22-29,
202.160.116.0/22^22-29,
202.124.106.0/23^23-29,
202.160.114.0/23^23-29,
192.88.85.0/24^24-29,
192.122.171.0/24^24-29,
192.133.31.0/24^24-29,
192.195.219.0/24^24-29,
198.32.71.0/24^24-29,
202.20.97.0/24^24-29,
202.36.33.0/24^24-29,
202.36.119.0/24^24-29,
202.36.162.0/24^24-29,
202.36.218.0/24^24-29,
202.46.190.0/24^24-29,
202.49.106.0/24^24-29,
202.50.247.0/24^24-29,
202.55.105.0/24^24-29,
203.119.56.0/24^24-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: peering(a)fx.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20080812
source: NZRR
REPLACED BY:
route-set: AS9560:RS-ROUTES:AS9503
descr: advertised to AS9560 by FX Networks - AS9503
members: 131.203.0.0/16^16-29,
161.29.0.0/16^16-29,
161.65.0.0/16^16-29,
166.65.0.0/16^16-29,
119.15.0.0/19^19-29,
202.14.32.0/19^19-29,
202.53.176.0/20^20-29,
202.191.32.0/20^20-29,
210.48.160.0/20^20-29,
120.89.80.0/21^21-29,
192.173.16.0/21^21-29,
202.46.176.0/21^21-29,
202.49.0.0/21^21-29,
202.78.240.0/21^21-29,
203.190.208.0/21^21-29,
202.37.48.0/22^22-29,
202.89.4.0/22^22-29,
202.160.116.0/22^22-29,
202.124.106.0/23^23-29,
202.160.114.0/23^23-29,
124.248.128.0/24^24-29,
124.248.132.0/24^24-29,
124.248.136.0/24^24-29,
124.248.140.0/24^24-29,
192.88.85.0/24^24-29,
192.122.171.0/24^24-29,
192.133.31.0/24^24-29,
192.195.219.0/24^24-29,
198.32.71.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.168.0/24^24-29,
202.46.190.0/24^24-29,
202.49.106.0/24^24-29,
202.50.247.0/24^24-29,
202.55.105.0/24^24-29,
203.119.56.0/24^24-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: peering(a)fx.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20080903
source: NZRR
------------------------------------------------------------
Hi,
I'm seeing TCP ECN issues on the final hop to www.airnewzealand.co.nz.
If there's someone from Air NZ on this list, you might want to look
into it. I can provide traceroute / testing information if required.
As an aside, I thought the "some routers break packets with ECN
enabled" bug went away ages ago. Is anyone else seeing ECN related
brokenness, or is it now SOP to disable ECN and leave it off?
Daniel
At the APNIC meeting in Christchurch last week Sam Sargeant gave a nice talk
on this. See http://www.apnic.net/meetings/26/program/apops/ for his slides.
Leo Vegoda from ICANN pointed to this tool:
http://recursive.iana.org/
which would be an interesting one for service providers to point out to their
customers (unless of course they run the DNS for them and their servers are
not right).
A number of organisations in New Zealand have still not upgraded their
software and many more are running servers that are recursive and authoritive
at the same time.
Time to get with the program!
