Changes between Version 25 and Version 26 of ClientClassificationRequirements


Ignore:
Timestamp:
Jan 19, 2016, 6:50:41 PM (22 months ago)
Author:
tomek
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ClientClassificationRequirements

    v25 v26  
    132132With client classification implemented, there will be multiple places where options could be defined. Here is the order in which options will be assigned. Each "level" takes precedence over previous ones.
    133133
    134 1. global
    135 2. global class
    136 3. subnet
    137 4. subnet class (this scope will likely not be implemented for 1.0)
    138 5. host (see #3571, #3572, #3573)
     1341. global (implemented in prehistory, Kea 0.8 or earlier)
     1352. global class (implemented in phase 1/Kea 1.0)
     1363. subnet (implemented in phehistory, Kea 0.8 or earlier)
     1374. subnet class (to be implemented in Kea 1.1)
     1385. host (see #3571, #3572, #3573) (planned for Kea 1.1)
    139139
    140140For example, let's consider a case that the DNS server option is specified on the global level as 1.1.1.1, on subnet level as 2.2.2.2 and third time for a class FOO as 3.3.3.3. The client connected to the subnet and belonging to class FOO will get 3.3.3.3. Another client connected to the same subnet that does not belong to the foo class, will get 2.2.2.2.