httpbisa

Re: Issue 271 of 5987bis - Proposed Standard or Internet Standard?Re: Issue 271 of 5987bis - Proposed Standard or Internet Standard?

Julian Reschke

2017-01-31

Re: Issue 271 of 5987bis - Proposed Standard or Internet Standard?Re: Issue 271 of 5987bis - Proposed Standard or Internet Standard?

Patrick McManus

2017-01-31

Re: I-D Action: draft-ietf-httpbis-client-hints-03.txtRe: I-D Action: draft-ietf-httpbis-client-hints-03.txt

Mark Nottingham

2017-01-31

Re: I-D Action: draft-ietf-httpbis-client-hints-03.txtRe: I-D Action: draft-ietf-httpbis-client-hints-03.txt

Mark Nottingham

2017-01-31

Re: Change to padding in encryption -- examples look okRe: Change to padding in encryption -- examples look ok

Martin Thomson

2017-01-31

RE: Change to padding in encryption -- examples look okRE: Change to padding in encryption -- examples look ok

Manger, James

2017-01-31

Re: Change to padding in encryption -- enabling random accessRe: Change to padding in encryption -- enabling random access

Martin Thomson

2017-01-30

RE: Change to padding in encryption -- enabling random accessRE: Change to padding in encryption -- enabling random access

Manger, James

2017-01-30

Re: Change to padding in encryption -- enabling random accessRe: Change to padding in encryption -- enabling random access

Martin Thomson

2017-01-30

RE: Change to padding in encryption -- enabling random accessRE: Change to padding in encryption -- enabling random access

Manger, James

2017-01-30

RE: aes128gcm: why verify padding?RE: aes128gcm: why verify padding?

Manger, James

2017-01-30

Change to padding in encryptionChange to padding in encryption

Martin Thomson

2017-01-30

Re: aes128gcm: why verify padding?Re: aes128gcm: why verify padding?

Martin Thomson

2017-01-30

RE: aes128gcm: why verify padding?RE: aes128gcm: why verify padding?

Manger, James

2017-01-30

Re: aes128gcm: why verify padding?Re: aes128gcm: why verify padding?

Ilari Liusvaara

2017-01-27

Re: HTTP/2 plaintext upgradeRe: HTTP/2 plaintext upgrade

Kazuho Oku

2017-01-27

RE: aes128gcm: why verify padding?RE: aes128gcm: why verify padding?

Manger, James

2017-01-27

Re: HTTP/2 plaintext upgradeRe: HTTP/2 plaintext upgrade

Daniel Stenberg

2017-01-26

Re: HTTP/2 plaintext upgradeRe: HTTP/2 plaintext upgrade

Loïc Hoguin

2017-01-26

HTTP/2 plaintext upgradeHTTP/2 plaintext upgrade

Cory Benfield

2017-01-26

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

[ietf-http-wg] <none>[ietf-http-wg] <none>

geronimotita

2017-01-26

Re: aes128gcm: why verify padding?Re: aes128gcm: why verify padding?

Martin Thomson

2017-01-25

[Errata Rejected] RFC7231 (4734)[Errata Rejected] RFC7231 (4734)

RFC Errata System

2017-01-25

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

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

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

Re: Proposed text for erratum on PRIORITY in RFC 7540Re: Proposed text for erratum on PRIORITY in RFC 7540

Scott Mitchell

2017-01-25

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

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

Re: Proposed text for erratum on PRIORITY in RFC 7540Re: Proposed text for erratum on PRIORITY in RFC 7540

Patrick McManus

2017-01-25

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

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

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

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

[ietf-http-wg] <none>[ietf-http-wg] <none>

geronimotita

2017-01-24

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

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

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

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

FILTER BY TIME

FILTER BY FROM