Re: [dnsext] slave signing, was does making names the same NEED protocol changes at all?

John Levine <johnl@iecc.com> Sun, 27 February 2011 05:04 UTC

Return-Path: <johnl@iecc.com>
X-Original-To: dnsext@core3.amsl.com
Delivered-To: dnsext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BC7EF3A69AE for <dnsext@core3.amsl.com>; Sat, 26 Feb 2011 21:04:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.658
X-Spam-Level:
X-Spam-Status: No, score=-110.658 tagged_above=-999 required=5 tests=[AWL=0.541, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7MhVpisXzCJb for <dnsext@core3.amsl.com>; Sat, 26 Feb 2011 21:04:05 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [64.57.183.53]) by core3.amsl.com (Postfix) with ESMTP id 749C23A68E5 for <dnsext@ietf.org>; Sat, 26 Feb 2011 21:04:04 -0800 (PST)
Received: (qmail 50072 invoked from network); 27 Feb 2011 05:05:00 -0000
Received: from mail1.iecc.com (64.57.183.56) by mail1.iecc.com with QMQP; 27 Feb 2011 05:05:00 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:cc:mime-version:content-type:content-transfer-encoding:vbr-info; s=b97.4d69db7c.k1102; i=johnl@user.iecc.com; bh=7qq9FhHGeryC4hYpfv/0Qpzd4aL9GliSS6bEaDncBcY=; b=ZGiKNr1XghsQNMqj76AEO6XGH5t1RhGIrgLSWTutu8Z81J7XitdbzJqtTyTqbDNzAjhqaFyidm84modM3lTVgyVfXr+Z8fW2Z+i8fEVJmHKYMN9mQFXhp13y9oEJffuamsp8umVC4uF3j+kcyMRRD/9X3H4bHCV2No2kpJH4ork=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: Sun, 27 Feb 2011 05:05:00 -0000
Message-ID: <20110227050500.2966.qmail@joyce.lan>
From: John Levine <johnl@iecc.com>
To: dnsext@ietf.org
In-Reply-To: <AANLkTinvqqGTGPeMXUcAv5iY1KGn_=LwfGr3debWo_GE@mail.gmail.com>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 7bit
Subject: Re: [dnsext] slave signing, was does making names the same NEED protocol changes at all?
X-BeenThere: dnsext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: DNS Extensions working group discussion list <dnsext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsext>
List-Post: <mailto:dnsext@ietf.org>
List-Help: <mailto:dnsext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 27 Feb 2011 05:04:06 -0000

>Requiring slaves to be signers is a major change to the security model.

Maybe, but this isn't the only place it's an issue.

IPv6 rDNS is a can of worms that I'd prefer not to open here, but
making forward and reverse DNS match on consumer IPv6 is another
problem that has no straightforward solution.  One of the possiblities
that keeps coming up is stunt servers that synthesize the records as
needed, which obviously means that if they do DNSSEC they need to have
the signing keys.

R's,
John