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

Jim Reid <jim@rfc1035.com> Tue, 13 March 2018 01:31 UTC

Return-Path: <jim@rfc1035.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 5345512420B for <dnsop@ietfa.amsl.com>; Mon, 12 Mar 2018 18:31:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] 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 AQb2b39SiVF0 for <dnsop@ietfa.amsl.com>; Mon, 12 Mar 2018 18:31:47 -0700 (PDT)
Received: from shaun.rfc1035.com (shaun.rfc1035.com [93.186.33.42]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E277D120721 for <dnsop@ietf.org>; Mon, 12 Mar 2018 18:31:46 -0700 (PDT)
Received: from gromit.rfc1035.com (gromit.rfc1035.com [195.54.233.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by shaun.rfc1035.com (Postfix) with ESMTPSA id 15ED4242147B; Tue, 13 Mar 2018 01:31:44 +0000 (UTC)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
From: Jim Reid <jim@rfc1035.com>
In-Reply-To: <ADC2635D-6C02-44EB-A95C-0656455E5E88@vpnc.org>
Date: Tue, 13 Mar 2018 01:31:41 +0000
Cc: dnsop WG <dnsop@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <E9E6A2DC-2EC3-4D06-9A75-47F99BFC0360@rfc1035.com>
References: <B7531E71-AC04-4D40-86B0-74F2DCA92446@letsencrypt.org> <0EE4F82D-AD7B-4D50-B415-6B5558B7E974@vpnc.org> <7B867A66-4B80-4070-ACA9-7C94A63FBC17@rfc1035.com> <A111B1F1-2AD5-472B-A261-77E8E815E679@vpnc.org> <F917A3E4-2F87-4670-8370-9DEA2E85D6B2@rfc1035.com> <ADC2635D-6C02-44EB-A95C-0656455E5E88@vpnc.org>
To: Paul Hoffman <paul.hoffman@vpnc.org>
X-Mailer: Apple Mail (2.3445.5.20)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/PMMqT9gJnKIvWRGL_dkHTaVi8GM>
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: Tue, 13 Mar 2018 01:31:48 -0000


> On 13 Mar 2018, at 00:07, Paul Hoffman <paul.hoffman@vpnc.org> wrote:
> 
> How could you use ACME to validate the IP address of a roving client or a P2P application that has no fixed IP address?

In pretty much the same way as ACME tokens would/could be used to validate clients that have (fixed) names.

Or perhaps these hypothetical IP-flavoured tokens contain a public key which could be used for opportunistic encryption with whatever’s at that IP address. Add hand-waving to taste.

At this very eary stage, questions shouldn’t about how these hypothericals will get implemented. I’m just giving some possible examples of use cases other than webbery, like you asked for. They might be bad or stupid use cases. Or turn out to be pointless. Or unworkable. Or all of the above. For now they’re just things that might be on the list that you, me and Roland eventually produce.