@techreport{drew-dhc-v4-routed-prefix-00,
    number =    {draft-drew-dhc-v4-routed-prefix-00},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-drew-dhc-v4-routed-prefix/00/},
    author =    {Brendon Drew},
    title =     {{DHCPv4 Routed Prefix Option}},
    pagetotal = 18,
    year =      2026,
    month =     aug,
    day =       11,
    abstract =  {This document defines a DHCPv4 option that conveys one or more IPv4 prefixes that are routed toward a DHCP client independently of the client's on-link DHCP-assigned IPv4 address and default-router configuration. The option is intended for requesting routers whose upstream attachment address is distinct from IPv4 prefix space routed toward them. Examples include access networks in which a customer router receives a private-use address {[}RFC1918{]} or Shared Address Space {[}RFC6598{]} attachment address while one or more additional public or private IPv4 prefixes are routed toward that router. This document does not define how the upstream network establishes the route, does not require Network Address Translation (NAT), and does not specify how a client uses, assigns, translates, or delegates an advertised prefix after receipt.},
}