Hi SM,
Responses inline.
On Sat, Mar 16, 2019 at 3:12 PM S Moonesamy <sm+ietf@xxxxxxxxxxxx> wrote:
Hi Richard,
At 04:28 AM 13-03-2019, Richard Barnes wrote:
>The posts from Let's Encrypt et al. provide data that are
>informative on this question. Many of the participants in the ACME
>process were newcomers to the IETF. That they've put in all the
>effort to get an RFC published and still failed to note the various
>maturity levels should be instructive.
Certificates which are automatically accepted by a web browser were
not free before. The change brought by "Let's Encrypt" is the
availability of free certificates.
That's not all. Let's Encrypt enabled free and *automatic* certificate issuance, both of which helped the ecosystem grow. The standardization of ACME allows the "automatic" part to be used across the rest of the industry.
There is the following in the blog article: "Security protocols such
as TLS 1.3 provide encryption that protects ..." The video displays
the following "The connection uses TLS 1.2".
It's an old video :) And obviously, the same applies to TLS 1.2.
There is an image about web pages using HTTPS over time [1]. Is
there any data about the number of web pages at the continental level?
I don't have that data; someone at Mozilla might be able to derive it from their telemetry. The source of that graph is <https://letsencrypt.org/stats/>, which has the US and Japan broken out.
Hope that helps,
--Richard
Regards,
S. Moonesamy
1.
https://www.ietf.org/media/images/Screen_Shot_2019-03-12_at_2.53.28_PM.original.png
