Yakov Rekhter

Yakov Rekhter's public standards record shows how inter-domain routing and address scope became manageable through explicit permissions, visible protocol state, bounded uniqueness, and honest accounting for the cost of later change.

Yakov Rekhter is the only named author common to two different standards teams at the centre of BGP/MPLS VPN routing. With Srihari R. Sangli and Dan Tappan, he co-authored RFC 4360’s reusable Extended Communities carrier. With Eric C. Rosen, he co-authored RFC 4364’s use of that carrier to move routes between VPNs. The hand-off matters: a Route Distinguisher gives overlapping IPv4 routes separate identities, while Route Targets and VRFs govern membership. Rekhter’s documented place across both author groups makes the separation visible without turning collaborative standards into personal property.

Two customers can use the same IPv4 prefix and still need a provider backbone to carry both routes without confusing them. The obvious move is to put another number in front. The dangerous move is to imagine that this new number also says who owns the route, who may receive it or what the VPN means. RFC 4364 refuses that shortcut. Its Route Distinguisher makes identical addresses distinct; Route Targets and VRF policy decide membership. Yakov Rekhter’s documented work on that separation reveals a wider rule of infrastructure: uniqueness can be thin precisely because permission remains somewhere else.

The most revealing sentence in BGP's base specification is not about a packet format. It says that whether a route enters the forwarding table is a local policy decision and is not specified by the document. That sentence marks a durable division of labour. Networks need a common language to exchange reachability, but they do not need a central planner to choose every path. Yakov Rekhter's standards record helps show both the power of that boundary and the danger of mistaking local choice for verified truth.