@techreport{tojens-dhcp-option-concat-considerations-01,
    number =    {draft-tojens-dhcp-option-concat-considerations-01},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-tojens-dhcp-option-concat-considerations/01/},
    author =    {Tommy Jensen and Milan Justel},
    title =     {{DHCP Option Concatenation Considerations}},
    pagetotal = 7,
    year =      2025,
    month =     mar,
    day =       3,
    abstract =  {DHCP has a length limit of 255 on individual options because of its one-byte length field for options. To accommodate longer options, splitting option data across multiple instances of the same Option Type is defined by RFC 3396. However, this mechanism was defined to require support for all option types. This has led to real-world implementations in the years since the RFC was published to deviate from these requirements to avoid breaking basic functionality. This document updates RFC 3396 to be more flexible regarding when DHCP agents are required to concatenate options to reflect deployement experiences.},
}