Ticket #14 (defect)

Opened 3 years ago

Last modified 3 years ago

NSEC3 hash name and legitimate zone name collision is okay

Status: new

Reported by: ben Assigned to: ben
Priority: normal Milestone:
Component: drafts Version:
Severity: normal Keywords:
Cc:

The editor believes this is not an issue. Rob Austein said that he's 3/4 close to leaning towards Peter Koch's half-serious new label type proposal. He feels this is a much cleaner solution to all this collision stuff and has the added benefit that it can be defined as a binary-only label type which removes the sort order issue as well. Ben Laurie asked how this would interact with caches that don't grok the new label type. Rob replied that dnssec-bis doesn't work through dnssec-oblivious middle boxes, so this might just be a non-issue. Paul Vixie stated that the original idea behind the separate label type was to provide a way to store the various sets of metadata that aren't truly dns data and hence don't really belong in the actual database proper. This data we're talking about here is also not dns data and so a separate label type would go a long way to helping this. Ben asked if people were okay waiting until implementations were done before deciding on this.

Change History

11/13/05 14:23:43: Modified by ben

  • component changed from bind-patches to drafts.