[Apologies for duplicates...]
NZNOG 2011 - Call for Participation and Papers
The next conference of the New Zealand Network Operators' Group is to be
held in Wellington, New Zealand between 26 January and 28 January 2011. Our
host is Vodafone New Zealand.
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 2011 will consist of up to three days of workshops and tutorials 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: 1 November 2010
Deadline for speaker submissions: 1 December 2010
Responses to speaker submissions: 7 December 2010
Draft program published: 15 December 2010
Final program published: 15 January 2011
NZNOG 2011 Conference: 26 - 29 January 2011
SIG / Miniconf / Tutorials / Workshops
--------------------------------------
In previous years we have had a single day of workshops and tutorials,
this year however we are looking at having up to three days of workshops
and tutorials, if we can get the submissions.
Examples of past activities workshops include 'MPLS and fixed access
networks for beginners', 'Mikrotik RouterOS Training', 'APNIC Internet
Resource Management Essentials', and a System Administrators
mini-conference which included talks on 'Using Debian packages for
system administration' and '42 hosts in 1U: Using virtual machines'.
Conference Presentations
------------------------
The main conference program for 2011 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
- How to build a router in these tough and difficult economic times
- Current Internet research in NZ
- Wireless networking
- QOS over carrier networks
- Content distribution networks and media streaming
- Open Source VoIP Platform in Carrier Environments
- Lawful Interception
- Designing networks for High Availability
- ISP scenarios for IPv6 deployment
- Monkeying around on the APE
Some ideas for this year also include the following:
- IPv6, been there done that
- DNS Security
- Routing Security
- Review of 2010
- IPSec
- Internet Filtering
- How Cloud Computing has impacted Network Design
If you are interested in submitting a talk please fill out the questions
at then end of this document and submit them to http://submission.nznog.org
Alternatively, you can 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 15 January 2011.
Note: While the majority of speaking slots will be submitted by 15
December 2010,
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 2011 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
-------
General Enquiries
* info(a)nznog.org
Talks and Papers
* http://submission.nznog.org
* talks(a)nznog.org
Talk Proposals
--------------
Please submit all talk proposals (including lightning talks) via
http://submission.nznog.org or email 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:
[Obligatory apology for duplicates...]
Asia Pacific Regional Internet Conference on Operational Technologies
(APRICOT)
15 - 25 February 2011, Hong Kong
http://www.apricot2011.net
CALL FOR PAPERS
===============
The APRICOT 2011 Programme Committee is now seeking contributions for
Presentations and Tutorials for APRICOT 2011.
We are looking for people and proposals that would:
- Offer a technical tutorial on an appropriate topic; and/or
- Participate in the technical conference sessions as a speaker; and/or
- Convene and chair a Birds of a Feather (BOF) session.
Please submit proposals on-line at
http://www.apricot2011.net/call-for-papers/submission
CONFERENCE MILESTONES
---------------------
Call for Papers Opens: 29 October 2010
First Deadline for Submissions: 29 November 2010
First Draft Programme Published: 6 December 2010
Final Deadline for Submissions: 4 February 2011
Final Programme Published: 11 February 2011
Final Slides Received: 19 February 2011
PROGRAM MATERIAL
----------------
The APRICOT Programme is organised in three parts, including
workshops, tutorials and the conference. The APNIC Policy SIG and
Annual Members Meeting will be held during the APRICOT conference.
Topics for tutorials and conference would include amongst others
relevant to Internet Operations and Technologies:
- IPv4 / IPv6 Routing and operations
- IPv4 address runout / IPv6 deployment and transition technologies
- Backbone operations
- ISP and Carrier services
- Network security issues (NSP-SEC, DDoS Anti-Spam, Anti-Malware)
- Peering / IXPs
- DNS / DNSSEC
- Internet policy (Security, Regulation, Content Management,
Addressing, etc)
- Access and Transport Technologies, including broadband deployment,
Cable/DSL, wireless, WiMax, metro ethernet, fiber network, MPLS
- Content & Service Delivery (Multicast, Voice, Video, "telepresence",
Gaming)
CFP SUBMISSION
--------------
Draft slides for both tutorials and conference sessions MUST be
provided with CFP submissions otherwise the Programme Committee will
be unable to review the submission. For work in progress, the most
current information available at time of submission is acceptable.
Final slides are to be provided by the specified deadline for
publication on the APRICOT website.
While the majority of speaking slots will be filled by the first
submission deadline, a limited number of slots may be available up to
the final submission deadline for presentations that are exceptionally
timely, important, or of critical operational importance.
Please submit on-line at
http://www.apricot2011.net/call-for-papers/submission
Any questions or concerns should be addressed to the Programme
Committee by e-mail.
We look forward to receiving your presentation proposals.
Jonny Martin & Mark Tinka
Co-Chairs, APRICOT Programme Committee
program(a)apricot.net
KSK CEREMONY 3
The third KSK ceremony for the root zone will take place in Culpeper,
VA, USA on Monday 2010-11-01. The ceremony is scheduled to begin
at 1300 local time (1700 UTC) and is expected to end by 1900 local
time (2300 UTC).
Video from Ceremony 3 will be recorded for audit purposes. Video
and associated audit materials will be published 1 to 2 weeks after
the ceremony, and will be available as usual by following the "KSK
Ceremony Materials" link at <https://www.iana.org/dnssec/>.
ICANN will operate a separate camera whose video will not be retained
for audit purposes, but which will instead be streamed live in order
to provide remote observers an opportunity to watch the ceremony.
The live stream will be provided on a best-effort basis. The live
video stream will be available at <http://dns.icann.org/ksk/stream/>.
Ceremony 3 will include processing of a Key Signing Request (KSR)
generated by VeriSign, and the resulting Signed Key Response (SKR)
will contain signatures for Q1 2011, for use in the root zone between
2011-01-01 and 2011-02-28.
CONTACT INFORMATION
We'd like to hear from you. If you have feedback for us, please
send it to rootsign(a)icann.org.
Dear Colleague,
This is to notify you that one or more objects in which you are
designated for notification have been modified in the NZRR routing
registry database.
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.
Diagnostic output:
------------------------------------------------------------
---
PREVIOUS OBJECT:
route-set: AS9439:RS-ROUTES:AS45831
descr: advertised to AS9439 by Datalight Limited - AS45831
members: 180.189.192.0/19^19-29,
113.197.96.0/22^22-29,
203.114.148.128/29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: davey(a)opto.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20100721
source: NZRR
REPLACED BY:
route-set: AS9439:RS-ROUTES:AS45831
descr: advertised to AS9439 by Datalight Limited - AS45831
members: 180.189.192.0/19^19-29,
120.136.0.0/21^21-29,
113.197.96.0/22^22-29,
203.114.148.128/29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: davey(a)opto.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20101029
source: NZRR
------------------------------------------------------------
Hey all,
I have an urgent (today/tomorrow) requirement for how to deliver a normal internet service in Singapore... most likely the downtown area.
Has anyone got any contacts or links to pricing - also maybe someone who can install a router configured in Australia.
I'm looking for a good download limit includes, or flat rate, with static IP a must.
Please reply off-list.
...Skeeve
--
Skeeve Stevens, CEO
eintellego Pty Ltd - The Networking Specialists
skeeve(a)eintellego.net / www.eintellego.net
Phone: 1300 753 383, Fax: (+612) 8572 9954
Cell +61 (0)414 753 383 / skype://skeeve
www.linkedin.com/in/skeeve ; facebook.com/eintellego
--
eintellego - The Experts that the Experts call
- Juniper - HP Networking - Cisco - Arista -
Disclaimer: Limits of Liability and Disclaimer: This message is for the named person's use only. It may contain sensitive and private proprietary or legally privileged information. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. eintellego Pty Ltd and each legal entity in the Tefilah Pty Ltd group of companies reserve the right to monitor all e-mail communications through its networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them to be the views of any such entity. Any reference to costs, fee quotations, contractual transactions and variations to contract terms is subject to separate confirmation in writing signed by an authorised representative of eintellego. Whilst all efforts are made to safeguard inbound and outbound e-mails, we cannot guarantee that attachments are virus-free or compatible with your systems and do not accept any liability in respect of viruses or computer problems experienced.
Dear Colleague,
This is to notify you that one or more objects in which you are
designated for notification have been modified in the NZRR routing
registry database.
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.
Diagnostic output:
------------------------------------------------------------
---
PREVIOUS OBJECT:
route-set: AS9439:RS-ROUTES6:AS4770
descr: Route set advertised to AS9439 by Iconz Ltd - AS4770
mp-members: 2001:F50:0:0:0:0:0:0/32^32-64,
2001:DCE:0:0:0:0:0:0/32^32-64,
2401:D400:0:0:0:0:0:0/32^32-64,
2405:6000:0:0:0:0:0:0/32^32-64
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 20100715
source: NZRR
REPLACED BY:
route-set: AS9439:RS-ROUTES6:AS4770
descr: Route set advertised to AS9439 by Iconz Ltd - AS4770
mp-members: 2405:6000:0:0:0:0:0:0/32^32-64,
2001:F50:0:0:0:0:0:0/32^32-64,
2401:D400:0:0:0:0:0:0/32^32-64,
2001:DCE:0:0:0:0:0:0/32^32-64,
2404:130:0:0:0:0:0:0/32^32-64
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 20101028
source: NZRR
------------------------------------------------------------
Dear Colleague,
This is to notify you that one or more objects in which you are
designated for notification have been modified in the NZRR routing
registry database.
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.
Diagnostic output:
------------------------------------------------------------
---
PREVIOUS OBJECT:
route-set: AS9560:RS-ROUTES6:AS9503
descr: Route set advertised to AS9560 by FX Networks - AS9503
mp-members: 2402:6000:0:0:0:0:0:0/32^32-64,
2404:3800:0:0:0:0:0:0/32^32-64,
2001:DCE:0:0:0:0:0:0/32^32-64,
2001:DCE:E000:0:0:0:0:0/48^48-64,
2001:DF0:4A:0:0:0:0:0/48^48-64,
2404:1800:0:0:0:0:0:0/32^32-64,
2001:4530:0:0:0:0:0:0/32^32-64,
2400:B400:0:0:0:0:0:0/32^32-64,
2404:130:0:0:0:0:0:0/32^32-64,
2403:E00:0:0:0:0:0:0/32^32-64,
2400:1200:0:0:0:0:0:0/32^32-64,
2403:C200:0:0:0:0:0:0/32^32-64
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: tim(a)fx.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20100830
source: NZRR
REPLACED BY:
route-set: AS9560:RS-ROUTES6:AS9503
descr: Route set advertised to AS9560 by FX Networks - AS9503
mp-members: 2402:6000:0:0:0:0:0:0/32^32-64,
2404:3800:0:0:0:0:0:0/32^32-64,
2001:DCE:0:0:0:0:0:0/32^32-64,
2001:DCE:E000:0:0:0:0:0/48^48-64,
2001:DF0:4A:0:0:0:0:0/48^48-64,
2404:1800:0:0:0:0:0:0/32^32-64,
2001:4530:0:0:0:0:0:0/32^32-64,
2400:B400:0:0:0:0:0:0/32^32-64,
2404:130:0:0:0:0:0:0/32^32-64,
2403:E00:0:0:0:0:0:0/32^32-64,
2400:1200:0:0:0:0:0:0/32^32-64,
2403:C200:0:0:0:0:0:0/32^32-64,
2404:1E00:0:0:0:0:0:0/32^32-64,
2401:F000:0:0:0:0:0:0/32^32-64,
2407:2400:0:0:0:0:0:0/32^32-64,
2403:7000:0:0:0:0:0:0/32^32-64,
2404:138:103:0:0:0:0:0/48^48-64,
2404:138:104:0:0:0:0:0/48^48-64,
2404:138:4000:0:0:0:0:0/48^48-64,
2404:D000:0:0:0:0:0:0/32^32-64
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 20101028
source: NZRR
------------------------------------------------------------
Dear Colleague,
This is to notify you that one or more objects in which you are
designated for notification have been modified in the NZRR routing
registry database.
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.
Diagnostic output:
------------------------------------------------------------
---
PREVIOUS OBJECT:
route-set: AS9560:RS-ROUTES:AS24324
descr: advertised to AS9560 by Kordia Networks - AS24324
members: 118.148.0.0/15^15-29,
124.157.64.0/18^18-29,
182.48.128.0/19^19-29,
203.152.96.0/19^19-29,
58.84.224.0/20^20-29,
114.134.0.0/20^20-29,
202.56.32.0/20^20-29,
202.68.80.0/20^20-29,
203.96.0.0/20^20-29,
203.96.32.0/20^20-29,
117.104.176.0/21^21-29,
124.150.160.0/21^21-29,
202.20.0.0/21^21-29,
202.49.128.0/21^21-29,
202.56.48.0/21^21-29,
202.137.240.0/21^21-29,
180.222.64.0/22^22-29,
202.27.88.0/23^23-29,
202.27.250.0/23^23-29,
202.36.172.0/23^23-29,
202.49.164.0/23^23-29,
202.65.160.0/23^23-29,
202.174.6.0/23^23-29,
202.174.184.0/23^23-29,
202.174.190.0/23^23-29,
192.11.175.0/24^24-29,
202.21.130.0/24^24-29,
202.27.34.0/24^24-29,
202.27.90.0/24^24-29,
202.27.135.0/24^24-29,
202.27.247.0/24^24-29,
202.36.29.0/24^24-29,
202.36.121.0/24^24-29,
202.36.137.0/24^24-29,
202.36.157.0/24^24-29,
202.36.181.0/24^24-29,
202.36.182.0/24^24-29,
202.37.112.0/24^24-29,
202.37.198.0/24^24-29,
202.37.234.0/24^24-29,
202.49.168.0/24^24-29,
202.49.183.0/24^24-29,
202.129.253.0/24^24-29,
203.92.25.0/24^24-29,
203.170.56.0/24^24-29,
203.174.26.0/24^24-29,
203.191.7.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: marlon.nacario(a)kordia.co.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20100730
source: NZRR
REPLACED BY:
route-set: AS9560:RS-ROUTES:AS24324
descr: advertised to AS9560 by Kordia Ltd - AS24324
members: 118.148.0.0/15^15-29,
124.157.64.0/18^18-29,
182.48.128.0/19^19-29,
203.152.96.0/19^19-29,
58.84.224.0/20^20-29,
114.134.0.0/20^20-29,
202.56.32.0/20^20-29,
202.68.80.0/20^20-29,
203.96.0.0/20^20-29,
203.96.32.0/20^20-29,
117.104.176.0/21^21-29,
124.150.160.0/21^21-29,
180.222.64.0/21^21-29,
202.20.0.0/21^21-29,
202.49.128.0/21^21-29,
202.56.48.0/21^21-29,
202.137.240.0/21^21-29,
202.27.88.0/23^23-29,
202.27.250.0/23^23-29,
202.36.172.0/23^23-29,
202.49.164.0/23^23-29,
202.65.160.0/23^23-29,
202.174.6.0/23^23-29,
202.174.184.0/23^23-29,
202.174.190.0/23^23-29,
192.11.175.0/24^24-29,
202.21.130.0/24^24-29,
202.27.34.0/24^24-29,
202.27.90.0/24^24-29,
202.27.135.0/24^24-29,
202.27.247.0/24^24-29,
202.36.29.0/24^24-29,
202.36.121.0/24^24-29,
202.36.137.0/24^24-29,
202.36.157.0/24^24-29,
202.36.181.0/24^24-29,
202.36.182.0/24^24-29,
202.37.112.0/24^24-29,
202.37.198.0/24^24-29,
202.37.234.0/24^24-29,
202.49.168.0/24^24-29,
202.49.183.0/24^24-29,
202.129.253.0/24^24-29,
203.92.25.0/24^24-29,
203.170.56.0/24^24-29,
203.174.26.0/24^24-29,
203.191.7.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: raymond.tso(a)kordia.co.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20101028
source: NZRR
------------------------------------------------------------
Dear Colleague,
This is to notify you that one or more objects in which you are
designated for notification have been modified in the NZRR routing
registry database.
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.
Diagnostic output:
------------------------------------------------------------
---
NEW OBJECT CREATION:
route-set: AS9560:RS-ROUTES:AS2686
descr: advertised to AS9560 by AT&T - AS2686
members: 124.248.128.0/20^20-29,
202.27.216.0/22^22-29,
202.36.192.0/22^22-29,
202.169.192.0/22^22-29,
32.114.24.0/23^23-29,
122.248.172.0/23^23-29,
202.27.136.0/23^23-29,
202.36.68.0/23^23-29,
202.37.70.0/23^23-29,
202.169.198.0/23^23-29,
202.169.202.0/23^23-29,
202.169.206.0/23^23-29,
202.169.212.0/23^23-29,
202.175.142.0/23^23-29,
203.99.128.0/23^23-29,
203.163.70.0/23^23-29,
203.176.122.0/23^23-29,
32.234.80.0/24^24-29,
192.88.190.0/24^24-29,
192.203.216.0/24^24-29,
202.12.105.0/24^24-29,
202.14.252.0/24^24-29,
202.14.254.0/24^24-29,
202.20.92.0/24^24-29,
202.27.77.0/24^24-29,
202.27.83.0/24^24-29,
202.27.160.0/24^24-29,
202.27.222.0/24^24-29,
202.27.236.0/24^24-29,
202.27.247.0/24^24-29,
202.27.251.0/24^24-29,
202.36.12.0/24^24-29,
202.36.29.0/24^24-29,
202.36.43.0/24^24-29,
202.36.75.0/24^24-29,
202.36.80.0/24^24-29,
202.36.154.0/24^24-29,
202.36.198.0/24^24-29,
202.37.68.0/24^24-29,
202.37.167.0/24^24-29,
202.37.168.0/24^24-29,
202.37.187.0/24^24-29,
202.37.254.0/24^24-29,
202.49.189.0/24^24-29,
202.49.216.0/24^24-29,
202.50.240.0/24^24-29,
202.135.38.0/24^24-29,
202.135.49.0/24^24-29,
202.135.64.0/24^24-29,
202.135.85.0/24^24-29,
202.135.111.0/24^24-29,
202.135.112.0/24^24-29,
202.135.116.0/24^24-29,
202.135.142.0/24^24-29,
202.135.146.0/24^24-29,
202.135.190.0/24^24-29,
202.135.192.0/24^24-29,
202.135.231.0/24^24-29,
202.169.196.0/24^24-29,
202.169.201.0/24^24-29,
202.169.205.0/24^24-29,
202.169.223.0/24^24-29,
203.163.68.0/24^24-29,
203.163.94.0/24^24-29,
203.163.98.0/24^24-29,
203.196.101.0/24^24-29,
203.196.119.0/24^24-29,
203.196.121.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: dl-globalwork(a)att.com
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20101028
source: NZRR
------------------------------------------------------------
