IETF Logo Mail Archive

Re: [ietf-smtp] [OT] (signed TLDs)

Viktor Dukhovni <ietf-dane@dukhovni.org> Fri, 11 October 2019 17:20 UTC

Return-Path: <ietf-dane@dukhovni.org>
X-Original-To: ietf-smtp@ietfa.amsl.com
Delivered-To: ietf-smtp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 48E4912001A for <ietf-smtp@ietfa.amsl.com>; Fri, 11 Oct 2019 10:20:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 CvGPQtICIta5 for <ietf-smtp@ietfa.amsl.com>; Fri, 11 Oct 2019 10:20:22 -0700 (PDT)
Received: from straasha.imrryr.org (straasha.imrryr.org [100.2.39.101]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8405D120018 for <ietf-smtp@ietf.org>; Fri, 11 Oct 2019 10:20:22 -0700 (PDT)
Received: from [192.168.1.161] (unknown [192.168.1.161]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by straasha.imrryr.org (Postfix) with ESMTPSA id 6CB082B680F for <ietf-smtp@ietf.org>; Fri, 11 Oct 2019 13:20:21 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
From: Viktor Dukhovni <ietf-dane@dukhovni.org>
In-Reply-To: <20191011160802.50C81C9B780@ary.qy>
Date: Fri, 11 Oct 2019 13:20:20 -0400
Content-Transfer-Encoding: quoted-printable
Reply-To: ietf-smtp@ietf.org
Message-Id: <EA77F2DD-D7F3-47E8-A636-83EEF205C0F0@dukhovni.org>
References: <20191011160802.50C81C9B780@ary.qy>
To: ietf-smtp@ietf.org
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/OdQvu4s3q3FZTfbx2RThGgZso5o>
Subject: Re: [ietf-smtp] [OT] (signed TLDs)
X-BeenThere: ietf-smtp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion of issues related to Simple Mail Transfer Protocol \(SMTP\) \[RFC 821, RFC 2821, RFC 5321\]" <ietf-smtp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-smtp>, <mailto:ietf-smtp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-smtp/>
List-Post: <mailto:ietf-smtp@ietf.org>
List-Help: <mailto:ietf-smtp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-smtp>, <mailto:ietf-smtp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Oct 2019 17:20:26 -0000

> On Oct 11, 2019, at 12:08 PM, John Levine <johnl@taugh.com> wrote:
> 
>> CDS support at registries is essential to removing this roadblock to DNSSEC
>> adoption, by getting the registrar out of the critical path.
> 
> Unless I missed something, CDS currently only lets you update DS records,
> not install them initially.

At least two registries supports bootstrapping DNSSEC via CDS.

	https://www.nic.ch/faqs/dnssec/cds/
	https://ripe75.ripe.net/presentations/123-CDNSKEY-FRED-KNOT-RIPE75.pdf

Further links:

	https://meetings.icann.org/en/dublin54/schedule/wed-dnssec/presentation-dnssec-bootstrapping-21oct15-en.pdf
	https://github.com/CIRALabs/DSAP
	https://blog.dnsimple.com/2019/02/cds_cdnskey/

-- 
	Viktor.

v2.23.0 | Report a Bug | By Email