Enke Chen

A BGP router can change its forwarding choice even when the challenger is no better by policy, path length, origin, MED, session type or interior cost. RFC 5004 asks a narrower question: if the only remaining reason to move is the remote speaker's lower BGP Identifier, why move at all? Enke Chen's proposal turns that late tie into a rule of continuity—and makes the history of arrival an operational fact that must be observed rather than mistaken for quality.

A BGP session can disappear while the forwarding state learned through it still works. RFC 9494 permits some of that old state to remain far longer than ordinary graceful restart—but it does not call the state current. It marks the route, lowers its preference, limits where it may travel and gives the receiving operator control over its lifetime. Enke Chen's documented role in this mechanism is a study in continuity made honest by degradation.

Enke Chen's attributed IETF record connects three practical questions in inter-domain routing: how a BGP speaker contains malformed UPDATE messages, how it distinguishes multiple paths for one prefix, and why redistribution needs deterministic decision boundaries. Read together, the records show that routing continuity depends on preserving identity, scope, provenance, and observable failure state rather than treating the control plane as a single unquestionable answer.