BIND 10 #2776: Resolver research: mixed authoritative/resolver mode
BIND 10 Development
do-not-reply at isc.org
Tue Mar 5 09:18:46 UTC 2013
#2776: Resolver research: mixed authoritative/resolver mode
-------------------------------------+-------------------------------------
Reporter: shane | Owner:
Type: task | UnAssigned
Priority: high | Status:
Component: resolver | reviewing
Keywords: | Milestone:
Sensitive: 0 | Sprint-20130305
Sub-Project: DNS | Resolution:
Estimated Difficulty: 8 | CVSS Scoring:
Total Hours: 0 | Defect Severity: N/A
| Feature Depending on Ticket:
| resolver-ng
| Add Hours to Ticket: 0
| Internal?: 0
-------------------------------------+-------------------------------------
Changes (by vorner):
* owner: vorner => UnAssigned
* status: accepted => reviewing
Comment:
It seems the discussion is calming down and the conclusion is that
receptionist
is viable solution to the problem. So, I think it is time to do something
with
the ticket.
I put some text in the `doc/design/resolver/02-mixed-recursive-authority-
setup`
which I'd like to merge into master. I don't want to merge the experiment
(it
is ugly code and it actually breaks TCP for normal use). So, I'd be glad
if
someone could review the text, skip the code and I'd then cherry-pick the
design changes into a new branch and merged it to master.
Should I create a ticket to plan the work needed on receptionist? Should
we
bring this up first on the technical call, before the ticket is closed?
--
Ticket URL: <http://bind10.isc.org/ticket/2776#comment:5>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list