RE: Need /24 (arin) asap

["McBride, Mack" <C-Mack.McBride () charter com>]

Large providers still have to deal with geolocation, ip reputation etc.
We just have to deal with it on an exponentially larger scale.

Mack

-----Original Message-----
From: NANOG [mailto:nanog-bounces () nanog org] On Behalf Of Mike Hammett
Sent: Monday, June 11, 2018 10:58 AM
Cc: nanog () nanog org
Subject: Re: Need /24 (arin) asap

*nods* Having v6 does solve a lot, but the ones that are difficult to work with in v4 are still using v4, so you still 
have problems. 

I think those experiences are ones felt only by small to medium service providers. Large carriers, academia, 
hosting\datacenter, etc. don't really have those problems. They do have different problems, but they're fairly well 
known problems with processes laid out on how to deal with it. 

See my thread from a few weeks ago calling on people doing IP reputation or any sort of geolocation, filtering, 
blocking, etc. being more transparent. There are ISPs that have tried everything short of driving to the content 
provider's location and demanding resolution. 




-----
Mike Hammett
Intelligent Computing Solutions
http://www.ics-il.com 

Midwest-IX
http://www.midwest-ix.com 

----- Original Message -----

From: "Ca By" <cb.list6 () gmail com>
To: "Michael Crapse" <michael () wi-fiber io>
Cc: nanog () nanog org
Sent: Monday, June 11, 2018 11:50:55 AM
Subject: Re: Need /24 (arin) asap 

On Mon, Jun 11, 2018 at 9:27 AM, Michael Crapse <michael () wi-fiber io> wrote: 

> For an eyeball network, you cannot count on an IPv6 only network. 
> Because all of your "customers" will complain because they can't get 
> to hulu, or any other ipv4 only eyeball service. You still need the 
> ipv4s to operate a proper network, and good luck figuring out which 
> services are blacklisting your new /24 because the ipv4 space used to be a VPN provider, and the "in"
> thing to do for these services is to block VPNs. 

There are many IPv6-only eyeball networks. Definitely many examples in 
wireless (T-Mobile, Sprint, BT ) and wireline (DT with DS-Lite in Germany, 
Orange Poland ...) and even more where IPv4 NAT44 + IPv6 is used. Just 
saying, having ipv6 hedges a lot of risk associate with blacklisting and 
translation related overhead and potentially scale and cost of IPv4 
addresses. 


> On 11 June 2018 at 09:21, Ca By <cb.list6 () gmail com> wrote: 
>
> > On Sun, Jun 10, 2018 at 8:43 AM Stan Ouchakov <stano () imaginesoftware com> 
> > wrote: 
> >
> > > Hi, 
> > >
> > > Can anyone recommend transfer market brokers for ipv4 addresses? Need 
> > > clean /24 asap. ARIN's waiting list is too long... 
> > >
> > > Thanks! 
> > >
> > >
> > > -Stan 
> > >
> > > Meanwhile, FB reports that 75% of mobiles in the USA reach them via ipv6 
> >
> > https://code.facebook.com/posts/635039943508824/how-ipv6- 
> > deployment-is-growing-in-u-s-and-other-countries/ 
> >
> >
> > And Akaimai reports 80% of mobiles 
> >
> > https://blogs.akamai.com/2018/06/six-years-since-world-ipv6- 
> > launch-entering-the-majority-phases.html 
> >
> >
> > And they both report ipv6 is faster / better. 

E-MAIL CONFIDENTIALITY NOTICE: 
The contents of this e-mail message and any attachments are intended solely for the addressee(s) and may contain 
confidential and/or legally privileged information. If you are not the intended recipient of this message or if this 
message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this 
message and any attachments. If you are not the intended recipient, you are notified that any use, dissemination, 
distribution, copying, or storage of this message or any attachment is strictly prohibited.