<?xml version="1.0" encoding="UTF-8"?><xml><records><record><source-app name="Biblio" version="7.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">David Naylor</style></author><author><style face="normal" font="default" size="100%">Kyle Schomp</style></author><author><style face="normal" font="default" size="100%">Matteo Varvello</style></author><author><style face="normal" font="default" size="100%">Ilias Leontiadis</style></author><author><style face="normal" font="default" size="100%">Jeremy Blackburn</style></author><author><style face="normal" font="default" size="100%">Diego Lopez</style></author><author><style face="normal" font="default" size="100%">Konstantina Papagiannaki</style></author><author><style face="normal" font="default" size="100%">Pablo Rodriguez</style></author><author><style face="normal" font="default" size="100%">Peter Steenkiste</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">multi-context TLS (mcTLS): Enabling Secure In-Network Functionality in TLS</style></title><secondary-title><style face="normal" font="default" size="100%">2015 ACM SIGCOMM Conference (SIGCOMM ’15)</style></secondary-title></titles><dates><year><style  face="normal" font="default" size="100%">2015</style></year></dates><publisher><style face="normal" font="default" size="100%">ACM</style></publisher><pub-location><style face="normal" font="default" size="100%">London</style></pub-location><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">&lt;p&gt;Transport Layer Security (TLS), is the de facto protocol supporting secure HTTP (HTTPS), and is being discussed as the default transport protocol for HTTP2.0. It has seen wide adoption and is currently carrying a significant fraction of the overall HTTP traffic (Facebook, Google and Twitter use it by default). However, TLS makes the fundamental assumption that all functionality resides solely at the endpoints, and is thus unable to utilize the many in-network services that optimize network resource usage, improve user experience, and protect clients and servers from security threats. Re-introducing such in-network functionality into secure TLS sessions today is done through hacks, in many cases weakening overall security.&lt;/p&gt;&lt;p&gt;In this paper we introduce multi-context TLS (mcTLS) which enhances TLS by allowing middleboxes to be fully supported participants in TLS sessions. mcTLS breaks the &quot;all-or-nothing&quot; security model by allowing endpoints and content providers to explicitly introduce middleboxes in secure end-to-end sessions, while deciding whether they should have read or write access, and to which specific parts of the content. mcTLS enables transparency and control for both clients and servers.&lt;/p&gt;&lt;p&gt;We evaluate a prototype mcTLS implementation in both controlled and &quot;live&quot; experiments, showing that the benefits offered have minimal overhead.More importantly, we show that mcTLS can be incrementally deployed and requires small changes to clients, servers, and middleboxes, for a large number of use cases.&lt;/p&gt;</style></abstract></record></records></xml>