Summary

  • RFC 3442 gave DHCPv4 option 121 a way to deliver routes with explicit prefix lengths, fixing the classful assumption in the older static-route option.
  • A supporting client had to install those routes and prefer them over the Router and option 33 values when they arrived together; the RFC warned that a wrong next hop could misdirect traffic.

An address lease usually sounds like an assignment: the network tells a host which address it may use and how long it may keep it. But a host also needs to know where to send packets that are not local. RFC 3442 made that second decision part of DHCP's configuration conversation. Its classless static-route option could deliver a destination prefix and the router address for reaching it.

The change answered a mismatch. DHCP option 33, defined in RFC 2132, described static routes without a separate mask for each destination. That made sense when the network boundary could be inferred from the address class. Classless routing had displaced that assumption: 10.0.0.0/8 and 10.0.0.0/24 are different destinations, even though their network numbers begin alike. A client needs the prefix length to know which bits define the route.

Option 121 encoded that scope compactly. A destination descriptor began with a prefix width and carried only the significant address octets; a four-byte router address followed. The client reconstructed the destination and zeroed the bits outside the mask before installing it. RFC 3442 did not make DHCP a routing protocol or distribute an Internet routing table. It let an administrator use a server already providing host configuration to install selected static routes on clients.

That moved a consequential choice across an administrative boundary. The route table still lived on the host, and the client still applied its own processing rules. Yet a route could now originate in DHCP server configuration rather than a person editing that device locally. For a client that supported option 121, the RFC required the routes to be installed, subject to a local-subnet exception. If the new option appeared with the older Router option or option 33, the client had to ignore those older values. The order in which a client requested options mattered too: option 121 had to precede Router and option 33 in its Parameter Request List.

Compatibility was part of the design. Clients that did not implement option 121 had to ignore it. RFC 3442 therefore recommended that administrators also send the Router option, duplicating default-router information for older clients. That was a transition strategy, not proof of how many devices supported the new option or how quickly networks adopted it. A specification can define a safe precedence rule; it cannot make every client implement the rule.

The boundary also had a security consequence. RFC 3442 explicitly warned that an incorrect router address could cause denial of service or steer traffic through a snooper. The risk was not unique to option 121; older route and router options could also point at the wrong next hop. The option itself did not prove that a proposed route was authorized, correct or safe. Message authentication, where used, was a separate DHCP mechanism and would not by itself establish that the route choice was wise.

Even packet size shaped the hand-off. A large route list could exceed the traditional DHCP message size, so RFC 3442 discussed larger-message negotiation and required support for long-option concatenation. On shared links with multiple IP subnets, it also defined a special use of next hop 0.0.0.0 to mark a directly reachable local subnet; clients without the needed stack behavior had to ignore that entry.

RFC 3442's historical move was modest but revealing: once a network's routing became classless, address configuration needed a way to express route scope too. The lease became a possible vehicle for local forwarding policy. The client remained the installation point, the server administrator became a route-setting actor, and the next-hop decision carried consequences beyond address assignment.

Sources