Re: [DNSOP] CDS and/or CDNSKEY

Doug Barton <dougb@dougbarton.us> Tue, 08 October 2013 20:33 UTC

Return-Path: <dougb@dougbarton.us>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A408221F9AE3 for <dnsop@ietfa.amsl.com>; Tue, 8 Oct 2013 13:33:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kOs1y3N2xZql for <dnsop@ietfa.amsl.com>; Tue, 8 Oct 2013 13:33:03 -0700 (PDT)
Received: from dougbarton.us (dougbarton.us [IPv6:2607:f2f8:ab14::2]) by ietfa.amsl.com (Postfix) with ESMTP id AD4E021F9FD6 for <dnsop@ietf.org>; Tue, 8 Oct 2013 13:33:02 -0700 (PDT)
Received: from [IPv6:2001:470:d:5e7:3479:3991:40da:8b9] (unknown [IPv6:2001:470:d:5e7:3479:3991:40da:8b9]) by dougbarton.us (Postfix) with ESMTPSA id 4ED2F22B36 for <dnsop@ietf.org>; Tue, 8 Oct 2013 20:33:02 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dougbarton.us; s=dougbarton.us; t=1381264382; bh=5v34UfAG9HGgswnEzgfj3lcJJxPo3dtuGDtbgnGfHrQ=; h=Date:From:To:Subject:References:In-Reply-To; b=h05fMkYySjG1471ME1U5YLWlL0bZmW7iRUuK0We7umB3kbzF2JOPhuHWZcIoNIgB6 Mq/J3nn+td/kjt5K8PguS+qDwUzwZNEOaI4PAIPNfAGBRDFHSAAGDvZy4OPj8AfTia ru+vD7HKu4Btuq4nHE7gwIi0tBpHKe5xnixaai5g=
Message-ID: <52546BFE.7050904@dougbarton.us>
Date: Tue, 08 Oct 2013 13:33:02 -0700
From: Doug Barton <dougb@dougbarton.us>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: dnsop <dnsop@ietf.org>
References: <5243DCAB.80507@nlnetlabs.nl> <311D023E-9425-416E-B3E6-96F3347F162B@kumari.net> <52451D58.5040107@nlnetlabs.nl> <FC382AE9-C360-47B3-B1B6-35276C624AAC@kumari.net> <524D9B65.30704@teamaol.com> <52543899.3090801@dougbarton.us> <alpine.LFD.2.10.1310081408570.7675@bofh.nohats.ca> <52545387.2010607@dougbarton.us> <24BAD69C-F0AA-4F33-8A3D-536494864D34@vpnc.org> <525466A5.6000006@dougbarton.us> <A1CA88FF-4008-477B-A917-0AAE37AF927B@kumari.net>
In-Reply-To: <A1CA88FF-4008-477B-A917-0AAE37AF927B@kumari.net>
X-Enigmail-Version: 1.5.2
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [DNSOP] CDS and/or CDNSKEY
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Oct 2013 20:33:04 -0000

On 10/08/2013 01:22 PM, Warren Kumari wrote:
> In many regulatory environments (the polite way of saying where ICANN
> says "No!")

Just FYI, it's not ICANN that says no. It's the registrars who do not 
want ANY channel of communication with their customers that does not go 
through them. ICANN simply provides a context around which to solidify 
the agreed upon relationships contractually.

> the *registrar*  will fetch the CDS / CDNSKEY and will
> push the updated records into the *registry*  through existing
> mechanisms (like EPP).

Right, so instead of convincing hundreds of registries you're going to 
convince thousands of registrars? And you've had exactly how much 
interest from them?

Doug