BIND 10 #553: canceling wildcard match due to an empty non terminal

[BIND 10 Development]

#553: canceling wildcard match due to an empty non terminal
-------------------------------------+-------------------------------------
                 Reporter:  jinmei   |                Owner:  vorner
                     Type:           |               Status:  assigned
  enhancement                        |            Milestone:  A-Team-
                 Priority:  major    |  Sprint-20110223
                Component:  data     |           Resolution:
  source                             |            Sensitive:  0
                 Keywords:           |  Add Hours to Ticket:  0
Estimated Number of Hours:  5.0      |          Total Hours:  0
                Billable?:  1        |
                Internal?:  0        |
-------------------------------------+-------------------------------------

Comment (by vorner):

 Replying to [comment:2 jinmei]:
 > That is, we should be able to reject this case by checking whether the
 > "last comparison" is "COMMONANCESTOR" (and if so, cancel wildcard
 > matching).  With this approach we don't need #552.

 Seems it's not that simple, because if we cancel by COMMONANCESTOR, we
 cancel all wildcard matches. When we are checking for
 a.wildcard.example.org, the last comparison we do is with
 *.wildcard.example.org and that one is COMMONANCESTOR as well. I'll think
 a while if we can work around this somehow easily and if I come to no
 conclusion, I'll just pull #552 in and do it the previous way.

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