Live data from Hacker News

Did AS8003 just disappear?

kentik.com

41–50 of 75 posts

Re: Did AS8003 just disappear?

#41
post #20
post #14

Earlier quoted context omitted.

I'm baffled too. This is why there is an RFC 1918 so everyone knows what's public and private.

There's probably some group of network operators out there who decided amongst themselves that it'd be cheaper and easier to squat the dod ranges when shuffling traffic amongst themselves, than having to wrap each packet with a tunneling header. Or who knows maybe some third world dictator told their isps to use the dod ranges because they mistakenly assumed it would isolate their nation's traffic from the rest of th…

I was going to suggest 240 and up but apparently Windows will flat-out reject those addresses for any use.

Re: Did AS8003 just disappear?

#42
post #29

Earlier quoted context omitted.

I get plenty of requests for static ipv4 from smb and home users.

You get plenty of requests for the static part of it and less so for actual ipv4. If there was an option for static ipv6 then people would also request that instead. Static IPs have use cases that people in the wild need, however I don’t think anyone cares if it’s ipv4 or ipv6.

I mean, I'd love static both, but I'm going to ask for static v4 first, because I can always run a tunnel for static v6.

Re: Did AS8003 just disappear?

#43
post #20
post #14

Earlier quoted context omitted.

I'm baffled too. This is why there is an RFC 1918 so everyone knows what's public and private.

There's probably some group of network operators out there who decided amongst themselves that it'd be cheaper and easier to squat the dod ranges when shuffling traffic amongst themselves, than having to wrap each packet with a tunneling header. Or who knows maybe some third world dictator told their isps to use the dod ranges because they mistakenly assumed it would isolate their nation's traffic from the rest of th…

Wait. One of my last actions as the DISA.MIL Technical POC was to turn one of those Class-A network ranges back into the NIC. I thought it was 21/8?

You mean they never actually turned that one back in?

Dang it! I thought that was one of my minor successes during my time in that role.

;(

Re: Did AS8003 just disappear?

#44
post #25

Earlier quoted context omitted.

I’ve begged my isp to get on it

I just got a /32 from ARIN to start implementing it on our network but it is by no stretch of the imagination worth the effort. I will probably have at least 40 hours into testing it and no increased revenue will be realized by it. Maybe IPv6 was the the right thing to due but the practical implementation is ridiculous.

I doubt you'll see more revenue from it. If you're low on v4 addresses and you're willing to put (some) subscribers behind CGNAT, then inplementing v6 should reduce the number of v4 addresses you need and thus reduce your costs.

If you give each subscriber an IPv4, then yeah, added operational cost, no revenue, maybe added capital cost depending on your equipment. Not much upside for a small ISP. In a competitive market, v6 can get you some points with the technical folks, but not many.

Re: Did AS8003 just disappear?

#45
post #19
post #10

Not a popular idea here, but IPv6 folks. Even for k8s, even for your internal stuff.

Why is IPv6 not a popular idea here?

IMO, it is frequently seen as a solution in search of a problem, that breaks things and makes things harder when used to no real benefit. Whether any of that is accurate is left as an exercise for the reader.

Re: Did AS8003 just disappear?

#46
post #23
post #19

Earlier quoted context omitted.

Why is IPv6 not a popular idea here?

I work at an ISP and not a single customer has ever even mentioned IPv6. There zero demand on the residential side.

How many customers directly ask for an IPv4? If ISP wait for the average consumer to ask for IPv6, it will never get implemented.

Re: Did AS8003 just disappear?

#47

I'm surprised kentik is still around. They were selling an inferior product to a company I worked at that was bought by Nokia. I figured they would've gone out of business by now.

Nobody wonders why Microsoft is still around. Selling a technically inferior product is not a problem if you can find customers. There can be many reasons. Markets are far from perfect.

Re: Did AS8003 just disappear?

#48
post #25

Earlier quoted context omitted.

I’ve begged my isp to get on it

I just got a /32 from ARIN to start implementing it on our network but it is by no stretch of the imagination worth the effort. I will probably have at least 40 hours into testing it and no increased revenue will be realized by it. Maybe IPv6 was the the right thing to due but the practical implementation is ridiculous.

There's not much upside for a legacy network that already has all the IPv4 it needs, but an upstart ISP will do well starting with IPv6 and layering CGNAT IPv4 on top. With 30% of the Alexa top 500 supporting IPv6 (and a lot of the top traffic sites like Google/YouTube, Facebook/Instagram, Netflix etc) it will reduce the amount of IPv4 you need to buy

Re: Did AS8003 just disappear?

#49
post #20

Earlier quoted context omitted.

There's probably some group of network operators out there who decided amongst themselves that it'd be cheaper and easier to squat the dod ranges when shuffling traffic amongst themselves, than having to wrap each packet with a tunneling header. Or who knows maybe some third world dictator told their isps to use the dod ranges because they mistakenly assumed it would isolate their nation's traffic from the rest of th…

Wait. One of my last actions as the DISA.MIL Technical POC was to turn one of those Class-A network ranges back into the NIC. I thought it was 21/8? You mean they never actually turned that one back in? Dang it! I thought that was one of my minor successes during my time in that role. ;(

49/8 and 50/8 were returned by DoD in the late 90s if that is what you are thinking of.

Re: Did AS8003 just disappear?

#50
post #14

Earlier quoted context omitted.

Was it ever common to use 11/8 internally? Did people just roll dice because it wasn't being announced? The reference in the post is the first I've heard of people possibly using it.

I'm baffled too. This is why there is an RFC 1918 so everyone knows what's public and private.

The problem is that every one reuses the same RFC1918 space and this becomes a problem when you join them all together. For instance I discovered this year there is a electronic payments processor here in Australia that uses the 29/8 space. I'm doing a project for a large retail company that has to route payments to lots of providers. Each one has a different way of handling the conflict - either through properly registered public space, or through NATting to their own or the customers space. I did raise the issue that 29/8 was now actually routable on the internet, and maybe the provider should pick another strategy. But I don't think they see it as an issue mainly because these networks are quite closed and separated from regular internet space
Post reply on HN