[dhcwg] FW: New Version Notification for draft-tojens-dhcp-o ption-concat-considerations-01.txt

Hello dhc,

Milan and I updated our draft to make it clearer that this is intended to update an old RFC to reflect the current realities and help implementors understand the inconsistencies between the literal text and common practice twenty+ years later, rather than add novel functionality to DHCP. Let us know what you think! 

Thanks,
Tommy

-----Original Message-----
From: [email protected] <[email protected]> 
Sent: Monday, March 3, 2025 3:36 PM
To: Milan Justel <[email protected]>; Tommy Jensen <[email protected]>
Subject: New Version Notification for draft-tojens-dhcp-option-concat-considerations-01.txt

A new version of Internet-Draft
draft-tojens-dhcp-option-concat-considerations-01.txt has been successfully submitted by Tommy Jensen and posted to the IETF repository.

Name:     draft-tojens-dhcp-option-concat-considerations
Revision: 01
Title:    DHCP Option Concatenation Considerations
Date:     2025-03-03
Group:    Individual Submission
Pages:    7
URL:      https://www.ietf.org/archive/id/draft-tojens-dhcp-option-concat-considerations-01.txt
Status:   https://datatracker.ietf.org/doc/draft-tojens-dhcp-option-concat-considerations/
HTML:     https://www.ietf.org/archive/id/draft-tojens-dhcp-option-concat-considerations-01.html
HTMLized: https://datatracker.ietf.org/doc/html/draft-tojens-dhcp-option-concat-considerations
Diff:     https://author-tools.ietf.org/iddiff?url2=draft-tojens-dhcp-option-concat-considerations-01

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.



The IETF Secretariat




_______________________________________________
dhcwg mailing list -- [email protected]
To unsubscribe send an email to [email protected]