Skip to main content

Martin Duke

Martin Duke became Transport Area co-director in 2020. He is a heavily involved individual contributor in the QUIC and TAPS Working Groups, and participates actively in TCP-related working groups. At Google in Seattle, he is working on QUIC and TCP-related projects. Before that, he spent 8 years at F5 both managing and developing their TCP, QUIC, and HTTP implementations. He also was a researcher on link-layer, routing, and transport-layer protocols with Boeing. A native of Maryland and 20+ year resident of Washington State, Martin holds degrees from the University of Washington and MIT.

Roles

Role Group Email
Area Director Transport Area (tsv) martin.h.duke@gmail.com
Area Director Multiplexed Application Substrate over QUIC Encryption (masque) martin.h.duke@gmail.com
Area Director IP Performance Measurement (ippm) martin.h.duke@gmail.com
Area Director Transport Area Working Group (tsvwg) martin.h.duke@gmail.com
Area Director Application-Layer Traffic Optimization (alto) martin.h.duke@gmail.com
Area Director TCP Maintenance and Minor Extensions (tcpm) martin.h.duke@gmail.com
Area Director Transport Area Open Meeting (tsvarea) martin.h.duke@gmail.com
Area Director Internet Engineering Steering Group (iesg) martin.h.duke@gmail.com
Chair Transport Area Review Team (tsvart) martin.h.duke@gmail.com
Chair Transport Area Open Meeting (tsvarea) martin.h.duke@gmail.com
Delegate IP Performance Measurement (ippm) martin.h.duke@gmail.com
Liaison Member Nominating Committee 2022/2023 (nomcom2022) martin.h.duke@gmail.com
Reviewer Transport Area Review Team (tsvart) martin.h.duke@gmail.com
Secretary Transport Area Review Team (tsvart) martin.h.duke@gmail.com

External Resources

Name Value
GitHub Username martinduke

RFCs (3)

RFC Date Title Cited by
RFC 4614 Sep 2006 A Roadmap for Transmission Control Protocol (TCP) Specification Documents 10 RFCs
RFC 7414 Feb 2015 A Roadmap for Transmission Control Protocol (TCP) Specification Documents 12 RFCs
RFC 9137 Oct 2021 Considerations for Cancellation of IETF Meetings

Active Drafts (7)

Expired Drafts (18)

(Excluding replaced drafts.)

Draft Activity