RE: Why allow empty STREAM frames when offset is zero?RE: Why allow empty STREAM frames when offset is zero?
Mike Bishop
2018-05-10
quic
/arch/msg/quic/KUY3Yt_S1xymtQzu6NQpBbc9C04/
2581642
1784480
Why allow empty STREAM frames when offset is zero?Why allow empty STREAM frames when offset is zero?
Dmitri Tikhonov
2018-05-10
quic
/arch/msg/quic/z55Nf2K9EXtTrrj-8ayf9-Yq9xI/
2581628
1784480
Re: Impact of hardware offloads on network stack performanceRe: Impact of hardware offloads on network stack performance
craigt
2018-05-10
quic
/arch/msg/quic/0VY0Qj0HwGz8Ygq_mZlpaEdPuUs/
2581549
1779355
RE: Cost of parsing ACK frames in QUICRE: Cost of parsing ACK frames in QUIC
Mikkel Fahnøe Jørgensen
2018-05-10
quic
/arch/msg/quic/5G70IKexv6byiMNtQT-MpYuQy2o/
2581527
1784425
Re: Impact of hardware offloads on network stack performanceRe: Impact of hardware offloads on network stack performance
Mikkel Fahnøe Jørgensen
2018-05-10
quic
/arch/msg/quic/-5-Df5NSNbmFA8Njk-Qptsr39nU/
2581510
1779355
Re: Impact of hardware offloads on network stack performanceRe: Impact of hardware offloads on network stack performance
Mikkel Fahnøe Jørgensen
2018-05-10
quic
/arch/msg/quic/HeEOqM6jTRtJ_43oq5qpR_zKJ2g/
2581503
1779355
RE: Cost of parsing ACK frames in QUICRE: Cost of parsing ACK frames in QUIC
Mikkel Fahnøe Jørgensen
2018-05-10
quic
/arch/msg/quic/sOf1uLNnPA1ss_yXMCkT9kzm4L0/
2581491
1784425
RE: Cost of parsing ACK frames in QUICRE: Cost of parsing ACK frames in QUIC
Nick Banks
2018-05-10
quic
/arch/msg/quic/I8GxMLCIt6UtHWk382BggAr_ROI/
2581490
1784425
RE: Cost of parsing ACK frames in QUICRE: Cost of parsing ACK frames in QUIC
Lubashev, Igor
2018-05-10
quic
/arch/msg/quic/45aUS1GXFaos-dxQJW6epsywDkI/
2581487
1784425
Re: Cost of parsing ACK frames in QUICRe: Cost of parsing ACK frames in QUIC
Mikkel Fahnøe Jørgensen
2018-05-10
quic
/arch/msg/quic/Ufnuw7Oc5nH_vv2vj4wulgMh7pk/
2581481
1784425
Cost of parsing ACK frames in QUICCost of parsing ACK frames in QUIC
Deval, Manasi
2018-05-10
quic
/arch/msg/quic/pGD2nWPCN0c3lgGbwZA5SVygBxA/
2581466
1784425
Re: Impact of hardware offloads on network stack performanceRe: Impact of hardware offloads on network stack performance
Eggert, Lars
2018-05-10
quic
/arch/msg/quic/Po9hfm9DsneyuCEzozUCtU146M0/
2581454
1779355
Re: Impact of hardware offloads on network stack performanceRe: Impact of hardware offloads on network stack performance
Boris Pismenny
2018-05-10
quic
/arch/msg/quic/6RGieKIWDReYnKQcJie_B4eTpsg/
2581451
1779355
Re: Impact of hardware offloads on network stack performanceRe: Impact of hardware offloads on network stack performance
Mikkel Fahnøe Jørgensen
2018-05-10
quic
/arch/msg/quic/govcAIh770k3H95f6JiuvWj-54k/
2581443
1779355
RE: Impact of hardware offloads on network stack performanceRE: Impact of hardware offloads on network stack performance
Deval, Manasi
2018-05-10
quic
/arch/msg/quic/LK8z32Qni0wJcVBxgO7GAfkh8Xw/
2581436
1779355
Re: Impact of hardware offloads on network stack performanceRe: Impact of hardware offloads on network stack performance
Eggert, Lars
2018-05-10
quic
/arch/msg/quic/AatVUfAlAf1NvU7dsC8sYT952NQ/
2581434
1779355
Re: Impact of hardware offloads on network stack performanceRe: Impact of hardware offloads on network stack performance
Mikkel Fahnøe Jørgensen
2018-05-10
quic
/arch/msg/quic/sKVpvo3WFdGB9hYKqVxrm-Anppg/
2581433
1779355
Re: Impact of hardware offloads on network stack performanceRe: Impact of hardware offloads on network stack performance
craigt
2018-05-10
quic
/arch/msg/quic/JXWQV1yEQiSJzSrP4zbKQr3Mj6M/
2581419
1779355
RE: Clarification of transport and HTTP version compatibilityRE: Clarification of transport and HTTP version compatibility
Lucas Pardue
2018-05-09
quic
/arch/msg/quic/4KwzNw44DJ3pWkA39TYhTMFzix4/
2581159
1784216
RE: Clarification of transport and HTTP version compatibilityRE: Clarification of transport and HTTP version compatibility
Mike Bishop
2018-05-09
quic
/arch/msg/quic/4OG52SSp3ItD52hZAEP4co_Vq6g/
2581146
1784216
RE: Clarification of transport and HTTP version compatibilityRE: Clarification of transport and HTTP version compatibility
Lucas Pardue
2018-05-09
quic
/arch/msg/quic/vOxm48oGNr6N1GZL-V7Uq8uWXn8/
2581097
1784216
RE: Clarification of transport and HTTP version compatibilityRE: Clarification of transport and HTTP version compatibility
Mike Bishop
2018-05-09
quic
/arch/msg/quic/Ke3AAb1bYjaXCuFplO1z9GI1Hms/
2581067
1784216
RE: Clarification of transport and HTTP version compatibilityRE: Clarification of transport and HTTP version compatibility
Lucas Pardue
2018-05-09
quic
/arch/msg/quic/q4Uoo2M_MCWOjm7MPxP5PdiLOt4/
2580961
1784216
RE: Clarification of transport and HTTP version compatibilityRE: Clarification of transport and HTTP version compatibility
Mike Bishop
2018-05-09
quic
/arch/msg/quic/k0kjoM9G2DfBEfcmEfE-zWpTK6k/
2580932
1784216
Clarification of transport and HTTP version compatibilityClarification of transport and HTTP version compatibility
Samuel Hurst
2018-05-09
quic
/arch/msg/quic/nQGhH1Kajwk7wIdfaloNPDGB36g/
2580889
1784216
RE: QPACK - proposal to optimize compressionRE: QPACK - proposal to optimize compression
Mike Bishop
2018-05-08
quic
/arch/msg/quic/SRmsYgcKA3sutuVkuTuwbc_5eGY/
2580526
1783896
RE: QPACK - proposal to optimize compressionRE: QPACK - proposal to optimize compression
Brian Swander
2018-05-08
quic
/arch/msg/quic/Wk02uzBEjKuPf9gKxMU7wQ5l21Y/
2580503
1783896
Re: QPACK - proposal to optimize compressionRe: QPACK - proposal to optimize compression
Alan Frindell
2018-05-08
quic
/arch/msg/quic/iGqBU3u95V7-6cIcX2QSJrkyWeA/
2580499
1783896
QPACK - proposal to optimize compressionQPACK - proposal to optimize compression
Brian Swander
2018-05-07
quic
/arch/msg/quic/Wa6UiaaYH5RYg4e3lAhLuPL1_ao/
2580087
1783896
Re: Working Group Last Call: QUIC InvariantsRe: Working Group Last Call: QUIC Invariants
Mark Nottingham
2018-05-07
quic
/arch/msg/quic/7THHfB4TQVzJtWgCQwLTYeyH2R8/
2579700
1776983
Re: Collecting measurements with Multipath QUICRe: Collecting measurements with Multipath QUIC
Quentin De Coninck
2018-05-04
quic
/arch/msg/quic/AlOaH7n8JsSt2FjxPM7oXFrGbY4/
2579168
1777263
Re: unique tuplesRe: unique tuples
Mikkel Fahnøe Jørgensen
2018-05-04
quic
/arch/msg/quic/RRRgHVV_lWohH9xyKWJexjCPNaQ/
2579126
1783514
Re: unique tuplesRe: unique tuples
Martin Thomson
2018-05-04
quic
/arch/msg/quic/uWLhihk5WVtTl5cSQlGibLFLkuU/
2579076
1783514
unique tuplesunique tuples
Mikkel Fahnøe Jørgensen
2018-05-04
quic
/arch/msg/quic/mjKGfF6DnluAKqeyhBBpH9MgHBU/
2579062
1783514
Re: Getting to consensus on packet number encryptionRe: Getting to consensus on packet number encryption
Christian Huitema
2018-05-02
quic
/arch/msg/quic/CtufHc1TKHGuMRhLyxktSgmCgEs/
2578328
1777632
Re: Getting to consensus on packet number encryptionRe: Getting to consensus on packet number encryption
Mikkel Fahnøe Jørgensen
2018-05-02
quic
/arch/msg/quic/lQ8UlM4d_DRXrlkoGMEo0MY9yXI/
2578275
1777632
Re: Getting to consensus on packet number encryptionRe: Getting to consensus on packet number encryption
Christian Huitema
2018-05-02
quic
/arch/msg/quic/icwScHilA4vwD065U2l5HinRAnU/
2578270
1777632
RE: Getting to consensus on packet number encryptionRE: Getting to consensus on packet number encryption
Praveen Balasubramanian
2018-05-02
quic
/arch/msg/quic/A2J7YUJkqrWG1ZItUTUFuqMYe9Q/
2578241
1777632
Re: Getting to consensus on packet number encryptionRe: Getting to consensus on packet number encryption
Gorry Fairhurst
2018-05-02
quic
/arch/msg/quic/fppmc_fFPgWAVDYAv16o5xbLsCs/
2578177
1777632
Re: Getting to consensus on packet number encryptionRe: Getting to consensus on packet number encryption
Dmitri Tikhonov
2018-05-02
quic
/arch/msg/quic/QE_8bv4vdo1Fg_-Yl_6gOFi4akc/
2578161
1777632
40 Messages