BIND 10 #506: Analysis of Wildcard Processing

[BIND 10 Development]

#506: Analysis of Wildcard Processing
-------------------------------------+-------------------------------------
                 Reporter:  stephen  |                Owner:  jinmei
                     Type:           |               Status:  reviewing
  enhancement                        |            Milestone:  A-Team-
                 Priority:  major    |  Sprint-20110209
                Component:           |           Resolution:
  b10-auth                           |            Sensitive:  0
                 Keywords:           |  Add Hours to Ticket:  0
Estimated Number of Hours:  3.0      |          Total Hours:  0
                Billable?:  1        |
                Internal?:  0        |
-------------------------------------+-------------------------------------
Changes (by vorner):

 * owner:  vorner => jinmei


Comment:

 I didn't check it against RFC. Should I?

 It mostly makes sense, but I have few questions.
  - What if we add "*.example.com." and "example.com." isn't there yet? Do
 we add it? Won't it change NXDOMAIN into NXRRSET?
  - The wildcards are handled inside MemoryZone? Including creation of the
 names?
  - Do we store the „I met a wild node“ on the path here? The first part
 suggest yes, but the second doesn't mention it and it seems to me looking
 at the node we got from last partial match is enough.
  - How does the case with "foo.*.example.com." work while searching? We
 will encounter "example.com." and it is wild, therefore we would like to
 search for "*.example.com.", but that one isn't there. What we do then?
 (Provided we are looking for example for "foo.bar.example.com.")
  - The task for previous primitive for RBTree should list next as well?

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