IETF Logo Mail Archive

Re: [DNSOP] Question about usage of ip6.arpa and in-addr.arpa

"Paul Hoffman" <paul.hoffman@vpnc.org> Mon, 12 March 2018 23:27 UTC

Return-Path: <paul.hoffman@vpnc.org>
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 5AAED124F57 for <dnsop@ietfa.amsl.com>; Mon, 12 Mar 2018 16:27:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=no
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 i9uSchAo-VkM for <dnsop@ietfa.amsl.com>; Mon, 12 Mar 2018 16:27:49 -0700 (PDT)
Received: from mail.proper.com (Opus1.Proper.COM [207.182.41.91]) (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 3669D124BFA for <dnsop@ietf.org>; Mon, 12 Mar 2018 16:27:49 -0700 (PDT)
Received: from [10.32.60.132] (50-1-51-141.dsl.dynamic.fusionbroadband.com [50.1.51.141]) (authenticated bits=0) by mail.proper.com (8.15.2/8.15.2) with ESMTPSA id w2CNRGov084304 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 12 Mar 2018 16:27:17 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: mail.proper.com: Host 50-1-51-141.dsl.dynamic.fusionbroadband.com [50.1.51.141] claimed to be [10.32.60.132]
From: Paul Hoffman <paul.hoffman@vpnc.org>
To: Jim Reid <jim@rfc1035.com>
Cc: dnsop WG <dnsop@ietf.org>
Date: Mon, 12 Mar 2018 16:27:45 -0700
X-Mailer: MailMate (1.10r5443)
Message-ID: <A111B1F1-2AD5-472B-A261-77E8E815E679@vpnc.org>
In-Reply-To: <7B867A66-4B80-4070-ACA9-7C94A63FBC17@rfc1035.com>
References: <B7531E71-AC04-4D40-86B0-74F2DCA92446@letsencrypt.org> <0EE4F82D-AD7B-4D50-B415-6B5558B7E974@vpnc.org> <7B867A66-4B80-4070-ACA9-7C94A63FBC17@rfc1035.com>
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/LbdZUD-iuZyPkwSHVJq1h2SSkeo>
Subject: Re: [DNSOP] Question about usage of ip6.arpa and in-addr.arpa
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
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: Mon, 12 Mar 2018 23:27:50 -0000


On 12 Mar 2018, at 16:12, Jim Reid wrote:

>> On 12 Mar 2018, at 17:37, Paul Hoffman <paul.hoffman@vpnc.org> wrote:
>>
>> If the use case here is to be able to issue certificates for TLS 
>> servers based on the IP address instead of the domain name, creating 
>> something new in the DNS may be overkill. That is, why even have 
>> Section 4.1 of draft-ietf-acme-ip at all? What's wrong with only 
>> having direct HTTPS access?
>
> Is web the only protocol that runs on the Internet now? I realise that 
> might seem to be the case these days, but even so... :-)

For which other protocols did you want certificates with IP addresses as 
identifiers? If your list is longer than zero, are you willing to help 
Roland with a solution using DNS records for validation that has any 
chance of being usable? (No smiley here.)

--Paul Hoffman

v2.23.0 | Report a Bug | By Email