Changes between Version 8 and Version 9 of DhcpOptionDefinitionRequirements


Ignore:
Timestamp:
Oct 1, 2012, 10:56:43 AM (5 years ago)
Author:
marcin
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • DhcpOptionDefinitionRequirements

    v8 v9  
    3434    * Arrays of text strings or arrays of byte lists are not allowed (as the protocol includes no way to define the length of string or list unless the option length field is used).
    3535
    36 * It must be possible to specify which options are always sent to the client and which are sent only when requested.
    3736
    3837* It must be possible to define vendor-specific options.
     
    6665    * relays, clients and servers would need to use different .spec files (e.g. it is valid for the client to set fixed CLIENTID but it is not valid for the server).
    6766
    68 
     67* It must be possible to specify which options are always sent to the client and which are sent only when requested. This requirement seems to be beyond the scope of Option Definition so we might want to some other, more appropriate place.