IETF Logo Mail Archive

Re: [DNSOP] New draft, seeking comments: draft-sah-resolver-information

"John R Levine" <johnl@taugh.com> Sat, 04 May 2019 16:22 UTC

Return-Path: <johnl@taugh.com>
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 9B969120114 for <dnsop@ietfa.amsl.com>; Sat, 4 May 2019 09:22:37 -0700 (PDT)
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_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=ZWofQoTT; dkim=pass (1536-bit key) header.d=taugh.com header.b=cf9avHu9
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 Yw7OtmRzEWha for <dnsop@ietfa.amsl.com>; Sat, 4 May 2019 09:22:35 -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 96487120103 for <dnsop@ietf.org>; Sat, 4 May 2019 09:22:35 -0700 (PDT)
Received: (qmail 80956 invoked from network); 4 May 2019 16:22:33 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=13c39.5ccdbc49.k1905; i=johnl-iecc.com@submit.iecc.com; bh=XBqzDHdWKmqyXi4OylwlXLYM4ip0ydYyKG/sCETF3yw=; b=ZWofQoTTwnIxauw6s4m8QI0P83JloF/pNzSx9hd2WMFn/g6DtbSNlSrPtFSVV/0Shj928YrecqN4Z/X6Bz1IvrjIxMFTdf+t2pixmwIQqsLmNFQWq71/vt5lKV4Bf8j0wINvB51EaicHwv7zo6T9IdypMNI6SPtwMHjNBdW6OgtfVjBM/IVnVaHXZI/zElbRX5Y6b08Bymn2HeyQPLjUK7lkrBIyTLoIJ6CJxnaGN4Q+okNmT4oA6WkO9nyjJCQh
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=13c39.5ccdbc49.k1905; olt=johnl-iecc.com@submit.iecc.com; bh=XBqzDHdWKmqyXi4OylwlXLYM4ip0ydYyKG/sCETF3yw=; b=cf9avHu9V++h2QC/loodEXqhetM31oaitPtI5zF3trl+TcQU7dSfZa5/gTjs0rqpW2BfT9HcnzlIyHDHakzHxeEbislig+4GAOkXjKTkhSHRij07I8XCy+FV5qmACg3oF6VJfwUQVvxLDCR7AyoeL23HTZ+wjvKUojInp+Nv6Q5dJZLYFOvJE7iih/yy2YlIrzL/fZk/LoN3PLpfukG32RXnEAPtMDabjW5+xRvupkSfOp605oKxq7MUEi2VIKXH
Received: from localhost ([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, johnl@iecc.com) via TCP6; 04 May 2019 16:22:33 -0000
Date: Sat, 04 May 2019 12:22:32 -0400
Message-ID: <alpine.OSX.2.21.1905041208370.64085@ary.qy>
From: John R Levine <johnl@taugh.com>
To: Vladimír Čunát <vladimir.cunat+ietf@nic.cz>
Cc: dnsop@ietf.org
In-Reply-To: <84c709ae-a019-0341-be56-81e3550f3009@nic.cz>
References: <20190502205938.604982013404D1@ary.qy> <1b371074-2500-40ec-2627-00b3f46e8114@nic.cz> <alpine.OSX.2.21.1905031108440.61118@ary.qy> <84c709ae-a019-0341-be56-81e3550f3009@nic.cz>
User-Agent: Alpine 2.21 (OSX 202 2017-01-01)
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="0-2093992115-1556986953=:64085"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/_NjScbt9iadlhJ3pjEguI2R7gmM>
Subject: Re: [DNSOP] New draft, seeking comments: draft-sah-resolver-information
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Sat, 04 May 2019 16:22:38 -0000

>>> Resolver, at least.  On a related note, I'd also expect to send the name
>>> as SNI by default; 8.8.8.8 was not even sending me a certificate unless
>>> I sent SNI (only when using TLS 1.3 though)
>>
>> When I said verify by name I meant by DNS name, so the certs can be
>> signed by the existing ACME protocol or whatever.
>
> I also meant verification by DNS (host)name in certificate's CN, signed
> by some commonly accepted authority.  I don't know where the
> misunderstanding is.

Oh, OK, it sounded like you would ask for SNI for an IP.

Google's servers are inconsistent.  When I connect to 8.8.8.8 it's OK with 
no SNI, but 8.8.4.4 wants an SNI host name, not an IP.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly

v2.23.0 | Report a Bug | By Email