It��s been around here for a long time. Perhaps it��s a bit dated these days, sure.

Getting through cables was expensive, so people offered connectivity to other NZ networks at a significantly cheaper price (think at least an order of magnitude).

It wasn��t always delivered as seperate transit - often it would be a single connection but ��domestic�� was zero rated, and ��international�� was billed.. or, similar thing but shaping rather than billing. You get the idea. A large number of regular business Internet connections had this sort of thing on them I dunno, 10 years ago maybe? Few have it now, but it won��t have been too long ago that it got like that.

I��m pretty sure my home internet had some different ��international�� component on it at some point, too.

It��s meant we��ve always cared a lot about local content, which has meant our peering and the community around it has been strong, even when the economics aren��t quite as glaring anymore.

It��s also a hard thing to take away - providers offering both ��domestic" and ��international�� transit have to either take a stab at their costs (like they do for US vs. AU for the ��international�� part) and risk a loss, or they have to effectively say ��domestic is the same price as international��. That��s a fast way to have your transit customers move elsewhere, I��d say.

Worth noting, most ��international�� products also include ��domestic�� routes and transit. It��s really ��domestic�� and ��global��.

On 19/09/2018, at 5:13 PM, Tom Paseka <tom+lists@cloudflare.com> wrote:

I'd call that partial transit ;-)

(BGP sanity questions remain).

On Tue, Sep 18, 2018 at 10:05 PM Dave Mill <dave@mill.net.nz> wrote:
Buying 'domestic' is a way of paying for the privilege of sending/receiving traffic to Spark :)

On Wed, Sep 19, 2018 at 5:02 PM, Tom Paseka <tom+lists@cloudflare.com> wrote:
If I can ask, what does a "domestic" table genuinely bring you. If you carry routes to your edge(s) that have both peering and transit, do you need to extend the DFZ all the way through your network? If you've got a single exit path (or a few) do you need to extend the domestic routes any further?

Another thing to note: BGP Sanity. Apply AS_PATH filters to all your peers. This doubly so if you're extending the routes throughout your network. Much of HE's routes might not be relevant to your network and could have easily been sanitized with some nice filters.

Also congrats to HE/Team!
-Tom

On Tue, Sep 18, 2018 at 9:50 PM Tim Hoffman <tim@hoffman.net.nz> wrote:
Don't forget that the NZ/AU concept of 'domestic table' is a fairly unique concept that isn't seen in much of the rest of the world- generally any feed is going to be default, a peering feed (customer routes), or a full table.... Doubt anyone thought of it ;).

Congrats to Mike & Walt on extending to NZ... pretty cool to see a worldwide carrier finally making it there - fantastic to see how far the NZ internet has progressed!

On Tue, Sep 18, 2018 at 9:47 PM Bill <bill@wjw.nz> wrote:

Perhaps those that had issues should use such tools as prefix limits on their inbound feeds. We get notified by our edge routers quite regularly that the number of prefixes has or is about to max out.

Sent from my iPhone

On 19/09/2018, at 4:39 PM, Liam Farr <liam@maxumdata.com> wrote:

IMO I think its great that a large carrier has come to our neck of the woods, and they are openly peering on both our major IX's. This is a good thing for internet in NZ.

Notifications were sent to the affected parties who peer, months in advance.

I don't believe HE had any malicious intent to break your internet.

If your stuff broke because you have a shit upstream, fix it and move on.

On Wed, 19 Sep 2018 at 16:35, Michael Fincham <michael@hotplate.co.nz> wrote:
On Wed, 19 Sep 2018 16:32:09 +1200
Nathan Ward <nznog@daork.net> wrote:

> Through whoever you buy domestic transit from - communication for these sorts of changes, and if required protecting customers who want to run such a service on c2610s, is a core part of such a service. If your transit providers are unable to do this I would suggest looking towards other operators.

This is a bad attitude IMO. An operator turns up in NZ, breaks a bunch of stuff, doesn't even bother to post to NZNOG letting us know they're going to break things, and you're just blaming my transit provider?

Also, none of the IXes posted on NZNOG?

--
Michael
_______________________________________________
NZNOG mailing list
NZNOG@list.waikato.ac.nz
https://list.waikato.ac.nz/mailman/listinfo/nznog

--
Kind Regards

Liam Farr

Maxum Data
+64-9-950-5302

_______________________________________________
NZNOG mailing list
NZNOG@list.waikato.ac.nz
https://list.waikato.ac.nz/mailman/listinfo/nznog
_______________________________________________
NZNOG mailing list
NZNOG@list.waikato.ac.nz
https://list.waikato.ac.nz/mailman/listinfo/nznog

_______________________________________________
NZNOG mailing list
NZNOG@list.waikato.ac.nz
https://list.waikato.ac.nz/mailman/listinfo/nznog

_______________________________________________
NZNOG mailing list
NZNOG@list.waikato.ac.nz
https://list.waikato.ac.nz/mailman/listinfo/nznog

_______________________________________________
NZNOG mailing list
NZNOG@list.waikato.ac.nz
https://list.waikato.ac.nz/mailman/listinfo/nznog