rfc.dk

M. Thomson

45 RFCs, 2008-2026 · working groups: geopriv, httpbis, quic, tls, webpush, rtcweb

RFCTitleStatusDate
10036Incremental Forwarding of HTTP MessagesK. Oku, T. Pauly, M. ThomsonProposed StandardAugust 2026
9998Report from the IAB/W3C Workshop on Age-Based Restrictions on Content AccessM. Nottingham, M. ThomsonInformationalJune 2026
9896SVG in RFCsA. Rossi, N. Brownlee, J. Mahoney, M. ThomsonInformationalJanuary 2026
9850The SSLKEYLOGFILE Format for TLSM. Thomson, Y. Rosomakho, H. TschofenigInformationalJuly 2026
9458Oblivious HTTPM. Thomson, C. A. WoodProposed StandardJanuary 2024
9413Maintaining Robust ProtocolsM. Thomson, D. SchinaziInformationalJune 2023
9292Binary Representation of HTTP MessagesM. Thomson, C. A. WoodProposed StandardAugust 2022
9287Greasing the QUIC BitM. ThomsonProposed StandardAugust 2022
9170Long-Term Viability of Protocol Extension MechanismsM. Thomson, T. PaulyInformationalDecember 2021
9113HTTP/2M. Thomson, Ed., C. Benfield, Ed.Proposed StandardJune 2022
9001Using TLS to Secure QUICM. Thomson, Ed., S. Turner, Ed.Proposed StandardMay 2021
9000QUIC: A UDP-Based Multiplexed and Secure TransportJ. Iyengar, Ed., M. Thomson, Ed.Proposed StandardMay 2021
8999Version-Independent Properties of QUICM. ThomsonProposed StandardMay 2021
8874Working Group GitHub Usage GuidanceM. Thomson, B. StarkInformationalAugust 2020
8844Unknown Key-Share Attacks on Uses of TLS with the Session Description Protocol (SDP)M. Thomson, E. RescorlaProposed StandardJanuary 2021
8833Application-Layer Protocol Negotiation (ALPN) for WebRTCM. ThomsonProposed StandardJanuary 2021
8752Report from the IAB Workshop on Exploring Synergy between Content Aggregation and the Publisher Ecosystem (ESCAPE)M. Thomson, M. NottinghamInformationalMarch 2020
8470Using Early Data in HTTPM. Thomson, M. Nottingham, W. TarreauProposed StandardSeptember 2018
8449Record Size Limit Extension for TLSM. ThomsonProposed StandardAugust 2018
8448Example Handshake Traces for TLS 1.3M. ThomsonInformationalJanuary 2019
8292Voluntary Application Server Identification (VAPID) for Web PushM. Thomson, P. BeverlooProposed StandardNovember 2017
8291Message Encryption for Web PushM. ThomsonProposed StandardNovember 2017
8188Encrypted Content-Encoding for HTTPM. ThomsonProposed StandardJune 2017
8164Opportunistic Security for HTTP/2M. Nottingham, M. ThomsonHistoricMay 2017
8030Generic Event Delivery Using HTTP PushM. Thomson, E. Damaggio, B. Raymor, Ed.Proposed StandardDecember 2016
7675Session Traversal Utilities for NAT (STUN) Usage for Consent FreshnessM. Perumal, D. Wing, R. Ravindranath, T. Reddy, M. ThomsonProposed StandardOctober 2015
7639The ALPN HTTP Header FieldA. Hutton, J. Uberti, M. ThomsonProposed StandardAugust 2015
7568Deprecating Secure Sockets Layer Version 3.0R. Barnes, M. Thomson, A. Pironti, A. LangleyProposed StandardJune 2015
7540Hypertext Transfer Protocol Version 2 (HTTP/2)M. Belshe, R. Peon, M. Thomson, Ed. · obsoleted by RFC 9113Proposed StandardMay 2015
7459Representation of Uncertainty and Confidence in the Presence Information Data Format Location Object (PIDF-LO)M. Thomson, J. WinterbottomProposed StandardFebruary 2015
7216Location Information Server (LIS) Discovery Using IP Addresses and Reverse DNSM. Thomson, R. BellisProposed StandardApril 2014
7199Location Configuration Extensions for Policy ManagementR. Barnes, M. Thomson, J. Winterbottom, H. TschofenigProposed StandardApril 2014
7105Using Device-Provided Location-Related Measurements in Location Configuration ProtocolsM. Thomson, J. WinterbottomProposed StandardJanuary 2014
7035Relative Location RepresentationM. Thomson, B. Rosen, D. Stanley, G. Bajko, A. ThomsonProposed StandardOctober 2013
6848Specifying Civic Address Extensions in the Presence Information Data Format Location Object (PIDF-LO)J. Winterbottom, M. Thomson, R. Barnes, B. Rosen, R. GeorgeProposed StandardJanuary 2013
6772Geolocation Policy: A Document Format for Expressing Privacy Preferences for Location InformationH. Schulzrinne, Ed., H. Tschofenig, Ed., J. Cuellar, J. Polk, J. Morris, M. ThomsonProposed StandardJanuary 2013
6753A Location Dereference Protocol Using HTTP-Enabled Location Delivery (HELD)J. Winterbottom, H. Tschofenig, H. Schulzrinne, M. ThomsonProposed StandardOctober 2012
6225Dynamic Host Configuration Protocol Options for Coordinate-Based Location Configuration InformationJ. Polk, M. Linsner, M. Thomson, B. Aboba, Ed.Proposed StandardJuly 2011
6155Use of Device Identity in HTTP-Enabled Location Delivery (HELD)J. Winterbottom, M. Thomson, H. Tschofenig, R. BarnesProposed StandardMarch 2011
5986Discovering the Local Location Information Server (LIS)M. Thomson, J. WinterbottomProposed StandardSeptember 2010
5964Specifying Holes in Location-to-Service Translation (LoST) Service BoundariesJ. Winterbottom, M. ThomsonProposed StandardAugust 2010
5962Dynamic Extensions to the Presence Information Data Format Location Object (PIDF-LO)H. Schulzrinne, V. Singh, H. Tschofenig, M. ThomsonProposed StandardSeptember 2010
5573Asynchronous Channels for the Blocks Extensible Exchange Protocol (BEEP)M. ThomsonExperimentalJune 2009
5491GEOPRIV Presence Information Data Format Location Object (PIDF-LO) Usage Clarification, Considerations, and RecommendationsJ. Winterbottom, M. Thomson, H. TschofenigProposed StandardMarch 2009
5139Revised Civic Location Format for Presence Information Data Format Location Object (PIDF-LO)M. Thomson, J. WinterbottomProposed StandardFebruary 2008