BIND 10 #3203: Minimalistic client classification is needed for docsis (classification, part 1)

BIND 10 Development do-not-reply at isc.org
Fri Jan 3 13:01:51 UTC 2014


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

 * owner:  tomek => UnAssigned
 * status:  assigned => reviewing


Comment:

 Please review. Keep in mind that this is a first ticket in a planned
 series of at least 3 tickets. Some of the code written (specific to cable
 modems) should be moved to an external library, but the classifier itself
 is a generic mechanism that can be used in many scenarios, not necessarily
 cable-related. Ultimately, we may consider developing dedicated hook
 points for client classification.

 Proposed ChangeLog entry
 {{{
 719.    [func]          tomek
         b10-dhcp4, b10-dhcp6: Support for simplified client classification
         added. Incoming packets are now assigned to a client class based
 on
         the content of user class (DHCPv4) or vendor class (DHCPv6). Two
 classes
         (docsis3.0 and eRouter1.0) have class specific behavior in
 b10-dhcp4.
         See DHCPv4 Client Classification and DHCPv6 Client Classification
 in
         BIND10 Developer's Guide for details. This is a first ticket in a
 series
         of planned at least three tickets.
         (Trac #3203, git ABCD)
 }}}

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


More information about the bind10-tickets mailing list