On Wed, Jun 29, 2016 at 12:25 PM Brian Smith <br...@briansmith.org> wrote:
> Dmitry Khovratovich <khovratov...@gmail.com> wrote: > > It allows cheap and memoryless verification by the server even though the > > puzzle solving guaranteely requires dozens of MB of RAM from a client > > I feel like this is impractical simply because lots of people are > building HTTPS clients that don't even have dozens of MB of RAM total. > I think we should avoid doing anything that requires the client to > have more than ~16KB of memory total to devote to TLS stuff. > Otherwise, we force the internet to have an architecture where all > small devices require a smart proxy to solve these puzzles for them > and do other things. > > I have to second Brian's opinion---it's difficult enough to get embedded devices to use HTTPS already. Requiring dozens of megabytes of memory will make HTTPS impossible for these devices in many cases. > Cheers, > Brian > -- > https://briansmith.org/ > > _______________________________________________ > TLS mailing list > TLS@ietf.org > https://www.ietf.org/mailman/listinfo/tls >
_______________________________________________ TLS mailing list TLS@ietf.org https://www.ietf.org/mailman/listinfo/tls
