- NZNOG - lists.nznog.org

problems with NTP on bigben?
by Simon Blake 03 Mar '05

03 Mar '05

Anybody else observed that bigben gained about 19 years at about 1:25pm this arvo? $ date Tue Jan 1 14:54:33 NZDT 2002 $ /usr/sbin/ntpdate -q truechimer.waikato.ac.nz server 130.217.76.32, stratum 2, offset -0.001089, delay 0.04276 1 Jan 14:49:38 ntpdate[17537]: adjust time server 130.217.76.32 offset -0.001089 sec $ /usr/sbin/ntpdate -q bigben.clix.net.nz server 203.167.224.60, stratum 1, offset 619315199.998172, delay 0.03613 1 Jan 14:49:55 ntpdate[17540]: step time server 203.167.224.60 offset 619315199.998172 sec - To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

13 20

How fair practice is this; is it spam?
by Barry Murphy 03 Mar '05

03 Mar '05

ok.... how fair is this... I purchase telehousing from orcon and register domains through them. They have spammed one of my customers offering to host their website free of charge in return for advertising space on their website. After hearing this I emailed my account manager at orcon and this was his response. "As Im sure you are aware, Orcon also runs hosting, and as such, from a marketing perspective we have to treat other web hosting companies as competition, even if they are buying wholesale services from us. All other ISP's do the same - Telecom actively market to our customers for all ISP services even though we purchase a massive amount of wholesale services off them. " Is this spam/fair practice? Seeing as they could obtain a list of these domains in their database (as they're the registrar for this domain) Kindest Regards Barry Murphy

3 2

Notification of NZRR Database changes
by NZRR Database Notifications 03 Mar '05

03 Mar '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. The update causing these changes had the following mail headers: - From: Andy Linton <asjl(a)citylink.co.nz> - Cc: - Subject: [CityLink #1987] Routing updates for APE Route Servers (fwd) - Date: Fri, 4 Mar 2005 13:10:15 +1300 (NZDT) - Msg-Id: <Pine.LNX.4.58.0503041309040.991(a)jennings.citylink.co.nz> NZRR Database Notification Department --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS4770 descr: advertised to AS9439 by ICONZ - AS4770 members: 138.235.0.0/16^16-29, 192.107.113.0/24^24-29, 192.173.16.0/21^21-29, 198.32.66.0/24^24-29, 199.212.90.0/23^23-29, 199.212.92.0/23^23-29, 202.6.84.0/24^24-29, 202.12.70.0/24^24-29, 202.12.248.0/21^21-29, 202.14.100.0/24^24-29, 202.21.130.0/24^24-29, 202.21.136.0/23^23-29, 202.36.155.0/24^24-29, 202.36.157.0/24^24-29, 202.36.32.0/24^24-29, 202.36.36.0/22^22-29, 202.36.44.0/24^24-29, 202.36.45.0/24^24-29, 202.36.76.0/23^23-29, 202.37.136.0/24^24-29, 202.37.140.0/22^22-29, 202.37.144.0/21^21-29, 202.37.163.0/24^24-29, 202.37.197.0/24^24-29, 202.37.200.0/22^22-29, 202.37.224.0/21^21-29, 202.37.232.0/24^24-29, 202.37.240.0/23^23-29, 202.37.252.0/23^23-29, 202.37.76.0/24^24-29, 202.37.85.0/24^24-29, 202.41.136.0/22^22-29, 202.41.140.0/24^24-29, 202.49.62.0/24^24-29, 202.49.89.0/24^24-29, 202.49.249.0/24^24-29, 202.50.87.0/24^24-29, 202.50.246.0/24^24-29, 202.55.96.0/20^20-29, 202.74.224.0/21^21-29, 202.182.192.0/19^19-29, 205.233.128.0/21^21-29, 205.233.136.0/23^23-29, 205.233.243.0/24^24-29, 210.185.0.0/18^18-29, 210.48.0.0/17^17-29, 210.54.136.0/22^22-29, 210.54.140.0/24^24-29, 210.54.160.0/19^19-29, 210.55.182.0/23^23-29, 210.55.24.0/22^22-29, 210.55.253.0/24^24-29, 210.56.32.0/20^20-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: john(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050225 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS4770 descr: advertised to AS9439 by ICONZ - AS4770 members: 138.235.0.0/16^16-29, 192.107.113.0/24^24-29, 192.173.16.0/21^21-29, 198.32.66.0/24^24-29, 199.212.93.0/24^24-29, 202.6.84.0/24^24-29, 202.12.70.0/24^24-29, 202.12.248.0/21^21-29, 202.14.100.0/24^24-29, 202.20.6.0/24^24-29, 202.21.130.0/24^24-29, 202.21.136.0/23^23-29, 202.36.155.0/24^24-29, 202.36.157.0/24^24-29, 202.36.32.0/24^24-29, 202.36.36.0/22^22-29, 202.36.44.0/24^24-29, 202.36.45.0/24^24-29, 202.36.76.0/23^23-29, 202.36.119.0/24^24-29, 202.37.136.0/24^24-29, 202.37.140.0/22^22-29, 202.37.144.0/21^21-29, 202.37.163.0/24^24-29, 202.37.197.0/24^24-29, 202.37.200.0/22^22-29, 202.37.224.0/21^21-29, 202.37.232.0/24^24-29, 202.37.240.0/23^23-29, 202.37.252.0/23^23-29, 202.37.76.0/24^24-29, 202.37.85.0/24^24-29, 202.41.136.0/22^22-29, 202.41.140.0/24^24-29, 202.46.190.0/24^24-29, 202.49.62.0/24^24-29, 202.49.89.0/24^24-29, 202.49.249.0/24^24-29, 202.49.159.0/24^24-29, 202.50.87.0/24^24-29, 202.50.246.0/24^24-29, 202.55.96.0/20^20-29, 202.74.224.0/21^21-29, 202.78.240.0/23^23-29, 202.182.192.0/19^19-29, 205.233.128.0/21^21-29, 205.233.136.0/23^23-29, 205.233.243.0/24^24-29, 210.185.0.0/18^18-29, 210.48.0.0/17^17-29, 210.54.136.0/22^22-29, 210.54.140.0/24^24-29, 210.54.160.0/19^19-29, 210.55.182.0/23^23-29, 210.55.24.0/22^22-29, 210.55.253.0/24^24-29, 210.56.32.0/20^20-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: john(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050304 source: NZRR --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS4770 descr: advertised to AS9560 by ICONZ - AS4770 members: 138.235.0.0/16^16-29, 192.107.113.0/24^24-29, 192.173.16.0/21^21-29, 198.32.66.0/24^24-29, 199.212.90.0/23^23-29, 199.212.92.0/23^23-29, 202.6.84.0/24^24-29, 202.12.70.0/24^24-29, 202.12.248.0/21^21-29, 202.14.100.0/24^24-29, 202.21.130.0/24^24-29, 202.21.136.0/23^23-29, 202.36.155.0/24^24-29, 202.36.157.0/24^24-29, 202.36.32.0/24^24-29, 202.36.36.0/22^22-29, 202.36.44.0/24^24-29, 202.36.45.0/24^24-29, 202.36.76.0/23^23-29, 202.37.136.0/24^24-29, 202.37.140.0/22^22-29, 202.37.144.0/21^21-29, 202.37.163.0/24^24-29, 202.37.197.0/24^24-29, 202.37.200.0/22^22-29, 202.37.224.0/21^21-29, 202.37.232.0/24^24-29, 202.37.240.0/23^23-29, 202.37.252.0/23^23-29, 202.37.76.0/24^24-29, 202.37.85.0/24^24-29, 202.41.136.0/22^22-29, 202.41.140.0/24^24-29, 202.49.62.0/24^24-29, 202.49.89.0/24^24-29, 202.49.249.0/24^24-29, 202.50.87.0/24^24-29, 202.50.246.0/24^24-29, 202.55.96.0/20^20-29, 202.74.224.0/21^21-29, 202.182.192.0/19^19-29, 205.233.128.0/21^21-29, 205.233.136.0/23^23-29, 205.233.243.0/24^24-29, 210.185.0.0/18^18-29, 210.48.0.0/17^17-29, 210.54.136.0/22^22-29, 210.54.140.0/24^24-29, 210.54.160.0/19^19-29, 210.55.182.0/23^23-29, 210.55.24.0/22^22-29, 210.55.253.0/24^24-29, 210.56.32.0/20^20-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: john(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050225 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS4770 descr: advertised to AS9560 by ICONZ - AS4770 members: 138.235.0.0/16^16-29, 192.107.113.0/24^24-29, 192.173.16.0/21^21-29, 198.32.66.0/24^24-29, 199.212.93.0/24^24-29, 202.6.84.0/24^24-29, 202.12.70.0/24^24-29, 202.12.248.0/21^21-29, 202.14.100.0/24^24-29, 202.20.6.0/24^24-29, 202.21.130.0/24^24-29, 202.21.136.0/23^23-29, 202.36.155.0/24^24-29, 202.36.157.0/24^24-29, 202.36.32.0/24^24-29, 202.36.36.0/22^22-29, 202.36.44.0/24^24-29, 202.36.45.0/24^24-29, 202.36.76.0/23^23-29, 202.36.119.0/24^24-29, 202.37.136.0/24^24-29, 202.37.140.0/22^22-29, 202.37.144.0/21^21-29, 202.37.163.0/24^24-29, 202.37.197.0/24^24-29, 202.37.200.0/22^22-29, 202.37.224.0/21^21-29, 202.37.232.0/24^24-29, 202.37.240.0/23^23-29, 202.37.252.0/23^23-29, 202.37.76.0/24^24-29, 202.37.85.0/24^24-29, 202.41.136.0/22^22-29, 202.41.140.0/24^24-29, 202.46.190.0/24^24-29, 202.49.62.0/24^24-29, 202.49.89.0/24^24-29, 202.49.249.0/24^24-29, 202.49.159.0/24^24-29, 202.50.87.0/24^24-29, 202.50.246.0/24^24-29, 202.55.96.0/20^20-29, 202.74.224.0/21^21-29, 202.78.240.0/23^23-29, 202.182.192.0/19^19-29, 205.233.128.0/21^21-29, 205.233.136.0/23^23-29, 205.233.243.0/24^24-29, 210.185.0.0/18^18-29, 210.48.0.0/17^17-29, 210.54.136.0/22^22-29, 210.54.140.0/24^24-29, 210.54.160.0/19^19-29, 210.55.182.0/23^23-29, 210.55.24.0/22^22-29, 210.55.253.0/24^24-29, 210.56.32.0/20^20-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: john(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050304 source: NZRR

1 0

The Impact of the Reworked TTL Field on Regional IP Allocations
by Jim Fleming 02 Mar '05

02 Mar '05

The Impact of the Reworked TTL Field on Regional IP Allocations The TTL Field (or Hop Count) is normally 8-bits wide. Some operating systems start it with a value of 255 (all 1s) and some with 64 and other smaller values. In order to improve services for broad-band users, there is a benefit in **reducing** the size of the TTL Field from 8-bits to 4-bits. That limits the maximum number of hops to 15. Equipment that auto-encapsulates can work around this by moving a packet a long distance and then removing a wrapper and allowing it to have some of the hops near the source and some near the destination. Reducing the TTL Field to 4-bits frees up 4-bits for address expansion. With two of those bits for the Source and two bits for the Destination, the entire legacy Internet plus three more equal size address spaces can be supported, without changing the existing protocol header size. One could view that as a planar Internet or a 4-story office building. Existing allocations of address space could all be viewed as from one plane or one could map regions to the 4 planes, allowing a region to expand to space used by another region because the extra bits prevent collisions and provide unique allocations. Another approach is to use the 4 planes for local networks, VPNs, a wireless extranet, and the legacy Internet (core). In a restricted approach only intra-plane traffic is allowed. A totally open approach would allow any node to address any other node. This would be like any location in the 4-story office being able to connect with any other, rather then be restricted to intra-floor-only connections. A more conservative approach is simply to zero the left-most 4 bits and reserve (save) the other three planes for future generations, once equipment is better able to route and process the reworked TTL Field. Current market trials and tests with broad-band-only subscribers will help to determine which approach has the most benefit. IP address allocations are already being red-lined for re-allocation and use in other planar nets because they can not be reached in 15 hops from/to certain regions of the world. Since there may not be any bandwidth to those regions anyway, it does not matter because the laws of physics will prevent broadband services from becoming available in one region with the same level of service observed in another region. Voice services are of course "the killer apps" and place great demands on the aging best-effort transports. As new equipment is provisioned it can be done with an awareness of the benefits of using a smaller TTL Field. Some might argue that 15 hops is stilll too many and one or two more bits should be removed leaving a 7 hop or a 3 hop limit. The 7 hop approach only frees up 1 more bit and it can be combined with the unused 49th bit to add another entire bit to both the source and destination fields. The 3 hop approach makes one look sooner at the needed equipment to bypass the aging legacy core. Having 6 added bits for addressing and 8 planar levels can have more long-term benefits and there can still be a short-term work-around because the 3-bits of the destination address field can be allowed to be processed by *existing* TTL algorithms and packets then transform their addressing as they pass thru the core network. The address bits can then be used to prioritize delivery by allowing packets that come from a long distance to be processed before those that come from closer locations. They appear to be going to different destinations by looking at the changed TTL value as an address. Since packets now travel greater distances with less decrements of the hop-count the 7 hop approach may be the best compromise. Eventually, the free-market place will decide. People can not make "governance" decisions based on 20 year old designs and how they are applied in regions of the world that have no bandwidth. That is the lowest-common-denominator approach advocated by The Big Lie Society. As people have seen, that prevents a nation from Running at the speed of light. Jim Fleming A.Net

4 3

Read-Only BLOB (packet) Additions to the IP Protocol
by Jim Fleming 02 Mar '05

02 Mar '05

Read-Only BLOB (packet) Additions to the IP Protocol An analysis of many packets of data show that the same binary content appears over and over. This is especially the case when a smaller and smaller size BLOB is considered. For example, a 512 byte (octet) BLOB contains 4096 bits (ones or zeroes) and there can be a large number of **unique** BLOBs, in fact, approximately (1.0443888814131525066917527107166e+1233). If users are able to create (own?) any number of the unique BLOBs and then place them in a public cache (library), then new broadband modems can pull those BLOBs in and attach them to packet headers. Since the BLOBS are read-only and never change, once created, they can each have their own IP address as the "source". The destination address is the end-user's system. One obvious BLOB is a 512 byte BLOB of all zeroes. Another obvious one is all ones. Those can be two of the possible BLOBS. If a 32-bit index (handle) is used to specify a unique BLOB, then there can be exactly 4,294,967,296. It might take several BLOBS to hold commonly communicated binary content. Also, several BLOBS may be needed if graphics/voice/sound is recorded vs. text. Compression can be allowed because the BLOB is just 512 bytes of arbitrary ones and zeroes. Also, careful attention to repetition in tones (like dial-tone in VOIP) can result in the same BLOB being used over and over with no clicks or gaps noticed between BLOBs. With that as a bit of an intro, no pun intended, some "Internet Governance" questions come to mind. 1. Who owns the content of the BLOBs ? 2. If it costs $1 dollar (OZ dollars) to "register" a unique BLOB who collects that $4,294,967,296 ? 3. How and where will the BLOBs be cached ? 4. Do the users really care where they come from as long as their broad-band system works "better" ? 5. Are people concerned that the same BLOB may appear over and over, creating boring content ? 6. Are people concerned that a small error could become part of a read-only archive and live for a long time ? 7. As a follow-on to #6, would another BLOB be allowed ? to fix that error ? 8. Is first-come-first-serve the best way to sell off the BLOBs? 9. Should existing archives and databases be encoded first ? at no charge ? 10. Once one BLOB address space is used up, should another be opened up ? 11. Will there be vanity-value in owning a BLOB ? Is the one-millionth BLOB special ? 12. Will BLOBs that can be compressed be favored ? 13. Should there be an age-limit to register a BLOB ? For the curious, the entire BLOB cache would be 2,199,023,255,552 bytes without compression. An ISP can cache the entire BLOB space and do inserts in the last mile of the broad-band connection. The broad-band "modem" can of course cache a working set of the most common BLOBs. Is this bit torrent at the IP level ? http://bittorrent.com/ Jim Fleming A.Net

3 2

ICONZ Prefix list update - 2005-03-03
by John Johnston 02 Mar '05

02 Mar '05

AS: 4770 APE: 192.203.154.44 WIX: 202.7.1.1 Hey all, For all those that peer with ICONZ here is yet another update. Current list is attached or goto http://www.iconz.net/prefix Regards John Johnston Network Engineering Manager ICONZ New Zealand Limited DDI: +64 9 977 3500 FAX: +64 9 977 3535 Mobile: 021 277 5692 Email: john.johnston(a)iconz.net 0800 THE NET www.iconz.net

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 02 Mar '05

02 Mar '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. The update causing these changes had the following mail headers: - From: Andy Linton <asjl(a)citylink.co.nz> - Cc: - Subject: - Date: Thu, 3 Mar 2005 13:21:39 +1300 (NZDT) - Msg-Id: <Pine.LNX.4.58.0503031320190.31409(a)jennings.citylink.co.nz> NZRR Database Notification Department --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS2687 descr: Route set advertised to AS9439 by AT&T Global - AS2687 members: 152.158.254.0/24^24-29, 152.158.255.0/24^24-29, 202.14.142.0/24^24-29, 202.27.160.0/24^24-29, 202.36.68.0/24^24-29, 202.36.69.0/24^24-29, 202.36.80.0/24^24-29, 202.36.195.0/24^24-29, 202.37.93.0/24^24-29, 202.37.254.0/24^24-29, 202.46.160.0/20^20-29, 202.49.144.0/24^24-29, 202.50.137.0/24^24-29, 202.135.20.0/24^24-29, 202.135.34.0/24^24-29, 202.135.38.0/24^24-29, 202.135.48.0/24^24-29, 202.135.49.0/24^24-29, 202.135.62.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.182.0/24^24-29, 202.135.185.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 203.163.68.0/24^24-29, 203.163.70.0/24^24-29, 203.163.71.0/24^24-29, 203.163.86.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.119.0/24^24-29, 219.88.103.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: greg.kapp(a)ap.att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050302 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS2687 descr: Route set advertised to AS9439 by AT&T Global - AS2687 members: 152.158.254.0/24^24-29, 152.158.255.0/24^24-29, 202.14.142.0/24^24-29, 202.27.160.0/24^24-29, 202.36.68.0/24^24-29, 202.36.69.0/24^24-29, 202.36.80.0/24^24-29, 202.36.195.0/24^24-29, 202.37.93.0/24^24-29, 202.37.254.0/24^24-29, 202.46.160.0/20^20-29, 202.49.144.0/24^24-29, 202.50.137.0/24^24-29, 202.135.20.0/24^24-29, 202.135.34.0/24^24-29, 202.135.38.0/24^24-29, 202.135.48.0/24^24-29, 202.135.49.0/24^24-29, 202.135.62.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.182.0/24^24-29, 202.135.185.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 203.163.68.0/24^24-29, 203.163.70.0/24^24-29, 203.163.71.0/24^24-29, 203.163.86.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.119.0/24^24-29, 219.88.103.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: attnzdns(a)ap.att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050303 source: NZRR

1 0

RE: [nznog] VON anyone?
by Mark Frater 02 Mar '05

02 Mar '05

Ahh flames... Spin.. Crash.. Burn.. Die.. Before the flames grow higher, humble apologies for html.. etc. < does no sig on this one make up for it?> --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com) Version: 6.0.775 / Virus Database: 522 - Release Date: 8/10/2004

1 0

VON anyone?
by Mark Frater 02 Mar '05

02 Mar '05

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 01 Mar '05

01 Mar '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. The update causing these changes had the following mail headers: - From: Andy Linton <asjl(a)citylink.co.nz> - Cc: - Subject: RE: [CityLink #1983] AutoReply: Routing updates for APE Route Servers (fwd) - Date: Wed, 2 Mar 2005 20:02:24 +1300 (NZDT) - Msg-Id: <Pine.LNX.4.58.0503022001510.30819(a)jennings.citylink.co.nz> NZRR Database Notification Department --- PREVIOUS OBJECT: route-set: AS9560:rs-routes:AS9889 descr: Route set for AS9889 members: 202.14.217.0/24, 202.27.204.0/24, 202.36.70.0/24, 202.37.72.0/24, 202.37.181.0/24, 202.50.167.0/24, 202.89.32.0/19^19-24, 210.55.29.0/24, 210.55.100.0/22^22-24, 210.55.104.0/22^22-24, 210.55.110.0/24, 210.55.155.0/24, 210.55.169.0/24, 210.55.214.0/24, 210.55.230.0/24 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: alastair.johnson(a)maxnet.co.nz notify: nznog(a)list.waikato.ac.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20031016 changed: rpsl-admin(a)nzix.net 20041008 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9889 descr: advertised to AS9560 by Maxnet - AS9889 members: 210.55.230.0/24^24-29, 210.55.214.0/24^24-29, 210.55.169.0/24^24-29, 210.55.155.0/24^24-29, 210.55.104.0/22^22-29, 210.55.100.0/22^22-29, 202.37.181.0/24^24-29, 202.37.72.0/24^24-29, 202.36.70.0/24^24-29, 202.27.204.0/24^24-29, 202.89.32.0/19^19-29, 202.6.5.0/24^24-29, 202.49.141.0/24^24-29, 203.89.160.0/19^19-29, 202.7.5.32/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: david.fox(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050302 source: NZRR --- PREVIOUS OBJECT: route: 210.55.230.0/24 descr: Route for Maxnet - AS9889 origin: AS9889 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: alastair.johnson(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041008 source: NZRR REPLACED BY: route: 210.55.230.0/24 descr: Route for Maxnet - AS9889 origin: AS9889 notify: rpsl-admin(a)nzix.net notify: david.fox(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050302 source: NZRR --- PREVIOUS OBJECT: route: 210.55.214.0/24 descr: Route for Maxnet - AS9889 origin: AS9889 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: alastair.johnson(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041008 source: NZRR REPLACED BY: route: 210.55.214.0/24 descr: Route for Maxnet - AS9889 origin: AS9889 notify: rpsl-admin(a)nzix.net notify: david.fox(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050302 source: NZRR --- PREVIOUS OBJECT: route: 210.55.169.0/24 descr: Route for Maxnet - AS9889 origin: AS9889 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: alastair.johnson(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041008 source: NZRR REPLACED BY: route: 210.55.169.0/24 descr: Route for Maxnet - AS9889 origin: AS9889 notify: rpsl-admin(a)nzix.net notify: david.fox(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050302 source: NZRR --- PREVIOUS OBJECT: route: 210.55.155.0/24 descr: Route for Maxnet - AS9889 origin: AS9889 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: alastair.johnson(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041008 source: NZRR REPLACED BY: route: 210.55.155.0/24 descr: Route for Maxnet - AS9889 origin: AS9889 notify: rpsl-admin(a)nzix.net notify: david.fox(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050302 source: NZRR --- PREVIOUS OBJECT: route: 210.55.104.0/22 descr: Route for Maxnet - AS9889 origin: AS9889 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: alastair.johnson(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041008 source: NZRR REPLACED BY: route: 210.55.104.0/22 descr: Route for Maxnet - AS9889 origin: AS9889 notify: rpsl-admin(a)nzix.net notify: david.fox(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050302 source: NZRR --- PREVIOUS OBJECT: route: 210.55.100.0/22 descr: Route for Maxnet - AS9889 origin: AS9889 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: alastair.johnson(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041008 source: NZRR REPLACED BY: route: 210.55.100.0/22 descr: Route for Maxnet - AS9889 origin: AS9889 notify: rpsl-admin(a)nzix.net notify: david.fox(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050302 source: NZRR --- PREVIOUS OBJECT: route: 202.37.181.0/24 descr: Route for Maxnet - AS9889 origin: AS9889 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: alastair.johnson(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041008 source: NZRR REPLACED BY: route: 202.37.181.0/24 descr: Route for Maxnet - AS9889 origin: AS9889 notify: rpsl-admin(a)nzix.net notify: david.fox(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050302 source: NZRR --- PREVIOUS OBJECT: route: 202.37.72.0/24 descr: Route for Maxnet - AS9889 origin: AS9889 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: alastair.johnson(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041008 source: NZRR REPLACED BY: route: 202.37.72.0/24 descr: Route for Maxnet - AS9889 origin: AS9889 notify: rpsl-admin(a)nzix.net notify: david.fox(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050302 source: NZRR --- PREVIOUS OBJECT: route: 202.36.70.0/24 descr: Route for Maxnet - AS9889 origin: AS9889 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: alastair.johnson(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041008 source: NZRR REPLACED BY: route: 202.36.70.0/24 descr: Route for Maxnet - AS9889 origin: AS9889 notify: rpsl-admin(a)nzix.net notify: david.fox(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050302 source: NZRR --- PREVIOUS OBJECT: route: 202.27.204.0/24 descr: Route for Maxnet - AS9889 origin: AS9889 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: alastair.johnson(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041008 source: NZRR REPLACED BY: route: 202.27.204.0/24 descr: Route for Maxnet - AS9889 origin: AS9889 notify: rpsl-admin(a)nzix.net notify: david.fox(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050302 source: NZRR --- PREVIOUS OBJECT: route: 202.89.32.0/19 descr: Route for Maxnet - AS9889 origin: AS9889 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: alastair.johnson(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041008 source: NZRR REPLACED BY: route: 202.89.32.0/19 descr: Route for Maxnet - AS9889 origin: AS9889 notify: rpsl-admin(a)nzix.net notify: david.fox(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050302 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 01 Mar '05

01 Mar '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. --- PREVIOUS OBJECT: aut-num: AS3856 as-name: NZRR-AS3856 descr: PCH2 descr: APE peering at '192.203.154.253' descr: see Citylink RT job #1924 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9560 accept ANY AND NOT fltr-bogons export: to AS9560 announce AS3856 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: scg(a)pch.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050302 source: NZRR REPLACED BY: aut-num: AS3856 as-name: NZRR-AS3856 descr: PCH2 descr: APE peering at '192.203.154.254' descr: see Citylink RT job #1924 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9560 accept ANY AND NOT fltr-bogons export: to AS9560 announce AS3856 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: scg(a)pch.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050302 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 01 Mar '05

01 Mar '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS3856 descr: advertised to AS9560 by Packet Clearing House - AS3856 members: 192.36.148.0/24^24-29, 194.146.106.0/24^24-29, 194.146.107.0/24^24-29, 194.146.108.0/24^24-29, 199.7.77.0/24^24-29, 199.7.64.0/24^24-29, 204.61.210.0/24^24-29, 204.61.210.0/23^23-29, 204.61.212.0/23^23-29, 204.61.216.0/23^23-29, 206.220.228.0/22^22-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: scg(a)pch.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050302 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS3856 descr: Route set advertised to AS9560 by PCH2 - AS3856 members: 192.36.148.0/24^24-29, 194.146.106.0/24^24-29, 194.146.107.0/24^24-29, 194.146.108.0/24^24-29, 199.7.77.0/24^24-29, 199.7.64.0/24^24-29, 204.61.210.0/24^24-29, 204.61.210.0/23^23-29, 204.61.212.0/23^23-29, 204.61.216.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: scg(a)pch.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050302 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 01 Mar '05

01 Mar '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS42 descr: advertised to AS9560 by Packet Clearing House - AS42 members: 192.36.148.0/24^24-29, 194.146.106.0/24^24-29, 194.146.107.0/24^24-29, 194.146.108.0/24^24-29, 199.7.77.0/24^24-29, 199.7.64.0/24^24-29, 204.61.210.0/24^24-29, 204.61.210.0/23^23-29, 204.61.212.0/23^23-29, 204.61.216.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: scg(a)pch.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050302 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS42 descr: Route set advertised to AS9560 by PCH1 - AS42 members: 192.36.148.0/24^24-29, 194.146.106.0/24^24-29, 194.146.107.0/24^24-29, 194.146.108.0/24^24-29, 199.7.77.0/24^24-29, 199.7.64.0/24^24-29, 204.61.210.0/24^24-29, 204.61.210.0/23^23-29, 204.61.212.0/23^23-29, 204.61.216.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: scg(a)pch.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050302 source: NZRR

1 0

Spam levels in the last 24 hours?
by neil gardner 01 Mar '05

01 Mar '05

Hi guys - Has anyone else noticed a huge increase in Spam levels in the last 24 or so hours? This is only from 2-3 accounts on 2 ISPs (Orcon and Paradise), but I have gone from seeing 1-2 per day to about 30 making it past the (ISP based) filters in the last 24 hours. Interested to hear from mail admins as to whether this is just me being unlucky, or if there's something screwy happening here... Cheers - Neil G NOTICE: This message contains privileged and confidential information intended only for the use of the addressee named above. If you are not the intended recipient of this message you are hereby notified that you must not disseminate, copy or take any action in reliance on it. If you have received this message in error please notify Allied Telesyn Research Ltd immediately. Any views expressed in this message are those of the individual sender, except where the sender has the authority to issue and specifically states them to be the views of Allied Telesyn Research.

5 6

Notification of NZRR Database changes
by NZRR Database Notifications 01 Mar '05

01 Mar '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. The update causing these changes had the following mail headers: - From: Andy Linton <asjl(a)citylink.co.nz> - Cc: - Subject: - Date: Wed, 2 Mar 2005 18:56:43 +1300 (NZDT) - Msg-Id: <Pine.LNX.4.58.0503021854360.30667(a)jennings.citylink.co.nz> NZRR Database Notification Department --- OBJECT BELOW CREATED: route-set: AS9560:RS-ROUTES:AS42 descr: advertised to AS9560 by Packet Clearing House - AS42 members: 192.36.148.0/24^24-29, 194.146.106.0/24^24-29, 194.146.107.0/24^24-29, 194.146.108.0/24^24-29, 199.7.77.0/24^24-29, 199.7.64.0/24^24-29, 204.61.210.0/24^24-29, 204.61.210.0/23^23-29, 204.61.212.0/23^23-29, 204.61.216.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: scg(a)pch.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050302 source: NZRR --- OBJECT BELOW CREATED: route-set: AS9560:RS-ROUTES:AS3856 descr: advertised to AS9560 by Packet Clearing House - AS3856 members: 192.36.148.0/24^24-29, 194.146.106.0/24^24-29, 194.146.107.0/24^24-29, 194.146.108.0/24^24-29, 199.7.77.0/24^24-29, 199.7.64.0/24^24-29, 204.61.210.0/24^24-29, 204.61.210.0/23^23-29, 204.61.212.0/23^23-29, 204.61.216.0/23^23-29, 206.220.228.0/22^22-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: scg(a)pch.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050302 source: NZRR

1 0

Peering exchange in the Wairarapa?
by Blair Harrison 01 Mar '05

01 Mar '05

Hi Guys, I'm just wondering if there is any interest at all in having a peering exchange of some kind in the Wairarapa. I know I've been thinking about such a beast for a while, but at the moment there's only a couple of ISP-like entities (that I know of) who might possibly be interested. WISE Net would be happy to house such a beast if it could be shown that there was sufficient interest, although I'm not sure we're exactly what you might call neutral territory :) So really what I'm asking is, is there anyone else out there? Do you want to peer with us? With others? Have you got a network you want to connect to others with in the Wairarapa at a central place? Raise your hands now, or forever shall your cat5 be under-utilised :) Cheers, Blair Harrison Systems Administrator WISE Net | http://wise.net.nz

4 3

I-Root Server avaiable at the WIX
by Andy Linton 28 Feb '05

28 Feb '05

There is now an instance of an anycast I-Root name server attached to the WIX. Those peering with the WIX route servers should be seeing an announcment for 192.36.148.0/24. From Wellington I'm seeing RTTs like this: $ ping 192.36.148.17 PING 192.36.148.17 (192.36.148.17) 56(84) bytes of data. 64 bytes from 192.36.148.17: icmp_seq=1 ttl=252 time=3.90 ms 64 bytes from 192.36.148.17: icmp_seq=2 ttl=252 time=1.12 ms 64 bytes from 192.36.148.17: icmp_seq=3 ttl=252 time=1.73 ms 64 bytes from 192.36.148.17: icmp_seq=4 ttl=252 time=2.07 ms 64 bytes from 192.36.148.17: icmp_seq=5 ttl=252 time=1.18 ms 64 bytes from 192.36.148.17: icmp_seq=6 ttl=252 time=1.62 ms 64 bytes from 192.36.148.17: icmp_seq=7 ttl=252 time=1.80 ms 64 bytes from 192.36.148.17: icmp_seq=8 ttl=252 time=1.92 ms 64 bytes from 192.36.148.17: icmp_seq=9 ttl=252 time=1.43 ms --- 192.36.148.17 ping statistics --- 9 packets transmitted, 9 received, 0% packet loss, time 8080ms rtt min/avg/max/mdev = 1.125/1.867/3.905/0.782 ms and from a host in Auckland which doesn't see the announcement I see: $ ping 192.36.148.17 PING 192.36.148.17 (192.36.148.17): 56 data bytes 64 bytes from 192.36.148.17: icmp_seq=0 ttl=55 time=257.7 ms 64 bytes from 192.36.148.17: icmp_seq=1 ttl=55 time=255.9 ms 64 bytes from 192.36.148.17: icmp_seq=2 ttl=55 time=255.9 ms 64 bytes from 192.36.148.17: icmp_seq=3 ttl=55 time=256.8 ms 64 bytes from 192.36.148.17: icmp_seq=4 ttl=55 time=256.2 ms 64 bytes from 192.36.148.17: icmp_seq=5 ttl=55 time=257.9 ms 64 bytes from 192.36.148.17: icmp_seq=6 ttl=55 time=259.5 ms 64 bytes from 192.36.148.17: icmp_seq=7 ttl=55 time=256.5 ms 64 bytes from 192.36.148.17: icmp_seq=8 ttl=55 time=257.2 ms --- 192.36.148.17 ping statistics --- 9 packets transmitted, 9 packets received, 0% packet loss round-trip min/avg/max = 255.9/257.0/259.5 ms Thanks to InternetNZ who funded this and to Packet Clearing House and Autonomica for making it happen. Enjoy!

9 13

RE: [nznog] I-Root Server avaiable at the WIX
by Matt Mariu 28 Feb '05

28 Feb '05

I sort of came along late in the 'news' game when the Major Telco's decided to de-peer.. To that effect, Does anyone out there have a solid explanation from them as to why they chose to do what they Did ? Joe, You used to work @ Clear.. Surely you have inside knowledge :) Sorry if this is old news, if theres a link, post it please. -----Original Message----- From: Keith Davidson [mailto:keith(a)wise.net.nz] Sent: Tuesday, 1 March 2005 14:19 To: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] I-Root Server avaiable at the WIX Hmmm, so the aberrant nature of peering in NZ rears its ugly head... Seems strange that the telcos would prefer to route offshore at a financial and a performance cost, rather than peer in NZ and give their users faster speeds and cost reductions... Keith Davidson

2 1

RE: [nznog] I-Root Server avaiable at the WIX
by neil gardner 28 Feb '05

28 Feb '05

>But it still says on Paradises website: > >Citylink Traffic is calculated in the same way as JetStart Traffic, with the >exception of traffic delivered through the Wellington Internet Exchange >(WIX), which is completely free! And there's nothing inaccurate about that is there? They just don't send any more traffic over WIX - but if they did - it would be free. :-) Anyway, good to see they aren't letting elegant solutions get in the way of MORE MONEY!!! Cheers - N. NOTICE: This message contains privileged and confidential information intended only for the use of the addressee named above. If you are not the intended recipient of this message you are hereby notified that you must not disseminate, copy or take any action in reliance on it. If you have received this message in error please notify Allied Telesyn Research Ltd immediately. Any views expressed in this message are those of the individual sender, except where the sender has the authority to issue and specifically states them to be the views of Allied Telesyn Research.

1 0

IPv6 national peering
by Leigh Smith 27 Feb '05

27 Feb '05

Hi all Just to let the people that are interested in IPv6 WorldxChange are now peered at the APE a second peer point will be available soon 2001:7fa:4:c0cb::9a03 AS 17435 Regards Leigh

1 0

IPV6, Cisco
by Philip D'Ath 27 Feb '05

27 Feb '05

After much torment this weekend I have managed to get IPv6 running nicely on a low end Cisco DSL router (Cisco 837). If anyone wants an IPv6 connection at home (and a /48 block of real world IPv6 address space) to experiment with, say yourself some grief and start with this. http://www.ifm.net.nz/cookbooks/ipv6configwizard.html Now if we can just get a critical mass of users we might be able to tempt an ISP to offer native connections ... and actually use Joe's IPv6 F root server.

1 0

RE: [nznog] IPv6, NAT-PT
by Philip D'Ath 26 Feb '05

26 Feb '05

I'm talking about using NAT-PT to allow a native ipv6 network to talk to an ipv4 network. Without some kind of protocol translation (aka PT) ipv6 can't talk to ipv4. The reason this has to be done is because you can't buy an ipv6 connection to an ISP in NZ yet. -----Original Message----- From: Cameron Kerr [mailto:cameron(a)humbledown.org] Sent: Saturday, 26 February 2005 2:27 p.m. To: Philip D'Ath Cc: nznog Subject: Re: [nznog] IPv6, NAT-PT On 26/02/2005, at 1:25 PM, Philip D'Ath wrote: > I'm trying to get NAT-PT support working on a Cisco DSL router to > support native ipv6 clients behind it. I've done a lot of searching, > and can't find the answers to what I'm doing wrong. I have two > problems. Why are you using NAT with IPv6? There is very little reason pros for using IPv6 with NAT, and many cons. Afterall, NAT is just a hack for IPv4 to prevent address exhaustion. IIRC, ISPs are not to give out single IP addresses, but rather /64 allocations. Anyone care to correct me on this? -- Cameron Kerr Telecommunications Teaching Fellow & SysAdmin ckerr(a)cs.otago.ac.nz

7 15

Paradise bouncing emails?
by PhoneNet 25 Feb '05

25 Feb '05

Anyone else getting complaints from customers re email destined for Paradise accounts being bounced? Ian

3 2

RE: [nznog] IPv6, NAT-PT
by Philip D'Ath 25 Feb '05

25 Feb '05

I'm not wishing to get access to ipv6 content at this stage (but will of course eventually want to do this). I'm wanting to start using ipv6 internally. Once we are using it, I'll probably start some of our clients using it later this year. Once enough people are using it hopefully some ISP will start offering native ipv6 connections, because they will have a business case to do so. Hence, the desire to use NAT-PT, otherwise I'll be stuck running dual stacks. -----Original Message----- From: Joe Abley [mailto:jabley(a)isc.org] Sent: Saturday, 26 February 2005 4:57 p.m. To: Philip D'Ath Cc: nznog; Cameron Kerr Subject: Re: [nznog] IPv6, NAT-PT On 25 Feb 2005, at 20:39, Philip D'Ath wrote: > I'm talking about using NAT-PT to allow a native ipv6 network to talk > to an ipv4 network. Without some kind of protocol translation (aka > PT) > ipv6 can't talk to ipv4. The reason this has to be done is because > you can't buy an ipv6 connection to an ISP in NZ yet. Most people running v6 are only using their v6 access to reach content served over v6. Most of the mechanisms suggested to allow a v6-only host to access v4 content remain undeployed. If you want to reach v6 content, the easiest thing to do is find an ISP who can give you v6 transit. In the absense of local carriers with dual-stack edge routers (i.e. in the case of most of the planet) the way you do this is terminate a tunnel somewhere. Joe

1 0

IPv6, NAT-PT
by Philip D'Ath 25 Feb '05

25 Feb '05

I'm trying to get NAT-PT support working on a Cisco DSL router to support native ipv6 clients behind it. I've done a lot of searching, and can't find the answers to what I'm doing wrong. I have two problems. First, I can't get them to grab additional parameters from DHCP. I'm using: ipv6 dhcp pool dhcppool dns-server ::210.55.12.1 - I know the above is not likely to answer AAAA requests, but I plan to use DNS-ALG domain-name local.arpa Interface Ethernet0 ipv6 enable ipv6 nd other-config-flag ipv6 dhcp server dhcppool The second problem is I can't NAT-PT to work at all. It doesn't even attempt to do translations. Snippits I'm using are: Interface Dialer0 description ipv4 Interface connecting to Internet ipv6 nat Interface Ethernet0 description ipv6 Interface connection to local lan (aka LINK-LOCAL) ipv6 address 3FFE:AAAA:BBBB:1::9/64 - An address copied from an example, hope to use LINK-LOCAL addresses later ipv6 enable ipv6 nat ipv6 nat translation udp-timeout 600 ipv6 nat v6v4 source list pt-list1 interface Dialer0 overload ipv6 nat prefix 3FFE:B00:1::/96 ipv6 access-list pt-list1 permit ipv6 3FFE:AAAA:BBBB:1::/64 any

3 2

Notification of NZRR Database changes
by NZRR Database Notifications 24 Feb '05

24 Feb '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. The update causing these changes had the following mail headers: - From: Andy Linton <asjl(a)citylink.co.nz> - Cc: - Subject: [CityLink #1958] Routing updates for WIX Route Servers (fwd) - Date: Fri, 25 Feb 2005 17:41:59 +1300 (NZDT) - Msg-Id: <Pine.LNX.4.58.0502251727510.24165(a)jennings.citylink.co.nz> NZRR Database Notification Department --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS18119 descr: advertised to AS9439 by LinuxNet - AS18119 members: 192.107.113.0/24^24-29, 202.7.4.80/29, 202.21.136.0/23^23-29, 202.36.44.0/24^24-29, 202.37.136.0/24^24-29, 202.49.249.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: lincoln(a)linuxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050222 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS18119 descr: advertised to AS9439 by LinuxNet - AS18119 members: 192.107.113.0/24^24-29, 202.7.4.80/29, 202.7.6.32/28^28-29, 202.21.136.0/23^23-29, 202.36.44.0/24^24-29, 202.37.136.0/24^24-29, 202.49.249.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: lincoln(a)linuxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050225 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 24 Feb '05

24 Feb '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. The update causing these changes had the following mail headers: - From: Andy Linton <asjl(a)citylink.co.nz> - Cc: - Subject: [CityLink #1951] Routing updates for APE Route Servers (fwd) - Date: Fri, 25 Feb 2005 16:57:10 +1300 (NZDT) - Msg-Id: <Pine.LNX.4.58.0502251654230.24165(a)jennings.citylink.co.nz> NZRR Database Notification Department --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS4770 descr: Route set for AS4770 members: 138.235.0.0/16, 192.107.113.0/24, 192.173.16.0/21, 198.32.66.0/24, 199.212.90.0/23, 199.212.92.0/23^23-24, 202.6.84.0/24, 202.12.70.0/24, 202.12.248.0/21, 202.14.100.0/24, 202.21.130.0/24, 202.21.136.0/23, 202.36.155.0/24, 202.36.157.0/24, 202.36.32.0/24, 202.36.36.0/22, 202.36.44.0/24, 202.36.45.0/24, 202.36.76.0/23, 202.37.136.0/24, 202.37.140.0/22, 202.37.144.0/21, 202.37.163.0/24, 202.37.197.0/24, 202.37.200.0/22, 202.37.224.0/21, 202.37.232.0/24, 202.37.240.0/23, 202.37.252.0/23, 202.37.76.0/24, 202.37.85.0/24, 202.41.136.0/22, 202.41.140.0/24, 202.49.62.0/24, 202.49.89.0/24, 202.49.249.0/24, 202.50.87.0/24, 202.50.246.0/24, 202.55.96.0/20, 202.74.224.0/21, 203.9.179.0/24, 203.9.180.0/24, 205.233.128.0/21, 205.233.136.0/23, 205.233.243.0/24, 210.185.0.0/18, 210.48.0.0/17, 210.54.136.0/22, 210.54.140.0/24, 210.54.160.0/19, 210.55.182.0/23, 210.55.24.0/22, 210.55.253.0/24, 210.56.32.0/20 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: john.johnston(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20030407 changed: rpsl-admin(a)nzix.net 20040629 changed: rpsl-admin(a)nzix.net 20040831 changed: rpsl-admin(a)nzix.net 20040930 changed: rpsl-admin(a)nzix.net 20050224 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS4770 descr: advertised to AS9560 by ICONZ - AS4770 members: 138.235.0.0/16^16-29, 192.107.113.0/24^24-29, 192.173.16.0/21^21-29, 198.32.66.0/24^24-29, 199.212.90.0/23^23-29, 199.212.92.0/23^23-29, 202.6.84.0/24^24-29, 202.12.70.0/24^24-29, 202.12.248.0/21^21-29, 202.14.100.0/24^24-29, 202.21.130.0/24^24-29, 202.21.136.0/23^23-29, 202.36.155.0/24^24-29, 202.36.157.0/24^24-29, 202.36.32.0/24^24-29, 202.36.36.0/22^22-29, 202.36.44.0/24^24-29, 202.36.45.0/24^24-29, 202.36.76.0/23^23-29, 202.37.136.0/24^24-29, 202.37.140.0/22^22-29, 202.37.144.0/21^21-29, 202.37.163.0/24^24-29, 202.37.197.0/24^24-29, 202.37.200.0/22^22-29, 202.37.224.0/21^21-29, 202.37.232.0/24^24-29, 202.37.240.0/23^23-29, 202.37.252.0/23^23-29, 202.37.76.0/24^24-29, 202.37.85.0/24^24-29, 202.41.136.0/22^22-29, 202.41.140.0/24^24-29, 202.49.62.0/24^24-29, 202.49.89.0/24^24-29, 202.49.249.0/24^24-29, 202.50.87.0/24^24-29, 202.50.246.0/24^24-29, 202.55.96.0/20^20-29, 202.74.224.0/21^21-29, 202.182.192.0/19^19-29, 205.233.128.0/21^21-29, 205.233.136.0/23^23-29, 205.233.243.0/24^24-29, 210.185.0.0/18^18-29, 210.48.0.0/17^17-29, 210.54.136.0/22^22-29, 210.54.140.0/24^24-29, 210.54.160.0/19^19-29, 210.55.182.0/23^23-29, 210.55.24.0/22^22-29, 210.55.253.0/24^24-29, 210.56.32.0/20^20-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: john(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050225 source: NZRR --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS4770 descr: Route set for AS4770 members: 138.235.0.0/16, 192.107.113.0/24, 192.173.16.0/21, 198.32.66.0/24, 199.212.90.0/23, 199.212.92.0/23^23-24, 202.6.84.0/24, 202.12.70.0/24, 202.12.248.0/21, 202.14.100.0/24, 202.21.130.0/24, 202.21.136.0/23, 202.36.155.0/24, 202.36.157.0/24, 202.36.32.0/24, 202.36.36.0/22, 202.36.44.0/24, 202.36.45.0/24, 202.36.76.0/23, 202.37.136.0/24, 202.37.140.0/22, 202.37.144.0/21, 202.37.163.0/24, 202.37.197.0/24, 202.37.200.0/22, 202.37.224.0/21, 202.37.232.0/24, 202.37.240.0/23, 202.37.252.0/23, 202.37.76.0/24, 202.37.85.0/24, 202.41.136.0/22, 202.41.140.0/24, 202.49.62.0/24, 202.49.89.0/24, 202.49.249.0/24, 202.50.87.0/24, 202.50.246.0/24, 202.55.96.0/20, 202.74.224.0/21, 203.9.179.0/24, 203.9.180.0/24, 205.233.128.0/21, 205.233.136.0/23, 205.233.243.0/24, 210.185.0.0/18, 210.48.0.0/17, 210.54.136.0/22, 210.54.140.0/24, 210.54.160.0/19, 210.55.182.0/23, 210.55.24.0/22, 210.55.253.0/24, 210.56.32.0/20 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: john.johnston(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20030407 changed: rpsl-admin(a)nzix.net 20040629 changed: rpsl-admin(a)nzix.net 20040831 changed: rpsl-admin(a)nzix.net 20040930 changed: rpsl-admin(a)nzix.net 20050224 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS4770 descr: advertised to AS9439 by ICONZ - AS4770 members: 138.235.0.0/16^16-29, 192.107.113.0/24^24-29, 192.173.16.0/21^21-29, 198.32.66.0/24^24-29, 199.212.90.0/23^23-29, 199.212.92.0/23^23-29, 202.6.84.0/24^24-29, 202.12.70.0/24^24-29, 202.12.248.0/21^21-29, 202.14.100.0/24^24-29, 202.21.130.0/24^24-29, 202.21.136.0/23^23-29, 202.36.155.0/24^24-29, 202.36.157.0/24^24-29, 202.36.32.0/24^24-29, 202.36.36.0/22^22-29, 202.36.44.0/24^24-29, 202.36.45.0/24^24-29, 202.36.76.0/23^23-29, 202.37.136.0/24^24-29, 202.37.140.0/22^22-29, 202.37.144.0/21^21-29, 202.37.163.0/24^24-29, 202.37.197.0/24^24-29, 202.37.200.0/22^22-29, 202.37.224.0/21^21-29, 202.37.232.0/24^24-29, 202.37.240.0/23^23-29, 202.37.252.0/23^23-29, 202.37.76.0/24^24-29, 202.37.85.0/24^24-29, 202.41.136.0/22^22-29, 202.41.140.0/24^24-29, 202.49.62.0/24^24-29, 202.49.89.0/24^24-29, 202.49.249.0/24^24-29, 202.50.87.0/24^24-29, 202.50.246.0/24^24-29, 202.55.96.0/20^20-29, 202.74.224.0/21^21-29, 202.182.192.0/19^19-29, 205.233.128.0/21^21-29, 205.233.136.0/23^23-29, 205.233.243.0/24^24-29, 210.185.0.0/18^18-29, 210.48.0.0/17^17-29, 210.54.136.0/22^22-29, 210.54.140.0/24^24-29, 210.54.160.0/19^19-29, 210.55.182.0/23^23-29, 210.55.24.0/22^22-29, 210.55.253.0/24^24-29, 210.56.32.0/20^20-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: john(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050225 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 24 Feb '05

24 Feb '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. The update causing these changes had the following mail headers: - From: Andy Linton <asjl(a)citylink.co.nz> - Cc: - Subject: - Date: Fri, 25 Feb 2005 11:03:24 +1300 (NZDT) - Msg-Id: <Pine.LNX.4.58.0502251102510.23787(a)jennings.citylink.co.nz> NZRR Database Notification Department --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS23754 descr: advertised to AS9560 by Citylink - AS23754 members: 198.48.0.0/22^22-24, 202.8.44.0/22^22-24, 202.7.5.0/24, 202.7.7.0/24, 203.118.144.0/24 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041029 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS23754 descr: advertised to AS9560 by Citylink - AS23754 members: 198.48.0.0/22^22-24, 202.8.44.0/22^22-24, 202.7.5.0/24, 202.7.6.0/24, 203.118.144.0/24 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041029 source: NZRR

1 0

Email hammering from mta20X-rme.xtra.co.nz
by Simon Buchanan 24 Feb '05

24 Feb '05

Hi there, im wondering if anyone could point me in the rite direction here. Starting last night we have been hammered by xtra's mail servers from the email address haggis(a)guard.co.nz... Has any body on the list had simlar problems... How can i follow this up? Suggestions please :) Regards, Simon

3 2

RE: [nznog] (OT) Fax spam (Anti-spam legislation update)
by Regan Murphy 24 Feb '05

24 Feb '05

>You will need: > >* An older fax machine that scans the document slowly as it sends it >* A vivid marker >* Some sellotape This is the age of technology. Surely a few lines of code, a modem and some fax protocols could achieve the same result. Maybe you could even redirect your email spam junk folders to your fax spammer to give it a nice twist. ;) -- Regan

2 1

RE: [nznog] Anti-spam legislation update
by Jonathan Woolley 24 Feb '05

24 Feb '05

> The bill will apply to e-mails, text messaging and instant messaging > requiring that senders of multiple commercial electronic marketing > messages only send them to people who have agreed to get them. Senders > of promotional electronic messages will be required to stop sending > messages if recipients decide to opt out. Won't this result in most people getting more spam? 1. Spammer sends spam 2. You 'opt-out' 3. He tells his 20 spam buddies (who may or may not be in NZ and come under fancy new law) that it's an active email address with a real person at the other end 4. His 20 spam buddies give you 20 times the spam Even worse: 1. International spammer sends spam looking like it comes from NZ 2. Joe public 'opts-out' 3. International spammer spams twice as hard and tells his buddies Or am I missing something???

4 5

TelstraClear to disconnect from WIX route servers
by Dean Pemberton 23 Feb '05

23 Feb '05

At around 1100 today. TelstraClear (AS7714 and AS4768) will disconnect from the WIX route servers. Technical queries should be directed at the TelstraClear Customer Help team (0508 555 500) or to your normal fault escalation point. Business queries should be directed to your TelstraClear account manager. Thanks Dean Pemberton

9 9

ICONZ prefix-list update
by John Johnston 23 Feb '05

23 Feb '05

AS: 4770 APE: 192.203.154.44 WIX: 202.7.1.1 Hey all, For all those that peer with ICONZ here is an update. There has been a few adds and removes so please overwrite existing prefix list. Current list is attached or goto http://www.iconz.net/prefix Regards John Johnston Network Engineering Manager ICONZ New Zealand Limited DDI: +64 9 977 3500 FAX: +64 9 977 3535 Mobile: 021 277 5692 Email: john.johnston(a)iconz.net 0800 THE NET www.iconz.net

1 0

who wants some v6 APE action
by Joe Abley 23 Feb '05

23 Feb '05

ISC/F-Root are now live on the APE with IPv6: AS 23710 2001:7fa:4:c0cb::9a62 2001:7fa:4:c0cb::9a63 http://www.isc.org/peering We'll be advertising 2001:500::/48, the F-root prefix [*]. The corresponding AAAA record for F (2001:500::1035) is not in the root zone, yet, so this can be considered pre-production at this time. An application to add the AAAA record is pending with the IANA, however. If anybody would like to set up a native v6 session over the APE, we would be very pleased to peer. We are already peering with the Citylink v6ix route server at the APE, and so people peering with that (or with its counterpart at the WIX) should be able to see us with no additional work [*]. Many thanks to Juniper for their continued support of F in New Zealand: http://www.juniper.net/company/presscenter/pr/2005/pr-050208.html I wonder how many spam filters are going to object to "v6 APE action". [*] the network bits are done; 2001:500::/48 won't actually propagate until the servers have finished their v6alisation, which should happen in the next day or so.

6 10

Notification of NZRR Database changes
by NZRR Database Notifications 23 Feb '05

23 Feb '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. The update causing these changes had the following mail headers: - From: Andy Linton <asjl(a)citylink.co.nz> - Cc: - Subject: - Date: Thu, 24 Feb 2005 10:22:08 +1300 (NZDT) - Msg-Id: <Pine.LNX.4.58.0502241021280.22349(a)jennings.citylink.co.nz> NZRR Database Notification Department --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS4770 descr: Route set for AS4770 members: 138.235.0.0/16, 192.107.113.0/24, 192.173.16.0/21, 198.32.66.0/24, 199.212.90.0/23, 199.212.92.0/23^23-24, 202.6.84.0/24, 202.12.70.0/24, 202.12.248.0/21, 202.14.100.0/24, 202.21.130.0/24, 202.21.136.0/23, 202.36.155.0/24, 202.36.157.0/24, 202.36.32.0/24, 202.36.36.0/22, 202.36.44.0/24, 202.36.45.0/24, 202.36.76.0/23, 202.37.136.0/24, 202.37.140.0/22, 202.37.144.0/21, 202.37.163.0/24, 202.37.197.0/24, 202.37.200.0/22, 202.37.224.0/21, 202.37.232.0/24, 202.37.240.0/23, 202.37.252.0/23, 202.37.76.0/24, 202.37.85.0/24, 202.41.136.0/22, 202.41.140.0/24, 202.49.62.0/24, 202.49.89.0/24, 202.49.249.0/24, 202.50.87.0/24, 202.50.246.0/24, 202.55.96.0/20, 202.74.224.0/21, 203.9.179.0/24, 203.9.180.0/24, 205.233.128.0/21, 205.233.136.0/23, 205.233.243.0/24, 210.185.0.0/18, 210.48.0.0/17, 210.54.136.0/22, 210.54.140.0/24, 210.54.160.0/19, 210.55.182.0/23, 210.55.24.0/22, 210.55.253.0/24, 210.56.32.0/20 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: john.johnston(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20030407 changed: rpsl-admin(a)nzix.net 20040629 changed: rpsl-admin(a)nzix.net 20040831 changed: rpsl-admin(a)nzix.net 20040930 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS4770 descr: Route set for AS4770 members: 138.235.0.0/16, 192.107.113.0/24, 192.173.16.0/21, 198.32.66.0/24, 199.212.90.0/23, 199.212.92.0/23^23-24, 202.6.84.0/24, 202.12.70.0/24, 202.12.248.0/21, 202.14.100.0/24, 202.21.130.0/24, 202.21.136.0/23, 202.36.155.0/24, 202.36.157.0/24, 202.36.32.0/24, 202.36.36.0/22, 202.36.44.0/24, 202.36.45.0/24, 202.36.76.0/23, 202.37.136.0/24, 202.37.140.0/22, 202.37.144.0/21, 202.37.163.0/24, 202.37.197.0/24, 202.37.200.0/22, 202.37.224.0/21, 202.37.232.0/24, 202.37.240.0/23, 202.37.252.0/23, 202.37.76.0/24, 202.37.85.0/24, 202.41.136.0/22, 202.41.140.0/24, 202.49.62.0/24, 202.49.89.0/24, 202.49.249.0/24, 202.50.87.0/24, 202.50.246.0/24, 202.55.96.0/20, 202.74.224.0/21, 203.9.179.0/24, 203.9.180.0/24, 205.233.128.0/21, 205.233.136.0/23, 205.233.243.0/24, 210.185.0.0/18, 210.48.0.0/17, 210.54.136.0/22, 210.54.140.0/24, 210.54.160.0/19, 210.55.182.0/23, 210.55.24.0/22, 210.55.253.0/24, 210.56.32.0/20 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: john.johnston(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20030407 changed: rpsl-admin(a)nzix.net 20040629 changed: rpsl-admin(a)nzix.net 20040831 changed: rpsl-admin(a)nzix.net 20040930 changed: rpsl-admin(a)nzix.net 20050224 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 23 Feb '05

23 Feb '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. The update causing these changes had the following mail headers: - From: Andy Linton <asjl(a)citylink.co.nz> - Cc: - Subject: - Date: Thu, 24 Feb 2005 10:20:23 +1300 (NZDT) - Msg-Id: <Pine.LNX.4.58.0502241019150.22349(a)jennings.citylink.co.nz> NZRR Database Notification Department --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS4770 descr: Route set for AS4770 members: 138.235.0.0/16, 192.107.113.0/24, 192.173.16.0/21, 198.32.66.0/24, 199.212.90.0/23, 199.212.92.0/23, 202.6.84.0/24, 202.12.70.0/24, 202.12.248.0/21, 202.14.100.0/24, 202.21.130.0/24, 202.21.136.0/23, 202.36.155.0/24, 202.36.157.0/24, 202.36.32.0/24, 202.36.36.0/22, 202.36.44.0/24, 202.36.45.0/24, 202.36.76.0/23, 202.37.136.0/24, 202.37.140.0/22, 202.37.144.0/21, 202.37.163.0/24, 202.37.197.0/24, 202.37.200.0/22, 202.37.224.0/21, 202.37.232.0/24, 202.37.240.0/23, 202.37.252.0/23, 202.37.76.0/24, 202.37.85.0/24, 202.41.136.0/22, 202.41.140.0/24, 202.49.62.0/24, 202.49.89.0/24, 202.49.249.0/24, 202.50.87.0/24, 202.50.246.0/24, 202.55.96.0/20, 202.74.224.0/21, 203.9.179.0/24, 203.9.180.0/24, 205.233.128.0/21, 205.233.136.0/23, 205.233.243.0/24, 210.185.0.0/18, 210.48.0.0/17, 210.54.136.0/22, 210.54.140.0/24, 210.54.160.0/19, 210.55.182.0/23, 210.55.24.0/22, 210.55.253.0/24, 210.56.32.0/20 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: john.johnston(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20030407 changed: rpsl-admin(a)nzix.net 20040629 changed: rpsl-admin(a)nzix.net 20040831 changed: rpsl-admin(a)nzix.net 20040930 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS4770 descr: Route set for AS4770 members: 138.235.0.0/16, 192.107.113.0/24, 192.173.16.0/21, 198.32.66.0/24, 199.212.90.0/23, 199.212.92.0/23^23-24, 202.6.84.0/24, 202.12.70.0/24, 202.12.248.0/21, 202.14.100.0/24, 202.21.130.0/24, 202.21.136.0/23, 202.36.155.0/24, 202.36.157.0/24, 202.36.32.0/24, 202.36.36.0/22, 202.36.44.0/24, 202.36.45.0/24, 202.36.76.0/23, 202.37.136.0/24, 202.37.140.0/22, 202.37.144.0/21, 202.37.163.0/24, 202.37.197.0/24, 202.37.200.0/22, 202.37.224.0/21, 202.37.232.0/24, 202.37.240.0/23, 202.37.252.0/23, 202.37.76.0/24, 202.37.85.0/24, 202.41.136.0/22, 202.41.140.0/24, 202.49.62.0/24, 202.49.89.0/24, 202.49.249.0/24, 202.50.87.0/24, 202.50.246.0/24, 202.55.96.0/20, 202.74.224.0/21, 203.9.179.0/24, 203.9.180.0/24, 205.233.128.0/21, 205.233.136.0/23, 205.233.243.0/24, 210.185.0.0/18, 210.48.0.0/17, 210.54.136.0/22, 210.54.140.0/24, 210.54.160.0/19, 210.55.182.0/23, 210.55.24.0/22, 210.55.253.0/24, 210.56.32.0/20 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: john.johnston(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20030407 changed: rpsl-admin(a)nzix.net 20040629 changed: rpsl-admin(a)nzix.net 20040831 changed: rpsl-admin(a)nzix.net 20040930 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 23 Feb '05

23 Feb '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. The update causing these changes had the following mail headers: - From: Andy Linton <asjl(a)citylink.co.nz> - Cc: - Subject: - Date: Thu, 24 Feb 2005 10:15:51 +1300 (NZDT) - Msg-Id: <Pine.LNX.4.58.0502241014080.22349(a)jennings.citylink.co.nz> NZRR Database Notification Department --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS4770 descr: Route set for AS4770 members: 138.235.0.0/16, 192.107.113.0/24, 192.173.16.0/21, 198.32.66.0/24, 199.212.90.0/23, 199.212.92.0/23, 202.6.84.0/24, 202.12.70.0/24, 202.12.248.0/21, 202.14.100.0/24, 202.21.130.0/24, 202.21.136.0/23, 202.36.155.0/24, 202.36.157.0/24, 202.36.32.0/24, 202.36.36.0/22, 202.36.44.0/24, 202.36.45.0/24, 202.36.76.0/23, 202.37.136.0/24, 202.37.140.0/22, 202.37.144.0/21, 202.37.163.0/24, 202.37.197.0/24, 202.37.200.0/22, 202.37.224.0/21, 202.37.232.0/24, 202.37.240.0/23, 202.37.252.0/23, 202.37.76.0/24, 202.37.85.0/24, 202.41.136.0/22, 202.41.140.0/24, 202.49.62.0/24, 202.49.89.0/24, 202.49.249.0/24, 202.50.87.0/24, 202.50.246.0/24, 202.55.96.0/20, 202.74.224.0/21, 203.9.179.0/24, 203.9.180.0/24, 205.233.128.0/21, 205.233.136.0/23, 205.233.243.0/24, 210.185.0.0/18, 210.48.0.0/17, 210.54.136.0/22, 210.54.140.0/24, 210.54.160.0/19, 210.55.182.0/23, 210.55.24.0/22, 210.55.253.0/24, 210.56.32.0/20 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: john.johnston(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20030407 changed: rpsl-admin(a)nzix.net 20040629 changed: rpsl-admin(a)nzix.net 20040831 changed: rpsl-admin(a)nzix.net 20040930 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS4770 descr: Route set for AS4770 members: 138.235.0.0/16, 192.107.113.0/24, 192.173.16.0/21, 198.32.66.0/24, 199.212.90.0/23, 199.212.92.0/23^23-24, 202.6.84.0/24, 202.12.70.0/24, 202.12.248.0/21, 202.14.100.0/24, 202.21.130.0/24, 202.21.136.0/23, 202.36.155.0/24, 202.36.157.0/24, 202.36.32.0/24, 202.36.36.0/22, 202.36.44.0/24, 202.36.45.0/24, 202.36.76.0/23, 202.37.136.0/24, 202.37.140.0/22, 202.37.144.0/21, 202.37.163.0/24, 202.37.197.0/24, 202.37.200.0/22, 202.37.224.0/21, 202.37.232.0/24, 202.37.240.0/23, 202.37.252.0/23, 202.37.76.0/24, 202.37.85.0/24, 202.41.136.0/22, 202.41.140.0/24, 202.49.62.0/24, 202.49.89.0/24, 202.49.249.0/24, 202.50.87.0/24, 202.50.246.0/24, 202.55.96.0/20, 202.74.224.0/21, 203.9.179.0/24, 203.9.180.0/24, 205.233.128.0/21, 205.233.136.0/23, 205.233.243.0/24, 210.185.0.0/18, 210.48.0.0/17, 210.54.136.0/22, 210.54.140.0/24, 210.54.160.0/19, 210.55.182.0/23, 210.55.24.0/22, 210.55.253.0/24, 210.56.32.0/20 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: john.johnston(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20030407 changed: rpsl-admin(a)nzix.net 20040629 changed: rpsl-admin(a)nzix.net 20040831 changed: rpsl-admin(a)nzix.net 20040930 changed: rpsl-admin(a)nzix.net 20050224 source: NZRR

1 0

Anti-spam legislation update
by Ian McDonald 23 Feb '05

23 Feb '05

>From http://www.stuff.co.nz/stuff/0,2106,3197634a10,00.html Anti-spam law change proposed 24 February 2005 Organisations that send spam could be fined up to half a million dollars and individuals $200,000 under legislation to be introduced to Parliament. Communications Minister David Cunliffe said yesterday that introducing the Unsolicited Electronic Messages Bill would be a priority but no date had been set. The bill "will be an important step in the war against spam," Mr Cunliffe said in a statement. "The legislation will complement codes of practice, technical measures and consumer education to help fight the deluge of spam. It will also help New Zealand's efforts to address this problem at an international level." The bill will apply to e-mails, text messaging and instant messaging requiring that senders of multiple commercial electronic marketing messages only send them to people who have agreed to get them. Senders of promotional electronic messages will be required to stop sending messages if recipients decide to opt out. The bill will also set out requirements relating to accurate sender identification and the provision of an unsubscribe facility. Maximum penalties under the proposed law will be $500,000 for organisations and $200,000 for individualise. The Department of Internal Affairs will enforce the law. "While this bill alone will not solve the problem of spam it is an important step alongside other measures to ensure New Zealand is not a soft target for spammers," Mr Cunliffe said.

1 0

Linux conference Australia 06 in Dunedin.
by Simon Lyall 22 Feb '05

22 Feb '05

Something you may want to put on your calendars: http://lca2006.linux.org.au/ See http://linux.conf.au for more information about this year's conference (to be held in a couple of months). Roughly speaking this is one of the big three Linux conferences held each year. I remember suggesting at one point that if LCA was held in NZ then NZNOG could be a "mini-conference" on the first 2 days of it. -- Simon J. Lyall. | Very Busy | Mail: simon(a)darkmere.gen.nz "To stay awake all night adds a day to your life" - Stilgar | eMT.

3 3

Notification of NZRR Database changes
by NZRR Database Notifications 22 Feb '05

22 Feb '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. The update causing these changes had the following mail headers: - From: Andy Linton <asjl(a)citylink.co.nz> - Cc: - Subject: [CityLink #1941] Routing updates for APE Route Servers (fwd) - Date: Wed, 23 Feb 2005 16:52:56 +1300 (NZDT) - Msg-Id: <Pine.LNX.4.58.0502231652350.21457(a)jennings.citylink.co.nz> NZRR Database Notification Department --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS9790 descr: Route set advertised to AS9560 by CallPlus - AS9790 members: 202.0.151.0/24, 202.36.232.0/24, 202.36.244.0/23^23-24, 202.37.129.0/24, 202.49.34.0/23^23-24, 202.49.62.0/24, 202.50.109.0/24, 202.50.170.0/24, 202.180.64.0/18^18-24, 203.97.152.0/24, 203.100.223.208/20^20-24, 203.184.0.0/18^18-24, 203.215.142.0/23^23-24, 210.55.111.0/24, 210.55.254.0/24 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: noc(a)callplus.co.nz notify: nznog(a)list.waikato.ac.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20030428 changed: rpsl-admin(a)nzix.net 20040813 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9790 descr: advertised to AS9560 by CallPlus Limited - AS9790 members: 202.36.232.0/24^24-27, 202.37.22.0/24^24-27, 202.37.129.0/24^24-27, 202.49.34.0/23^23-27, 202.50.109.0/24^24-27, 202.180.64.0/18^18-27, 203.97.152.0/24^24-27, 203.100.208.0/20^20-27, 203.184.0.0/18^18-27, 203.215.142.0/23^23-27 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)callplus.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050223 source: NZRR

1 0

FYI - Upcoming Webcasts on R2.co.nz
by Richard Naylor 21 Feb '05

21 Feb '05

Evening All, There are several webcasts coming up in the next few weeks. These are brought to your attention so that Help Desks, etc may be forewarned of potential calls. There may even be some network activity. 1-3 March - Hui Taumata - Maori Economic Development Summit, at Te Papa Will be webcast during normal business hours - not likely to have a huge viewer base, but will be webcast in 5 streams as is usual for us. (3 video, 2 audio). Server will be on WIX with limited international capacity. 11-13 March Girl's Day Out - Big Sister Event - AKL Showgrounds It appears to be a 72 hour non-stop webcast with 6 simultaneous cameras. Each camera will stream in 56k, 128k and 256kbps. Which adds up to quite a bit of bandwidth. We will be using 3 carriers to supply the van (which will be bigger, coz we can't fit all the gear in). We do have a web page which allows you to watch all 6 cameras, but don't try it on a telephone modem. The event will (hopefully) use servers on WIX, APE and PNIX and will have national + international routes for operators not peering on those exchanges - but will be heavily rate limited. Operators are STRONGLY urged to peer before the event. This has the potential to be a "large traffic generator" and operators should be aware of this. Fortunately it is a week end. Help Desks may also experience an increase in calls for assistance. 26 March - Wedding in Carterton A Saturday event over Easter week end. Mainly for family of the happy couple. It is unlikely that it will cause any traffic or Help Desk calls as the main audience is in the UK.. Server will be on WIX or APE + international. Early April - Sports event - unconfirmed. We will advise next month if this is going ahead. Thank you for your co-operation. Please contact me if you have any questions. (we don't need any more crew sorry - 2 extras from the office are joining us) Rich (wearing my R2 hat)

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 21 Feb '05

21 Feb '05

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. The update causing these changes had the following mail headers: - From: Andy Linton <asjl(a)citylink.co.nz> - Cc: - Subject: [CityLink #1857] Routing updates for WIX Route Servers (fwd) - Date: Tue, 22 Feb 2005 18:09:55 +1300 (NZDT) - Msg-Id: <Pine.LNX.4.58.0502221809350.19784(a)jennings.citylink.co.nz> NZRR Database Notification Department --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS18119 descr: advertised to AS9439 by LinuxNet - AS18119 members: 192.107.113.0/24^24-29, 202.7.4.80/29, 202.21.136.0/23^23-29, 202.36.44.0/24^24-29, 202.37.136.0/24^24-29, 202.49.249.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: lincoln(a)linuxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050210 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS18119 descr: advertised to AS9439 by LinuxNet - AS18119 members: 192.107.113.0/24^24-29, 202.7.4.80/29, 202.21.136.0/23^23-29, 202.36.44.0/24^24-29, 202.37.136.0/24^24-29, 202.49.249.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: lincoln(a)linuxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050222 source: NZRR

1 0

APNIC 19 daily summaries
by Simon Lyall 21 Feb '05

21 Feb '05

Forwarded since the nznog list software rejected it. ---------- Forwarded message ---------- Date: Tue, 22 Feb 2005 13:23:09 +1000 From: Nurani Nimpuno <nurani(a)apnic.net> Subject: [apops] APNIC 19 daily summaries Keep up to date with APNIC 19 daily summaries --------------------------------------------- APNIC is publishing daily summaries of activities at APNIC 19 to keep the Internet community keep up to date with the status of proposed policies and discussion at the meeting in Kyoto. The first daily summary has now been published: http://www.apnic.net/meetings/19/programme/summary/ Daily summaries will be published every day through to Friday. Best regards ______________________________________________________________________ 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 ______________________________________________________________________

1 0

Monitoring etc
by Dan Clark 21 Feb '05

21 Feb '05

no worries, I've found the message I was looking for. Regards Dan

1 0

Monitoring List
by Dan Clark 21 Feb '05

21 Feb '05

Can someone remember the name of that list we setup a wee while back re monitoring etc? Regards Dan Clark Technical Director Synaptic Ltd

1 0

Conference makes the press.
by Simon Lyall 20 Feb '05

20 Feb '05

A little article about the conference at: http://computerworld.co.nz/news.nsf/UNID/3D671C88184ACEBBCC256FAB00804976?O… I'd have hoped for something a little better but better than nothing, the printed version has a group photo. Also could somebody at waikato have a look at warlock.cs.waikato.ac.nz , it seems to have problems (bad dns I think) so the www.nznog.org site is offline. -- Simon J. Lyall. | Very Busy | Mail: simon(a)darkmere.gen.nz "To stay awake all night adds a day to your life" - Stilgar | eMT.

2 1

nznog 05 videos
by Richard Naylor 18 Feb '05

18 Feb '05

Lots of people have asked for other versions of the video or to be able to get CD copies etc. We can do that if you want (hint $), but to make them more available, we've copied them onto an http server as well. http://s2.r2.co.nz/20050203 I'll get around to putting a link up on the main page soon. Be careful, theres around 2.5GB And the at least one tutorial will go up as well - when I've edited the video down a little and taken out the lunch break etc. rich

1 0

RE: [nznog] crack!
by Donald Neal 17 Feb '05

17 Feb '05

> From: Steve Phillips [mailto:steve(a)focb.co.nz] > Sent: Friday, 18 February 2005 2:18 p.m. > To: nznog > Subject: RE: [nznog] crack! > > On Fri, 18 Feb 2005, Donald Neal wrote: > [snip] > >> > >> right, this is where Donald steps in and says something along > >> the lines > >> of having lost any operational relevance. > > > > Yep. > > > > So was that Donald agreeing that it had lost relevance but > not actually > saying that "it had lost relevance and to please stop posting on this > subject" or was it Donald saying "please dont post anymore on > this subject > as it is no longer relevant" ? That was Donald agreeing that it had lost any operational relevance. Seriously, if a thread has lost all relevance, we should be to stop without needing explicit instructions. The posting to which I was replying is evidence that some on this list do know that. - Donald Neal Donald Neal |"we don't want kids going to Support Engineer |university if they are not going NGN Operations |to success" - Kate Colbert, NZQA Integration & Services Division +----------------------------------- Alcatel NZ Ltd - Telecom's network operations manager ------------------------------------------------------------------------------ "This communication, including any attachments, is confidential. If you are not the intended recipient, you should not read it - please contact me immediately, destroy it, and do not copy or use any part of this communication or disclose anything about it. Thank you. Please note that this communication does not designate an information system for the purposes of the Electronic Transactions Act 2002." ------------------------------------------------------------------------------

1 0

RE: [nznog] crack!
by Donald Neal 17 Feb '05

17 Feb '05

> From: Jamie Baddeley [mailto:jamie.baddeley(a)vpc.co.nz] > Sent: Friday, 18 February 2005 12:09 p.m. > To: Dean Pemberton > Cc: nznog > Subject: Re: [nznog] crack! > > right, this is where Donald steps in and says something along > the lines > of having lost any operational relevance. Yep. - Donald Neal List Administrator etc. Donald Neal |"we don't want kids going to Support Engineer |university if they are not going NGN Operations |to success" - Kate Colbert, NZQA Integration & Services Division +----------------------------------- Alcatel NZ Ltd - Telecom's network operations manager ------------------------------------------------------------------------------ "This communication, including any attachments, is confidential. If you are not the intended recipient, you should not read it - please contact me immediately, destroy it, and do not copy or use any part of this communication or disclose anything about it. Thank you. Please note that this communication does not designate an information system for the purposes of the Electronic Transactions Act 2002." ------------------------------------------------------------------------------

4 3

crack!
by Dean Pemberton 17 Feb '05

17 Feb '05

>Ooops! >what was that? >did I just hear The Internet break? >Oh dear. >;-) >jamie >clue:depeer clue:the-sound-of-jamie-jumping-to-conclusions

4 4