IETF Logo Mail Archive

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

"John Levine" <johnl@taugh.com> Fri, 11 October 2019 18:44 UTC

Return-Path: <johnl@iecc.com>
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 8F0E2120018 for <ietf-smtp@ietfa.amsl.com>; Fri, 11 Oct 2019 11:44:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level:
X-Spam-Status: No, score=-1.75 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=HTKsfeHG; dkim=pass (1536-bit key) header.d=taugh.com header.b=ywKGKUWQ
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 GRotLG6YSgIh for <ietf-smtp@ietfa.amsl.com>; Fri, 11 Oct 2019 11:44:46 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F1AC012006A for <ietf-smtp@ietf.org>; Fri, 11 Oct 2019 11:44:45 -0700 (PDT)
Received: (qmail 48275 invoked from network); 11 Oct 2019 18:44:44 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=bc8f.5da0cd9c.k1910; i=printer-iecc.com@submit.iecc.com; bh=wvFOALmssjMpYqXrROU++Q8lEtBL3nxuTvcXWLPHyrA=; b=HTKsfeHG8SR7EMbKU79GCe8rMOQpkKDUA4WBW0XFIbQvzoiV3V0UhkDWBPSazWM55u0J0yIwZhKld4MyiMi9YHRkd9XVIA9EkCUzhPhOm5PzY6DFOVuLlJb+3xESTsLNsxf5IKpTb+/6+q6eTj+pzLnA1CIFexndU0SzbtpbfRXmmV/tkrJUogPfeMQPW1KJLdTXVFB+n9gjISQStUEjgskmMZgksrS9x1xPTCfYHBtg9uNP9tvPIF42cFf8oII1
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=bc8f.5da0cd9c.k1910; olt=printer-iecc.com@submit.iecc.com; bh=wvFOALmssjMpYqXrROU++Q8lEtBL3nxuTvcXWLPHyrA=; b=ywKGKUWQqD17duNYYxGQmFdSRCcSk1oIesNnmte6I0PiLSbzubHL3Ublmpzxmd5WFO97Jrr+idYUkQZA9zr2GnkDMYZ8204cAkKA4qXCJGyOlHj3olyAo0x+k+06zUG1txbOG7mcOJHPiv3nfjOFp9icN5+XE/kYfqeUHVM2SmvWVM2AKWtX/AsTAu0px2TvMN/FZXdl/FfkMysLSSxzB/9cADF/vNZNdLfd/BHwkyf7eyUuKyXeSDCGJ3j9kZlo
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPSA (TLS1.2 ECDHE-RSA AES-256-GCM AEAD, printer@iecc.com) via TCP6; 11 Oct 2019 18:44:44 -0000
Received: by ary.qy (Postfix, from userid 501) id B3780C9DFD7; Fri, 11 Oct 2019 14:44:43 -0400 (EDT)
Date: Fri, 11 Oct 2019 14:44:43 -0400
Message-Id: <20191011184443.B3780C9DFD7@ary.qy>
From: John Levine <johnl@taugh.com>
To: ietf-smtp@ietf.org
In-Reply-To: <EA77F2DD-D7F3-47E8-A636-83EEF205C0F0@dukhovni.org>
Organization: Taughannock Networks
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/1TkQpT4fa-jJjl8OXwwm48hUJWM>
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 18:44:48 -0000

In article <EA77F2DD-D7F3-47E8-A636-83EEF205C0F0@dukhovni.org> you write:
>> 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.

I suppose I can put in CDS records and see what happens.


>
>	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