- NZNOG - lists.nznog.org

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