BIND 10 #3203: Minimalistic client classification is needed for docsis

BIND 10 Development do-not-reply at isc.org
Mon Dec 30 18:20:22 UTC 2013


#3203: Minimalistic client classification is needed for docsis
-------------------------------------+-------------------------------------
            Reporter:  tomek         |                        Owner:  tomek
                Type:  enhancement   |                       Status:
            Priority:  high          |  assigned
           Component:  dhcp6         |                    Milestone:  DHCP-
            Keywords:                |  Kea1.0-alpha
           Sensitive:  0             |                   Resolution:
         Sub-Project:  DHCP          |                 CVSS Scoring:
Estimated Difficulty:  0             |              Defect Severity:  N/A
         Total Hours:  0             |  Feature Depending on Ticket:
                                     |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------

Comment (by tomek):

 ISC-DHCP allows to say something like:

 {{{
 class pxe {
   match if substring(option vendor-class-identifier, 0, 9) = "PXEClient";
 }
 }}}

 Kea will not allow such things in any foreseeable future. The plan for now
 is to support so called minimalistic client classification. It is called
 minimalistic, because (compared to classes in ISC-DHCP) there is no way
 for user to define its own classes or define what does it mean "a class".
 Kea will merely use content of user-class option.

 Here's the plan for adding minimalistic client classification.

 1. add generic class support in v4/v6 packets.
 2. add client specific processing for v4 packets. This will include docsis
 specific processing that will be later extracted into separate library.
 3. use client classes in subnet selection (white list, black list for
 subnets)
 4. move docsis specific processing to external hook library.

 Tasks 1-2 will be completed in this ticket. Tasks 3 and will be done in
 separate tickets.

-- 
Ticket URL: <http://bind10.isc.org/ticket/3203#comment:4>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development


More information about the bind10-tickets mailing list