Opened 8 years ago

Closed 6 years ago

#2111 closed task (wontfix)

Define a dedicated result context and additional record handling.

Reported by: jinmei Owned by:
Priority: medium Milestone: Remaining BIND10 tickets
Component: data source Version: bind10-old
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity: N/A
Sub-Project: DNS Feature Depending on Ticket: scalable inmemory
Estimated Difficulty: 4 Add Hours to Ticket: 0
Total Hours: 0 Internal?: no

Description (last modified by jinmei)

This is a revised version of current RBNodeResultContext
and InMemoryZoneFinder::Context. But right now additional shortcut
is not available, so it's actually pretty simple.

Iterate over each RDATA of the given RRset using the encoded version
of iterator, and use findNode() to get the node for each name field of
the RDATA whose attribute indicates additional handling is needed.
Then go through the nodes' RdataSet to find specified type of data.
Construct TreeNodeRRset for them and push them to the result.

One open question is whether we should distinguish "glue ok" case or
not. I'm now inclined to skip this differentiation, but we can
discuss it.

Depend on #2096, and in practice, on #2107, #2108 and #2109 (and
even #2110 for comprehensive support).


Change History (5)

comment:1 Changed 8 years ago by jinmei

  • Description modified (diff)

comment:2 Changed 8 years ago by shane

  • Estimated Difficulty changed from 0 to 4

comment:3 Changed 8 years ago by jinmei

  • Milestone set to Next-Sprint-Proposed

comment:4 Changed 6 years ago by tomek

  • Milestone set to Remaining BIND10 tickets

comment:5 Changed 6 years ago by tomek

  • Resolution set to wontfix
  • Status changed from new to closed
  • Version set to old-bind10

This issue is related to bind10 code that is no longer part of Kea.

If you are interested in BIND10/Bundy framework or its DNS components,
please check

Closing ticket.

Note: See TracTickets for help on using tickets.