Changes between Version 3 and Version 4 of DhcpPoolLeaseRequirements


Ignore:
Timestamp:
Sep 3, 2012, 11:27:21 AM (5 years ago)
Author:
stephen
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • DhcpPoolLeaseRequirements

    v3 v4  
    3434 * H2. It MUST be possible to provision different options for selected hosts. It MUST be possible to specify this on per-host basis.
    3535
    36 DNS Update requirements:
    37  * D1. It MUST be possible to define DNS Update parameters:
    38    * D1.1 server address (v4 or v6),
    39    * D1.2 protocol (TCP, UDP or both will fallout),
    40    * D1.3 timeout
    41  * D2. It MUST be possible to sign updates.
    42    * D2.1 MD5 in TSIG MUST be supported.
    43  * D3. It MUST be possible to specify secret shared-key.
    44  * D4. It MUST be possible to keep DNS update information for existing leases, even when the DNS configuration changes. This is useful for cleaning up old leases.
    45  * D5. It MUST be possible to specify different server-key pairs for different pools.
    46 
     36DNS Update requirements:[[BR]]
     37 * See DhcpDdnsRequirements
    4738Scalability requirements:
    4839 * S1. MUST scale to many cores (including many worker threads or processes)