Re: [dane] [Trans] CT for DNSSEC

[Wei Chuang <[e-mail]>]

On Wed, Mar 29, 2017 at 8:11 AM, Viktor Dukhovni <[e-mail]>
wrote:

>
> > On Mar 29, 2017, at 10:33 AM, Wei Chuang <[e-mail]> wrote:
> >
> > Why not create an explicit Non-existence of DS (NDS) RR that gets logged
> along with DS and NS?
>
> This is not needed, the NSEC/NSEC3 RRs already serve that role.
>
> For NSEC records (RFC4034), an unsigned delegation looks like:
>
>         example.com. IN NS ns1.example.com.
>         example.com. IN NSEC examplf.com NS
>         example.com. IN RRSIG NSEC ...
>
> this proves that NS (or other depending on the content of the type
> bitmap of the NSEC record) records exist for example.com, but DS
> records do not.
>
> With NSEC3 (rfc5155), and the "opt-out" bit the situation can be
> more complex because the answer may not establish the existence of
> example.com.  Instead we may get an existence proof for the closest
> encloser (ancestor domain) and proof that "example.com" is not signed,
> but no proof of its existence.  This means that to avoid spam, a log
> might want to independently verify the existence of the insecure
> delegation by repeating the query, so as to avoid storing data for
> non-existent domains with the insecure NXDOMAIN modified to NOERROR
> with made up NS records.
>
>
Sorry this reply is coming late.  Your response helped a lot (thanks!) but
I had nagging concern that couldn't make concrete till now.

When a DOE lookup occurs on DNSSEC, the authoritative nameserver services
the request and determines to respond with what you describe above (the
NSEC and its RRSIG).  The complication occurs with CT.  While we may log
the NSEC or NSEC3 record and these records will be present for lookups in
CT of existing records, there isn't an online server to assist with lookups
in CT of non-existing records.  I suppose it may be possible to replicate
the state of the authoritative nameserver but consider that this likely
doesn't scale as CT servers are servicing a scope potentially much larger
than the authoritative nameservers.  The approach I describe earlier with
an explict Non-existence of DS (NDS) should allow for direct lookup of NDS
entry.

Also agreed with later comments suggesting that the entire key signing
chain needs to be CT logged with its proofs and non-existance records for
this to work.

-Wei


> --
>         Viktor.
>
> _______________________________________________
> dane mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/dane
>