Re: RIPE our of IPv4

2019-12-01 Thread Justin Streiner
On Sat, Nov 30, 2019 at 7:58 PM Brandon Martin wrote: > Does Verizon still own/manage ANY of their Fios territories? I thought it > was all sold off to Frontier at this point. It certainly all is, along > with all their legacy LEC territories not having FTTx and having some form > of DSL, aroun

Re: RIPE our of IPv4

2019-12-01 Thread bzs
This is that reasoning that because this particular shiny bauble is laying right here on the table then that's the whole picture. More likely if some of them decided to sell that IPv4 block they'd catch up on the rent or cut deductibles on the health care plan or or get rid of some of that 100mb

Re: RIPE our of IPv4

2019-12-01 Thread Brandon Martin
On 12/1/19 8:56 PM, Mark Andrews wrote: End Users End users receive IP addresses for use in their internal networks only, and not for distribution to external users of their Internet services. I guess it's possible that these networks would be considered end users, but I get the impression th

Re: RIPE our of IPv4

2019-12-01 Thread Mark Andrews
End Users End users receive IP addresses for use in their internal networks only, and not for distribution to external users of their Internet services. End Users with Registration Services Plan End users may opt to pay for ARIN registration services on the same schedule as ISPs detailed above b

Re: RIPE our of IPv4

2019-12-01 Thread Matthew Kaufman
I get $500, not $150, when I read the price list. On Sun, Dec 1, 2019 at 4:06 PM Owen DeLong wrote: > You’re saying that there are two networks that are of sufficient > complexity/size/whatever to require PA addressing, yet lack the resources > for $150/year in registration fees? > > I suppose i

Re: RIPE our of IPv4

2019-12-01 Thread Owen DeLong
You’re saying that there are two networks that are of sufficient complexity/size/whatever to require PA addressing, yet lack the resources for $150/year in registration fees? I suppose it’s not impossible, but I’m wondering how they afford the other expenses associated with maintaining such a n

Re: Disney+ Streaming

2019-12-01 Thread Jared Mauch
Speaking as a consumer I tend to purchase content and things like OTA broadcasts are available overnight without commercials. Thus is worth it for me. Cut the 30 minute show to 18-22 and can download without geo locks wherever I am. Sent from my iFridge > On Dec 1, 2019, at 4:31 PM, Jay R. As

Re: AWS re:Invent

2019-12-01 Thread Ben Cannon
Not to belabor a point, but this (perhaps just the OP and not a follow-up) but this is EXACTLY what I love about NANOG and why I’ve been a member for. Uh. Ever. This little community of people that get together with a united purpose of connecting the world. BGP requires us in a way to

Re: Disney+ Streaming

2019-12-01 Thread Jay R. Ashworth
Each service *is a cable company*, requiring it's own set-top box (or a plug-in that works on your current box/tv. Note also that you can't DVR any of this stuff, and it *does* go away. Cheers, -- jra - Original Message - > From: "Ross Tajvar" > To: "Owen DeLong" > Cc: "North American

Re: RIPE our of IPv4

2019-12-01 Thread Mark Tinka
On 1/Dec/19 02:54, Brandon Martin wrote: > How slim are your margins to have been around long enough to have a legacy > IPv4 block but not be able to afford the ARIN fees to get a comparable/very > usable (/48 to /52 for each IPv4) amount of IPv6? And if you don't need a > "comparable" amou

Re: RIPE our of IPv4

2019-12-01 Thread Mark Tinka
On 30/Nov/19 18:45, Ca By wrote: > > > Sadly, ipv6 is creating a bifurcation of the internet.  Scale shops > have v6, and non-scale shops don’t. The big players are pulling away, > and that makes things bleak for the folks just trying to tread water > in ipv4. Well, China have scale, but perhap

Re: RIPE our of IPv4

2019-12-01 Thread Simon Leinen
Matthew Kaufman writes: > This is a great example (but just one of many) of how server software > development works: Small addition/correction to this example (which I find interesting and also sad): > Kubernetes initial release June 2014. Developed by Google engineers. [...] > Full support inclu