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:AS38037
descr: Route set advertised to AS9439 by InternetNZ - AS38037
members: 202.46.176.0/21^21-29,
131.203.101.48/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: noc(a)fx.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20060615
source: NZRR
REPLACED BY:
route-set: AS9439:RS-ROUTES:AS38037
descr: advertised to AS9439 by InternetNZ - AS38037
members: 202.46.176.0/21^21-29,
131.203.101.48/28^28-29,
161.29.193.16/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: noc-minor(a)fx.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20060911
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:
route-set: AS9439:RS-ROUTES:AS17412
descr: advertised to AS9439 by Woosh Wireless Limited - AS17412
members: 202.74.192.0/19^19-29,
203.211.64.0/19^19-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: sysadmin(a)woosh.com
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20060315
source: NZRR
REPLACED BY:
route-set: AS9439:RS-ROUTES:AS17412
descr: advertised to AS9439 by Woosh Wireless Limited - AS17412
members: 203.211.64.0/18^18-29,
202.74.192.0/19^19-29,
202.89.128.0/19^19-29,
202.21.16.0/20^20-29,
202.37.90.0/23^23-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: sysadmin(a)woosh.com
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20060911
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:
route-set: AS9560:RS-ROUTES:AS17412
descr: advertised to AS9560 by Woosh Wireless Limited - AS17412
members: 202.74.192.0/19^19-29,
203.211.64.0/19^19-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: sysadmin(a)woosh.com
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20060315
source: NZRR
REPLACED BY:
route-set: AS9560:RS-ROUTES:AS17412
descr: advertised to AS9560 by Woosh Wireless Limited - AS17412
members: 203.211.64.0/18^18-29,
202.74.192.0/19^19-29,
202.89.128.0/19^19-29,
202.21.16.0/20^20-29,
202.37.90.0/23^23-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: sysadmin(a)woosh.com
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20060911
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:
route-set: AS9560:RS-ROUTES:AS4770
descr: advertised to AS9560 by ICONZ - AS4770
members: 131.203.0.0/16^16-29,
161.29.0.0/16^16-29,
161.65.0.0/16^16-29,
210.48.0.0/17^17-29,
210.185.0.0/18^18-29,
210.54.160.0/19^19-29,
202.50.208.0/20^20-29,
202.53.176.0/20^20-29,
202.55.96.0/20^20-29,
202.174.160.0/20^20-29,
202.191.32.0/20^20-29,
210.56.32.0/20^20-29,
192.173.16.0/21^21-29,
202.12.248.0/21^21-29,
202.37.144.0/21^21-29,
202.37.224.0/21^21-29,
202.46.176.0/21^21-29,
202.50.200.0/21^21-29,
202.74.224.0/21^21-29,
202.78.240.0/21^21-29,
202.126.80.0/21^21-29,
203.190.208.0/21^21-29,
205.233.128.0/21^21-29,
202.36.36.0/22^22-29,
202.37.140.0/22^22-29,
202.37.200.0/22^22-29,
202.41.136.0/22^22-29,
202.50.52.0/22^22-29,
202.50.196.0/22^22-29,
202.59.4.0/22^22-29,
210.54.136.0/22^22-29,
210.55.24.0/22^22-29,
202.21.136.0/23^23-29,
202.36.44.0/23^23-29,
202.36.76.0/23^23-29,
202.37.86.0/23^23-29,
202.37.240.0/23^23-29,
202.37.252.0/23^23-29,
202.49.80.0/23^23-29,
202.50.246.0/23^23-29,
202.124.106.0/23^23-29,
205.233.136.0/23^23-29,
210.55.182.0/23^23-29,
192.88.85.0/24^24-29,
192.107.113.0/24^24-29,
192.133.31.0/24^24-29,
192.173.24.0/24^24-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.14.100.0/24^24-29,
202.20.6.0/24^24-29,
202.20.97.0/24^24-29,
202.21.130.0/24^24-29,
202.27.208.0/24^24-29,
202.36.119.0/24^24-29,
202.36.155.0/24^24-29,
202.36.157.0/24^24-29,
202.36.183.0/24^24-29,
202.36.226.0/24^24-29,
202.37.76.0/24^24-29,
202.37.85.0/24^24-29,
202.37.136.0/24^24-29,
202.37.163.0/24^24-29,
202.37.197.0/24^24-29,
202.37.232.0/24^24-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.159.0/24^24-29,
202.49.249.0/24^24-29,
202.50.87.0/24^24-29,
203.97.5.0/24^24-29,
205.233.243.0/24^24-29,
210.54.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: john(a)iconz.net
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20060721
source: NZRR
REPLACED BY:
route-set: AS9560:RS-ROUTES:AS4770
descr: advertised to AS9560 by ICONZ - AS4770
members: 131.203.0.0/16^16-29,
161.29.0.0/16^16-29,
161.65.0.0/16^16-29,
210.48.0.0/17^17-29,
210.185.0.0/18^18-29,
210.54.160.0/19^19-29,
202.50.208.0/20^20-29,
202.53.176.0/20^20-29,
202.55.96.0/20^20-29,
202.174.160.0/20^20-29,
202.191.32.0/20^20-29,
210.48.160.0/20^20-29,
210.56.32.0/20^20-29,
192.173.16.0/21^21-29,
202.12.248.0/21^21-29,
202.37.144.0/21^21-29,
202.37.224.0/21^21-29,
202.46.176.0/21^21-29,
202.50.200.0/21^21-29,
202.74.224.0/21^21-29,
202.78.240.0/21^21-29,
202.126.80.0/21^21-29,
203.190.208.0/21^21-29,
205.233.128.0/21^21-29,
202.36.36.0/22^22-29,
202.37.140.0/22^22-29,
202.37.200.0/22^22-29,
202.41.136.0/22^22-29,
202.50.52.0/22^22-29,
202.50.196.0/22^22-29,
202.59.4.0/22^22-29,
210.54.136.0/22^22-29,
210.55.24.0/22^22-29,
202.21.136.0/23^23-29,
202.36.44.0/23^23-29,
202.36.76.0/23^23-29,
202.37.86.0/23^23-29,
202.37.240.0/23^23-29,
202.37.252.0/23^23-29,
202.49.80.0/23^23-29,
202.50.246.0/23^23-29,
202.124.106.0/23^23-29,
205.233.136.0/23^23-29,
210.55.182.0/23^23-29,
192.88.85.0/24^24-29,
192.107.113.0/24^24-29,
192.133.31.0/24^24-29,
192.173.24.0/24^24-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.14.100.0/24^24-29,
202.20.6.0/24^24-29,
202.20.97.0/24^24-29,
202.21.130.0/24^24-29,
202.27.208.0/24^24-29,
202.36.119.0/24^24-29,
202.36.155.0/24^24-29,
202.36.183.0/24^24-29,
202.36.226.0/24^24-29,
202.37.76.0/24^24-29,
202.37.85.0/24^24-29,
202.37.136.0/24^24-29,
202.37.163.0/24^24-29,
202.37.197.0/24^24-29,
202.37.232.0/24^24-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.159.0/24^24-29,
202.49.249.0/24^24-29,
202.50.87.0/24^24-29,
203.97.5.0/24^24-29,
205.233.243.0/24^24-29,
210.54.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: deon(a)iconz.net
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20060911
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:
route-set: AS9560:RS-ROUTES:AS24324
descr: advertised to AS9560 by Broadcast Communications Ltd - AS24324
members: 124.157.64.0/19^19-29,
202.49.128.0/21^21-29,
218.185.224.0/21^21-29,
202.27.83.0/24^24-29,
202.36.75.0/24^24-29,
202.36.154.0/24^24-29,
202.37.168.0/24^24-29,
202.49.183.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: smc(a)bclnz.com
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20060810
source: NZRR
REPLACED BY:
route-set: AS9560:RS-ROUTES:AS24324
descr: advertised to AS9560 by BCL - AS24324
members: 124.157.64.0/19^19-29,
202.49.128.0/21^21-29,
218.185.24.0/21^21-29,
202.27.83.0/24^24-29,
202.36.75.0/24^24-29,
202.36.154.0/24^24-29,
202.37.168.0/24^24-29,
202.49.183.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: leon.chang(a)bclnz.com
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20060911
source: NZRR
Why is snap not peering with the Auckland peering exchange? Damn slow
exchanging data with some clients when using snap internet through
the global gateway compared to when using an ISP who use APE.
Regards,
Ernest Cunningham
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:AS9889
descr: advertised to AS9560 by Maxnet - AS9889
members: 202.89.32.0/19^19-29,
203.89.160.0/19^19-29,
210.55.100.0/22^22-29,
210.55.104.0/22^22-29,
192.138.251.0/24^24-29,
202.6.5.0/24^24-29,
202.27.204.0/24^24-29,
202.36.70.0/24^24-29,
202.36.227.0/24^24-29,
202.37.72.0/24^24-29,
202.37.181.0/24^24-29,
202.49.141.0/24^24-29,
202.150.102.0/24^24-29,
203.97.42.0/24^24-29,
210.54.13.0/24^24-29,
210.54.142.0/24^24-29,
210.55.169.0/24^24-29,
210.55.214.0/24^24-29,
210.55.230.0/24^24-29,
203.167.219.56/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 20051125
source: NZRR
REPLACED BY:
route-set: AS9560:RS-ROUTES:AS9889
descr: advertised to AS9560 by Maximum Internet Ltd - AS9889
members: 202.89.32.0/19^19-29,
203.89.160.0/19^19-29,
210.55.100.0/22^22-29,
210.55.104.0/22^22-29,
202.6.116.0/23^23-29,
192.138.251.0/24^24-29,
202.6.5.0/24^24-29,
202.27.204.0/24^24-29,
202.36.70.0/24^24-29,
202.36.227.0/24^24-29,
202.37.72.0/24^24-29,
202.37.181.0/24^24-29,
202.49.141.0/24^24-29,
202.150.102.0/24^24-29,
203.97.42.0/24^24-29,
210.54.13.0/24^24-29,
210.54.142.0/24^24-29,
210.55.169.0/24^24-29,
210.55.214.0/24^24-29,
210.55.230.0/24^24-29,
203.167.219.56/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)maxnet.co.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20060907
source: NZRR
NZNOG 07 - Call for Participation and Papers
The next conference of the New Zealand Network Operators' Group is to be held
in Palmerston North, New Zealand between 31 January and 2 February 2007. Our
host is Inspire.net and the venue is to be at Massey University's campus.
NZNOG meetings provide opportunities for the exchange of technical
information and discussion of issues relating to the operation and
support of network services, with particular emphasis on New Zealand.
The conference is low priced and has a strong technical focus with the
aim and history of getting a strong turnout of technical personal from
New Zealand Internet orientated companies.
Conference Overview
-------------------
NZNOG 2007 will consist of one day Special Interest Group ( SIG ) Meetings
followed by two days of conference presentations. There will also be
opportunity for more informal and small lightening talks. These are typically
around five minutes long and are organised closer to the actual conference.
Important Dates
---------------
Call for Papers opens: 5 September 2006
Deadline for speaker submissions: 20 October 2006
Responses to speaker submissions: 27 October 2006
Draft program published: 1 November 2006
Final program published: 18 December 2006
NZNOG 2007 Conference: 31 January - 2 February 2007
SIG Meetings
------------
The first day of the conference is arranged as parallel tracks to
cover subject material which is of interest to particular groups of
attendees. Proposals are requested for workshops, tutorials and other
appropriate special-interest meetings of interest to Network Operators.
Topics which have been successful in the past, or have been requested
for this year are:
* Advanced BGP gubbins
* IPV6 implementation
* Service Provider wireless networking
* VoIP
* BIND and DNSSEC
* MPLS and high performance IP backbone routing
* Systems Administration.
The program committee will consider proposals for tutorials in any of these
or new areas. There is a single day of SIGs with up to five running
concurrently.
If you have an idea for a tutorial subject that is not listed, please feel
free to submit it to us.
Conference Presentations
------------------------
The main conference program for 2007 will be made up of two days with a
single stream where possible. Presentations don't need to fit any particular
fixed length and can be from 30 minutes to 3 hours in length.
NZNOG conferences have traditionally spanned the entire operational spectrum,
and then some. Proposals for conference presentations are invited for
virtually any topic with a degree of relevance to the NZNOG community.
Past years' talks have included the following:
- Internet exchange operations
- Global anycast networks and the building thereof
- Peering, peering, and peering
- Network security
- 10GB ethernet operations
- Advanced networks in NZ
- Current Internet research in NZ
- Wireless networking
- QOS over carrier networks
- Content distribution networks and media streaming
If you are interested in submitting a talk please fill out the questions
at then end of this document and email them to talks(a)nznog.org .
Submission Guidelines
---------------------
When considering a presentation or SIG, remember that the NZNOG audience
is mainly comprised of technical network operators and engineers with a wide
range of experience levels from beginners to multi-year experience. There is
a strong orientation to offer core skills and basic knowledge in the SIGs
and to address issues relevant to the day-to-day operations of ISPs and
network operators in the conference sessions.
The inclusion of a title, bio, topic, abstract, and slides with proposals
is not compulsory but each will help us determine the quality of your
proposal and increase the likelihood it will be accepted.
Final slides are to be provided by 22 January 2007.
Note: While the majority of speaking slots will be submitted by 20 October
2006, a limited number of slots may be available for presentations that are
exceptionally timely, important, or of critical operational importance.
The NZNOG conference is a TECHNICAL conference so marketing and commercial
content is NOT allowed within the program. The program committee is charged
with maintaining the technical standard of NZNOG conferences, and will
therefore not accept inappropriate materials. It is expected that the
presenter be a technical person and not a sales or marketing person. The
audience is extremely technical and unforgiving, and expects that the speakers
are themselves very knowledgeable. All sessions provide time for questions,
so presenters should expect technical questions and be prepared to deliver
insightful and technically deep responses.
Funding and Support
-------------------
NZNOG conferences are community run and funded events that try to keep the
cost to attendees as low as possible so generally we are unable to pay the
travel costs of speakers. There is a limited amount of funding available to
international speakers.
Conference presenters will not have to pay any registration fee for the day
they are presenting. Discounts for SIG and lightning talk presenters may
be available but are not automatic.
Lightning talks
---------------
Lightning talks are short talks/presentations that last no more than 10
minutes. This is a good opportunity to get your pet topic out there or
perhaps to get some experience with presenting without having to go to a
full talk. At NZNOG'07 it is planned that there will be at least one
hour long lightning talk session.
Sponsors
--------
There are opportunities remaining for organisations to sponsor various
aspects of the NZNOG meeting.
Please contact sponsorship(a)nznog.org for more information
Contact
-------
Website
* www.nznog.org
General Enquiries
* info(a)nznog.org
Talks and Papers
* talks(a)nznog.org
Talk Proposals
--------------
Please send all talk proposals (including lightning talks) to talks(a)nznog.org
along with the requested information. Questions regarding talks can be
sent to the same address.
Sponsorship may be available for a limited number of overseas speakers
to attend the conference, please indicate if you require assistance
with travel and/or accommodation.
Author's Full Name:
Author's Email Address:
Author's affiliation:
Author's short biography:
Title of Talk:
Abstract:
Length of talk:
Please provide details if a version of this talk has previously been given:
Will travel and accommodation assistance be required:
[Apologies for duplicate mails]
Dear Colleagues,
The RIPE NCC received the IPv4 address ranges 77.0.0.0/8 and 78.0.0.0/7
from the IANA in August 2006. We will begin allocating from these ranges
in the near future.
The minimum allocation size for these four /8s has been set at /21. You
may wish to adjust any filters you have in place accordingly.
More information on the IP space administered by the RIPE NCC can be
found on our web site at:
https://www.ripe.net/ripe/docs/ripe-ncc-managed-address-space.html
Additionally, please note that two "pilot" prefixes are being announced
from each /8. Details of the prefixes, 'pingable' target names and
addresses for each prefix can be found on our web site at:
http://www.ris.ripe.net/debogon/debogon.html
Best regards,
--
leo vegoda
Registration Services Manager
RIPE NCC
Today at 6pm (I think) they're launching KAREN (Kiwi Academic Research and
Education Network). Theres a webcast at
<http://www.r2.co.nz/20060831/>http://www.r2.co.nz/20060831/
and includes (hopefully) a webcast of the Access grid in session.
