- NZNOG - lists.nznog.org

ISP Jobs in NZ
by Ben O'Hara 11 May '05

11 May '05

Hi All, Im looking into maybe moving out to NZ from the UK for a year or so and wondering what the job prospects are like in the ISP industry? Ive previously worked fora large ISP here in the UK as a systems/network engineer and would prefer to get a job in the same sort of role over in NZ. Any tips, pointers etc gratefully appreciated. Whats the best area of the country for work? (im thinking Auckland or Wellington) Anything in the Gisborne region? (Ive got family there) Whats the pay like over there for sys/net eng positions? Regards Ben O'Hara

1 0

Survey Results for 2006
by Simon Lyall 11 May '05

11 May '05

Results from the 2006 bit of the survey are below. I'll do the rest of the survey over the next few days. -- Simon J. Lyall | Very Busy | Web: http://www.darkmere.gen.nz/ "To stay awake all night adds a day to your life" - Stilgar | eMT. "I'm sick of you people, your just a bunch of fickle mush heads" - Joe Quimby. NZNOG 06 -------- 38 Forms were returned and 37 were counted towards the total. Not all questions were answered by everybody. My comments are in [] brackets. I have tried to get quotes that generally represent what most people are saying. 1. Are you likely to attend NZNOG 06. Yes: 33 No: 2 Maybe: 2 2. Are you likely to attend Linux.conf.au in Dunedin at the end of Jan 06? Yes: 19 No: 18 3. The following are venues/times that NZNOG might be held. Please rate how likely your are to attend and which you would prefer. [ Most people who expressed a preference said they could attend both. ] (a) Jan/Feb: 7 (b) Mar/Apr: 9 Either: 16 "Yeah, but we've held great conferences in the past without ICANN. I just think that the whole ICANN/Internetnz thing has the capability to hijack NZNOG. " "May not be able to go if it's a teaching time. " "I'm OK for either, unless of course the cost is going to be much higher. A bit higher would be OK if we're talking 50-80 more. " "Very unlikely to attend, unless conf was over easter stat holidays. " "Not if I have to pay. " "Option B. It'd be easier to get to both Linux.conf.au & NZNOG if there is a bit of a gap between them. " "I would almost certainly attend either one, given that both the conference and I would be in Wellington. I'd have a slight preference for March/April due to (a) more chance of overseas networking folks (better timing for network-related things, and fewer clashes), and (b) making it easier to "catch up" on work immediately after Linux.Conf.au in Dunedin. " " If it is directly after linux.conf.au this would be good for getting overseas visitors with Linux interests (more interesting to me than networking people maybe), however it could be harder for me to get time off to go to two events in a row. " " Likely to attend either; more preference for option (b) on the basis that I'm not going to attend most of the ICANN stuff, so more likely to get interesting diverse speakers for an ICANN + NZNOG combo. " 4. Please comment on the following, how you feel about them and how important these are to you. # International Speakers "Important, but we only need a 2 or 3, - or at least 1 a day. " "Really important, it's the overseas speakers which many attendees need to justify the expense to bill payers. " "Good to have some, bad to have many. " "This is a big plus - makes the *management* see value in the event. " "It's very valuable to have 2-3 international speakers so that NZNOG doesn't become isolated from what's happening in the outside world. " "Important to give flavor and to justify attendance to boss. Perhaps only 2 or 3 needed. " > Low cost ( < $500 for programme + accommodation) [ Many people said low cost was *very* important while a few were happy to pay more. Perhaps a "professional" option could be offered ( with what? ) ] "I'm not convinced cost is as much of a barrier as people claim - I think that old saw of people struggling to get sign off on a $400 conference, but getting a $2400 conference approved with no hassle is probably more true than people realise. " "Too cheap for the quality of speakers / programme " "The cheaper it is, the more people I can send along. " " Important. Expense = must justify to bean counters. Certainly individuals are less likely to attend if its expensive. " "Very, I can't afford 500 for a conference " "Low costs means easy to get work to pay for it. " "It's good. It encourages participation. Participation is good. " " Important that it is affordable for people who have to pay their own way. (IE, don't aim it only as a company-sponsored-attendance event) " "Not fantastically important to cut the price to the bone. A good conference for teachers can be several thousand dollars! " " Personal I'd be happy with the program as long as it was sub-$1000 (easyish to get work to pay for that). However it would be great to see the cost stay low so people can pay for themselves if they want and to make it easy for the small-mid size companies. " "Important (helps to get a much bigger audience), but I don't think it's the end of the world if it went over a little over $500. " "I suspect attendance in Wellington will be lower simply due to a number of people in Auckland being willing/able to drive to Hamilton, but not willing/able to take the time to drive/fly to Wellington. (Adding in flights to the "total cost" may also be valuable in planning.) " "Very important to me. The low cost is the one of the main reasons why I decided to attend. " "Important. Low cost enables unfunded people to appear and for other to not to have to go to high up the food chain to attend. " "Yes - I pay for it myself. " "Very important - $500 would be about my limit " Types of attendees ------------------ [ Just about everybody was happy with the follow sort of people attending. ] - Network Operators (people who type BGP commands) - Admins of large websites - Admins of Large mail servers - Security Admins at large sites - Large ISP technical personal - Small ISP technical personal - Network researchers - Small Hosting providers - Students - Wireless Operators "I would like to hear about large mail system scaling. " "Am more interested if it is someone from a large site. " " I'd also like to see Design Engineers as there are people who don't necessarily type the commands into the 'live' systems, but they _design_ the system. " [ Re Security Admins at large sites ] "Especially dealing with large customer volumes and/or traffic volumes. (e.g. Managed firewalls doing 1Gb/s for 30,000 customers.) " " Yes. Small hosting providers could be future big hosting providers one day. " [ Most people were happy with the following although some expressed reservations. ] - Network consultants "as long as they're geeks and not suits" - Programmers (Open source projects) " Maybe, if they work on projects relevant to network operators " - Government Policy people ( eg MOC, CCIP) " In moderation. They seem to add little value and observe a hell of a lot. " " Definitely would like to see more policy presence. Policy becomes law becomes our implementation pain. " - Vendor sponsored speakers "If they agree to be 95% non-commercial " "As long as they aren't just salesman fine by me." "Great way of getting a speaker that would be otherwise hard to get" The following were less popular. - Equipment Vendor salesman " I suspect allowing too many vendors along spoils the open nature of the NZNOG conference, however the occasional bit is fine by me. " " No, Spray them with mace at the door. We can go do vendor sex at every other conference... " - Script Kiddies Ooh, this could be fun. We could all bring a baseball bat and have a go. That would be GREAT! [ NOTE: Similar to the above was said by several people. ] Other things ------------ # Official event dinner [ The majority of people felt this was very important ] "This is critical, as it involves beer." "Do it right or not at all" # Curry Night [ Many people rated this as more important than the official dinner while others were uninterested. ] "I prefer the socialising to the actual food. Personally I hate curries, but in a case like this I'll put up with them to be able to meet the people there. " "Being the night before, many people must have been like myself and unavailable... " "Important, but showing the strain of size. " # Joe and Dean [ Popular with most people. ] "NZNOG without Joe and Dean is like a fish without a bicycle! Important - as a guideline for the types of people we need there " " WTF? Is this NZ Network Idol? Puhhleeaazzee.. I mean they're good dudes and stuff, but this is about peering and not hierarchy isn't it? " # Wireless Access at event [ About one third of people didn't care while the others all rated it as vital. ] "Required. I actually fixed stuff while I was in a conference." # Nearness to the office. [ Not important to most, see Wireless question above. ] "The office is the laptop where the network connection terminates, isn't it? " "Important that it isn't " # Vendor Booths [ Quite a few negative comments here. I think people would be happy to have a few booths if they (a) Contributed to the bottom line of the conference and (b) Were targeted at the audience and interesting. ] "Prefer not to have them" "A couple would be nice especially if they had cute gear and helped subsidize events. " # Breaks between talks [ People thought these were good, no real consensus on how long however. People liked the free soft drinks in 05 but weren't so hot on the finger food ] "Smoker" "Hmm - I think the current format works, but there needs to be a larger 'buffer' zone to be used for spillover at the end of interesting presentations. Maybe if it could be structured so the presentations ran through to 6:30pm ish? " "Should be longish, talk is important." "Definitely good. Half of NZNOG's value is social" "It's very useful to have 10-15 minutes between talks to grab the speaker and ask questions. At most pairs of talks run together. The Linux.Conf.au pattern seems to work reasonably well. (45 minute talks, 15 minutes gap, talk often runs a little into the gab.) " "A few more than '05 might be good " "Keep them brief, a couple of sessions, then a break, etc.. I badly need a good way to secure my laptop. " "Not too long. While talk is good having 45 minute breaks all day is overdoing it. Perhaps 20 minutes for morning and afternoon tea and an hour for lunch. " # Start and finish times each day. [ Several people requested a slightly later start on Day 1 for those traveling. In general people seemed happy with a 9-6 , with perhaps some less official things going a little later. Starting before 9 was unpopular. ] "9-5 is good. " "I'd prefer a later start, since as we all know, we geeks tend to stay up late each night " # Wider programme or narrowly focused on Network operators. [ Very mixed results here. Hard core network geeks said keep it narrow while most other people wanted it a little wider. There appeared to be less objection if "non core" talks were on tutorial or in a separate stream. ] "I would enjoy a wider programme, but due to my work Network design/operation/engineering/support would be more useful to my employer. " "Focused on networks. I.E. not general Linux stuff." "Wider/Diverse programme, but with a Network Operator thing " "Wide programs are good if there are a couple of streams, otherwise you sit through stuff that isn't interest to. " "It occurred to me that it may make sense to (a) revive SAGE-NZ (a "NZ branch" of the System Administrators Guide) and (b) have some sort of system administrators stream. Perhaps there could be a SAGE-NZ "miniconf" the day before/after? " "Since network operators can also have other roles (mainly in small companies), its nice to have the programme focused a bit wider than just network operations. " # Single or Multiple streams. [ No real consensus ] "I would prefer single streams - if we have enough content, run for more days." "Multiple is good, but maybe just 2, ended up with overlaps of 2 interesting topics last time " "Single is best if the topics are related. If the two streams were quite separate (ie. Administrative and Technical) streamed would be OK. " "Single if possible but multiple might be an option. Perhaps if there were multiple then people could pick beforehand what talks they were interested in and we could schedule the clashes so a minimal number of people were disappointed." # Recording and/or broadcast of Events. [ This was split into two. Almost everyone was in favour of recording and making the event available later especially if there were multiple streams. Several people suggested not broadcasting it however to encourage people to tune up to the actual conference. ] "Absolutely to both." "great to go back to parts missed, or confirm something" "If I can't get there in person I will *definitely* watch the streams, either live or delayed. They're a great way to increase participation... " "Makes it difficult to argue I have to go. :) " "Recording everything definitely, especially if there are multiple streams. Broadcast isn't as important since it encourages people to actually attend. " "a good thing, but need to be much better quality than '05. Also open standards are good - I don't like having to install proprietary software. " # Giveaways [ People seemed to think these were okay to have but not very important. especially they didn't seem to want (a) Junk or (b) Lots of money being spent on them. ] " Yes - especially if it involves beer. " " Freebies rock. " " To be honest I'd happily trade a lower conference fee for no giveaways, or just a T-shirt. If they're sponsored bits then fine, but otherwise I think the money is better spent on something else. " " Not important to me " # Misc "Thinking back to '04, the best thing I felt about it was that the residential nature of the con forced a bunch of people to communicate who wouldn't otherwise do so (especially in person). So things that aid that (curry night, distance from the office, breaks between talks, common accommodation) seem to me important. " 5. Please rate on the following topics and make other comments if you like. [ I have rated the topics as following. The first number is the average score the topic received, the second is the number of people giving it a score of 4 or 5 while the 3rd number is the number giving it a score of 1 or 2. Around 30 to 35 people voted each time. I have chopped the list of topics into 3 groups (feel free to shuffle each group up or down a topic or two). The first groups appears to have a lot of people very interested and not many people disinterested. The second group have less but still positive net interest. The 3rd group have below average interest a a larger number of people uninterested. I would guess we aim for large or multiple talks from the first group and single, lightning, streamed or no talks on the others. All depends on offers and speakers obviously. Oh and if you don't know what LAMP is: http://en.wikipedia.org/wiki/LAMP ] VOIP : 4.3 27 0 Network Monitoring : 4.0 25 2 Peering : 4.0 23 2 Lightning talks : 3.9 23 3 Network Design Philosophy : 3.9 22 2 Network Measurement : 3.9 21 3 Internet Exchange Updates : 3.9 20 3 Security and Encryption : 3.8 21 2 IPV6 : 3.7 21 4 DDOS : 3.7 17 3 WAN Solutions / VPNs : 3.6 15 4 BGP and other routing protocols : 3.5 16 6 ENUM : 3.5 15 6 Fibre Optics : 3.3 12 8 Wireless : 3.3 10 4 Spam : 3.3 13 9 APNIC : 3.1 7 8 Mail Servers : 3.0 12 9 Virtual Servers (eg Xen, UML) : 3.0 11 10 MPLS : 2.9 11 13 Government Policy : 2.9 10 13 LDAP : 2.8 7 11 Multicast : 2.8 9 13 Web Server Administration : 2.7 7 15 Asset Management for Network Hardware : 2.6 9 15 UltraWideband : 2.6 9 15 LAMP : 2.6 6 12 INOC-DBA : 2.6 5 14 DNSSEC : 2.5 8 7 PGP Key Signing party : 2.5 8 20 Other Talk topics suggested: DNS (general) Clustering/Redundant Network Design Latest Internet practices (shaping etc) "things with cool factor For example unique and clever solutions to difficult problems. I think the conference should continue to aim not at a demographic (large ISP or small ISP), but just encouraging people to think up really just, I dunno *struggles trying not to use a buzz word* clever, outside the box solutions to hard problems. " 5. Are you interested in giving a talk? [ Around 1/3 the people who replied to the survey indicated interest in giving a talk. Some of these will be approached. ] 6. Other stuff. [ further quotes from people ] Fix the catering. - I thought the lightening talks were interesting, but maybe just a couple of minutes too short to be cover a complete topic, maybe 10 mins not 5 ? - Would be nice to see the program go up a little earlier to allow staff to plan to go (ie: not adding tutorials after people had booked) I don't recall having any linux/unix specific material at NOG '05, which is a fundamental part of most ISP networks in NZ. While it's a huge topic I'd have liked to hear some linux/Unix/Solaris specific content (not installfests) Perhaps some discussions of the future of Internet in NZ, and some predictions on where the Internet is heading based on current trends. I believe you touched on a couple of these areas briefly, which was nice. Not Hamilton, and a different time in the year. While publishing the programme early is good perhaps not having the exact timetable up will discourage managers from only assigning time for people to go to specific events. Perhaps an official wiki for people to post stuff or Blog aggregator. Small prizes ( USB fobs) for each speaker to give away per talk might encouraged people to ask good questions. Some howto guides for using network tools like nagios would be cool. A talk or two about how people see the Internet going. People I'd like to see: Somebody from Southern Cross talking about the cables. Somebody from Weta talking about the server or storage farm. Somebody from a large ISP talking about traffic shaping People talking about large storage Area networks People from some large sites ( Xtra, stuff, herald) talking about how they look after the network, servers, site, etc. Some practical VOIP stuff. I like Tshirts better than those with collars. If its in Wellington make some plan for flying people in and out of Palmerston and bus transit between. I have a hobbyist interest in community and non-profit networking; I don't know how that subject could be integrated though.

6 7

Ghetto colocation in wellington
by Tim Nicholas 11 May '05

11 May '05

Hi all, Does anywhere know of anyone who does cheap nasty collocation hosting in or around Wellington? I'm thinking no backup power, tower style boxes allowed, that sort of thing. Connectivity doesn't have to be too flash but availability of 8 or 16 IP addresses would be ideal. Reply to me directly. If there are enough responses to warrant it I'll summarise for the list. Thanks, Tim -- Tim Nicholas || TJN Email: tim(a)nicholas.net.nz || Wellington, New Zealand http://tim.nicholas.net.nz/ || Cell/SMS: +64 21 337 204

4 3

Barracuda Spam Firewalls...
by Dan Clark 09 May '05

09 May '05

Hi Guys, Can anyone who is using Barracuda Spam Firewalls in a Production ISP environment please contact me. I'm interested to know if they work well with multiple virtual hosts/domain names? Do they work straight out of the box? Are they fast? Is anyone running more than one in multiple locations, clustered etc? Are there any problems you may have noticed after you turned it on? Kind Regards Dan Clark Technical Director Synaptic Ltd

1 0

Videos of NZNOG-05 Tutorials now available
by Richard Naylor 04 May '05

04 May '05

Videos of the Tutorials from NZNOG-05 are now available at http://www.r2.co.nz/20050203/ We have updated the page with links to the tutorials. At this stage they are not available for downloading - that would depend on (polite) demand. Thanks to Jamie and the others for recording the sessions. Rich

1 0

Seminar in Hamilton.
by Richard Nelson 04 May '05

04 May '05

Rich Groves was scheduled to give a presentation at NZNOG'05 but was unable to make it due to immigration processing delays. He is going to give a (similar) presentation to WAND this Friday at 2pm at the University of Waikato. Sorry for the short notice, but if anybody would like to come, you would be welcome. Title "Creating a Passive Network Analysis Framework to Glean Internet Weather" Bio: Rich Groves is a former Principal Network Engineer at America Online and Network Architect at MCI and is now a Technologist at Endace as well as researcher for WAND. If anybody wants to come, please email me directly so I can keep track of numbers and I'll send you room details. The abstract of his planned NZNOG'05 talk was: The purpose of this project is to create a generic passive network monitoring framework for use with highly trafficked TCP applications. I will talk in depth about key performance indicators that we will use to assess the health of AOL Client streams as well as AOL Instant Messenger and ICQ. The location to glean this data is a number of tap points in front of the AOL Instant Messenger service. This is a staggering 400+ million TCP connects per day and places a veritable "Internet Weather Report" at our fingertips of round trip times, packet loss, latency and stability. This monitoring infrastructure will work as an "early warning" of negative client and transit network performance. Some other uses for this will be understanding the effects of changes during maintenance windows as well as providing data to compute a "user frustration index" that will give us more insight into client performance than active war dialers have. Richard Nelson richardn(a)cs.waikato.ac.nz WAND Network Research Group

1 0

any help appreciated
by Brett Johanson 03 May '05

03 May '05

Hello Im looking into setting up a data center, and am looking to peer with the ape, i was wondering how i can do this i am also applying for some IP space from apnic and having a little trouble setting up the PERSOn as it keeps failing. Any Help on this matter would be appreciated i just really need to know what to do to peer with the ape router recommendations etc Cheers _________________________________________________________________ Need more speed? Get Xtra Broadband @ http://jetstream.xtra.co.nz/chm/0,,202853-1000,00.html

6 7

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

02 May '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: filter-set: fltr-unallocated descr: Unallocated (by IANA) IPv4 prefixes. filter: {1.0.0.0/8^+, 2.0.0.0/8^+, 5.0.0.0/8^+, 7.0.0.0/8^+, 23.0.0.0/8^+, 27.0.0.0/8^+, 31.0.0.0/8^+, 36.0.0.0/8^+, 37.0.0.0/8^+, 39.0.0.0/8^+, 41.0.0.0/8^+, 42.0.0.0/8^+, 49.0.0.0/8^+, 50.0.0.0/8^+, 73.0.0.0/8^+, 74.0.0.0/8^+, 75.0.0.0/8^+, 76.0.0.0/8^+, 77.0.0.0/8^+, 78.0.0.0/8^+, 79.0.0.0/8^+, 89.0.0.0/8^+, 90.0.0.0/8^+, 91.0.0.0/8^+, 92.0.0.0/8^+, 93.0.0.0/8^+, 94.0.0.0/8^+, 95.0.0.0/8^+, 96.0.0.0/8^+, 97.0.0.0/8^+, 98.0.0.0/8^+, 99.0.0.0/8^+, 100.0.0.0/8^+, 101.0.0.0/8^+, 102.0.0.0/8^+, 103.0.0.0/8^+, 104.0.0.0/8^+, 105.0.0.0/8^+, 106.0.0.0/8^+, 107.0.0.0/8^+, 108.0.0.0/8^+, 109.0.0.0/8^+, 110.0.0.0/8^+, 111.0.0.0/8^+, 112.0.0.0/8^+, 113.0.0.0/8^+, 114.0.0.0/8^+, 115.0.0.0/8^+, 116.0.0.0/8^+, 117.0.0.0/8^+, 118.0.0.0/8^+, 119.0.0.0/8^+, 120.0.0.0/8^+, 121.0.0.0/8^+, 122.0.0.0/8^+, 123.0.0.0/8^+, 124.0.0.0/8^+, 125.0.0.0/8^+, 126.0.0.0/8^+, 173.0.0.0/8^+, 174.0.0.0/8^+, 175.0.0.0/8^+, 176.0.0.0/8^+, 177.0.0.0/8^+, 178.0.0.0/8^+, 179.0.0.0/8^+, 180.0.0.0/8^+, 181.0.0.0/8^+, 182.0.0.0/8^+, 183.0.0.0/8^+, 184.0.0.0/8^+, 185.0.0.0/8^+, 186.0.0.0/8^+, 187.0.0.0/8^+, 189.0.0.0/8^+, 190.0.0.0/8^+, 197.0.0.0/8^+, 223.0.0.0/8^+} remarks: For the complete set of bogons, please see: fltr-martians - special use and reserved prefixes. fltr-bogons - fltr-unallocated + fltr-martian. http://www.cymru.com/Documents/bogon-list.html admin-c: RTH32-ARIN tech-c: RTH32-ARIN notify: radb(a)cymru.com notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz mnt-by: MAINT-BOGON-FILTERS changed: rpsl-admin(a)nzix.net 20040819 source: NZRR REPLACED BY: filter-set: fltr-unallocated descr: Unallocated (by IANA) IPv4 prefixes. filter: {1.0.0.0/8^+, 2.0.0.0/8^+, 5.0.0.0/8^+, 7.0.0.0/8^+, 23.0.0.0/8^+, 27.0.0.0/8^+, 31.0.0.0/8^+, 36.0.0.0/8^+, 37.0.0.0/8^+, 39.0.0.0/8^+, 42.0.0.0/8^+, 49.0.0.0/8^+, 50.0.0.0/8^+, 74.0.0.0/8^+, 75.0.0.0/8^+, 76.0.0.0/8^+, 77.0.0.0/8^+, 78.0.0.0/8^+, 79.0.0.0/8^+, 89.0.0.0/8^+, 90.0.0.0/8^+, 91.0.0.0/8^+, 92.0.0.0/8^+, 93.0.0.0/8^+, 94.0.0.0/8^+, 95.0.0.0/8^+, 96.0.0.0/8^+, 97.0.0.0/8^+, 98.0.0.0/8^+, 99.0.0.0/8^+, 100.0.0.0/8^+, 101.0.0.0/8^+, 102.0.0.0/8^+, 103.0.0.0/8^+, 104.0.0.0/8^+, 105.0.0.0/8^+, 106.0.0.0/8^+, 107.0.0.0/8^+, 108.0.0.0/8^+, 109.0.0.0/8^+, 110.0.0.0/8^+, 111.0.0.0/8^+, 112.0.0.0/8^+, 113.0.0.0/8^+, 114.0.0.0/8^+, 115.0.0.0/8^+, 116.0.0.0/8^+, 117.0.0.0/8^+, 118.0.0.0/8^+, 119.0.0.0/8^+, 120.0.0.0/8^+, 121.0.0.0/8^+, 122.0.0.0/8^+, 123.0.0.0/8^+, 173.0.0.0/8^+, 174.0.0.0/8^+, 175.0.0.0/8^+, 176.0.0.0/8^+, 177.0.0.0/8^+, 178.0.0.0/8^+, 179.0.0.0/8^+, 180.0.0.0/8^+, 181.0.0.0/8^+, 182.0.0.0/8^+, 183.0.0.0/8^+, 184.0.0.0/8^+, 185.0.0.0/8^+, 186.0.0.0/8^+, 187.0.0.0/8^+, 189.0.0.0/8^+, 190.0.0.0/8^+, 197.0.0.0/8^+, 223.0.0.0/8^+} remarks: For the complete set of bogons, please see: fltr-martians - special use and reserved prefixes. fltr-bogons - fltr-unallocated + fltr-martian. http://www.cymru.com/Documents/bogon-list.html admin-c: RTH32-ARIN tech-c: RTH32-ARIN notify: radb(a)cymru.com notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz mnt-by: MAINT-BOGON-FILTERS changed: rpsl-admin(a)nzix.net 20040819 source: NZRR

1 0

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

02 May '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: AS2687 as-name: NZRR-AS2687 descr: AT&T Global descr: WIX peering at '202.7.0.49' descr: see Citylink RT job #1979 descr: APE peering at '192.203.154.74' descr: see Citylink RT job #2334 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS2687 import: from AS9560 accept ANY AND NOT fltr-bogons export: to AS9560 announce AS2687 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 20050503 source: NZRR REPLACED BY: aut-num: AS2687 as-name: NZRR-AS2687 descr: AT&T Global descr: WIX peering at '202.7.0.49' descr: see Citylink RT job #1979 descr: APE peering at '192.203.154.74' descr: see Citylink RT job #2334 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS2687 import: from AS9560 accept ANY AND NOT fltr-bogons export: to AS9560 announce AS2687 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 20050503 source: NZRR

1 0

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

02 May '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: AS2687 as-name: NZRR-AS2687 descr: AT&T descr: APE peering at '192.203.154.74' descr: see Citylink RT job #2334 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9560 accept ANY AND NOT fltr-bogons export: to AS9560 announce AS2687 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: Mark.Crawford(a)ap.att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050503 source: NZRR REPLACED BY: aut-num: AS2687 as-name: NZRR-AS2687 descr: AT&T Global descr: WIX peering at '202.7.0.49' descr: see Citylink RT job #1979 descr: APE peering at '192.203.154.74' descr: see Citylink RT job #2334 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS2687 import: from AS9560 accept ANY AND NOT fltr-bogons export: to AS9560 announce AS2687 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 20050503 source: NZRR

1 0