1<!DOCTYPE html> 2<html> 3 4 <head> 5 <meta charset="utf-8"> 6 <meta http-equiv="X-UA-Compatible" content="IE=edge"> 7 <meta name="viewport" content="width=device-width, initial-scale=1"> 8 <title>Quentin De Coninck - Research</title> 9 <meta name="description" content="Quentin De Coninck -- Research"> 10 <link rel="stylesheet" href="/css/main.css"> 11 <link rel="canonical" href="/research/"> 12<link rel="shortcut icon" type ="image/x-icon" href="/images/favicon.ico"> 13 14
15<script>
vendor: 345 bytes, lines 15-21
15 16 (function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){ 17 (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o), 18 m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m) 19 })(window,document,'script','https://www.google-analytics.com/analytics.js','ga'); 20 21 ga('create', '
21UA-82472331-1
vendor: 39 bytes, lines 21-23
21', 'auto'); 22 ga('send', 'pageview'); 23
24</script>
24 25 26 27</head> 28 29 30 <body> 31 32 <div class="navbar navbar-default navbar-fixed-top" role="navigation"> 33 <div class="container-fluid"> 34 <div class="navbar-header"> 35 <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-target="#navbar-collapse-1" aria-expanded="false"> 36 <span class="sr-only">Toggle navigation</span> 37 <span class="icon-bar"></span> 38 <span class="icon-bar"></span> 39 <span class="icon-bar"></span> 40 </button> 41 42 <a class="navbar-brand" href="/">Quentin De Coninck</a> 43 </div> 44 <div class="collapse navbar-collapse" id="navbar-collapse-1"> 45 <ul class="nav navbar-nav navbar-right"> 46 <li><a href="/">Home</a></li> 47 <li><a href="/allnews">News</a></li> 48 <li><a href="/research">Research</a></li> 49 <li><a href="/services">Services</a></li> 50 <li><a href="/software">Software</a></li> 51 <li><a href="/teaching">Teaching</a></li> 52 </ul> 53 </div> 54 </div> 55</div> 56 57 58 <div class="container-fluid"> 59 <div class="row"> 60 <div id="textid" class="col-sm-12"> 61 <h1 id="research">Research</h1> 62 63<p>My research interests include multipath transport protocols, system architecture and security of deployed systems. 64I also strive to provide reproducible results and release my softwares under open-source licenses. 65You can have more detail on the dedicated <a href="/software/">Software</a> section.</p> 66 67<h1 id="publications">Publications</h1> 68 69<h2 id="highlights">Highlights</h2> 70 71<p>(For a full list see <a href="#full-list">below</a> or go to <a href="https://scholar.google.be/citations?user=2akL5ySI3O0C&hl=en">Google Scholar</a>)</p> 72 73<div class="row"> 74 75 <div class="col-sm-6 clearfix"> 76 <div class="well"> 77 <pubtit>Core QUIC: Enabling Dynamic, Implementation-Agnostic Protocol Extensions</pubtit> 78 <p><img src="/images/pubpic/corequic.png" class="img-responsive img-margin" width="33%" style="float: left" /></p> 79 <p>Core QUIC introduces a framework in which <em>any</em> Core QUIC-compliant implementation can be safely extended using dynamically loaded plugins. We demonstrated the feasibility of our approach by making two popular QUIC implementations, Cloudflareâs <code class="language-plaintext highlighter-rouge">quiche</code> and <code class="language-plaintext highlighter-rouge">quinn</code>, Core QUIC compliant.</p> 80 <p><em>Q. De Coninck</em></p> 81 <p><strong><a href="https://doi.org/10.23919/IFIPNetworking62109.2024.10619827">IFIP Networking (2024)</a></strong></p> 82 <p class="text-danger"><strong> See the related website <a href="https://core-quic.github.io">https://core-quic.github.io</a></strong></p> 83 <p> </p> 84 </div> 85 </div> 86 87 <div class="col-sm-6 clearfix"> 88 <div class="well"> 89 <pubtit>URLink: Using Names As Sole Internet Addresses to Tackle Scanning Attacks in IoT</pubtit> 90 <p><img src="/images/pubpic/urlink.jpg" class="img-responsive img-margin" width="33%" style="float: left" /></p> 91 <p>The Internet has never connected so many devices as of today, with an increasing number of constrained/IoT devices being publicly reachable over the public Internet, and therefore scannable through IP address enumeration. This work questions the current TCP/IP architecture of the current Internet and envisions a network whose names, such as URLs, are the only information the client needs to know to reach the wanted service.</p> 92 <p><em>Q. De Coninck, S. Kalantari, L. Sion, D. Hughes</em></p> 93 <p><strong><a href="https://dl.acm.org/doi/abs/10.1145/3628356.3630115">SensorsS&P (2023)</a></strong></p> 94 <p class="text-danger"><strong> </strong></p> 95 <p> </p> 96 </div> 97 </div> 98 99</div> 100 101<div class="row"> 102 103 <div class="col-sm-6 clearfix"> 104 <div class="well"> 105 <pubtit>xBGP: Faster Innovation in Routing Protocols</pubtit> 106 <p><img src="/images/pubpic/xbgp.png" class="img-responsive img-margin" width="33%" style="float: left" /></p> 107 <p>How can we quickly deploy new BGP features in a network made of devices from different vendors? xBGP addresses this issue by proposing a vendor-neutral API enabling network operators to dynamically inject plugins in all xBGP-compliant implementations. We made FRRouting and BIRD xBGP-compliant and implemented different use-cases such as valley-free path checks and prefix origin validation. We also proposed a framework verifing the behavior of the injected plugins.</p> 108 <p><em>T. Wirtgen, T. Rousseaux, Q. De Coninck, R. Bush, L. Vanbever, A. Legay, O. Bonaventure</em></p> 109 <p><strong><a href="https://www.usenix.org/conference/nsdi23/presentation/wirtgen">USENIX NSDI (2023)</a></strong></p> 110 <p class="text-danger"><strong>
110 You may find our previous ACM HotNets paper <a href="https://dl.acm.org/doi/10.1145/3422604.3425952">xBGP: When You Canât Wait for the IETF and Vendors</a></strong></p> 111 <p> See also <a href="https://pluginized-protocols.org/xbgp/">https://pluginized-protocols.org/xbgp/</a>.</p> 112 </div> 113 </div> 114 115 <div class="col-sm-6 clearfix"> 116 <div class="well"> 117 <pubtit>Pluginizing QUIC</pubtit> 118 <p><img src="/images/pubpic/pquic.png" class="img-responsive img-margin" width="33%" style="float: left" /></p> 119 <p>We revisited the extensibility model of transport protocols by using plugins. The dynamic insertion of bytecode inside a running implementation let the connection adapt to the application it serves. We managed to implement various QUIC extensions (montoring, Multipath, Datagram, Forward Erasure Correction) only with plugins.</p> 120 <p><em>Q. De Coninck, F. Michel, M. Piraux, F. Rochet, T. Given-Wilson, A. Legay, O. Pereira, O. Bonaventure</em></p> 121 <p><strong><a href="https://dl.acm.org/doi/10.1145/3341302.3342078">ACM SIGCOMM (2019)</a></strong></p> 122 <p class="text-danger"><strong> </strong></p> 123 <p> See also <a href="https://pquic.org">pquic.org</a>.</p> 124 </div> 125 </div> 126 127</div> 128 129<div class="row"> 130 131 <div class="col-sm-6 clearfix"> 132 <div class="well"> 133 <pubtit>Multipath QUIC: Design and Evaluation</pubtit> 134 <p><img src="/images/pubpic/mpquic.png" class="img-responsive img-margin" width="33%" style="float: left" /></p> 135 <p>We developed and implemented multipath extensions for the QUIC protocol. We then compared then with the state-of-the-art Multipath TCP in a wide range of network parameters.</p> 136 <p><em>Q. De Coninck, O. Bonaventure</em></p> 137 <p><strong><a href="https://dl.acm.org/doi/10.1145/3143361.3143370">ACM CoNEXT (2017)</a></strong></p> 138 <p class="text-danger"><strong> See also <a href="https://multipath-quic.org">multipath-quic.org</a>, the current <a href="https://datatracker.ietf.org/doc/draft-deconinck-quic-multipath/">IETF draft</a>, the <a href="https://doi.org/10.1109/MCOM.001.2000892">journal publication on Multiflow QUIC at IEEE Communications Magazine (2021)</a> and my <a href="https://dl.acm.org/doi/abs/10.1145/3561954.3561956">ACM SIGCOMM CCR paper</a> guiding Multipath QUIC towards the right design (also presented at <a href="https://conferences.sigcomm.org/sigcomm/2023/program.html#program-program">ACM SIGCOMMâ23</a> in the âBest of CCRâ session).</strong></p> 139 <p> You might also be interested in our <a href="https://itunes.apple.com/us/app/multipathtester/id1351286809?mt=8">MultipathTester iOS app</a> to evaluate Multipath QUIC in mobile conditions.</p> 140 </div> 141 </div> 142 143 <div class="col-sm-6 clearfix"> 144 <div class="well"> 145 <pubtit>A First Analysis of Multipath TCP on Smartphones</pubtit> 146 <p><img src="/images/pubpic/pam.png" class="img-responsive img-margin" width="33%" style="float: left" /></p> 147 <p>Our first analysis of Multipath TCP in the smartphone environment. Our results showed that applications can use multiple wireless networks without modifying them, but it also highlighted the need for an adaptation of Multipath TCP to this particular use case.</p> 148 <p><em>Q. De Coninck, M. Baerts, B. Hesmans, O. Bonaventure</em></p> 149 <p><strong><a href="https://link.springer.com/chapter/10.1007/978-3-319-30505-9_5">Passive and Active Measurement (2016)</a></strong></p> 150 <p class="text-danger"><strong> </strong></p> 151 <p> See also <a href="http://smartphone.multipath-tcp.org/">smartphone.multipath-tcp.org</a>.</p> 152 </div> 153 </div> 154 155</div> 156 157<div class="row"> 158 159 <div class="col-sm-6 clearfix"> 160 <div class="well"> 161 <pubtit>Tuning Multipath TCP for Interactive Applications on Smartphones</pubtit> 162 <p><img src="/images/pubpic/multimob.png" class="img-responsive img-margin" width="33%" style="float: left" /></p> 163 <p>We designed and implemented an adapted version of Multipath TCP on Android smartphones. We showed that our version keeps the cellular consumption low while keeping advantage of the multiple wireless networks when the device moves.</p> 164 <p><em>Q. De Coninck, O. Bonaventure</em></p> 165 <p><strong><a href="https://ieeexplore.ieee.org/abstract/document/8696520">IFIP Networking (2018)</a></strong></p> 166 <p class="text-danger"><strong> </strong></p> 167 <p> See also <a href="http://multipath-tcp.org/multimob">http://multipath-tcp.org/multimob</a>.</p> 168 </div> 169 </div> 170 171</div> 172 173<p> Â </p> 174 175<h2 id="full-list">Full List</h2> 176 177<p><a id="cy-effective-orcid-url" class="underline" href="https://orcid.org/0000-0001-6483-3157" target="orcid.widget" rel="me noopener noreferrer" style="vertical-align: top"> 178 <img src="https://orcid.org/sites/default/files/images/orcid_16x16.png" style="width: 1em; margin-inline-start: 0.5em" alt="ORCID iD icon" /> 179 https://orcid.org/0000-0001-6483-3157 180</a></p> 181 182<p>
182Our ORBI institutional library gives access to pre-print of my papers.</p> 183 184<iframe src="https://orbi.umons.ac.be/widget?query=author_authority%3A%28538074%29&sort_1=issued_dt%3Adesc&lang_code=en" title="Publication List" allowfullscreen="true" mozallowfullscreen="true" webkitallowfullscreen="true" width="100%" height="5000" frameborder="0"></iframe> 185 186</div> 187 188 </div> 189 </div> 190 191 <div id="footer" class="panel"> 192 <div class="panel-footer"> 193 <div class="container-fluid"> 194 <div class="row"> 195 <div class="col-sm-4"> 196 197 <p>© 2020 Quentin De Coninck. Site made with <a href="https://jekyllrb.com">Jekyll</a> based on the great open source template of the <a href="https://www.allanlab.org/">Allan Lab group</a>.</p> 198 199 200 <p> </p><p> 201 202 203 </div> 204 <div class="col-sm-4"> 205 Funding:<br /> 206 - <a href="https://staff.umons.ac.be/Quentin.DECONINCK/">Lecturer at UMONS</a> <br /> 207 </div> 208 <div class="col-sm-4"> 209 Contact:<br /> 210 Rue de Houdain 9<br /> 211 7000 Mons<br /> 212 Belgium<br /> 213 <br /> 214 E-mail: quentin.deconinck (at) umons (dot) ac (dot) be 215 <!-- (<a href="https://goo.gl/maps/4f3DwjAY2QT2">Maps</a>, <a href="https://uclouvain.be/en/research-institutes/icteam/ingi/about.html">Directions</a>) --> 216 </div> 217 </div> 218 </div> 219 </div> 220</div> 221
222<script src="https://ajax.googleapis.com/ajax/libs/jquery/1.11.3/jquery.min.js"></script>
vendor: 1 bytes, line 222
222
223<script src="/js/bootstrap.min.js"></script>
223 224 225 226 </body> 227 228</html>
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.