RIPE our of IPv4

Mon Nov 25 18:31:03 UTC 2019

Hard to say that something that is in full implementation and use is dead.

On Mon, Nov 25, 2019 at 9:21 AM Owen DeLong <owen at delong.com> wrote:
>
> RIPE isn’t dead… Just IPv4.
>
> Owen
>
>
> > On Nov 25, 2019, at 08:03 , Ryland Kremeier <rkremeier at barryelectric.com> wrote:
> >
> > RIP RIPE
> >
> >
> > -----Original Message-----
> > From: NANOG <nanog-bounces at nanog.org> On Behalf Of Andy Ringsmuth
> > Sent: Monday, November 25, 2019 9:58 AM
> > To: NANOG mailing list <nanog at nanog.org>
> > Subject: Re: RIPE our of IPv4
> >
> >
> >
> >> On Nov 25, 2019, at 8:56 AM, Dmitry Sherman <dmitry at interhost.net> wrote:
> >>
> >> Just received a mail that RIPE is out of IPv4:
> >>
> >> Dear colleagues,
> >>
> >> Today, at 15:35 UTC+1 on 25 November 2019, we made our final /22 IPv4 allocation from the last remaining addresses in our available pool. We have now run out of IPv4 addresses.
> >
> > Does this mean we are finally ripe for widespread IPv6 adoption?
> >
> > (Admit it, someone had to say it!)
> >
> > ----
> > Andy Ringsmuth
> > 5609 Harding Drive
> > Lincoln, NE 68521-5831
> > (402) 304-0083
> > andy at andyring.com
>

-- 
Jeff Shultz

-- 
Like us on Social Media for News, Promotions, and other information!!

<https://www.facebook.com/SCTCWEB/>      
<https://www.instagram.com/sctc_503/>      
<https://www.yelp.com/biz/sctc-stayton-3>      
<https://www.youtube.com/c/sctcvideos>

_**** This message 
contains confidential information and is intended only for the individual 
named. If you are not the named addressee you should not disseminate, 
distribute or copy this e-mail. Please notify the sender immediately by 
e-mail if you have received this e-mail by mistake and delete this e-mail 
from your system. E-mail transmission cannot be guaranteed to be secure or 
error-free as information could be intercepted, corrupted, lost, destroyed, 
arrive late or incomplete, or contain viruses. The sender therefore does 
not accept liability for any errors or omissions in the contents of this 
message, which arise as a result of e-mail transmission. ****_