Opened 8 years ago

Closed 8 years ago

#1432 closed enhancement (duplicate)

NSEC3: QNAME does not exist

Reported by: stephen Owned by:
Priority: medium Milestone: Year 3 Task Backlog
Component: Unclassified Version:
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity: N/A
Sub-Project: DNS Feature Depending on Ticket: NSEC3
Estimated Difficulty: 4 Add Hours to Ticket: 0
Total Hours: 0 Internal?: no

Description

Modify the DatabaseClient code to returns appropriate NSEC3 records for the case where the QNAME does not exist. (See RFC 5155 section 7.2.2.) This will build on the closest encloser proof of ticket #1431

Subtickets

Change History (5)

comment:1 Changed 8 years ago by shane

  • Milestone changed from New Tasks to Next-Sprint-Proposed

comment:2 Changed 8 years ago by shane

  • Feature Depending on Ticket set to NSEC3

comment:3 Changed 8 years ago by jelte

  • Estimated Difficulty changed from 0 to 4

comment:4 Changed 8 years ago by jinmei

  • Milestone changed from Year 3 Task Backlog to Next-Sprint-Proposed

comment:5 Changed 8 years ago by jinmei

  • Resolution set to duplicate
  • Status changed from new to closed

More specific proposed ticket is created. Closing this one.

Note: See TracTickets for help on using tickets.