Re: [dns-privacy] [Errata Held for Document Update] RFC7858 (5375)

Patrick Mevzek <mevzek@uniregistry.com> Mon, 23 December 2019 18:01 UTC

Return-Path: <mevzek@uniregistry.com>
X-Original-To: dns-privacy@ietfa.amsl.com
Delivered-To: dns-privacy@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BDFE5120CA9 for <dns-privacy@ietfa.amsl.com>; Mon, 23 Dec 2019 10:01:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=uniregistry.com
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 QSocv9DCRjRR for <dns-privacy@ietfa.amsl.com>; Mon, 23 Dec 2019 10:01:08 -0800 (PST)
Received: from a-mx.uniregistry.com (a-mx.uniregistry.com [64.96.177.8]) (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 6A429120CA0 for <dns-privacy@ietf.org>; Mon, 23 Dec 2019 10:01:08 -0800 (PST)
Abuse: Forward to abuse@uniregistry.com with full headers
X-Virus-Scanned: Content filter at a-mx.uniregistry.com
Powered-By: https://www.uniregistry.com
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=uniregistry.com; s=bravo; t=1577124067; bh=ZB8OrZLyqUEEEi0rmwSb9hdSruobtv5SrPXC/nllDjk=; h=Subject:To:References:From:Date:In-Reply-To; b=q/OI4VpKS9w986JA/3Z+Ssk4ASZlBK37Y2h4GC6RLEsIcWELWV7DlbrX0KflzNsgV WImjsH7R0fN0hF1n55aM4eZdmXrAZrlmVF/OvXLkGost3A7MiZ2uwO9IFiYzpYUnSB Uqe8zhWjB2GHYw3z4ajylbeIm8fmeYRk1DFj/EOnWat1H7L29XzJL97VKpWjK5yIa4 wqA3WYm4VKMPHRFB+pWNIVRNJZG9sh+s0q/us2D87e+RVuoGhWXJrt93ooVqBr2yow FOpwQ6+XmV3FtuFD8RXNCp6ozeRPi8yfmftkAdAopGou3EZYP2K8YwfLJa+ppevErT eDweDKj9tQsKQ==
Received: from PatrickM.local (b01.uniregistrar.net [52.204.70.64]) (authenticated bits=0) by a-mx.uniregistry.com (8.15.2/8.15.2/Debian-8) with ESMTPSA id xBNI15T1032371 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Mon, 23 Dec 2019 18:01:07 GMT
To: dns-privacy@ietf.org
References: <20191219130836.C4D11F40709@rfc-editor.org> <c0983b61-79b7-0725-3bd7-ad353b7c4d12@nic.cz> <CAHw9_iJpb0nPvPZbrz9umo+XE8nYwTMjAd9vqsyyy41Kqc0KGw@mail.gmail.com>
From: Patrick Mevzek <mevzek@uniregistry.com>
Organization: Uniregistry
Message-ID: <e9004462-2091-d46e-cd79-1cd5f9be9ca8@uniregistry.com>
Date: Mon, 23 Dec 2019 13:01:05 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:68.0) Gecko/20100101 Thunderbird/68.3.1
MIME-Version: 1.0
In-Reply-To: <CAHw9_iJpb0nPvPZbrz9umo+XE8nYwTMjAd9vqsyyy41Kqc0KGw@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dns-privacy/O-W66ehjCH96OFptocg_NPnfMKY>
Subject: Re: [dns-privacy] [Errata Held for Document Update] RFC7858 (5375)
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <dns-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dns-privacy/>
List-Post: <mailto:dns-privacy@ietf.org>
List-Help: <mailto:dns-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Dec 2019 18:01:10 -0000

On 23/12/2019 12:54, Warren Kumari wrote:

> W
> p.s: if it were mine, I'd probably mark it hold for update with a note
> of "someone should validate this..."

In May 2018, I also reported that the correct one was probably more the
.info one than the .org one, because at that time both dnscrypt.org and
www.dnscrypt.org replied with wrong X.509 certificates.

At least right now both resolves correctly but with different content.

Maybe, people behind DNScrypt project/tools/implemnentations should
voice which website is the correct one...

-- 
Patrick Mevzek