Re: DNSSEXT Yokohama Minutes

Roy Arends <roy@logmess.com> Mon, 16 September 2002 15:31 UTC

Received: from psg.com (smmsp@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08654 for <dnsext-archive@lists.ietf.org>; Mon, 16 Sep 2002 11:31:33 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1) id 17qxkg-000EfI-00 for namedroppers-data@psg.com; Mon, 16 Sep 2002 08:25:30 -0700
Received: from vhe-530008.sshn.net ([195.169.222.38] helo=elektron.atoom.net) by psg.com with esmtp (Exim 3.36 #1) id 17qxkc-000Ef6-00 for namedroppers@ops.ietf.org; Mon, 16 Sep 2002 08:25:26 -0700
Received: from elektron.atoom.net (localhost [127.0.0.1]) by elektron.atoom.net (8.12.5/8.12.5/Debian-1) with ESMTP id g8GFPExG024557; Mon, 16 Sep 2002 17:25:14 +0200
Received: from localhost (roy@localhost) by elektron.atoom.net (8.12.5/8.12.5/Debian-1) with ESMTP id g8GFPDPW024553; Mon, 16 Sep 2002 17:25:13 +0200
X-Authentication-Warning: elektron.atoom.net: roy owned process doing -bs
Date: Mon, 16 Sep 2002 17:25:13 +0200
From: Roy Arends <roy@logmess.com>
X-X-Sender: roy@elektron.atoom.net
To: Edward Lewis <edlewis@arin.net>
cc: Scott Rose <scottr@antd.nist.gov>, namedroppers@ops.ietf.org
Subject: Re: DNSSEXT Yokohama Minutes
In-Reply-To: <a05111b09b9ab9e1cd919@[192.149.252.231]>
Message-ID: <Pine.LNX.4.44.0209161717170.17141-100000@elektron.atoom.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
X-Spam-Status: No, hits=-2.0 required=5.0 tests=IN_REP_TO, X_AUTH_WARNING, OPT_IN version=2.31
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk

On Mon, 16 Sep 2002, Edward Lewis wrote:

> At 4:16PM +0200 9/16/02, Roy Arends wrote:
> >Please inform me what a resolver should do with the ambiguity of both an
> >unsigned referral and a signed wildcard in a response.
>
> That's the problem.  It's getting harder and harder to tell what
> should be done.
>
> It's clear that a reply should have, barring EDNS1's multiple query
> proposal, 0 or 1 answering RRsets.  (0 means no data/name found.)
> The rest of the answer should be there to support the answer chosen.
>
> The problem is how do you protect answers that should have been
> synthesized from a signed wildcard answer (which does not have to be
> a delegation)

cannot be a delegation (wildcard delegations are not legal).

> from being spoofed away by OPT-IN modified NXT records
> and falsified answers?

I'm stumbling over your words now.

I do understand the problem. The problem is _not_ what should be in a
response, the problem is what a resolver should do with the ambiguity:
Follow unsigned delegation, or assume its a spoof, and go with the signed
wildcard.

Yes, with opt-in as is, you could simply spoof away signed wildcards with
unsecure delegations, and simply spoof away unsecure delegations with
secure wildcards.

How'bout we state in the Opt-In draft that, when using DNSSEC, having both
opt-in and wildcards are illegal.

Roy


--
to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/namedroppers/>