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
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
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
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
import: from AS9439
accept ANY AND NOT fltr-bogons
export: to AS9439
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 20050302
source: NZRR
REPLACED BY:
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
The New Zealand Network Operators' Group
The New Zealand Network Operators' Group (NZNOG) has no king,
president or formal membership. It consists of the subscribers to this
mailing list, which anyone is free to join.
Conference
Our next conference is expected to take place in Wellington in the first
half of 2006. If you're interested inattending, you have replied to the
survey, haven't you?
Other Meetings
See http://auckland.thursdaynightcurry.com/ or
http://wellington.thursdaynightcurry.com/ if you live in or near
Auckland or Wellington.
Operators' Contact List
See http://www.usenet.net.nz/noc/ for operational contact details
for most New Zealand ISP's. These are intended for use by other
network operators, not by most customers.
Internet Exchanges
See http://nzix.net/ for details of the Auckland, Palmerston North and
Wellington exchanges, and some information on others under construction.
About This Mailing List
This list has around 800 addresses subscribed. You may only post to the
list from a subscribed address. A number of people subscribe addresses
which do not receive email purely to allow posting from them.
You may choose to receive postings as they come in, or just to receive
daily "digests". See the bottom of the page
http://list.waikato.ac.nz/mailman/listinfo/nznog/ to change the form in
which you receive postings.
The NZNOG mailing list is provided through a server at The University of
Waikato, and is administered by employees of Alcatel NZ Ltd, Citylink
and Telecom. None of these organisations, nor any administrator, is
responsible for its content.
NZNOG Mailing List Acceptable Use Policy
The NZNOG mailing list exists to provide a forum for the exchange of
technical information and the discussion of implementation issues
that require cooperation among New Zealand network service providers.
In order to continue to provide a useful forum for discussion of
relevant technical issues, users of the list are asked to respect the
following guidelines.
1. Discussion will focus on Internet operational and technical
issues.
2. Discussion related to meetings of network service providers is
appropriate.
3. Discussion unrelated to these topics is not appropriate.
4. Postings to multiple mailing lists are discouraged.
5. Postings that include foul language, character assassination, and
lack of respect for other participants are unacceptable.
6. Blatant product or service marketing is unacceptable.
7. Postings of a political, philosophical or legal nature are
discouraged.
8. Postings to the list should be in ASCII or MIME encoded as
text/plain. Attachments should not be sent to the list. To
present a document, a suitable URL may be referred to. For
documents of general interest, the use of proprietary file
formats is discouraged.
9. Breaches of list etiquette should be dealt with privately with the
offending list user, and should not result in complaints being
sent to the list.
10. A person repeatedly breaching list etiquette shall receive warnings
from the list administrator. A further breach after the second such
warning within thirty days shall result in the offender being
unsubscribed from the list. Other action may also be taken to block
postings to the list by the offender. Any such unsubscription is to
be immediately announced to the list.
Mailing List Archives
A full archive is available at
http://list.waikato.ac.nz/pipermail/nznog/
Any message sent to the list will be archived and made available on the
web automatically. Changes are not made to the archive on request,
though the administrators remain happy to assist the Office of the
Privacy Commissioner should any complaint be laid with that office.
One way to search the archive is to use google and prefix your search
with
site:list.waikato.ac.nz .
Subscribing to the List
See http://list.waikato.ac.nz/mailman/listinfo/nznog to subscribe.
Donald Neal
NZNOG Mailing List Owner/Administrator/Muggins
"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."
Below is a series of questions about NZNOG 05 and 06. Please fill out as many
questions as you can and feel free to add extra comments wherever. The
results will be used to decide when, where and how NZNOG 06 will be run.
If you are short of time please fill out the 2006 questions first. Email
the filled in version back to simon(a)darkmere.gen.nz . Email me if you have
any questions.
Answers will be kept confidential. Results will be summarized back to the list.
Questions
=========
About you
---------
Which City/Country do you live/work in :
What position do you work in :
What does your job involve :
Attendance
----------
Did you attend NZNOG 05 ? :
Did you attend NZNOG 04 ? :
Did you attend earlier NZNOGs? :
If you didn't attended NZNOG 05:
a. what reasons didn't your attend?
b. What would have made you more likely to attend?
NZNOG 05
--------
If you attended NZNOG 05 please answer the following questions.
1. Did your employer pay for all or part of the costs? Did they give you
time to attend or did you have to take holidays?
2. Please comment on the following, how you feel about them and how important
these are to you.
General organization:
Accommodation:
Wednesday night dinner (curry):
Thursday Dinner (Official dinner):
Internet Access:
Other:
3. The main presentations.
Abstracts of the presentations and tutorials at nznog05 are at:
http://www.nznog.org/tutorial.phphttp://www.nznog.org/abstract.php
a. Can you list things in the programme or the conference that your
especially liked.
b. Can you list things in the programme or the conference that your
especially disliked.
c. Do you have any other comments about the programme or running of the
conference.
NZNOG 06
--------
1. Are you likely to attend NZNOG 06.
2. Are you likely to attend Linux.conf.au in Dunedin at the end of Jan 06?
3. The following are venues/times that NZNOG might be held. Please rate
how likely your are to attend and which you would prefer.
a. Wellington in late Jan or Early Feb ( after linux.conf.au)
Pro: Overseas people able to go to linux.conf.au and NZNOG
Pro: Cheaper Accommodation and Venue
Con: Clashes with NANOG or RIPE so harder to get overseas speakers
b. Wellington in March or early April
Pro: Less clashes with overseas events.
Pro: Overseas people able to go to ICANN and NZNOG
Con: Most expensive venue and accommodation.
4. Please comment on the following, how you feel about them and how important
these are to you.
International Speakers:
Low cost ( < $500 for programme + accommodation):
Types of attendees
- Network Operators (people who type BGP commands):
- Admins of large websites:
- Admins of Large mail servers:
- Security Admins at large sites:
- Network consultants:
- Large ISP technical personal:
- Small ISP technical personal:
- Programmers (Open source projects):
- Script Kiddies:
- Vendor sponsored speakers:
- Network researchers:
- Government Policy people ( eg MOC, CCIP):
- Small Hosting providers:
- Equipment Vendor salesman:
- Students:
- Wireless Operators:
Official event dinner:
Curry Night:
Joe and Dean:
Wireless Access at event:
Nearness to the office:
Vendor Booths:
Breaks between talks:
Start and finish times each day:
Wider programme or narrowly focused on Network operators:
Single or Multiple streams:
Recording and/or broadcast of Events:
Giveaways:
4. Please rate on the following topics and make other comments if you like.
5 is "Extremely interested"
3 is "Interested enough to attend"
1 is "I'll work on my minesweeper skills outside"
Peering :
DNSSEC :
Internet Exchange Updates :
INOC-DBA :
APNIC :
Virtual Servers (eg Xen, UML) :
Lightning talks :
PGP Key Signing party :
Mail Servers :
DDOS :
Network Monitoring :
LAMP :
Measurement :
Government Policy :
Wireless :
Spam :
IPV6 :
VOIP :
ENUM :
Multicast :
BGP and other routing protocols :
UltraWideband :
MPLS :
WAN Solutions / VPNs :
Fibre Optics :
LDAP :
Network Measurement :
Asset Management for Network Hardware :
Network Design Philosophy :
Security and Encryption :
Web Server Administration :
Other(s) (please add) :
5. Are you interested in giving a talk?
Talks can be tutorials, 30m-2h presentations or 5-10 minutes lightning talks.
Please let us know if you are interested in giving one and if possible what
type and what topic(s).
6. Other stuff.
Please add other comments, suggestions, feedback etc on what you would like
for the 06 conference including possible speakers, talks, events and topics
not mentioned above.
AS: 4770
APE: 192.203.154.44
WIX: 202.7.1.1
Hey all,
For all those that peer direct with ICONZ there is another update.
Please apply the full list as there have been a few additions.
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
Dear Colleagues,
This announcement is being sent to multiple lists. I apologise for
duplicates.
The RIPE NCC received the IPv4 address range 85.0.0.0 - 88.255.255.255
(85/8, 86/7 and 88/8) from the IANA in April 2004.
We began making allocation from 85/8 in August 2004 and from 86/8 in
March, this year. We expect to start making allocations from 87/8 in
the next few weeks.
We have been announcing two prefixes from 87/8: 87.192.0.0/16 and
87.255.248.0/21, which originated in AS12654. These announcements have
now been withdrawn as we will start to allocate from this /8. We are
currently announcing two prefixes from 88/8, from which we will
allocate in a few months. Those announcements are: 88.192.0.0/16 and
88.255.248.0/21, originating in AS12654.
Details of the BGP announcements, reachability tools and other
information are available on our web site at:
http://www.ris.ripe.net/debogon/debogon.html
You may want to update any filters you have in place.
Kind regards,
--
leo vegoda
Registration Services Manager
RIPE NCC
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: AS9439:RS-ROUTES:AS64562
descr: advertised to AS9439 by Liverton Limited - AS64562
members: 210.48.106.96/28^28-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: james.scott(a)liverton.com
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20050113
source: NZRR
REPLACED BY:
route-set: AS9439:RS-ROUTES:AS64562
descr: advertised to AS9439 by Liverton Limited - AS64562
members: 202.160.49.32/28^28-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: james.scott(a)liverton.com
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20050420
source: NZRR
---
PREVIOUS OBJECT:
route-set: AS9439:RS-ROUTES:AS24005
descr: advertised to AS9439 by SafeNZ Networks Limited - AS24005
members: 203.98.6.0/24^24-29,
203.97.68.0/28^28-29,
219.88.140.0/24^24-29,
60.234.32.0/23^23-29,
219.88.140.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: tonyw(a)tonyw.com
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20050318
source: NZRR
REPLACED BY:
route-set: AS9439:RS-ROUTES:AS24005
descr: advertised to AS9439 by safenz networks limited - AS24005
members: 203.98.6.0/24^24-29,
203.97.68.0/28^28-29,
219.88.140.0/24^24-29,
60.234.32.0/23^23-29,
202.137.240.0/21^21-29,
202.50.252.0/24^24-29,
203.167.254.0/24^24-29,
203.167.255.0/24^24-29,
203.97.6.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: tonyw(a)tonyw.com
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20050420
source: NZRR
