Opened 8 years ago

Closed 6 years ago

#1438 closed enhancement (wontfix)

NSEC3: consistent selection of NSEC3PARAM

Reported by: stephen Owned by:
Priority: medium Milestone: DNS Outstanding Tasks
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: 5 Add Hours to Ticket: 0
Total Hours: 0 Internal?: no


Consistent selection of NSEC3PARAM record for use in all subsequent NSEC3 code. RFC 5155 does not prohibit multiple NSEC3PARAM RRs at the apex of the zone and leaves flexibility in which one is used. The purpose of this ticket is to review the NSEC3 code and to ensure if multiple NSEC3PARAM records are present, the parameters of the same record are used throughout one query. (See RFC 5155 section 7.3.)

This relies on the completion of tickets #1431 through #1437.


Change History (9)

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 5

comment:4 Changed 8 years ago by jinmei

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

We need to think about how this fits in the in-memory centric design
(for simplicity it currently assumes only 1 NSEC3PARAM per zone).

comment:5 Changed 8 years ago by jelte

  • Milestone changed from Next-Sprint-Proposed to Sprint-20120207
  • Priority changed from major to critical

comment:6 Changed 8 years ago by jelte

  • Milestone changed from Sprint-20120207 to Year 3 Task Backlog

This one is not ready to go yet, shouldn't have moved it into this sprint, sorry.

comment:7 Changed 8 years ago by jinmei

  • Priority changed from high to medium

comment:8 Changed 6 years ago by stephen

  • Milestone set to DNS Outstanding Tasks

comment:9 Changed 6 years ago by tomek

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

DNS and BIND10 framework is outside of scope for Kea project.
The corresponding code has been removed from Kea git repository.
If you want to follow up on DNS or former BIND10 issues, see project.

Closing ticket.

Note: See TracTickets for help on using tickets.