David M Meyer People Intelligence Profile

Confidence

5

Public role: David M Meyer 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.
Information type: David M Meyer 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.

David M Meyer public affiliation evidence
RDAP public registry record links David M Meyer to public internet-number, routing, or registry context.
Public record
Public registry record
Public numbering evidence links David M Meyer to AS10876.
RIR member directory record
WHOIS public registry record names MAOZ-ASN; this observation does not by itself establish a relationship to David M Meyer.
RIR member directory
RIR member directory record
RIR member directory record names MAOZ-ASN; this observation does not by itself establish a relationship to David M Meyer.
RIR member directory
gnd_source_gap_consumer
profile enrichment source repair task execution
Public record

Last updated: 2026-07-08

Contact:techHigh confidence· 1 record

2

David Meyer and the Address That Had to Ask Where It Lived
LISP lets an endpoint keep one identifier while its network attachment is described separately. That does not make location disappear. It moves forwarding into a chain of registered, resolved, cached, selected and reachable EID-to-RLOC state—and turns each link in that chain into a separate claim that operators must prove.
Primary articlePublished 2026-08-29
David Meyer and the Uneasy Work of Making Network Control Public
David M Meyer's public record crosses four ways of coordinating a network that no participant fully controls: exposing interdomain routing through RouteViews, expressing routing policy through RPSL, serving standards and operator communities, and helping to lead OpenDaylight's early attempt at shared control software. The record is valuable precisely because it supports those connections without turning collective infrastructure into one person's achievement.
Primary articlePublished 2026-07-17