[Doh] IP address certificates

Paul Hoffman <paul.hoffman@icann.org> Fri, 15 March 2019 16:21 UTC

Return-Path: <paul.hoffman@icann.org>
X-Original-To: doh@ietfa.amsl.com
Delivered-To: doh@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id B8002127133 for <doh@ietfa.amsl.com>; Fri, 15 Mar 2019 09:21:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 5z4IxVdaHDqP for <doh@ietfa.amsl.com>; Fri, 15 Mar 2019 09:21:57 -0700 (PDT)
Received: from out.west.pexch112.icann.org (out.west.pexch112.icann.org []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 54532129284 for <doh@ietf.org>; Fri, 15 Mar 2019 09:21:57 -0700 (PDT)
Received: from PMBX112-W1-CA-1.pexch112.icann.org ( by PMBX112-W1-CA-1.pexch112.icann.org ( with Microsoft SMTP Server (TLS) id 15.0.1367.3; Fri, 15 Mar 2019 09:21:55 -0700
Received: from PMBX112-W1-CA-1.pexch112.icann.org ([]) by PMBX112-W1-CA-1.PEXCH112.ICANN.ORG ([]) with mapi id 15.00.1367.000; Fri, 15 Mar 2019 09:21:55 -0700
From: Paul Hoffman <paul.hoffman@icann.org>
To: DoH WG <doh@ietf.org>
Thread-Topic: IP address certificates
Thread-Index: AQHU20s053m571RCmE2FnR+Zj5DstQ==
Date: Fri, 15 Mar 2019 16:21:55 +0000
Message-ID: <F680895B-2BCA-48D9-8C28-C34E93BF73A3@icann.org>
References: <CAHbrMsCNyeabhk0sVexOHVedVkgG2dvV9T8wWL++om5juAUvEw@mail.gmail.com> <ED16E0D8-BBCB-4316-A116-BA8513F523A3@sky.uk>
In-Reply-To: <ED16E0D8-BBCB-4316-A116-BA8513F523A3@sky.uk>
Accept-Language: en-US
Content-Language: en-US
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: []
Content-Type: text/plain; charset="utf-8"
Content-ID: <7ED5796D5E4FED40B1B15DD51DFA7F13@pexch112.icann.org>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/qf7Q-uXthUyaEz7mDR4WovJSVu8>
Subject: [Doh] IP address certificates
X-BeenThere: doh@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DNS Over HTTPS <doh.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/doh>, <mailto:doh-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/doh/>
List-Post: <mailto:doh@ietf.org>
List-Help: <mailto:doh-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/doh>, <mailto:doh-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Mar 2019 16:22:00 -0000

For clarity: in draft-ietf-doh-resolver-associated-doh, IP address certificates are only used when getting the DoH servers using HTTPS. The format for that query is:

On Mar 15, 2019, at 6:41 AM, Winfield, Alister <Alister.Winfield=40sky.uk@dmarc.ietf.org> wrote:
> 	• IP-address certificates
> Bad ! Especially if the less enlightened think to try to create a certificate for a private IP. Very bad idea.

Can you say why they are bad? They are not common, but they are certainly available and have proven useful in some environments for a long time.

--Paul Hoffman