Subject
From
Date
List
[quicwg/base-drafts] Connection migration should be indistinguishable from a new connection (#203)[quicwg/base-drafts] Connection migration should be indistinguishable from a new connection (#203)
Lucas Clemente
2017-01-23
quic-issues
/arch/msg/quic-issues/pVkRmbdALmrMJgU3V1UegfH4Z1Q/
2319630
1683696
Re: [quicwg/base-drafts] Connection migration should be indistinguishable from a new connection (#203)Re: [quicwg/base-drafts] Connection migration should be indistinguishable from a new connection (#203)
ianswett
2017-01-23
quic-issues
/arch/msg/quic-issues/nbF-uCedS7tTM6tqTXjXbDiqN0w/
2319652
1683696
Re: [quicwg/base-drafts] Connection migration should be indistinguishable from a new connection (#203)Re: [quicwg/base-drafts] Connection migration should be indistinguishable from a new connection (#203)
mirjak
2017-01-23
quic-issues
/arch/msg/quic-issues/SgFba2rICCseGvf6rAxS6ICfxn8/
2319877
1683696
Re: [quicwg/base-drafts] Connection migration should be indistinguishable from a new connection (#203)Re: [quicwg/base-drafts] Connection migration should be indistinguishable from a new connection (#203)
Marten Seemann
2017-01-23
quic-issues
/arch/msg/quic-issues/Wx065yrMgtuPQmayKUiGBMEGQDQ/
2319960
1683696
Re: [quicwg/base-drafts] Connection migration should be indistinguishable from a new connection (#203)Re: [quicwg/base-drafts] Connection migration should be indistinguishable from a new connection (#203)
Igor Lubashev
2017-01-25
quic-issues
/arch/msg/quic-issues/1GZlbJ7A_EwnvOYV1olePsXIX8s/
2320469
1683696
Re: [quicwg/base-drafts] Connection migration should be indistinguishable from a new connection (#203)Re: [quicwg/base-drafts] Connection migration should be indistinguishable from a new connection (#203)
Lucas Clemente
2017-01-25
quic-issues
/arch/msg/quic-issues/SGHYJ_Fzf1JA0ko3JU1EvgdfHeE/
2320481
1683696
Re: [quicwg/base-drafts] Connection migration should be indistinguishable from a new connection (#203)Re: [quicwg/base-drafts] Connection migration should be indistinguishable from a new connection (#203)
Mike Bishop
2017-11-14
quic-issues
/arch/msg/quic-issues/UvKfOD1PK2Wn6h7KXnD_dXT_6QM/
2508700
1683696
Re: [quicwg/base-drafts] Connection migration should be indistinguishable from a new connection (#203)Re: [quicwg/base-drafts] Connection migration should be indistinguishable from a new connection (#203)
Mike Bishop
2017-11-14
quic-issues
/arch/msg/quic-issues/JQMzy3h3MzmPdMHrZnfULQprgzU/
2508701
1683696
Re: [quicwg/base-drafts] Connection migration should be indistinguishable from a new connection (#203)Re: [quicwg/base-drafts] Connection migration should be indistinguishable from a new connection (#203)
Mike Bishop
2017-11-14
quic-issues
/arch/msg/quic-issues/s5tvjSuandnFk9BukGlHMUODLKg/
2508705
1683696
Re: [quicwg/base-drafts] Connection migration should be indistinguishable from a new connection (#203)Re: [quicwg/base-drafts] Connection migration should be indistinguishable from a new connection (#203)
Mike Bishop
2017-11-14
quic-issues
/arch/msg/quic-issues/641c7lwEaA38niLJ2l6S9sR7R_g/
2508706
1683696
Re: [quicwg/base-drafts] Connection migration should be indistinguishable from a new connection (#203)Re: [quicwg/base-drafts] Connection migration should be indistinguishable from a new connection (#203)
Martin Thomson
2018-01-15
quic-issues
/arch/msg/quic-issues/YuiRLEuz9_TphHo4oqEmZodj1go/
2529617
1683696
Re: [quicwg/base-drafts] Connection migration should be indistinguishable from a new connection (#203)Re: [quicwg/base-drafts] Connection migration should be indistinguishable from a new connection (#203)
ianswett
2018-01-16
quic-issues
/arch/msg/quic-issues/qVEa3nKsPuvRBK29UEnK0JMORPQ/
2529880
1683696
Re: [quicwg/base-drafts] Connection migration should be indistinguishable from a new connection (#203)Re: [quicwg/base-drafts] Connection migration should be indistinguishable from a new connection (#203)
MikkelFJ
2018-01-16
quic-issues
/arch/msg/quic-issues/D73yNktKlU7JuK5Vusph9w4sHOI/
2529926
1683696
Re: [quicwg/base-drafts] Connection migration should be indistinguishable from a new connection (#203)Re: [quicwg/base-drafts] Connection migration should be indistinguishable from a new connection (#203)
mirjak
2018-01-18
quic-issues
/arch/msg/quic-issues/ssST542Gq7PQuTgIi6_6-MDitVE/
2530783
1683696
Re: [quicwg/base-drafts] Connection migration should be indistinguishable from a new connection (#203)Re: [quicwg/base-drafts] Connection migration should be indistinguishable from a new connection (#203)
Christian Huitema
2018-02-05
quic-issues
/arch/msg/quic-issues/OuZz0WR6CuBq8J7rEBVkQlHBj0k/
2537687
1683696
Re: [quicwg/base-drafts] Connection migration should be indistinguishable from a new connection (#203)Re: [quicwg/base-drafts] Connection migration should be indistinguishable from a new connection (#203)
Lars Eggert
2018-02-05
quic-issues
/arch/msg/quic-issues/ZZBvlESYyv_OYWcYkRcbOtqgWcw/
2537751
1683696
Re: [quicwg/base-drafts] Connection migration should be indistinguishable from a new connection (#203)Re: [quicwg/base-drafts] Connection migration should be indistinguishable from a new connection (#203)
Kazuho Oku
2018-02-05
quic-issues
/arch/msg/quic-issues/MdmoJgVB1ocSpf_00e1WJxuaIt0/
2537763
1683696
Re: [quicwg/base-drafts] Connection migration should be indistinguishable from a new connection (#203)Re: [quicwg/base-drafts] Connection migration should be indistinguishable from a new connection (#203)
MikkelFJ
2018-02-05
quic-issues
/arch/msg/quic-issues/yvBiBNFJuTTpwRlB2ZdDGvvfzA4/
2537766
1683696
Re: [quicwg/base-drafts] Connection migration should be indistinguishable from a new connection (#203)Re: [quicwg/base-drafts] Connection migration should be indistinguishable from a new connection (#203)
Kazuho Oku
2018-02-05
quic-issues
/arch/msg/quic-issues/W4HVj_kDlY5rCq8Jh-3rywCeQ_c/
2537811
1683696
Re: [quicwg/base-drafts] Connection migration should be indistinguishable from a new connection (#203)Re: [quicwg/base-drafts] Connection migration should be indistinguishable from a new connection (#203)
MikkelFJ
2018-02-05
quic-issues
/arch/msg/quic-issues/Rz9-wbhJMsJr4QiAJnigQRKXiso/
2537812
1683696
Re: [quicwg/base-drafts] Connection migration should be indistinguishable from a new connection (#203)Re: [quicwg/base-drafts] Connection migration should be indistinguishable from a new connection (#203)
Mike Bishop
2018-07-10
quic-issues
/arch/msg/quic-issues/2QyQM8_eS8IoJ-dyLsBkYqWKmBY/
2607237
1683696
Re: [quicwg/base-drafts] Connection migration should be indistinguishable from a new connection (#203)Re: [quicwg/base-drafts] Connection migration should be indistinguishable from a new connection (#203)
Kazuho Oku
2018-07-11
quic-issues
/arch/msg/quic-issues/Ej7mQqR5toYRWSUn_LnGa-opBf0/
2607938
1683696
Re: [quicwg/base-drafts] Connection migration should be indistinguishable from a new connection (#203)Re: [quicwg/base-drafts] Connection migration should be indistinguishable from a new connection (#203)
Mike Bishop
2018-07-11
quic-issues
/arch/msg/quic-issues/FRLBdbCooeZkepumx6nUZ0F_HSY/
2607941
1683696
Re: [quicwg/base-drafts] Connection migration should be indistinguishable from a new connection (#203)Re: [quicwg/base-drafts] Connection migration should be indistinguishable from a new connection (#203)
Kazuho Oku
2018-07-11
quic-issues
/arch/msg/quic-issues/ZcDS4WCRN9yjIo5RgacHwhtc2iA/
2607973
1683696
Re: [quicwg/base-drafts] Connection migration should be indistinguishable from a new connection (#203)Re: [quicwg/base-drafts] Connection migration should be indistinguishable from a new connection (#203)
Martin Thomson
2018-07-31
quic-issues
/arch/msg/quic-issues/0RBUxGHvyvtK0MhU90auDNG87mY/
2616999
1683696
Re: [quicwg/base-drafts] Connection migration should be indistinguishable from a new connection (#203)Re: [quicwg/base-drafts] Connection migration should be indistinguishable from a new connection (#203)
Martin Thomson
2019-01-30
quic-issues
/arch/msg/quic-issues/8JgvcoO0wPDP_RzL2DiDUub3-Og/
2686666
1683696
Re: [quicwg/base-drafts] Connection migration should be indistinguishable from a new connection (#203)Re: [quicwg/base-drafts] Connection migration should be indistinguishable from a new connection (#203)
Martin Thomson
2019-01-30
quic-issues
/arch/msg/quic-issues/zqRRes1pN-s9VgvByCQRIDGt6sI/
2686667
1683696
[quicwg/base-drafts] HTTP: Why are we defining CONNECT? (#202)[quicwg/base-drafts] HTTP: Why are we defining CONNECT? (#202)
ekr
2017-01-23
quic-issues
/arch/msg/quic-issues/at5ussMv_oN1J3yRWqpYfWU2jjs/
2319607
1683687
Re: [quicwg/base-drafts] HTTP: Why are we defining CONNECT? (#202)Re: [quicwg/base-drafts] HTTP: Why are we defining CONNECT? (#202)
Martin Thomson
2017-01-24
quic-issues
/arch/msg/quic-issues/tmZPkJhD7oC02XF3AEzY9p0heks/
2320003
1683687
Re: [quicwg/base-drafts] HTTP: Why are we defining CONNECT? (#202)Re: [quicwg/base-drafts] HTTP: Why are we defining CONNECT? (#202)
ekr
2017-01-24
quic-issues
/arch/msg/quic-issues/xYUV_Zio-AJG_lnc8HpafYrfGOk/
2320004
1683687
Re: [quicwg/base-drafts] HTTP: Why are we defining CONNECT? (#202)Re: [quicwg/base-drafts] HTTP: Why are we defining CONNECT? (#202)
Martin Thomson
2017-01-24
quic-issues
/arch/msg/quic-issues/B0vNZ-6t9AVnr6FeWnTvhMN3L9E/
2320006
1683687
Re: [quicwg/base-drafts] HTTP: Why are we defining CONNECT? (#202)Re: [quicwg/base-drafts] HTTP: Why are we defining CONNECT? (#202)
Patrick McManus
2017-01-24
quic-issues
/arch/msg/quic-issues/cL22uAzzm6RRQAKO8VZNkqYXw-Y/
2320007
1683687
Re: [quicwg/base-drafts] HTTP: Why are we defining CONNECT? (#202)Re: [quicwg/base-drafts] HTTP: Why are we defining CONNECT? (#202)
Mike Bishop
2017-01-25
quic-issues
/arch/msg/quic-issues/C_hwVtDv7WE4CxI5tkcVd6yYmNU/
2320506
1683687
Re: [quicwg/base-drafts] HTTP: Why are we defining CONNECT? (#202)Re: [quicwg/base-drafts] HTTP: Why are we defining CONNECT? (#202)
Tatsuhiro Tsujikawa
2017-01-25
quic-issues
/arch/msg/quic-issues/GlCgUUQMD86Y2RsgPzQSmUZiInc/
2320577
1683687
Re: [quicwg/base-drafts] HTTP: Why are we defining CONNECT? (#202)Re: [quicwg/base-drafts] HTTP: Why are we defining CONNECT? (#202)
Mark Nottingham
2017-01-25
quic-issues
/arch/msg/quic-issues/SIjX2gM2B0Uabw5vM7wmRng9TX8/
2320583
1683687
Re: [quicwg/base-drafts] HTTP: Why are we defining CONNECT? (#202)Re: [quicwg/base-drafts] HTTP: Why are we defining CONNECT? (#202)
Mark Nottingham
2017-01-25
quic-issues
/arch/msg/quic-issues/EtoGPdSdmECYhualHrjsGLHqOKE/
2320584
1683687
[quicwg/base-drafts] Do streams 0 and 1 count towards MSPC? (#201)[quicwg/base-drafts] Do streams 0 and 1 count towards MSPC? (#201)
ekr
2017-01-23
quic-issues
/arch/msg/quic-issues/B6jrSX_V4gcZA56B5w6OvLfTTJc/
2319596
1683685
Re: [quicwg/base-drafts] Do streams 0 and 1 count towards MSPC? (#201)Re: [quicwg/base-drafts] Do streams 0 and 1 count towards MSPC? (#201)
Marten Seemann
2017-01-23
quic-issues
/arch/msg/quic-issues/_FSagEW4aHgeNm7YYfnepVG5lW4/
2319602
1683685
Re: [quicwg/base-drafts] Do streams 0 and 1 count towards MSPC? (#201)Re: [quicwg/base-drafts] Do streams 0 and 1 count towards MSPC? (#201)
ekr
2017-01-23
quic-issues
/arch/msg/quic-issues/KyRgZg1-3YbaYOGPNYyX8BbCSyY/
2319604
1683685
Re: [quicwg/base-drafts] Do streams 0 and 1 count towards MSPC? (#201)Re: [quicwg/base-drafts] Do streams 0 and 1 count towards MSPC? (#201)
Martin Thomson
2017-01-24
quic-issues
/arch/msg/quic-issues/SiFOL184lzQe4T5P9-kjJ7Whdes/
2320001
1683685