Re: [Trans] [dane] CT for DNSSEC

Wei Chuang <weihaw@google.com> Mon, 20 March 2017 22:43 UTC

Return-Path: <weihaw@google.com>
X-Original-To: trans@ietfa.amsl.com
Delivered-To: trans@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 121761270AC for <trans@ietfa.amsl.com>; Mon, 20 Mar 2017 15:43:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id msLKbAiObP2O for <trans@ietfa.amsl.com>; Mon, 20 Mar 2017 15:43:24 -0700 (PDT)
Received: from mail-ot0-x230.google.com (mail-ot0-x230.google.com [IPv6:2607:f8b0:4003:c0f::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5CFD01293FF for <trans@ietf.org>; Mon, 20 Mar 2017 15:43:22 -0700 (PDT)
Received: by mail-ot0-x230.google.com with SMTP id o24so141487757otb.1 for <trans@ietf.org>; Mon, 20 Mar 2017 15:43:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=CO9gwViy4FGBFaS9nBgde26mTFXdve3d2ywBfYMtItU=; b=fHelsQj+Nl8QeHZN6Tp6WxYj6f/bigxorrIcqyt5kPqjObo04//oW4dvrmmvqHtXL1 X2uu1B5Pgn3L8uiv27wUn99Ee2SiVwmsSuh8w/fnPuznrWT24R3HbJjaeTdlKlYpv1LF 3SMKuJQSYw85y85+MjmfiPriWICt6wpkIgPDss2JaeQAud/6pqaf+e7gVa7MZIHUXrPR bRKKOJ/phuEcfsAa0bbT/e0MZuFuOd6zKdB+Cc9KdvXVrUeVQUZ5vOfq3dMaiRXfh9MF OxF7WHbEVOEfllGVw46pqvUHD6/pvCd/LjndUchUCKdIWXqC4mnpnpEiDcWIfGH78eVT QbOQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=CO9gwViy4FGBFaS9nBgde26mTFXdve3d2ywBfYMtItU=; b=KTIxb6OVLv8+suh6lfaWy6ctuCldkWVynul5aj1IEOcAR7zkwEUwTNQetRMNEdufz8 uifz/aeVEjs2QMH925OrQ76vOnIekOo3c8WwSL7tZJWwuT2PPYEJp1aXBM9H9TZPWbuE YMFWw/W64OWRPVs93lKFRZdMlqarY2mmXFOr9W2/PZrQnR9yHcrccoUdk/q9vCbR5KxA x04qNUjyaEGrQyqjkUvDZHU1ylKw4uHel2J8lggl66jgLEYwgZlxQ3rPVaOb0szw/EmC hf8NfAS/w6ceoKxi7O+0Lhysk+0hLvt9CyaoSIR/zzhUM0x0yTPYJVHnZCLbATuMl4Tg 0QWA==
X-Gm-Message-State: AFeK/H3xuwi1mZ5q92YX3U1jKwUgNa6kek+hXdtGmn1XAbi6BrUmIOBzs+RezKHqNjlYCKKPECHpZW9eCAG91OrO
X-Received: by 10.157.15.147 with SMTP id d19mr14923765otd.233.1490049801694; Mon, 20 Mar 2017 15:43:21 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.157.41.226 with HTTP; Mon, 20 Mar 2017 15:43:20 -0700 (PDT)
In-Reply-To: <1DA6DC8F-CA06-4453-96E6-D8D257555437@dukhovni.org>
References: <CAAFsWK0bCDZmg0csCfXAJ1=jqbOBc7sUUvSg-6ZKjxuAQKmQPA@mail.gmail.com> <455EC3FC-9140-40D3-88F8-77990B7C7DD0@vpnc.org> <CAAFsWK2z1AR6RZToQvw7s_t_u+333Jyk6pUQ5KznbsrQGxkvgQ@mail.gmail.com> <C54BF614-378D-4A0A-964F-AE372E064D42@vpnc.org> <1DA6DC8F-CA06-4453-96E6-D8D257555437@dukhovni.org>
From: Wei Chuang <weihaw@google.com>
Date: Mon, 20 Mar 2017 15:43:20 -0700
Message-ID: <CAAFsWK1Jeq18mLsKJpv3DJzhrHzX1Z=rQpyxX5TmF+AOLX8-3Q@mail.gmail.com>
To: Viktor Dukhovni <ietf-dane@dukhovni.org>
Cc: trans@ietf.org, IETF DANE Mailinglist <dane@ietf.org>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="001a113d196a24725e054b314145"
Archived-At: <https://mailarchive.ietf.org/arch/msg/trans/lfQJzX9hA9aPfNoe7M4YnIBkcIg>
Subject: Re: [Trans] [dane] CT for DNSSEC
X-BeenThere: trans@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Public Notary Transparency working group discussion list <trans.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/trans>, <mailto:trans-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/trans/>
List-Post: <mailto:trans@ietf.org>
List-Help: <mailto:trans-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/trans>, <mailto:trans-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Mar 2017 22:43:26 -0000

On Fri, Mar 17, 2017 at 11:46 AM, Viktor Dukhovni <ietf-dane@dukhovni.org>
wrote:

>
> > On Mar 17, 2017, at 2:20 PM, Paul Hoffman <paul.hoffman@vpnc.org> wrote:
> >
> >> Is this because you're worried about the parent removing evidence of
> DNSSEC
> >> for the child in the spoofing scenario?
> >
> > No, this is because the parent can spoof any data for the child. It is
> unrelated to DNSSEC.
>
> With qname minimization, the parent will first need to deny an NS
> RRset for the child, and those DOE records are better candidates
> for logging than routine non-NS queries.


Can you expand on how the the DOE record (which I assumes means
denial-of-existance) could work with an
adversarial parent?

The only approach I can think of is some sort of UI support which isn't
very compelling.  (Perhaps monitors
but alas I not really up-to-date where things are at with monitors and
gossip)


>   So logging can be limited
> to NS/DS queries, but that still leaves us with the problem of how
> to avoid logging non-existence of NS/DS for all the sundry leaf
> nodes. The public suffix list might be a useful resource here...
>

I agree.

-Wei


>
> --
>         Viktor.
>
> _______________________________________________
> Trans mailing list
> Trans@ietf.org
> https://www.ietf.org/mailman/listinfo/trans
>