Hi John,

First, thank you for your prompt response and for raising the compatibility
concern. However, I would like to clarify that the proposal actually
**preserves**
existing wildcard matching and expansion, including expansion over multiple
labels. TL;DR: It adds a validation check on RRSIG Labels to enforce the
signing zone’s authority.

For example, for an RRset at `a.child.example.`, a signature from
`child.example.` with Labels=1 reconstructs `*.example.`, which the child
key cannot authenticate. A legitimate source at `*.child.example.` with
Labels=2 remains valid, including expansion to `a.b.child.example.` when
existing applicability rules permit it.

To address your concern, we submitted revision -01:

https://datatracker.ietf.org/doc/draft-zhang-dnssec-wildcard-validation/01/
.

It explicitly states the unchanged wildcard semantics in the abstract and
introduction, adds valid multi-label and parent-zone expansion examples,
and clarifies source authentication versus expanded-answer validation.
These are explanatory changes; the normative requirements remain unchanged.

Section 3.1 links to the corresponding resolver advisories. Could you point
to a legitimate wildcard expansion that you believe the proposed check
would reject?

Best regards,
Qifan

On Fri, Oct 16, 2026 at 8:38 PM John Levine <[email protected]> wrote:

> It appears that Qifan Zhang  <[email protected]> said:
> >-=-=-=-=-=-
> >
> >Dear DNSOP colleagues,
> >
> >We have submitted a new individual Internet-Draft, “Signer-Zone
> Containment
> >for DNSSEC Wildcard Validation”:
> >
> >
> https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_doc_draft-2Dzhang-2Ddnssec-2Dwildcard-2Dvalidation_&d=DwIDaQ&c=V9IgWpI5PvzTw83UyHGVSoW3Uc1MFWe5J8PTfkrzVSo&r=G8Y2PafMWp_pxuBT8os_MllFpqBNVDXvAhGzwXTXJfs&m=biL346UC13wbVp0UyS0Xom39F8tB4Z6xp08lEff-3Egen14y6HkTnwtJ8aXp7SGv&s=MnP4J7RNPU105m7sy91UHhZi4wH46csZM8uVT4gLAuo&e=
> >
> >Based on findings from our DNSSECVerif research, accepted at ACM CCS 2026,
> >the draft proposes focused updates to RFCs 4035 and 8198 to:
> >
> >   - Require signer-zone containment of reconstructed RRset owner names.
> >   - Preserve authenticated wildcard-source associations during cache
> reuse.
>
> I can understand why you might not like the way that wildcards work, but
> changing
> the way wildcards are expanded would be a breaking change to a spec that
> has been in place for
> 40 years.  So, no.  Also, this would make wildcard expansion with DNSSEC
> give different
> answers to expansion without DNSSEC.  So doubly no.
>
> R's,
> John
>
_______________________________________________
DNSOP mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to