[162588] in North American Network Operators' Group
Re: IPv6 and HTTPS
daemon@ATHENA.MIT.EDU (shawn wilson)
Fri Apr 26 01:47:04 2013
In-Reply-To: <7C8838A3-70FA-478A-97E3-3F1F09FC4E15@ianai.net>
Date: Fri, 26 Apr 2013 01:46:52 -0400
From: shawn wilson <ag4ve.us@gmail.com>
To: "Patrick W. Gilmore" <patrick@ianai.net>
Cc: North American Network Operators Group <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Apr 26, 2013 12:29 AM, "Patrick W. Gilmore" <patrick@ianai.net> wrote:
>
> On Apr 26, 2013, at 00:19 , joel jaeggli <joelja@bogus.com> wrote:
> > On 4/25/13 6:24 PM, Jay Ashworth wrote:
>
> >> Ok, here's a stupid question[1], which I'd know the answer to if I ran
bigger
> >> networks:
> >>
> >> Does anyone know how much IPv4 space is allocated *specifically* to
cater
> >> to the fact that HTTPS requires a dedicated IP per DNS name?
> > It doesn't, or doesn't if if your clients are not stuck in the past.
> >
> > TLS SNI has existed for a rather long time.
> >> Is that a statistically significant percentage of all the IPs in use?
> >>
> >> Wasn't there something going on to make HTTPS IP muxable? How's that
coming?
> > there are stuborn legacy hosts.
> >> How fast could it be deployed?
> > you can use it now.
>
> Sure, you "can".
>
> But no one will. No one (especially someone doing SSL content) wants 99%
connectivity. And there's a lot more than 1% XP out there. (Hrm, that
explanation works to explain why to a couple decimal places 0% of the
Internet is on v6 only today.)
>
You like fuzzy math. OK.
http://tndh.net/~tony/ietf/ARIN-runout-projection.pdf
