- NZNOG - lists.nznog.org

Notification of NZRR Database changes
by NZRR Database Notifications 18 Jul '05

18 Jul '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: 210.55.248.0/21 descr: Route for ihug - AS7657 origin: AS7657 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041116 source: NZRR REPLACED BY: route: 210.55.248.0/21 descr: Route for Ihug - AS7657 origin: AS7657 notify: rpsl-admin(a)nzix.net notify: noc(a)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050719 source: NZRR --- PREVIOUS OBJECT: route: 202.49.176.0/23 descr: Route for ihug - AS7657 origin: AS7657 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041116 source: NZRR REPLACED BY: route: 202.49.176.0/23 descr: Route for Ihug - AS7657 origin: AS7657 notify: rpsl-admin(a)nzix.net notify: noc(a)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050719 source: NZRR --- PREVIOUS OBJECT: route: 210.55.202.0/23 descr: Route for ihug - AS7657 origin: AS7657 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041116 source: NZRR REPLACED BY: route: 210.55.202.0/23 descr: Route for Ihug - AS7657 origin: AS7657 notify: rpsl-admin(a)nzix.net notify: noc(a)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050719 source: NZRR

1 0

Re: [nznog] DPE and 3CIX
by Webmaster 18 Jul '05

18 Jul '05

For those who want to peer there, our content will be available at 3CIX when we launch. If you already peer with the 3CIX route servers then you need do nothing. regards, Richard Hulse Radio NZ >>> Andy Linton <asjl(a)citylink.co.nz> 19/07/2005 14:50 >>> CityLink is pleased to announce the addition of two more local Internet Exchange points to complement those in Auckland, Palmerston North and Wellington. The Dunedin Peering Exchange (DPE) and the 3 Cities Internet Exchange linking Hutt City, Upper Hutt City and Porirua City (3CIX) will provide opportunities for partipants to keep local traffic local to those centres and to do so over high speed unmetered connections. Content providers such as Radio New Zealand intend to provide copies of their high volume content at these Exchanges further increasing the value proposition. As more participants connect to a local Internet Exchange the benefits of having a high speed network connecting ISPs, businesses, education and municipal authorities become evident and the redundancy provided helps those connected even when major national telecommunication links have problems. We expect to roll out other Internet Exchanges in Nelson, Southland, Hamilton and Christchurch over the coming months. For more information on all the New Zealand Internet Exchanges, see http://nzix.net/ For information on these new Internet Exchanges see http://dpe.nzix.net/ and http://3cix.nzix.net/ _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

DPE and 3CIX
by Andy Linton 18 Jul '05

18 Jul '05

CityLink is pleased to announce the addition of two more local Internet Exchange points to complement those in Auckland, Palmerston North and Wellington. The Dunedin Peering Exchange (DPE) and the 3 Cities Internet Exchange linking Hutt City, Upper Hutt City and Porirua City (3CIX) will provide opportunities for partipants to keep local traffic local to those centres and to do so over high speed unmetered connections. Content providers such as Radio New Zealand intend to provide copies of their high volume content at these Exchanges further increasing the value proposition. As more participants connect to a local Internet Exchange the benefits of having a high speed network connecting ISPs, businesses, education and municipal authorities become evident and the redundancy provided helps those connected even when major national telecommunication links have problems. We expect to roll out other Internet Exchanges in Nelson, Southland, Hamilton and Christchurch over the coming months. For more information on all the New Zealand Internet Exchanges, see http://nzix.net/ For information on these new Internet Exchanges see http://dpe.nzix.net/ and http://3cix.nzix.net/

3 2

RE: [nznog] [OT]Ispmap / isp locations / core routers
by Donald Neal 18 Jul '05

18 Jul '05

On Tue, 19 Jul 2005, Barry Murphy wrote: [...] >> I'm guessing customers connect directly to the erx's, thus if the erxcrash's >> and goes down, customer falling off that node will be effected. >> >> The idea is a pretty map with colors indicating packet loss. >> Let's just see what happens when the next big network fault happens. >It is highly unlikely anyone will give you this information (and in some >cases this is 100% unlikely) as this would tend to be considered >"commercially sensitive" data to many large organisations. >Any information gathered through probing networks will most certainly be >inaccurate and could lead (as pointed out earlier) to increased >frustration in helpdesks when some clueless customer rings up to report an >ERX crash because they saw it on your intarwebnet page. There's a long history of people trying to understand routing or other changes using RTT's, with names like "Internet Weather Report". The classic problem with doing this on normal (e.g. DSL) customer links is that when that customer link becomes congested, packet loss and RTT go up. But that doesn't indicate that the network as a whole is doing anything unusual. This problem shouldn't exist for a node connected by high-speed link to (or at) an exchange point, but that approach is about looking at backbone links, not the network all the way out the the customer. The key question is what exactly it is anyone's trying to measure. - Donald Neal "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

Re: NZNOG Digest, Vol 31, Issue 14 (Out of Office)
by Lance Edwards 18 Jul '05

18 Jul '05

I will be out of the office starting noon Monday 18 July and will return Friday 22 July. I will be checking email once per day during this period. Regards, Lance ______________________________________________________________________________________________________ This message contains information, which is confidential and may be subject to legal privilege. If you are not the intended recipient, you must not peruse, use, disseminate, distribute or copy this message. If you have received this message in error, please notify us immediately (Phone 0800 665 463 or info(a)linz.govt.nz) and destroy the original message. LINZ accepts no responsibility for changes to this email, or for any attachments, after its transmission from LINZ. Thank you. ______________________________________________________________________________________________________

2 1

[OT]Ispmap / isp locations / core routers
by Barry Murphy 18 Jul '05

18 Jul '05

Hey guys, I thought I'd start the week off with a brainstorm as I'm looking for a few additional things for ISPmap.co.nz . 1./ I'm after a geo location for each ISP's main core routers and an IP address for it too. 2./ I'm after a geo location for each ISP's headoffice. To gather this info, simply fire up http://status.fast.co.nz/metric.html , zoom in to the closest location to your office/router as possible, center it in the screen and mail me the details of latitude and longitude. http://status.fast.co.nz will soon become apart of ispmap, if you go directly to this URL you will see what my aim is, to have a country map (with the ability to filter by ISP) with the status of each ISP's network. Please mail back (Off list) in the following format: ISP: Contact: Logitude: Latitude: IP Address: Services effected: (optional, but would be nice to see what parts of the country and what services would be effected) Equipment: (optional, but eg cisco, I may add logos to the map later) Thanks. Barry

8 12

RE: [nznog] [OT]Ispmap / isp locations / core routers
by Gordon Smith 18 Jul '05

18 Jul '05

I agree 100% with Steve on this. I doubt that there are many providers that wish to publicise their internal network structure. A pretty map has very little relevance to a modern MPLS-based network without a view of the underlying signalling. All you'll see is the switched paths, not the physical infrastructure. There is such a thing as too much information - I see little point in letting an end user try to diagnose a network fault when said user has little or no understanding of network topologies and protocols, even at layer 3. Cheers, Gordon

1 0

Frame Relay services
by Andy Linton 16 Jul '05

16 Jul '05

I'd appreciate hearing from ISPs who provide connectivity using Frame Relay. Replies off list and please no diatribes about how crap Frame Relay is and how I should use technology X instead.

1 0

RE: [nznog] [Fwd: Buzz.ThePeople]
by Scott Walsh 14 Jul '05

14 Jul '05

Interesting (and un-surprisingly), the privacy statement on their website (http://www.buzzchannel.co.nz/v1.1/research/surveys/privacy.asp?cid=42&sid=1 ) contradicts the statement below. -----Original Message----- From: Richard Patterson [mailto:richard(a)helix.net.nz] Sent: Friday, 15 July 2005 14:01 To: nznog(a)list.waikato.ac.nz Subject: [nznog] [Fwd: Buzz.ThePeople] <snip> IMPORTANT PRIVACY NOTE: The only time we will use this email is now, to send this introduction to you. From this point we will not contact you unless you choose to sign up to Buzz.ThePeople.

1 0

[Fwd: Buzz.ThePeople]
by Richard Patterson 14 Jul '05

14 Jul '05

Sorry to disrupt everybody from their ever so important SPF ranting. but, has anybody heard of this NZ spamm0r? registrant_contact_name: Buzz Channel Limited registrant_contact_address1: P.O. Box 68-953 registrant_contact_address2: Newton registrant_contact_city: Auckland registrant_contact_postalcode: 1003 registrant_contact_country: NZ (NEW ZEALAND) registrant_contact_phone: +64 9 5284883 registrant_contact_email: nick.macdonald(a)buzzconsult.com Registered Office 43 Bright St Eden Terrace Auckland Directors VANCE, Mary MACDONALD, Nicholas -------- Original Message -------- From: - Fri Jul 15 13:09:22 2005 X-Account-Key: account3 X-UIDL: 1121390459.30535.skywarp,S=1631 X-Mozilla-Status: 0001 X-Mozilla-Status2: 00000000 Return-Path: <buzz(a)buzzchannel.co.nz> Delivered-To: detonate(a)helix.net.nz Received: (qmail 30533 invoked by uid 89); 15 Jul 2005 01:20:58 -0000 Received: from unknown (HELO 216-55-168-48.dedicated.abac.net) (216.55.168.48) by skyfire.helix.net.nz with SMTP; 15 Jul 2005 01:20:58 -0000 Received: from BuzzServer1001.buzzone.buzzchannel.net (unverified [216.55.168.48]) by 216-55-168-48.dedicated.abac.net (SurgeMail 3.0c2) with ESMTP id 73137 for <detonate(a)helix.net.nz>; Thu, 14 Jul 2005 18:08:13 -0700 Return-Path: <buzz(a)buzzchannel.co.nz> From: Buzz.ThePeople <buzz(a)buzzchannel.co.nz> To: detonate(a)helix.net.nz Subject: Buzz.ThePeople Date: Thu, 14 Jul 2005 18:08:13 -0700 Message-ID: <20050714-18081356-cdc(a)BuzzServer1001.buzzone.buzzchannel.net> MIME-Version: 1.0 X-Server: High Performance Mail Server - http://surgemail.com Dear Richard Patterson, Help shape your future PLUS have the chance to win! Buzz.ThePeople is a new online way for you to have your say on lots of different topics. Many people are joining Buzz.ThePeople because they want their views considered by NZ decision makers (e.g. political pollsters, the media, marketers and market researchers). Others are joining because there are going to be great prizes and even opportunities to earn cash. If you are interested and want to know more (plus your chance to go into the draw for a new Dell Inspiron 6000 notebook computer) click on the following link: http://www.buzzthepeople.co.nz?c=43401 IMPORTANT PRIVACY NOTE: The only time we will use this email is now, to send this introduction to you. From this point we will not contact you unless you choose to sign up to Buzz.ThePeople. Kind Regards, The Buzz Team.

4 3

SPF Uptake in New Zealand
by Craig Whitmore 14 Jul '05

14 Jul '05

So you ask what is SPF? SPF (Sender Permitted From) is an anti-forgery method used with SMTP which stops people trying to send from your domain. Not designed for stopping spam, but helps reduce the amount of spam as well (stops people sending from other peoples domains). Spammers can add SPF records to their domains yes, (repeat: SPF doesn't stop spam but does a good job of it) but in the future may be improved to include trust factors (ie domain and SPF has been only around for 2 days and its sending 1000 emails to me... strange) There are quite a number of anti-forgery systems around at the moment, and the main ones are SPF, Sender-ID (Microsoft) and DomainKeys (Yahoo), SPF at the moment is the largest used worldwide. (over a million domain names having SPF records) The uptake in New Zealand is pretty small at the moment, but ISP's are starting to add SPF records for their domains. Xtra have added SPF rules for the xtra.co.nz Domain: v=spf1 ip4:210.86.15.0/24 ?all (host -t TXT xtra.co.nz) IHUG have added a SPF rule for ihug hosted domains to include: eg v=spf1 include:_spf.ihug.co.nz -all (host -t TXT _spf.ihug.co.nz) And a lot of Domains (see http://spam.co.nz/spf/working/) have started to add SPF Rules . This list is no where complete at the moment for .NZ (or other domainnames). Also quite a number of NZ domains have broken SPF records for various reasons which (if an ISP is testing for SPF will reject and cause bounces), so its quite important to make your rules correct (see http://www.spam.co.nz/spf/broken - This list is also quite imcomplete) I'm not saying SPF doesn't have its problems, but the major problem (at the moment) is forwarding emails . Ie user(a)ispa.com sends email to user(a)ispb.com and it gets forwarded to user(a)ispc.com. . If user(a)ispc.com checks for SPF it will fail as the user(a)ispa.com email address is coming from ISP B's email server. BUT mechanisms like SRS fix this problem. Mostly importantant is before SPF records are set up for a domain you must know how you users are using your domain. So maybe you think SPF is just something kids play around with and it will never be used for anything important and no one cares about it which is not so as its gaining momentum like just recently the IANA just gave SPF its own DNS RR (SPF) (see http://www.iana.org/assignments/dns-parameters) which will be used instead of the TXT records in the future to SPF records (maybe SPF v3 will use it only) More information can be read at: http://www.openspf.net/ and the mailing list and other information can be read at http://www.openspf.org/ Thanks Craig Whitmore www.spam.co.nz

9 11

RE: [nznog] SPF Uptake in New Zealand
by Nic Wise 14 Jul '05

14 Jul '05

> I'm guessing that this is a precursor to enforcing it for all > Microsoft controlled domains. Though presumably they will > have trouble enforcing it for Microsoft.com, unless they're > already prepping the next version of Exchange to include > spf/senderid support :) > I'm not 100% sure, but I think I read that this is going to be in Exchange 2003 SP2 - I think it's part of the "edge services" thing that's in SP2. Nic -- Nic Wise - Senior Developer - Microsoft MVP (.NET) AfterMail Limited. t. +64.21.676.418 w. http://www.aftermail.com/ e. nic.wise(a)aftermail.com b. http://www.fastchicken.co.nz/blog/

1 0

RE: [nznog] SPF Uptake in New Zealand
by Drew Broadley 14 Jul '05

14 Jul '05

> Just my 2c..... Nothing like a Friday morning rant... I need a V.... s/V/Beer/ ;) Cheers for that summary, it's helped me get my head around SPF, which I've flogged researching for the fear of adding False-Negatives possibilities on-top of my current SA setup (which, incidentally, has been flawless for a few months now). - Drew

1 0

RE: [nznog] SPF Uptake in New Zealand
by Simon Allard 13 Jul '05

13 Jul '05

> > If they set "v=spf1 ip4:210.86.15.0/24 -all" then some mail (for example > > that trademe.co.nz sends out) would get rejected as it would be coming > > from the wrong place > > > > This was a little unclear what I said . trademe.co.nz sends out emails > sometimes from the email address of the trademe user. If a user has email > address of customer(a)xtra.co.nz it will send from that address from trademe > mail server. and if tested for SPF with a -all will fail and get rejected. I can see SPF being a big learning curve to the NZ ISP customer base, once ISP's start enforcing SPF. We still see lots of email from customers who have an ispa email set as their email address but are using our email server because they moved ISP's but didn't want to change email address. I would be surprised if any ISP's don't see this. SPF seems like a very good idea, and will work perfectly for personal domains, but for big ISP's, xtra/clear/ihug etc. It's going to cause a huge influx of unhappy customers if it ever gets implemented. - Simon

2 1

RE: [nznog] SPF Uptake in New Zealand
by Nic Wise 13 Jul '05

13 Jul '05

Hey folks, Noone has mentioned building the SPF strings :) I found this a while back: http://www.anti-spamtools.org/SenderIDEmailPolicyTool/Default.aspx It's a nice little (online) wizard from MS, which allows you to build the string without having to work out a geekcode-look-alike. AFAIK, they don't store info - just show you the SPF for what you enter. No comment on how effective SPF might be, but the wizard is handy if you don't wanna work out the syntax :) Cheers. Nic, off to add the TXT record to his domains. -- Nic Wise - Senior Developer - Microsoft MVP (.NET) AfterMail Limited. t. +64.21.676.418 w. http://www.aftermail.com/ e. nic.wise(a)aftermail.com b. http://www.fastchicken.co.nz/blog/

4 6

RE: [nznog] SPF Uptake in New Zealand
by Drew Broadley 13 Jul '05

13 Jul '05

> Noone has mentioned building the SPF strings :) I found this a while > back: > > http://www.anti-spamtools.org/SenderIDEmailPolicyTool/Default.aspx > There is wizard on one of the one links posted by Craig. http://spf.pobox.com/ , http://www.openspf.net/ (some thing) The wizard is on the top left, where it says to enter your domain. - Drew

1 0

nz.pool.ntp.org??
by Simon 13 Jul '05

13 Jul '05

Hi There, Anyone know whats happened to this ntp server(s)? Im getting a connection timeout from a few days ago... # rdate -s nz.pool.ntp.org rdate: connect: Connection timed out Simon

3 3

RE: [nznog] nz.pool.ntp.org??
by Gavin Legge 13 Jul '05

13 Jul '05

Incidentally I tried nslookup on nz.pool.ntp.org a few minutes ago and it timed out. After the third or fourth attempt I got an answer with multiple IP's as expected. Hope that helps. -----Original Message----- From: Drew Broadley [mailto:drew(a)iws.co.nz] Sent: Thursday, 14 July 2005 9:12 a.m. To: nznog(a)list.waikato.ac.nz Subject: RE: [nznog] nz.pool.ntp.org?? > Hi There, Anyone know whats happened to this ntp server(s)? > Im getting a > connection timeout from a few days ago... > > # rdate -s nz.pool.ntp.org > rdate: connect: Connection timed out > > Simon I'm guessing you've tried multiple attempts ? Try a different nameserver in /etc/resolv.conf incase the one you're using has nutted out (for some unkonw reason) on the multiple A records ? - Drew _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. MailScanner Supplied by ITS-HelpDesk. ext 4001 or email helpdesk(a)irl.cri.nz-- This electronic transmission and any documents accompanying this electronic transmission contain confidential information belonging to the sender. This information may be legally privileged. The information is intended only for the use of the individual or entity named above. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or the taking of any action in reliance on or regarding the contents of this electronically transmitted information is strictly prohibited.

1 0

RE: [nznog] nz.pool.ntp.org??
by Drew Broadley 13 Jul '05

13 Jul '05

> Hi There, Anyone know whats happened to this ntp server(s)? > Im getting a > connection timeout from a few days ago... > > # rdate -s nz.pool.ntp.org > rdate: connect: Connection timed out > > Simon I'm guessing you've tried multiple attempts ? Try a different nameserver in /etc/resolv.conf incase the one you're using has nutted out (for some unkonw reason) on the multiple A records ? - Drew

1 0

RE: [nznog] nz.pool.ntp.org??
by Gavin Legge 13 Jul '05

13 Jul '05

Nope - but there is one at IRL - in fact the(one of many?) main reference for NZ. Msltime.irl.cri.nz enjoy -----Original Message----- From: Simon [mailto:dev(a)networker.co.nz] Sent: Thursday, 14 July 2005 9:00 a.m. To: nznog(a)list.waikato.ac.nz Subject: [nznog] nz.pool.ntp.org?? Hi There, Anyone know whats happened to this ntp server(s)? Im getting a connection timeout from a few days ago... # rdate -s nz.pool.ntp.org rdate: connect: Connection timed out Simon _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. MailScanner Supplied by ITS-HelpDesk. ext 4001 or email helpdesk(a)irl.cri.nz-- This electronic transmission and any documents accompanying this electronic transmission contain confidential information belonging to the sender. This information may be legally privileged. The information is intended only for the use of the individual or entity named above. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or the taking of any action in reliance on or regarding the contents of this electronically transmitted information is strictly prohibited.

1 0

Hostile takeover of Indonesia's .it registrar
by Mark Derricutt 13 Jul '05

13 Jul '05

Just saw a discussion of a hostile takeover of the .it domain management on IRC (#joiito @ freenode ) and thought it might be of interest to you NZNOGers: http://lists.apdip.net/pipermail/igovap/Week-of-Mon-20050711/000374.html Mark

2 2

ENUM Consultation Report by M-co for InternetNZ
by Michael Sutton 12 Jul '05

12 Jul '05

Members of NZNOG. On behalf of InternetNZ's ENUM Task Force we are pleased to provide you with a link to the full M-co report, "The staging of the first ENUM trial in New Zealand" (~100pages) <http://www.internetnz.net.nz/public/enum/2005-07-ENUM-Trial-Report-complete .pdf> http://www.internetnz.net.nz/public/enum/2005-07-ENUM-Trial-Report-complete. pdf This report was commissioned to provide advice to InternetNZ including recommendations and questions to be addressed in respect of ENUM's implementation in New Zealand. In parallel to the preparation and release of this report InternetNZ has agreed with the Telecommunication Carriers Forum (TCF) to form a joint Industry ENUM Steering Group as part of our initiative to provide a platform to plan and implement ENUM for New Zealand. We look forward to receiving feedback with a nominal close off date of July 21st 2005. If you require an extended period please let us know by that date. All comments should be sent to <mailto:enum-tf(a)internetnz.net.nz> mailto:enum-tf(a)internetnz.net.nz. Written submissions can also sent to our Office at: ENUM Task Force, InternetNZ, P.O.Box 11-881, Wellington, New Zealand, or can be faxed to the Task Force at +64 4 495 2115. The Consultation Report is also to being printed and to receive a physical copy please send a request and mailing address to Jordan Carter at <mailto:jordan(a)internetnz.net.nz> mailto:jordan(a)internetnz.net.nz. The Report in subsections (PDF format), are also available on the InternetNZ web site <http://www.internetnz.net.nz/public/enum/> http://www.internetnz.net.nz/public/enum/. You will also find links to the ENUM workshop and initiatives at this URL. You are welcome to distribute this Report to anyone this would be of interest too. Best Regards Michael S. Sutton Councillor - InternetNZ 2003 - 2006 Chairman - Enum Task Force InternetNZ Project Manager - UCI PUA Enum Prototype Telephone: +64 4 475 9235 Mobile: +64 21 305500 InternetNZ: +64 4 4721600 ext 730 <mailto:michael.sutton(a)internetnz.net.nz> mailto:michael.sutton(a)internetnz.net.nz> [ Please note this email is in HTML format to prevent long URL links being broken - my apologies to those who prefer plain text]

1 0

Not quite 255
by Juha Saarinen 10 Jul '05

10 Jul '05

Intelenet-Communications-Intelenet-Communications.so-6-0-0.ar3.LAX1.gblx.net -- Juha

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 10 Jul '05

10 Jul '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:AS7657 descr: advertised to AS9560 by Ihug Ltd - AS7657 members: 203.118.128.0/18^18-29, 203.173.192.0/18^18-29, 203.96.192.0/19^19-29, 202.46.160.0/20^20-29, 202.126.80.0/20^20-29, 203.109.144.0/20^20-29, 203.173.144.0/20^20-29, 203.109.192.0/21^21-29, 203.173.136.0/21^21-29, 203.173.168.0/21^21-29, 202.50.188.0/22^22-29, 203.109.132.0/22^22-29, 203.109.252.0/22^22-29, 203.173.164.0/22^22-29, 203.173.188.0/22^22-29, 202.21.136.0/23^23-29, 202.36.94.0/23^23-29, 202.36.230.0/23^23-29, 202.49.46.0/23^23-29, 202.49.148.0/23^23-29, 202.49.180.0/23^23-29, 202.61.2.0/23^23-29, 203.173.160.0/23^23-29, 203.173.186.0/23^23-29, 192.107.113.0/24^24-29, 202.21.130.0/24^24-29, 202.36.44.0/24^24-29, 202.37.182.0/24^24-29, 202.49.33.0/24^24-29, 202.49.63.0/24^24-29, 202.49.144.0/24^24-29, 202.49.178.0/24^24-29, 202.49.186.0/24^24-29, 202.49.249.0/24^24-29, 202.50.84.0/24^24-29, 202.50.103.0/24^24-29, 202.50.255.0/24^24-29, 203.109.163.0/24^24-29, 203.109.230.0/24^24-29, 203.109.233.0/24^24-29, 203.173.162.0/24^24-29, 210.55.110.0/24^24-29, 210.55.184.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050518 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS7657 descr: advertised to AS9560 by Ihug Ltd - AS7657 members: 203.109.128.0/17^17-29, 203.118.128.0/17^17-29, 203.173.128.0/17^17-29, 203.96.192.0/19^19-29, 202.36.16.0/20^20-29, 202.46.160.0/20^20-29, 202.49.64.0/21^21-29, 202.126.80.0/21^21-29, 198.48.0.0/22^22-29, 202.8.44.0/22^22-29, 202.50.188.0/22^22-29, 202.21.136.0/23^23-29, 202.36.94.0/23^23-29, 202.36.230.0/23^23-29, 202.49.46.0/23^23-29, 202.49.148.0/23^23-29, 202.49.180.0/23^23-29, 202.61.2.0/23^23-29, 192.107.113.0/24^24-29, 202.7.6.0/24^24-29, 202.21.130.0/24^24-29, 202.36.44.0/24^24-29, 202.36.174.0/24^24-29, 202.49.33.0/24^24-29, 202.49.59.0/24^24-29, 202.49.63.0/24^24-29, 202.49.89.0/24^24-29, 202.49.140.0/24^24-29, 202.49.144.0/24^24-29, 202.49.178.0/24^24-29, 202.49.186.0/24^24-29, 202.49.249.0/24^24-29, 202.50.84.0/24^24-29, 202.50.103.0/24^24-29, 202.50.255.0/24^24-29, 210.55.110.0/24^24-29, 210.55.184.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050711 source: NZRR --- PREVIOUS OBJECT: route: 203.109.128.0/17 descr: Route for ihug - AS7657 origin: AS7657 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041116 source: NZRR REPLACED BY: route: 203.109.128.0/17 descr: Route for Ihug Ltd - AS7657 origin: AS7657 notify: rpsl-admin(a)nzix.net notify: noc(a)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050711 source: NZRR --- PREVIOUS OBJECT: route: 203.173.128.0/17 descr: Route for ihug - AS7657 origin: AS7657 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041116 source: NZRR REPLACED BY: route: 203.173.128.0/17 descr: Route for Ihug Ltd - AS7657 origin: AS7657 notify: rpsl-admin(a)nzix.net notify: noc(a)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050711 source: NZRR --- PREVIOUS OBJECT: route: 202.49.140.0/24 descr: Route for ihug - AS7657 origin: AS7657 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20041116 source: NZRR REPLACED BY: route: 202.49.140.0/24 descr: Route for Ihug Ltd - AS7657 origin: AS7657 notify: rpsl-admin(a)nzix.net notify: noc(a)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050711 source: NZRR

1 0

Noc Contact list.
by Simon Lyall 10 Jul '05

10 Jul '05

Okay first up a big apology for getting behind with updates to this list, I've just gone though mail box and grabbed all the old ones so I have should have all the updates. Which means if they page isn't correct then please send me a new update. http://www.usenet.net.nz/noc/ Note that I'm not just including ISPs on the list but hosting companies and other large Internet connected organisations. Basically people who might need to be connected in a hurry. PS: I believe APNIC lets you do role based owners of IPs and AS numbers now, so there isn't really an excuse to not have your details updated 8 months after somebody leaves.. -- Simon J. Lyall | Very Busy | Web: http://www.darkmere.gen.nz/ "To stay awake all night adds a day to your life" - Stilgar | eMT.

1 0