This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Lukasa
Recipients Dima.Tisnek, Lukasa, alex, christian.heimes, giampaolo.rodola, janssen, jcea, mnot, pitrou
Date 2014-09-06.09:18:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1409995134.36.0.92163607863.issue20188@psf.upfronthosting.co.za>
In-reply-to
Content
Updating to mention a concern with ALPN implementation. HTTP/2 requires that a cipher with AEAD be negotiated. However, it also allows for offering a wider range of cipher suites: if an AEAD cipher is not present, this will allow fallback to HTTP/1.1.

There's some interplay between ALPN and cipher selection here. We'll want to ensure that either ALPN negotiation can inform cipher selection or vice-versa, or writing a Python HTTP/2 server will get tricky fast.
History
Date User Action Args
2014-09-06 09:18:54Lukasasetrecipients: + Lukasa, jcea, janssen, pitrou, mnot, giampaolo.rodola, christian.heimes, alex, Dima.Tisnek
2014-09-06 09:18:54Lukasasetmessageid: <1409995134.36.0.92163607863.issue20188@psf.upfronthosting.co.za>
2014-09-06 09:18:54Lukasalinkissue20188 messages
2014-09-06 09:18:53Lukasacreate