Mike McBride People Intelligence Profile

Confidence

5

Public role: The IETF Datatracker profile captured on 31 August 2026 lists Mike McBride as PIM chair, an MBONED and ANIMA delegate, a Routing Area Directorate reviewer and an author of nine RFCs. RFC 10028 identifies him with Futurewei and names him as one of three authors.
Information type: Mike McBride is tracked for collective standards work that separated previously overlapping dynamic IPv6 multicast group-ID ranges. RFC 10028, written with Nate Karstens and Dino Farinacci, narrows MADCAP, assigns distinct SSM, Private Use, Experimental Use and Solicited-Node ranges, and creates an IANA registry for future Standards Action. The profile preserves the boundary between a registry allocation and running-network evidence: it does not infer SSM availability, MADCAP deployment, multicast reachability, source validity, listener authorization, routing policy or service outcome. It is intentionally separate from the unresolved same-name GE POWER SYSTEMS CONTRACTUAL contact row.

RFC 10028 — Updates to Dynamic IPv6 Multicast Address Group IDs
Names McBride of Futurewei as one of three authors and defines the new six-part Dynamic Multicast Group IDs registry.
Official IETF Standards Track RFC
IETF Datatracker — Mike McBride
Supplies the public portrait and the dated PIM, MBONED, ANIMA, Routing Directorate and RFC record captured on 31 August 2026.
Official IETF contributor record
IANA — IPv6 Multicast Address Space
Publishes the Dynamic Multicast Group IDs ranges and registration procedure created by RFC 10028.
Official IANA protocol registry
RFC 10019 — Zeroconf Multicast Address Allocation Problem Statement and Requirements
Records McBride among the authors of the related collision and zero-configuration problem statement.
Official IETF Informational RFC
ONF — Why I Network: Mike McBride
Provides dated first-person career context and a historical public headshot for the networking professional.
Official Open Networking Foundation historical profile

Last updated: 2026-08-31

2

RFC 10028 and the Institutional Boundary of IPv6 Multicast
RFC 10028 did more than tidy an IPv6 registry. It shows how an IETF decision becomes operational authority: a standards document changes the allocation map, and IANA gives that decision a durable administrative surface. The result is a cleaner boundary between multicast uses—but not proof that every implementation, configuration or traffic path adopted it.
Primary articlePublished 2026-09-09
Mike McBride and the Multicast Registry That Prevented One Kind of Collision
Two IPv6 multicast allocation methods had been told to draw identifiers from the same box. RFC 10028 divided the box before a future host protocol and an old server protocol could make the same choice—and left operators with the harder job of proving that their networks had noticed.
Primary articlePublished 2026-08-31

2

RFC 10028 and the Institutional Boundary of IPv6 MulticastNot yet assessed
Mike McBride and the Multicast Registry That Prevented One Kind of CollisionNot yet assessed