_______________________________________________________________________
Application for India NIR - Call for Comments
_______________________________________________________________________
The National Internet Exchange of India (NIXI) has lodged an application
for recognition as a National Internet Registry (NIR). If recognized as
an NIR, NIXI would be able to offer IP (Internet Protocol) address
allocation and other APNIC services at a national level in India.
In the interests of openness and transparency, the APNIC Executive
Council (EC) requests public review of the NIXI application and has
issued a Call for Comments to gauge community support.
The EC will accept public or confidential comments until Monday, 30
November 2009 at 17:30 (UTC+10 - Brisbane time).
Confidential comments may be:
- Emailed to the Executive Secretary of the EC at exec-sec(a)apnic.net
- Submitted using the web form at http://www.apnic.net/NIR_Comments
Comments may also be made publicly and discussed on the "apnic-talk"
mailing list. More information on the list is available at:
http://www.apnic.net/mailing-lists
The APNIC EC is responsible for evaluating and approving the
application, but before the EC can do so, it must be satisfied that NIXI
meets the "Criteria for the recognition of NIRs in the APNIC region", as
set out in the policy available at:
http://www.apnic.net/policy/nir-criteria
These criteria require NIXI to:
- Demonstrate formal endorsement at the national level by the
appropriate government body
- Be an independent legal entity with a non-profit structure
- Demonstrate a stable funding model
- Demonstrate it holds a neutral position
- Have the organizational and technical capacity to implement
APNIC address management policies
For more information, see:
http://www.apnic.net/nir
_______________________________________________________________________
Paul Wilson, Director-General, APNIC dg(a)apnic.nethttp://www.apnic.net ph/fx +61 7 3858 3100/99
_______________________________________________________________________
_______________________________________________________________________
Making Allocations from 175/8 and 182/8 soon
_______________________________________________________________________
Hi NZNOG Community,
In August 2009, APNIC received two IPv4 address blocks from IANA. These
were:
- 175/8
- 182/8
Reachability and routability testing is now complete and exceeds 96% for
all prefixes.
APNIC will soon be allocating from these prefixes.
Please update your routing filters and network configurations
accordingly.
Please also double-check and release any blacklisted IP addresses from
the above ranges, as they now represent fresh /8 blocks.
Thank you for your cooperation. If you have any questions, please
contact the APNIC helpdesk:
helpdesk(a)apnic.net
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 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: AS9281:RS-ROUTES:AS17705
descr: advertised to AS9281 by InspireNet - AS17705
members: 203.114.128.0/18^18-29,
121.79.192.0/19^19-29,
192.138.251.0/24^24-29,
203.92.25.0/24^24-29,
210.7.46.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: brenden(a)staff.inspire.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20080410
source: NZRR
REPLACED BY:
route-set: AS9281:RS-ROUTES:AS17705
descr: advertised to AS9281 by InspireNet - AS17705
members: 203.114.128.0/18^18-29,
121.79.192.0/19^19-29,
202.174.160.0/20^20-29,
121.79.224.0/21^21-29,
140.200.248.0/22^22-29,
192.138.251.0/24^24-29,
203.92.25.0/24^24-29,
203.174.26.0/24^24-29,
210.7.46.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: noc(a)inspire.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20091116
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: AS9281:RS-ROUTES:AS38477
descr: advertised to AS9281 by Unleash - AS38477
members: 116.90.128.0/20^20-29,
113.130.120.0/22^22-29,
202.6.116.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: noc(a)unleash.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20091113
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:AS17705
descr: advertised to AS9439 by Inspire Net Ltd - AS17705
members: 203.114.128.0/18^18-29,
121.79.192.0/19^19-29,
121.79.224.0/21^21-29,
140.200.248.0/22^22-29,
192.138.251.0/24^24-29,
203.92.25.0/24^24-29,
203.174.26.0/24^24-29,
210.7.46.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: ops(a)inspire.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20091022
source: NZRR
REPLACED BY:
route-set: AS9439:RS-ROUTES:AS17705
descr: advertised to AS9439 by InspireNet - AS17705
members: 203.114.128.0/18^18-29,
121.79.192.0/19^19-29,
202.174.160.0/20^20-29,
121.79.224.0/21^21-29,
140.200.248.0/22^22-29,
192.138.251.0/24^24-29,
203.92.25.0/24^24-29,
203.174.26.0/24^24-29,
210.7.46.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: noc(a)inspire.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20091113
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:AS17705
descr: advertised to AS9560 by InspireNet - AS17705
members: 203.114.128.0/18^18-29,
121.79.192.0/19^19-29,
140.200.248.0/22^22-29,
192.138.251.0/24^24-29,
203.92.25.0/24^24-29,
203.174.26.0/24^24-29,
210.7.46.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: brenden(a)staff.inspire.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20080724
source: NZRR
REPLACED BY:
route-set: AS9560:RS-ROUTES:AS17705
descr: advertised to AS9560 by InspireNet - AS17705
members: 203.114.128.0/18^18-29,
121.79.192.0/19^19-29,
202.174.160.0/20^20-29,
121.79.224.0/21^21-29,
140.200.248.0/22^22-29,
192.138.251.0/24^24-29,
203.92.25.0/24^24-29,
203.174.26.0/24^24-29,
210.7.46.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: noc(a)inspire.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20091113
source: NZRR
------------------------------------------------------------
FYI to NZNOGers
...Skeeve
--
Skeeve Stevens, CEO/Technical Director
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
--
NOC, NOC, who's there?
-----Original Message-----
From: ausnog-bounces(a)lists.ausnog.net [mailto:ausnog-bounces(a)lists.ausnog.net] On Behalf Of Skeeve Stevens
Sent: Wednesday, 11 November 2009 5:44 PM
To: ausnog(a)ausnog.net
Subject: Re: [AusNOG] Soul/TPG buying Pipe ...
All,
I'm quite disappointed in this move.... yes, it is just my little opinion, but it is mine to give.
TPG's takeover of Soul, the way they run their network operations - from experience and the feedback of quite a few Soul staff, does not inspire me with any confidence with what will happen to Pipe. TPG basically gutted Soul in several areas and I can't see how, unless they've changed the way they do things, that this will be any good at all for Pipe.
Pipe, driven by Bevan and Steve have been amazing for this industry, building it, supporting it and making what it is today... I have never ever experienced TPG caring at all for the industry as a whole... sponsoring anything industry related or supporting it in other ways... if they have, I would like to be corrected.
Now Wholesale. I've been a big advocate of Pipe as a wholesale provider over anyone else - simply because of how much they've given the industry and my love for the guys.... but as a wholesale provider they never competed with ISP's in any real way. TPG is a retail based ISP primary.. Soul does other things, but again they shut down their wholesale business of DSL and other things very quickly after the takeover by TPG. What will happen to Pipe? Wholesale shutdown - prices up.. peering killed off?
One question I would really like to ask is 'Why Bevan why?'... I realise you guys together only had 27% - but did you have no choice? I am sure I am not the only one asking 'How could you do this to us?' Is it just about the money?
In the end.. whatever happens, we will adapt.... you never really do know how things will turn out. This might be a good thing... not that I can see how at the moment. If they leave Pipe alone and let it do what it does best... great... if they gut it and integrate... sad panda for all.
I see things like Pipe drinks disappearing, AUSNOG sponsorship disappearing, and amazing industry innovation - like PPC1 - things like that not happening anymore.
I remember Bevans' speech at the Pipe Xmas part in 2008... about being here for the small guy... What happened.
...Skeeve
--
Skeeve Stevens, CEO/Technical Director
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
--
NOC, NOC, who's there?
> -----Original Message-----
> From: ausnog-bounces(a)lists.ausnog.net [mailto:ausnog-
> bounces(a)lists.ausnog.net] On Behalf Of Matthew Moyle-Croft
> Sent: Wednesday, 11 November 2009 4:58 PM
> To: ausnog(a)ausnog.net
> Subject: [AusNOG] Soul/TPG buying Pipe ...
>
> http://www.asx.com.au/asx/statistics/displayAnnouncement.do?display=pdf&ids…
>
> I'd cut and paste, but it's been disabled.
>
> Have a read. How does the world change?
>
> MMC
> --
> Matthew Moyle-Croft
> Peering Manager and Team Lead - Commercial and DSLAMs
> Internode /Agile
>
> _______________________________________________
> AusNOG mailing list
> AusNOG(a)lists.ausnog.net
> http://lists.ausnog.net/mailman/listinfo/ausnog
_______________________________________________
AusNOG mailing list
AusNOG(a)lists.ausnog.nethttp://lists.ausnog.net/mailman/listinfo/ausnog
Thank you to everyone who emailed with suggestions for a switch for
my LAN upgrade to GigE. The issue is a little more complicated.
We have 3 main switches on the "base" network. They are all 24 ports,
not small 8 ports. The van and both encoder roadcases all have 24
port switches in them and we use the 24 ports. Plus there are
switches for "client use" (48 ports each). So I'm probably looking
for 6 to 8, 24 port switches with SFPs - and VLANs would be nice.
We use multiple internet links (sometimes as many as 4+) We build
the different networks via VLANS or sometimes separate physical networks.
And of course we use a VoIP pabx with lines in AKL, WLG and CHC. The
van has its own lines (2), and we have a portable VoIP pabx for event use.
When we need "more power", we connect the van to the office network,
both for uplink lines and encoders and for clearing the van-resident
disks. The neighbours are sort of used to seeing the van all lit up
at night. Satellite dishes sprout and disappear as
required. http://www.r2.co.nz/20080404/photos/
I hope this explains why things are a little more complicated. We
drink beer to stay sane (and on topic)
