Re: Change to padding in encryption -- enabling random accessRe: Change to padding in encryption -- enabling random access
Martin Thomson
2017-01-30
httpbisa
/arch/msg/httpbisa/6X6GgkbtmchTGMuGL4AKp_YOB9Q/
2321928
1684447
RE: Change to padding in encryption -- enabling random accessRE: Change to padding in encryption -- enabling random access
Manger, James
2017-01-30
httpbisa
/arch/msg/httpbisa/oyZ71p0wU1qk6vRyQH47XBo5ouI/
2321926
1684447
RE: aes128gcm: why verify padding?RE: aes128gcm: why verify padding?
Manger, James
2017-01-30
httpbisa
/arch/msg/httpbisa/ZSFvoqzob2jlQFJRfjUWMghT_4s/
2321923
1682785
Change to padding in encryptionChange to padding in encryption
Martin Thomson
2017-01-30
httpbisa
/arch/msg/httpbisa/yuFfjfB8D-TmgKmMc4oTQQCfkLo/
2321918
1684446
Re: aes128gcm: why verify padding?Re: aes128gcm: why verify padding?
Martin Thomson
2017-01-30
httpbisa
/arch/msg/httpbisa/_5eZr_pGHgRDMKjDeSOOKkykfks/
2321892
1682785
RE: aes128gcm: why verify padding?RE: aes128gcm: why verify padding?
Manger, James
2017-01-30
httpbisa
/arch/msg/httpbisa/c_ju8r7RPG7JW-I3HpEGZ00TnwU/
2321880
1682785
Re: aes128gcm: why verify padding?Re: aes128gcm: why verify padding?
Ilari Liusvaara
2017-01-27
httpbisa
/arch/msg/httpbisa/hK3jSZ1qiC5BuIkDwPAE_zQF-gM/
2321457
1682785
Re: HTTP/2 plaintext upgradeRe: HTTP/2 plaintext upgrade
Kazuho Oku
2017-01-27
httpbisa
/arch/msg/httpbisa/v6sGzOd55sYVc9nVizx3PQgF_6o/
2321446
1684136
RE: aes128gcm: why verify padding?RE: aes128gcm: why verify padding?
Manger, James
2017-01-27
httpbisa
/arch/msg/httpbisa/AK58pYzXDbEXvRgym9teJ0JSeHs/
2321443
1682785
Re: HTTP/2 plaintext upgradeRe: HTTP/2 plaintext upgrade
Daniel Stenberg
2017-01-26
httpbisa
/arch/msg/httpbisa/M_Ih8JKCEZ7xWXRuR2TxS4lr1bU/
2321223
1684136
Re: HTTP/2 plaintext upgradeRe: HTTP/2 plaintext upgrade
Loïc Hoguin
2017-01-26
httpbisa
/arch/msg/httpbisa/kcWFEhfckbJ0K2qBan4J2IPWkC4/
2321185
1684136
HTTP/2 plaintext upgradeHTTP/2 plaintext upgrade
Cory Benfield
2017-01-26
httpbisa
/arch/msg/httpbisa/Pkz1kX8dJOUdlb6JHmtrZWBf7sM/
2321178
1684136
Re: Is a faithful HTTP/2 response scheduler necessarily O(n) in the worst case?Re: Is a faithful HTTP/2 response scheduler necessarily O(n) in the worst case?
Amos Jeffries
2017-01-26
httpbisa
/arch/msg/httpbisa/VgQBTTdzBYRQtFJMEnpiKENDFco/
2321174
1683773
[ietf-http-wg] <none>[ietf-http-wg] <none>
geronimotita
2017-01-26
httpbisa
/arch/msg/httpbisa/sPmkp4AB8B4jPtgYuNKeLi9zV00/
2321166
1684132
Re: aes128gcm: why verify padding?Re: aes128gcm: why verify padding?
Martin Thomson
2017-01-25
httpbisa
/arch/msg/httpbisa/fFhBc5fiAmYO9KOavoKaBL-YmwQ/
2320986
1682785
[Errata Rejected] RFC7231 (4734)[Errata Rejected] RFC7231 (4734)
RFC Errata System
2017-01-25
httpbisa
/arch/msg/httpbisa/WNVHBeI_ePv35_OW3vCT2Bqo5Xk/
2320981
1684063
Re: Is a faithful HTTP/2 response scheduler necessarily O(n) in the worst case?Re: Is a faithful HTTP/2 response scheduler necessarily O(n) in the worst case?
Stefan Eissing
2017-01-25
httpbisa
/arch/msg/httpbisa/0ve3UfYtobpuM_4pFBEzKFIFI_Y/
2320671
1683773
Re: Is a faithful HTTP/2 response scheduler necessarily O(n) in the worst case?Re: Is a faithful HTTP/2 response scheduler necessarily O(n) in the worst case?
Cory Benfield
2017-01-25
httpbisa
/arch/msg/httpbisa/yQpmbuBQHD1Ilfk4PFPMsjSFTQg/
2320650
1683773
Re: Is a faithful HTTP/2 response scheduler necessarily O(n) in the worst case?Re: Is a faithful HTTP/2 response scheduler necessarily O(n) in the worst case?
Kazu Yamamoto ( 山本和彦 )
2017-01-25
httpbisa
/arch/msg/httpbisa/fdVhUhrcbEQM01xv8gDm6JxF3Ho/
2320572
1683773
Re: Proposed text for erratum on PRIORITY in RFC 7540Re: Proposed text for erratum on PRIORITY in RFC 7540
Scott Mitchell
2017-01-25
httpbisa
/arch/msg/httpbisa/W8vd_GBUx4LpL3Dx8CYeQQarEPs/
2320556
1683462
Re: Is a faithful HTTP/2 response scheduler necessarily O(n) in the worst case?Re: Is a faithful HTTP/2 response scheduler necessarily O(n) in the worst case?
Tatsuhiro Tsujikawa
2017-01-25
httpbisa
/arch/msg/httpbisa/9ZLUEYiNYqSx_9t_ttPtPMI-3P8/
2320531
1683773
Re: Is a faithful HTTP/2 response scheduler necessarily O(n) in the worst case?Re: Is a faithful HTTP/2 response scheduler necessarily O(n) in the worst case?
Kazuho Oku
2017-01-25
httpbisa
/arch/msg/httpbisa/tDEiKHkFLdU9cSNZoi6oT20pOoM/
2320530
1683773
Re: Proposed text for erratum on PRIORITY in RFC 7540Re: Proposed text for erratum on PRIORITY in RFC 7540
Patrick McManus
2017-01-25
httpbisa
/arch/msg/httpbisa/QbaBz69yFbEJZwkXWm-qOfwXtVI/
2320485
1683462
Re: Is a faithful HTTP/2 response scheduler necessarily O(n) in the worst case?Re: Is a faithful HTTP/2 response scheduler necessarily O(n) in the worst case?
Patrick McManus
2017-01-24
httpbisa
/arch/msg/httpbisa/um6sdQyKMHRBpFJoDMhw7ZOu27k/
2320445
1683773
Re: Is a faithful HTTP/2 response scheduler necessarily O(n) in the worst case?Re: Is a faithful HTTP/2 response scheduler necessarily O(n) in the worst case?
Tom Bergan
2017-01-24
httpbisa
/arch/msg/httpbisa/S2TcpMfFRZqTbT2_rXOy84za3-E/
2320442
1683773
Re: Is a faithful HTTP/2 response scheduler necessarily O(n) in the worst case?Re: Is a faithful HTTP/2 response scheduler necessarily O(n) in the worst case?
Kazu Yamamoto ( 山本和彦 )
2017-01-24
httpbisa
/arch/msg/httpbisa/Ptdctejw8MdomuceUMy91XHwNJ8/
2320439
1683773
Re: Is a faithful HTTP/2 response scheduler necessarily O(n) in the worst case?Re: Is a faithful HTTP/2 response scheduler necessarily O(n) in the worst case?
Tom Bergan
2017-01-24
httpbisa
/arch/msg/httpbisa/9qi7ARAIEFtoZOy_9DM2dIw0IaY/
2320426
1683773
[ietf-http-wg] <none>[ietf-http-wg] <none>
geronimotita
2017-01-24
httpbisa
/arch/msg/httpbisa/D-KgvdLFOC1bFJIvINAuKzkdatk/
2320397
1683894
Re: Is a faithful HTTP/2 response scheduler necessarily O(n) in the worst case?Re: Is a faithful HTTP/2 response scheduler necessarily O(n) in the worst case?
Stefan Eissing
2017-01-24
httpbisa
/arch/msg/httpbisa/jCGsqO4W2FVXiNl7enPxbjQY-eI/
2320142
1683773
Re: Is a faithful HTTP/2 response scheduler necessarily O(n) in the worst case?Re: Is a faithful HTTP/2 response scheduler necessarily O(n) in the worst case?
Kazu Yamamoto ( 山本和彦 )
2017-01-24
httpbisa
/arch/msg/httpbisa/dz_yiNjZYAbxUm-bqgVSpREodaE/
2320133
1683773
Re: Is a faithful HTTP/2 response scheduler necessarily O(n) in the worst case?Re: Is a faithful HTTP/2 response scheduler necessarily O(n) in the worst case?
Kazuho Oku
2017-01-24
httpbisa
/arch/msg/httpbisa/L_nMfAxqte0fGgTcz9ULXGb-HVg/
2320129
1683773
Is a faithful HTTP/2 response scheduler necessarily O(n) in the worst case?Is a faithful HTTP/2 response scheduler necessarily O(n) in the worst case?
Tom Bergan
2017-01-24
httpbisa
/arch/msg/httpbisa/lC5BBoR9uOdvD9Va9_738v74KDg/
2319972
1683773
RE: aes128gcm: why verify padding?RE: aes128gcm: why verify padding?
Manger, James
2017-01-24
httpbisa
/arch/msg/httpbisa/ZKf6nHzqf_SXjzElTZyDCgn99Jw/
2319967
1682785
Re: aes128gcm: why verify padding?Re: aes128gcm: why verify padding?
Martin Thomson
2017-01-23
httpbisa
/arch/msg/httpbisa/LoFusOqK4K0o1xqqSlQFbSKLFGk/
2319963
1682785
Re: aes128gcm: vulnerable to truncation attacksRe: aes128gcm: vulnerable to truncation attacks
Martin Thomson
2017-01-23
httpbisa
/arch/msg/httpbisa/xw9UcshUa12yfo4XFkmgjRZIug0/
2319961
1683672
Re: Proposed text for erratum on PRIORITY in RFC 7540Re: Proposed text for erratum on PRIORITY in RFC 7540
Martin Thomson
2017-01-23
httpbisa
/arch/msg/httpbisa/tRLJ6wA6_ixVIeQDd-g476nJLCs/
2319962
1683462
RE: aes128gcm: why verify padding?RE: aes128gcm: why verify padding?
Manger, James
2017-01-23
httpbisa
/arch/msg/httpbisa/wTBL7rieUI_qMvV_vfdMQQfTRkY/
2319706
1682785
Re: aes128gcm: why verify padding?Re: aes128gcm: why verify padding?
Ilari Liusvaara
2017-01-23
httpbisa
/arch/msg/httpbisa/i1HsB8P_v61G3Hrw2ugEvpN0jVo/
2319614
1682785
RE: aes128gcm: why verify padding?RE: aes128gcm: why verify padding?
Manger, James
2017-01-23
httpbisa
/arch/msg/httpbisa/aqqLlRkh6kgGk2J3uvvUn7Fs7-g/
2319586
1682785
aes128gcm: vulnerable to truncation attacksaes128gcm: vulnerable to truncation attacks
Manger, James
2017-01-23
httpbisa
/arch/msg/httpbisa/I9zNgmBbb0qsRmqegHUuWfeSDbw/
2319579
1683672