People, Roles & Contact Records

Haijun Li

Public policy participant

RIR policy participation Public policy entity

Haisheng Yu

Public policy participant

RIR policy participation Public policy entity

Saima Nisar

Public policy participant

RIR policy participation Public policy entity

Yazid Akanho

Public policy participant

RIR policy participation Public policy entity

Haitham El-Nakhal

Public policy participant

RIR policy participation Public policy entity

Gregoire Olaotan Ehoumi

Public policy participant

RIR policy participation Public policy entity

Izumi Okutani

Public policy participant

RIR policy participation Public policy entity

Sander Steffann

Sander Steffann is identified in cited public records as a person involved in decisions, litigation, governance, or operations relevant to internet infrastructure; the current role and affiliation remain subject to verification.

Sander Steffann Sander Steffann Executive Board Member Sander has been involved in the Internet since 1995, when he helped a friend start a small ISP. He was a founding board member of the Netherlands IPv6 Foundation, NLNOG and the Global NOG Alliance. Sander has been an involved member of the RIPE community since RIPE 49 in Manchester (2004). Sander was one of the RIPE Address Policy Working Grou Sander Steffann is identified in cited public records as a person involved in decisions, litigation, governance, or operations relevant to internet infrastructure; the current role and affiliation remain subject to verification.

LMAX USA

LMAX USA is a person lead in public internet-number registry records, helping readers trace links to ASNs, number resources, or network-operations records.

Public internet-number registry, RDAP, WHOIS, or routing evidence connects LMAX USA to internet-number resources; current affiliation, public responsibility, and responsibility boundary still require independent verification. LMAX USA is a person lead in public internet-number registry records, helping readers trace links to ASNs, number resources, or network-operations records.

Tawee Sribuddee

Tawee Sribuddee appears in public registry or source evidence as a person, role, or contact label; this record is retained as an open identity lead until current affiliation, identity type, and responsibility boundary are verified.

Tawee Sribuddee remains visible because public sources connect the label to internet-infrastructure records; the dossier still needs independent confirmation of whether it is a natural person, a role account, an organization label, or a current operational contact. Tawee Sribuddee appears in public registry or source evidence as a person, role, or contact label; this record is retained as an open identity lead until current affiliation, identity type, and responsibility boundary are verified.

Prasad Vadke

Prasad Vadke is a person lead in public internet-number registry records tied to AS137488, helping readers trace links to ASNs, number resources, or network-operations records.

India

Prasad Vadke profile intelligence explains the public role, affiliation context, sources of authority, geography, and decisions that make this person relevant to internet infrastructure markets. The summary links published evidence with company ties, governance exposure, career movement, technical authority, investment influence, and potential consequences for networks, registries, standards bodies, regional connectivity, and capital-allocation decisions.

Mirja Kühlewind

RFC 9312 and RFC 9308 name Mirja Kühlewind and Brian Trammell as co-authors of the IETF's written QUIC manageability and applicability analyses. Her official IETF profile, captured on 2 September 2026, describes her as a researcher at Ericsson Research focused on transport-protocol evolution, with earlier research in Internet measurement, transport design and TCP congestion control.

Mirja Kühlewind is tracked for the evidence boundary around QUIC's latency spin bit. An observed edge interval can estimate end-to-end RTT when both endpoints participate and traffic is continuous, but application or flow-control limitation, endpoint opt-out, path changes, reordering and filter choices can change or invalidate the result. Reliable assessment therefore preserves the raw signal, traffic conditions, path epoch, observation point and sample treatment instead of turning one visible bit into a universal network-latency verdict. RFC 9312 and RFC 9308 name Mirja Kühlewind and Brian Trammell as co-authors of the IETF's written QUIC manageability and applicability analyses. Her official IETF profile, captured on 2 September 2026, describes her as a researcher at Ericsson Research focused on transport-protocol evolution, with earlier research in Internet measurement, transport design and TCP congestion control.

Murray Kucherawy

RFC 6376 names Dave Crocker, Tony Hansen and Murray S. Kucherawy as the authors and editors of the DKIM specification. RFC 8601 names Kucherawy as author of the current Authentication-Results specification. At the 2 September 2026 capture, his official IETF Datatracker table listed 34 RFCs while the self-authored biography on the same page still said 33; the discrepancy is retained as a freshness gap.

Murray Kucherawy is tracked for the evidence boundary in DKIM signature scope. The optional l= tag can restrict the body hash to an initial canonicalized prefix, leaving a suffix outside DKIM validation even when verification succeeds. Reliable assessment therefore joins the selected signature, canonicalization, h= header coverage, l= body limit, observed key, verifier and display outcome instead of treating dkim=pass as a verdict on the whole visible message. RFC 6376 names Dave Crocker, Tony Hansen and Murray S. Kucherawy as the authors and editors of the DKIM specification. RFC 8601 names Kucherawy as author of the current Authentication-Results specification. At the 2 September 2026 capture, his official IETF Datatracker table listed 34 RFCs while the self-authored biography on the same page still said 33; the discrepancy is retained as a freshness gap.

John Klensin

The official IETF Datatracker profile identifies Dr. John C. Klensin and listed 60 RFCs at the 2 September 2026 capture. RFC 5321 names him as its author and defines the SMTP responsibility boundary examined here. These dated records establish standards authorship and participation, not control of a mail service, implementation or delivery result.

John Klensin is tracked for a precise SMTP evidence boundary. A positive reply to the final DATA terminator transfers responsibility for delivering or relaying an accepted message. That reply is not proof of mailbox placement, user reading, spam-policy release or downstream acceptance. The command-bound receipt, durable queue custody and later per-recipient outcomes must remain separate. The official IETF Datatracker profile identifies Dr. John C. Klensin and listed 60 RFCs at the 2 September 2026 capture. RFC 5321 names him as its author and defines the SMTP responsibility boundary examined here. These dated records establish standards authorship and participation, not control of a mail service, implementation or delivery result.

Tomek Mrugalski

RFC 9915, published as Internet Standard STD 102 in January 2026, names Tomek Mrugalski with Bernie Volz, Michael C. Richardson, Sheng Jiang and Timothy Winters. The IETF Datatracker records his broader DHCP RFC participation. A 2024 ISC staff profile identified him as Director of DHCP Engineering and described his Dibbler and Kea implementation work. These dated records establish standards and running-code experience, not sole authorship or authority over deployments.

Tomek Mrugalski is tracked for a precise DHCPv6 evidence boundary. A successful Confirm Reply says that the client's supplied addresses are appropriate for its present link. The responder ignores lease lifetime fields, and the client continues on its old clocks. Only a separate Renew or Rebind exchange can supply new lifetime evidence. Link fit, lease authority, uniqueness, reachability and routing therefore remain separate claims. RFC 9915, published as Internet Standard STD 102 in January 2026, names Tomek Mrugalski with Bernie Volz, Michael C. Richardson, Sheng Jiang and Timothy Winters. The IETF Datatracker records his broader DHCP RFC participation. A 2024 ISC staff profile identified him as Director of DHCP Engineering and described his Dibbler and Kea implementation work. These dated records establish standards and running-code experience, not sole authorship or authority over deployments.

Bob Briscoe

At the 2 September 2026 capture, Bob Briscoe's official site describes him as an independent research consultant on Internet communications. RFC 9332 lists him as an Independent author and editor with Koen De Schepper and Greg White; RFC 9331 also names him as editor and co-author, while RFC 9330 names him as editor among four authors. These records establish capture-dated work on congestion control, ECN and L4S, not sole invention, current market adoption or control of any operator deployment.

Bob Briscoe is tracked for a precise boundary between an end-to-end protocol identifier and local operational evidence. In RFC 9332, ECT(1) can identify L4S while an operator classifies the packet to the Classic queue; selected non-L4S traffic can enter the L queue without becoming L4S. Queue placement, coupled marking, overload and measured delay therefore require their own receipts before a low-latency claim is supported. At the 2 September 2026 capture, Bob Briscoe's official site describes him as an independent research consultant on Internet communications. RFC 9332 lists him as an Independent author and editor with Koen De Schepper and Greg White; RFC 9331 also names him as editor and co-author, while RFC 9330 names him as editor among four authors. These records establish capture-dated work on congestion control, ECN and L4S, not sole invention, current market adoption or control of any operator deployment.

Kent Watsen

At the 2 September 2026 capture, the official IETF Datatracker describes Kent Watsen as an industry expert in network management and security, lists current IETF chair and reviewer roles, and records RFC 8040, RFC 8342 and RFC 9984 among his RFCs. RFC 9984 names him with Alex Huang-Feng and Pierre Francois as authors of the Standards Track YANG groupings for UDP clients and servers. These records establish capture-dated participation and collective authorship, not sole invention, ownership of YANG or control of any implementation or deployment.

Kent Watsen is tracked for a precise boundary between portable network configuration and operational evidence. RFC 9984 defines reusable UDP client and server groupings but no protocol-accessible config-false nodes; a hostname still needs resolution, local port 0 still needs an operating-system choice, and a wildcard bind still needs a running listener receipt. The distinction matters because a clean intended configuration is not proof of an applied socket, traffic or application outcome. At the 2 September 2026 capture, the official IETF Datatracker describes Kent Watsen as an industry expert in network management and security, lists current IETF chair and reviewer roles, and records RFC 8040, RFC 8342 and RFC 9984 among his RFCs. RFC 9984 names him with Alex Huang-Feng and Pierre Francois as authors of the Standards Track YANG groupings for UDP clients and servers. These records establish capture-dated participation and collective authorship, not sole invention, ownership of YANG or control of any implementation or deployment.

David Schinazi

At the 2 September 2026 capture, the official IETF Datatracker describes David Schinazi as a senior staff software engineer and senior manager at Google working primarily on Privacy Proxy, MASQUE and OHTTP. RFC 9298 names him as author of the Standards Track specification Proxying UDP in HTTP; RFC 9297 and RFC 9484 record related collaborative authorship. These records establish capture-dated participation and authorship, not ownership of the MASQUE programme, control of deployments or a guarantee that any proxy service implements the standards correctly.

David Schinazi is tracked for writing a precise operational boundary into RFC 9298. Because UDP is connectionless, a successful CONNECT-UDP response proves that the proxy opened a socket toward the requested target and is willing to forward UDP payloads; it does not prove target reachability, delivery, application identity or application acceptance. This boundary is important for network evidence because authorization, DNS resolution, socket state, datagram movement and the inner protocol's outcome require different receipts. At the 2 September 2026 capture, the official IETF Datatracker describes David Schinazi as a senior staff software engineer and senior manager at Google working primarily on Privacy Proxy, MASQUE and OHTTP. RFC 9298 names him as author of the Standards Track specification Proxying UDP in HTTP; RFC 9297 and RFC 9484 record related collaborative authorship. These records establish capture-dated participation and authorship, not ownership of the MASQUE programme, control of deployments or a guarantee that any proxy service implements the standards correctly.

Christopher A. Wood

At the 1 September 2026 capture, the official IETF Datatracker described Christopher A. Wood as an engineer at Apple working on cryptographic engineering and associated 24 RFCs with his public identity. RFC 9458 names Wood and Martin Thomson as co-authors of the Standards Track Oblivious HTTP specification. These records establish capture-dated participation and authorship, not sole invention, control of deployments or a guarantee that any claimed OHTTP service follows the standard.

Christopher A. Wood is tracked for helping standardize a privacy architecture whose promise depends on splitting knowledge between independently operated roles. RFC 9458 lets a relay see the client's network origin without plaintext and lets a gateway see plaintext without the client's network origin. The boundary is operationally important because encryption alone does not supply unlinkability: role separation, state removal, fresh HPKE contexts, replay handling, authorization and resistance to traffic analysis remain distinct obligations. At the 1 September 2026 capture, the official IETF Datatracker described Christopher A. Wood as an engineer at Apple working on cryptographic engineering and associated 24 RFCs with his public identity. RFC 9458 names Wood and Martin Thomson as co-authors of the Standards Track Oblivious HTTP specification. These records establish capture-dated participation and authorship, not sole invention, control of deployments or a guarantee that any claimed OHTTP service follows the standard.

Martin Thomson

At the 1 September 2026 capture, the official IETF Datatracker described Martin Thomson as an engineer at Mozilla, listed 45 RFCs under his public identity and showed current roles in HPKE, SPICE, IETF-W3C, W3C liaison and review groups. RFC 9850 names Thomson with Yaroslav Rosomakho and Hannes Tschofenig as authors of the Informational SSLKEYLOGFILE specification. These records establish capture-dated participation, not sole invention, control of implementations or approval of production key logging.

Martin Thomson is tracked for helping standardize a diagnostic format whose technical usefulness depends on an unusually sharp security boundary. RFC 9850 lets tools use logged TLS secrets with captured records, while warning that the material destroys core TLS guarantees and must not be used in production. The format is operationally important because a decryption capability is often mistaken for an audit receipt even though the three-field record does not itself establish provenance, authorization, endpoint identity or chain of custody. At the 1 September 2026 capture, the official IETF Datatracker described Martin Thomson as an engineer at Mozilla, listed 45 RFCs under his public identity and showed current roles in HPKE, SPICE, IETF-W3C, W3C liaison and review groups. RFC 9850 names Thomson with Yaroslav Rosomakho and Hannes Tschofenig as authors of the Informational SSLKEYLOGFILE specification. These records establish capture-dated participation, not sole invention, control of implementations or approval of production key logging.

Todd Herr

At the 1 September 2026 capture, RFC 9989 named Todd M. Herr as co-editor with John Levine of the Standards Track DMARC specification published in May 2026. The RFC listed Herr with Valimail, while the official IETF Datatracker linked the same public identity to RFC 9989 and an ART Area Review Team reviewer role. These records establish a capture-dated standards contribution, not sole invention of DMARC, authority over receiver policy or verification of every deployment.

Todd Herr is tracked for co-editing a specification that makes the limits of email authentication unusually explicit. RFC 9989 defines DMARC pass as authorised use of the RFC5322.From domain through an aligned SPF or DKIM identifier, while withholding claims about human identity, content and safe delivery. It also keeps final handling with the receiver and describes published failure policies as requested preferences. That separation is operationally important because legitimate indirect mail can fail and malicious authorised mail can pass. At the 1 September 2026 capture, RFC 9989 named Todd M. Herr as co-editor with John Levine of the Standards Track DMARC specification published in May 2026. The RFC listed Herr with Valimail, while the official IETF Datatracker linked the same public identity to RFC 9989 and an ART Area Review Team reviewer role. These records establish a capture-dated standards contribution, not sole invention of DMARC, authority over receiver policy or verification of every deployment.

Adrian Farrel

At the 1 September 2026 capture, RFC 7942 named Adrian Farrel as co-author with Yaron Sheffer of BCP 205 on Implementation Status sections. The official IETF Datatracker listed the same public identity in current chair, editor, reviewer and technical-advisor roles and linked 82 RFCs. These records establish a long standards contribution and capture-dated roles, not sole authority over IETF consensus, implementation claims or network deployments.

Adrian Farrel is tracked for co-authoring a process that gives running-code evidence a deliberately temporary place in Internet-Drafts. RFC 7942 lets implementers disclose version, maturity, coverage, licensing, testing and interoperability while a specification can still change, but marks those reports as unverified and recommends removing them before RFC publication. This makes implementation evidence useful without turning a perishable self-report into permanent endorsement or adoption proof. At the 1 September 2026 capture, RFC 7942 named Adrian Farrel as co-author with Yaron Sheffer of BCP 205 on Implementation Status sections. The official IETF Datatracker listed the same public identity in current chair, editor, reviewer and technical-advisor roles and linked 82 RFCs. These records establish a long standards contribution and capture-dated roles, not sole authority over IETF consensus, implementation claims or network deployments.

Qin Wu

At the 1 September 2026 capture, RFC 9890 named Qin Wu of Huawei as a co-author with Andy Bierman and Mohamed Boucadair of the standards-track update to YANG module-name registration. The official IETF Datatracker records a long body of RFC work under the same public identity, and the IETF supplies a public portrait. These sources establish a standards contributor and a dated affiliation, not control of IETF consensus, IANA operations or any network deployment.

Qin Wu is tracked for work that corrected a mismatch between the wording of RFC 6020 and established IANA practice. RFC 9890 keeps initial YANG module and submodule names unique while requiring revisions to retain the initial name and, for modules, the initial XML namespace. That distinction makes the first assignment and later identity continuity separately auditable; registration does not prove implementation, interoperability or operational quality. At the 1 September 2026 capture, RFC 9890 named Qin Wu of Huawei as a co-author with Andy Bierman and Mohamed Boucadair of the standards-track update to YANG module-name registration. The official IETF Datatracker records a long body of RFC work under the same public identity, and the IETF supplies a public portrait. These sources establish a standards contributor and a dated affiliation, not control of IETF consensus, IANA operations or any network deployment.

Daniel Eggert

At the 1 September 2026 capture, RFC 10022 named Daniel Eggert of Apple Inc. as editor of the IMAP UIDBATCHES Extension. His official IETF Datatracker profile listed RFC 10022 and RFC 9979. A dated Swift.org author card identified him as a member of the Apple team working on Mail for iOS and macOS and linked his public GitHub identity. These sources establish a standards contributor and dated professional context, not control of IETF consensus or any mail-service deployment.

Daniel Eggert is tracked for work that lets IMAP clients predetermine UID ranges near a requested message count without turning those ranges into stable mailbox pages. RFC 10022 preserves implementation flexibility, mailbox-change handling and resource limits while leaving client scheduling, consistency response and operational outcomes to the systems that run them. At the 1 September 2026 capture, RFC 10022 named Daniel Eggert of Apple Inc. as editor of the IMAP UIDBATCHES Extension. His official IETF Datatracker profile listed RFC 10022 and RFC 9979. A dated Swift.org author card identified him as a member of the Apple team working on Mail for iOS and macOS and linked his public GitHub identity. These sources establish a standards contributor and dated professional context, not control of IETF consensus or any mail-service deployment.