Please use this identifier to cite or link to this item: http://hdl.handle.net/1942/27511
Full metadata record
DC FieldValueLanguage
dc.contributor.authorMARX, Robin-
dc.contributor.authorReynders, Jonas-
dc.contributor.authorPittevils, Kevin-
dc.contributor.authorQUAX, Peter-
dc.contributor.authorLAMOTTE, Wim-
dc.date.accessioned2018-12-14T09:45:49Z-
dc.date.available2018-12-14T09:45:49Z-
dc.date.issued2018-
dc.identifier.citationProceedings of the Workshop on the Evolution, Performance, and Interoperability of QUIC (EPIQ'18), ACM,p. 1-7-
dc.identifier.isbn9781450360821-
dc.identifier.urihttp://hdl.handle.net/1942/27511-
dc.description.abstractQUIC has been called the mother of all web protocols, as it deeply integrates aspects of TCP (reliability, flow control, congestion control, loss recovery), TLS (handshake, encryption keys) and HTTP/2 (streams, prioritization) together into one cross-layer implementation over UDP. However, such ambition comes at the cost of high complexity, which in turn leads to misinterpretations, bugs and unwanted behaviour in implementations. This was also witnessed in the recently standardized HTTP/2 protocol. We posit that QUIC should thus take a proactive approach in ensuring its testability and debuggability. To that end, this work introduces the first version of a common logging format for QUIC endpoints, called qlog. This format allows the capture of internal QUIC state that is not visible on the network. It is easily deployable and empowers the creation of reusable (visual) tools to aid in interpreting QUIC’s behaviour. We implement and evaluate three such tools (a timeline, sequence diagram and congestion/flow control graph) in the proposed QUICvis toolset and show their usefulness in comparing behaviours across three competing QUIC implementations, as well as in performing root cause analysis on bugs and issues. We hope this work will foster the discussion on QUIC debuggability and that it will raise community awareness.-
dc.language.isoen-
dc.publisherACM-
dc.subject.otherQUIC; Transport protocol; Logging; Interactive visualization-
dc.titleTowards QUIC Debuggability-
dc.typeProceedings Paper-
local.bibliographicCitation.conferencedate4 December 2018 - 7 December 2018-
local.bibliographicCitation.conferencenameWorkshop on the Evolution, Performance, and Interoperability of QUIC (EPIQ) at CoNEXT 2018-
local.bibliographicCitation.conferenceplaceHeraklion, Crete-
dc.identifier.epage7-
dc.identifier.spage1-
local.bibliographicCitation.jcatC1-
dc.description.notesMarx, R (reprint author), Hasselt Univ, tUL, EDM, Diepenbeek, Belgium. Res Fdn Flanders, FWO, 1S02717N, Brussels, Belgium. robin.marx@uhasselt.be-
local.publisher.placeNew York-
local.type.refereedRefereed-
local.type.specifiedProceedings Paper-
dc.identifier.doi10.1145/3284850.3284851-
dc.identifier.isi000473331700001-
dc.identifier.urlhttps://quic.edm.uhasselt.be-
local.bibliographicCitation.btitleProceedings of the Workshop on the Evolution, Performance, and Interoperability of QUIC (EPIQ'18)-
item.fulltextWith Fulltext-
item.fullcitationMARX, Robin; Reynders, Jonas; Pittevils, Kevin; QUAX, Peter & LAMOTTE, Wim (2018) Towards QUIC Debuggability. In: Proceedings of the Workshop on the Evolution, Performance, and Interoperability of QUIC (EPIQ'18), ACM,p. 1-7.-
item.accessRightsOpen Access-
item.validationecoom 2020-
item.contributorMARX, Robin-
item.contributorReynders, Jonas-
item.contributorPittevils, Kevin-
item.contributorQUAX, Peter-
item.contributorLAMOTTE, Wim-
Appears in Collections:Research publications
Files in This Item:
File Description SizeFormat 
QUIC_debuggability_Published_04dec2018.pdfPublished version1.12 MBAdobe PDFView/Open
Show simple item record

SCOPUSTM   
Citations

1
checked on Sep 3, 2020

WEB OF SCIENCETM
Citations

9
checked on May 10, 2024

Page view(s)

146
checked on Sep 7, 2022

Download(s)

276
checked on Sep 7, 2022

Google ScholarTM

Check

Altmetric


Items in DSpace are protected by copyright, with all rights reserved, unless otherwise indicated.