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

Joe Abley <jabley@90.212.199.in-addr.arpa> Tue, 13 March 2018 15:29 UTC

Return-Path: <jabley@90.212.199.in-addr.arpa>
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 9EDB7127342 for <dnsop@ietfa.amsl.com>; Tue, 13 Mar 2018 08:29:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.996
X-Spam-Level:
X-Spam-Status: No, score=-0.996 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RDNS_NONE=0.793, T_DKIM_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (OpenSSL error: data too large for key size)" header.d=automagic.org
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 zTtnPJgychhr for <dnsop@ietfa.amsl.com>; Tue, 13 Mar 2018 08:29:23 -0700 (PDT)
Received: from mail.hopcount.ca (unknown [IPv6:2001:4900:1:392::156]) (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 BDDDB126C22 for <dnsop@ietf.org>; Tue, 13 Mar 2018 08:29:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=simple/simple; d=automagic.org ; s=hopcount; h=To:References:Message-Id:Content-Transfer-Encoding:Cc:Date: In-Reply-To:From:Subject:Mime-Version:Content-Type:Sender:Reply-To:Content-ID :Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To: Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe :List-Post:List-Owner:List-Archive; bh=7VqBJYIY1Gcd6OKLVXQPNZav8K744zTavwSNFWhemR4=; b=t2fEuHERC11sbhZdHDTAmF6R5E 0cBrZQjRhJBjQtWZEWZKFsp3e4hYVXcbwEUlbw3ZCOIfJ64VN/xgtj5P4hUqhnFxQ6H/bkZj6BtD6 bHpDZm+ecyhD3fSPH4z6pULenjiSfO6pvaAY2k7Dkj+OokfJb27yBlhrF8+RnF0xHi+w7kneJxdN7 KTY3N3+nV1grmqcsWf2y0u89mg1ZOnk7K7XLQbyJmNpegZrPXFR5fH7l7LiMhQFIiS+PxgljwhsyJ 44ZcODhw5xbGoHoau5L01ZRVJkRAeV1DvDb2IQznLdAGwSZKZNxS6y0ykePsVixJgqeAQXy/waOyc BamhvqCg==;
Received: from [199.91.196.11] (helo=[10.196.200.90]) by mail.hopcount.ca with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89 (FreeBSD)) (envelope-from <jabley@90.212.199.in-addr.arpa>) id 1evlrd-0009LX-Py; Tue, 13 Mar 2018 15:29:22 +0000
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
From: Joe Abley <jabley@90.212.199.in-addr.arpa>
In-Reply-To: <alpine.DEB.2.11.1803131451330.27680@grey.csi.cam.ac.uk>
Date: Tue, 13 Mar 2018 11:29:20 -0400
Cc: Roland Bracewell Shoemaker <roland@letsencrypt.org>, dnsop@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <A1E882E7-E019-4CC9-A7AD-6907B631B107@90.212.199.in-addr.arpa>
References: <B7531E71-AC04-4D40-86B0-74F2DCA92446@letsencrypt.org> <alpine.DEB.2.11.1803131451330.27680@grey.csi.cam.ac.uk>
To: Tony Finch <dot@dotat.at>
X-Mailer: Apple Mail (2.3445.5.20)
X-SA-Exim-Connect-IP: 199.91.196.11
X-SA-Exim-Mail-From: jabley@90.212.199.in-addr.arpa
X-SA-Exim-Scanned: No (on mail.hopcount.ca); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/Ttvz3m_x7PyS6czeT-K9VQYQeqY>
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 15:29:25 -0000

On 13 Mar 2018, at 10:55, Tony Finch <dot@dotat.at> wrote:

> From the operational point of view, you're going to bump into a lot of
> annoying road blocks: undelegated reverse DNS, provisioning systems that
> only allow for PTR, etc.

Data point: Google's MXes evidently have no interest accepting mail from me directly when I use this e-mail address :-)


Joe