Álvaro Retana

An OSPF adjacency can remain full, its topology edge can continue to influence SPF, and packets can still cross the link even after the link's numbered prefix has vanished from remote routing tables. RFC 6860 makes that separation an operational tool. For Álvaro Retana, one of its three co-authors, it is also a precise lesson in evidence: a hidden prefix is a forwarding-state claim, not a claim that the link, address or risk has ceased to exist.

Alvaro Retana's public standards record connects three practical routing problems to three dated technical documents: conserving IPv4 addresses on point-to-point links, keeping an OSPF router reachable while removing it from transit service, and comparing independent BGP implementations before treating protocol text as operational evidence.

Alvaro Retana's name appears with Michael Behringer, Russ White and Geoff Huston on a document that refuses to certify a network as “simple.” RFC 7980 instead exposes five trades: less state can lengthen paths, less local variation can enlarge a shared failure surface, and faster signals can outrun calculation. Its discipline is not to count what disappeared, but to identify who received the cost.

The proposal sounds clean: aggregate more routes, move policy into one controller, reduce the number of configuration lines and make every failure detector faster. Each move lowers a visible count. Yet traffic may take a longer path, the controller becomes a shared dependency, five exceptional interfaces become harder to understand than a thousand standard ones, and rapid signals can drive the control plane faster than it can calculate. The complexity did not vanish. It changed address.