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

Frederico A C Neves <fneves@registro.br> Tue, 13 March 2018 15:59 UTC

Return-Path: <fneves@registro.br>
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 5FFD612E04B for <dnsop@ietfa.amsl.com>; Tue, 13 Mar 2018 08:59:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level:
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, 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 0UAnwDvBcPj0 for <dnsop@ietfa.amsl.com>; Tue, 13 Mar 2018 08:59:13 -0700 (PDT)
Received: from clone.registro.br (clone.registro.br [IPv6:2001:12ff:0:2::4]) (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 5FE54127419 for <dnsop@ietf.org>; Tue, 13 Mar 2018 08:59:09 -0700 (PDT)
Received: by clone.registro.br (Postfix, from userid 1000) id 601732942B0; Tue, 13 Mar 2018 12:59:07 -0300 (BRT)
Date: Tue, 13 Mar 2018 12:59:07 -0300
From: Frederico A C Neves <fneves@registro.br>
To: Joe Abley <jabley@90.212.199.in-addr.arpa>
Cc: Roland Bracewell Shoemaker <roland@letsencrypt.org>, dnsop@ietf.org
Message-ID: <20180313155907.GM62837@registro.br>
References: <B7531E71-AC04-4D40-86B0-74F2DCA92446@letsencrypt.org> <62E857A4-6184-4F1A-A6E2-16AC5C16F574@90.212.199.in-addr.arpa>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <62E857A4-6184-4F1A-A6E2-16AC5C16F574@90.212.199.in-addr.arpa>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/HcobBlzc5qCVp6z4DmVPrC-B9IQ>
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:59:17 -0000

On Tue, Mar 13, 2018 at 11:16:56AM -0400, Joe Abley wrote:
> On 12 Mar 2018, at 11:58, Roland Bracewell Shoemaker <roland@letsencrypt.org> wrote:
> 
> > After a number of discussions I’m interested in returning to the original concept as it simplifies a number of use cases that this document is intended to support but am still not sure whether or not this would be widely considered ‘ok’ by DNS folks. Obviously it’s entirely possible to do this as these child zones are delegated to users and they _can_ put whatever they want in them. Does this WG have strong opinions on whether we should/shouldn’t do this for technical reasons or we just being a bit too strict in our reading of 3172?
> 
> I think that if Tony can be dot@dotat.at, surely I can be jabley@90.212.199.in-addr.arpa.
> 
> A zone is a zone. ARPA is only special by convention, not by protocol.
> 

Sure. Extra data, people in less stocked address networks have being
following BCP20 with the extra trick of putting delegations and
associated glue inside the same in-addr.arpa zone for ages.

Fred