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:AS17435
descr: advertised to AS9560 by WorldxChange Communications LTD - AS17435
members: 58.28.0.0/16^16-29,
118.90.0.0/16^16-29,
182.154.0.0/16^16-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: lsmith(a)wxc.co.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20100308
source: NZRR
REPLACED BY:
route-set: AS9560:RS-ROUTES:AS17435
descr: advertised to AS9560 by WorldxChange Communications Ltd - AS17435
members: 58.28.0.0/16^16-29,
118.90.0.0/16^16-29,
182.154.0.0/16^16-29,
203.171.223.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: cbarr(a)wxc.co.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20100615
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: AS9439:RS-ROUTES:AS17435
descr: advertised to AS9439 by WorldxChange Communications Ltd - AS17435
members: 58.28.0.0/16^16-29,
118.90.0.0/16^16-29,
182.154.0.0/16^16-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: cbarr(a)wxc.co.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20100308
source: NZRR
REPLACED BY:
route-set: AS9439:RS-ROUTES:AS17435
descr: advertised to AS9439 by WorldxChange Communications Ltd - AS17435
members: 58.28.0.0/16^16-29,
118.90.0.0/16^16-29,
182.154.0.0/16^16-29,
203.171.223.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: cbarr(a)wxc.co.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20100615
source: NZRR
------------------------------------------------------------
[Sent on behalf of the APrIGF Committee]
_______________________________________________________________________
Asia Pacific Regional IGF (APrIGF) in Hong Kong
_______________________________________________________________________
Hi NZNOG Community,
To complement and supplement the global IGF (Internet Governance
Forum), a group of active participants, with the OGCIO (Office of the
Government Chief Information Officer) as the advisor, have come
together to organize the first Asia Pacific Regional IGF in Hong Kong.
The event will consist of 3 parts:
- Youth IGF Camp
June 12-14, Jockey Club Sai Kung Outdoor Training Camp
- Asia Pacific Regional IGF Roundtable
June 15-16, Cyberport
Language: English (with real-time English transcription)
- Hong Kong IGF Conference
June 17-18, Cyberport
Language: English (with real-time English transcription)
Cantonese and Mandarin interpretation also available
All 3 component events combine to become a platform for regional
collaboration and, even though organized independently of the global
IGF, intends to report its discussion to the global IGF in Vilnius,
Lithuania, September 14-17. This adds to the significance of the APrIGF
in that the ideas, recommendations, and other outputs from the event
will be used as inputs for the coming global IGF meeting in September.
For more information, see:
http://www.rigf.asia
Follow APrIGF online!
---------------------
Watch the sessions online if you can't attend in person:
http://webcast.rigf.asia
To view a longer, HTML version of this message, see:
http://www.rigf.asia/images/rigf-edm-webcast.html
For more information, contact:
Secretariat, Asia Pacific Regional Internet Governance Forum
email: info(a)rigf.asia
Kind regards,
Elly
------------------------------------------------------------------------
Elly Tawhai email: elly(a)apnic.net
Senior Internet Resource Analyst/ sip: elly(a)voip.apnic.net
Liaison Officer(Pacific), APNIC phone: +61 7 3858 3188
http://www.apnic.net fax: +61 7 3858 3199
------------------------------------------------------------------------
Dear NZNOG community and InternetNZ members,
I think this might be of interest to some of you. The linked story
towards the end of the email includes contact details for the TAG if
you were interested in being involved with it directly.
Cheers
Jordan
---------- Forwarded message ----------
From: Donna McCague <mccague(a)isoc.org>
Date: 10 June 2010 02:56
Subject: [isoc-advisory-council] US Broadband Internet Technical Advisory Group
To: isoc-advisory-council(a)elists.isoc.org
Dear Colleagues,
This message is being sent to you on behalf of Sally Wentworth, Regional
Bureau Manager, North America. Â Sally recently became aware of an
opportunity she wanted to share with the Advisory Council:
"The Internet Society has lent initial support to a U.S. industry effort to
form a Broadband Internet Technical Advisory Group (BITAG) to develop
consensus on broadband network management practices or other related
technical issues that can affect users' Internet experience. Â This is a
collaborative industry effort to identify and address operational issues
that have been at the heart of some of the recent issues attracting
governmental attention. Â Constructively, this activity could result in
organized, forward-looking discussion driven by key stakeholders and also
provide opportunities to educate and inform policy makers by shedding light
on underlying technical issues from the perspectives of diverse
stakeholders.
While this is initially a US-centric activity, it is our expectation that
this could yield useful results and/or a model that will be effective more
broadly across the globe. Â It is certainly our intention to inject that
broader, global perspective into their discussions.
The group has announced initial plans to form the BITAG and commit to work
out details regarding the operational and organizational structure of the
BITAG over the coming weeks. Â This is the early stages of the effort and
many details have yet to be worked out but the Internet Society believes
this is an important opportunity to address key operational challenges
facing the Internet user experience. Â You can see the announcement they put
on the wire, here:
http://www.prnewswire.com/news-releases/initial-plans-for-broadband-interne…
ISOC participation in this endeavor will be led out of ISOC's North American
Bureau and the office of the Chief Internet Technology Officer.
As the group is formed, the Internet Society will bring a global, user-
centric approach to the issues and will work to ensure that any output is
appropriately integrated with the work of existing Internet standards
activities. Â The creation of the BITAG addresses an industry need that falls
outside the IETF remit but it is important to integrate the output with
relevant activities by the IETF and other standards bodies."
If you have any questions, please contact me or Sally at wentworth(a)isoc.org.
Best regards,
Donna
Donna McCague
Organization Membership Coordinator
 <mailto:mccague(a)isoc.org> mccague(a)isoc.org
Internet Society
1775 Wiehle Ave., Suite 201
Reston, VA Â 20190
+ 1 703 439-2130/direct
+ 1 703 326-9881/fax
--
Jordan Carter
Policy Director, InternetNZ
+64 21 442 649 | skype: jordancarter
To protect and promote the Internet for New Zealand
<www.internetnz.net.nz>
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:AS9503
descr: advertised to AS9560 by FX Networks - AS9503
members: 130.123.0.0/16^16-29,
131.203.0.0/16^16-29,
161.29.0.0/16^16-29,
161.65.0.0/16^16-29,
166.65.0.0/16^16-29,
203.114.128.0/18^18-29,
119.15.0.0/19^19-29,
121.79.192.0/19^19-29,
202.14.32.0/19^19-29,
112.109.64.0/20^20-29,
114.134.160.0/20^20-29,
119.47.112.0/20^20-29,
121.79.224.0/20^20-29,
124.248.128.0/20^20-29,
202.53.176.0/20^20-29,
202.86.96.0/20^20-29,
202.160.48.0/20^20-29,
202.174.160.0/20^20-29,
210.48.160.0/20^20-29,
112.109.80.0/21^21-29,
117.18.80.0/21^21-29,
120.89.80.0/21^21-29,
121.79.240.0/21^21-29,
192.173.16.0/21^21-29,
202.36.96.0/21^21-29,
202.37.32.0/21^21-29,
202.46.176.0/21^21-29,
202.49.0.0/21^21-29,
202.78.240.0/21^21-29,
202.160.112.0/21^21-29,
203.190.208.0/21^21-29,
110.232.144.0/22^22-29,
113.197.64.0/22^22-29,
140.200.248.0/22^22-29,
175.111.100.0/22^22-29,
192.206.152.0/22^22-29,
202.37.28.0/22^22-29,
202.37.48.0/22^22-29,
202.89.4.0/22^22-29,
203.99.132.0/22^22-29,
192.206.156.0/23^23-29,
202.36.214.0/23^23-29,
202.36.218.0/23^23-29,
202.46.190.0/23^23-29,
202.49.164.0/23^23-29,
202.65.160.0/23^23-29,
203.84.134.0/23^23-29,
203.217.142.0/23^23-29,
116.90.129.0/24^24-29,
116.90.138.0/24^24-29,
116.90.140.0/24^24-29,
192.88.85.0/24^24-29,
192.88.99.0/24^24-29,
192.105.10.0/24^24-29,
192.122.171.0/24^24-29,
192.133.31.0/24^24-29,
192.138.251.0/24^24-29,
192.195.219.0/24^24-29,
192.245.185.0/24^24-29,
202.8.13.0/24^24-29,
202.12.0.0/24^24-29,
202.12.91.0/24^24-29,
202.20.97.0/24^24-29,
202.27.83.0/24^24-29,
202.36.33.0/24^24-29,
202.36.75.0/24^24-29,
202.36.119.0/24^24-29,
202.36.154.0/24^24-29,
202.36.162.0/24^24-29,
202.36.221.0/24^24-29,
202.37.168.0/24^24-29,
202.37.205.0/24^24-29,
202.46.188.0/24^24-29,
202.49.106.0/24^24-29,
202.49.168.0/24^24-29,
202.50.247.0/24^24-29,
202.50.252.0/24^24-29,
202.55.99.0/24^24-29,
202.55.105.0/24^24-29,
202.55.107.0/24^24-29,
202.89.57.0/24^24-29,
203.89.178.0/24^24-29,
203.89.181.0/24^24-29,
203.89.187.0/24^24-29,
203.92.25.0/24^24-29,
210.7.46.0/24^24-29,
202.89.43.0/25^25-29
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 20100604
source: NZRR
REPLACED BY:
route-set: AS9560:RS-ROUTES:AS9503
descr: advertised to AS9560 by FX Networks - AS9503
members: 130.123.0.0/16^16-29,
131.203.0.0/16^16-29,
161.29.0.0/16^16-29,
161.65.0.0/16^16-29,
166.65.0.0/16^16-29,
203.114.128.0/18^18-29,
119.15.0.0/19^19-29,
121.79.192.0/19^19-29,
202.14.32.0/19^19-29,
112.109.64.0/20^20-29,
114.134.160.0/20^20-29,
119.47.112.0/20^20-29,
121.79.224.0/20^20-29,
124.248.128.0/20^20-29,
202.53.176.0/20^20-29,
202.86.96.0/20^20-29,
202.160.48.0/20^20-29,
202.174.160.0/20^20-29,
210.48.160.0/20^20-29,
112.109.80.0/21^21-29,
117.18.80.0/21^21-29,
120.89.80.0/21^21-29,
121.79.240.0/21^21-29,
192.173.16.0/21^21-29,
202.36.96.0/21^21-29,
202.37.32.0/21^21-29,
202.46.176.0/21^21-29,
202.49.0.0/21^21-29,
202.78.240.0/21^21-29,
202.160.112.0/21^21-29,
203.190.208.0/21^21-29,
110.232.144.0/22^22-29,
113.197.64.0/22^22-29,
140.200.248.0/22^22-29,
175.111.100.0/22^22-29,
192.206.152.0/22^22-29,
202.37.28.0/22^22-29,
202.37.48.0/22^22-29,
202.89.4.0/22^22-29,
203.99.132.0/22^22-29,
192.206.156.0/23^23-29,
202.36.214.0/23^23-29,
202.36.218.0/23^23-29,
202.46.190.0/23^23-29,
202.49.164.0/23^23-29,
202.65.160.0/23^23-29,
203.84.134.0/23^23-29,
203.217.142.0/23^23-29,
116.90.129.0/24^24-29,
116.90.138.0/24^24-29,
116.90.140.0/24^24-29,
192.88.85.0/24^24-29,
192.88.99.0/24^24-29,
192.105.10.0/24^24-29,
192.122.171.0/24^24-29,
192.133.31.0/24^24-29,
192.138.251.0/24^24-29,
192.195.219.0/24^24-29,
192.245.185.0/24^24-29,
202.8.13.0/24^24-29,
202.12.0.0/24^24-29,
202.12.91.0/24^24-29,
202.20.97.0/24^24-29,
202.27.83.0/24^24-29,
202.36.33.0/24^24-29,
202.36.75.0/24^24-29,
202.36.119.0/24^24-29,
202.36.154.0/24^24-29,
202.36.162.0/24^24-29,
202.36.221.0/24^24-29,
202.37.168.0/24^24-29,
202.37.205.0/24^24-29,
202.46.188.0/24^24-29,
202.49.106.0/24^24-29,
202.49.168.0/24^24-29,
202.50.247.0/24^24-29,
202.50.252.0/24^24-29,
202.55.99.0/24^24-29,
202.55.105.0/24^24-29,
202.55.107.0/24^24-29,
202.89.57.0/24^24-29,
203.89.178.0/24^24-29,
203.89.181.0/24^24-29,
203.89.187.0/24^24-29,
203.92.25.0/24^24-29,
210.7.46.0/24^24-29,
202.89.43.0/25^25-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: craig.wallace(a)fx.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20100609
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:AS9889
descr: advertised to AS9560 by Maxnet - AS9889
members: 123.100.64.0/18^18-29,
124.198.128.0/18^18-29,
202.89.32.0/19^19-29,
203.89.160.0/19^19-29,
112.109.64.0/20^20-29,
119.47.112.0/20^20-29,
112.109.80.0/21^21-29,
114.134.160.0/21^21-29,
124.150.160.0/21^21-29,
202.189.160.0/21^21-29,
113.197.64.0/22^22-29,
114.134.168.0/22^22-29,
122.102.108.0/22^22-29,
210.55.100.0/22^22-29,
210.55.104.0/22^22-29,
117.53.150.0/23^23-29,
202.49.88.0/23^23-29,
203.84.134.0/23^23-29,
210.54.142.0/23^23-29,
114.134.172.0/24^24-29,
192.138.251.0/24^24-29,
202.6.5.0/24^24-29,
202.27.8.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.162.0/24^24-29,
202.37.181.0/24^24-29,
202.37.232.0/24^24-29,
202.46.187.0/24^24-29,
202.49.141.0/24^24-29,
202.150.102.0/24^24-29,
203.12.15.0/24^24-29,
203.97.42.0/24^24-29,
205.233.243.0/24^24-29,
210.54.13.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 20100330
source: NZRR
REPLACED BY:
route-set: AS9560:RS-ROUTES:AS9889
descr: advertised to AS9560 by Maxnet - AS9889
members: 123.100.64.0/18^18-29,
124.198.128.0/18^18-29,
202.89.32.0/19^19-29,
203.89.160.0/19^19-29,
112.109.64.0/20^20-29,
119.47.112.0/20^20-29,
124.150.160.0/20^20-29,
112.109.80.0/21^21-29,
114.134.160.0/21^21-29,
182.236.120.0/21^21-29,
202.189.160.0/21^21-29,
113.197.64.0/22^22-29,
114.134.168.0/22^22-29,
122.102.108.0/22^22-29,
210.55.100.0/22^22-29,
210.55.104.0/22^22-29,
117.53.150.0/23^23-29,
202.49.88.0/23^23-29,
203.84.134.0/23^23-29,
210.54.142.0/23^23-29,
114.134.172.0/24^24-29,
192.138.251.0/24^24-29,
202.6.5.0/24^24-29,
202.27.8.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.162.0/24^24-29,
202.37.181.0/24^24-29,
202.37.232.0/24^24-29,
202.46.187.0/24^24-29,
202.49.141.0/24^24-29,
202.150.102.0/24^24-29,
203.12.15.0/24^24-29,
203.97.42.0/24^24-29,
205.233.243.0/24^24-29,
210.54.13.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 20100609
source: NZRR
------------------------------------------------------------
[Apologies for duplicates]
________________________________________________________________________
APNIC 30 - Call for Papers
________________________________________________________________________
The APNIC 30 Program Committee is now seeking presentations for APNIC
30 to be held at Gold Coast, Australia from 24 - 27 August 2010. We are
looking for presentations that would suit technical conference sessions.
Please submit proposals online at:
http://submission.apnic.net/
KEY DATES
---------
Call for Papers Opens: 8 June 2010
First Deadline for Submissions: 9 July 2010
First Draft Program Published: 16 July 2010
Final Deadline for Submissions: 6 August 2010
Final Program Published: 10 August 2010
Final Slides Received: 20 August 2010
PROGRAM MATERIAL
----------------
APNIC 30 Technical sessions will include presentations relevant to
Internet Operations and Technologies. Here are some ideas for technical
sessions relevant to APNIC 30:
- IPv4 exhaustion / IPv6 deployment & operations
- ISP, Peering, Carrier, and IXP services
- Network security
- Internet policy
- Access and Transport Technologies
- Content & Service Delivery
If you have another idea, feel free to submit your proposal.
CFP SUBMISSION
--------------
Draft slides must be provided with all submissions. For work in
progress, the most current information available at the time of
submission is acceptable.
Remember to submit early so you have plenty of time to arrange
visas and travel!
If you have questions, please email the Program Chair:
pc-chair(a)apnic.net
For more information about APNIC 30, please visit:
http://meetings.apnic.net/30
Regards,
Jonny Martin
Chair, APNIC 30 Program Committee
