- From: Maxthon Chan <xcvista@me.com>
- Date: Wed, 01 Apr 2015 15:32:27 +0800
- To: Yoav Nir <ynir.ietf@gmail.com>
- Cc: "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
I understand there are still certain places that encryption itself is too expensive to use like microcontrollers, but that does not mean they cannot stick to existing plaintext HTTP/1.1 For those microcontrollers using HTTP/2 would actually introduce more state (aka memory use) and given the compatibility requirement of HTTP/2 they would also have to include a minimal HTTP/1.1 support (aka code size) so ion;t think HTTP/2 would be appropriate for those applications anyway. For pretty much all other applications TLS won’t be expensive at all, according to what I know. So maybe if Let’s Encrypt is a success we can mark plain HTTP/2 as deprecated after all, since it bring no benefit either way. > On Apr 1, 2015, at 15:01, Yoav Nir <ynir.ietf@gmail.com> wrote: > > That project, if successful, will reduce the already-low price of a TLS certificate. > > The new enrollment protocol that was discussed in the ACME BoF, if successful, will lower the already-low administrative burden of getting and renewing a certificate. > > Neither will make HTTPS free. > > Yoav > >> On Apr 1, 2015, at 6:51 AM, ChanMaxthon <xcvista@me.com> wrote: >> >> Just wondering, have you guys heard of Let's Encrypt project led by EFF and backed by a few major companies including Cisco, providing SSL certificates with a valid trust chain to everybody for free? If that project is successful we may be able to treat any plaintext traffic as deprecated - just deprecate plaintext HTTP/2 upon release as well as plain HTTP/1.1 >> >> Sent from my iPhone >> >>> On Apr 1, 2015, at 07:15, Stephen Farrell <stephen.farrell@cs.tcd.ie> wrote: >>> >>> >>> >>>> On 01/04/15 00:07, Poul-Henning Kamp wrote: >>>> >>>> The only real solution is to make make privacy a protected human right. >>> >>> It is in theory, says the UDHR. [1] But I think we've wandered far >>> from this list's remit. Happy to continue off list though, or you >>> could sign up to the (quite new) hrpc@irtf.org list [2] that was >>> previously hosted at. [3] ([3] was just migrated to [2] yesterday.) >>> >>> S. >>> >>> [1] http://www.un.org/en/documents/udhr/index.shtml/index.shtml#a12 >>> [2] https://irtf.org/mailman/listinfo/hrpc >>> [3] https://lists.ghserv.net/mailman/listinfo/hrpc >>> >>> >> >
Received on Wednesday, 1 April 2015 07:33:27 UTC