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

Ólafur Guðmundsson <olafur@cloudflare.com> Tue, 13 March 2018 15:18 UTC

Return-Path: <olafur@cloudflare.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 5E618126C22 for <dnsop@ietfa.amsl.com>; Tue, 13 Mar 2018 08:18:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cloudflare.com
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 oxIwpLsBbt89 for <dnsop@ietfa.amsl.com>; Tue, 13 Mar 2018 08:18:53 -0700 (PDT)
Received: from mail-wr0-x22e.google.com (mail-wr0-x22e.google.com [IPv6:2a00:1450:400c:c0c::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 11668126D73 for <dnsop@ietf.org>; Tue, 13 Mar 2018 08:18:53 -0700 (PDT)
Received: by mail-wr0-x22e.google.com with SMTP id k3so4388821wrg.6 for <dnsop@ietf.org>; Tue, 13 Mar 2018 08:18:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cloudflare.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=OKrhJT1pqbUr/lCGZ7/4r24XdBxTQYK62QhOaJm1EeM=; b=jkJFPLEfZcSe3GmsRi5G/rBghgZi52n2z6u5ah6x0jRm3Lo5EGrrnocCfO/Qukwk3+ Vu5dQ51yWRyN3R5dSp0ov9Ul+uO1P4A/5KH74bGUNnnOPI3UwZZOAe276HASwI3TUIYj LmORn3LI8FSTvbS8ULT14zGl/XWgM+FtvW9kw=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=OKrhJT1pqbUr/lCGZ7/4r24XdBxTQYK62QhOaJm1EeM=; b=jCFDCwMQPRsiyDU+rWj46cS2E1cE56inQPYq8RrFJ6v2fLdCwqfUgnCKzwTmHO0nFZ g/do/NBz2dtC+pC2kRNWYE29VObWXlNYyB2lP4knsMtUTBYZQVDd89L6DyITn76ayVJX XzImhEzNbtwhDn4Hp0vfYPbVcsVlrGx4jC5KoO6QBJVGAQeN7/MI1N/ukz6SHXX839bV 6ueLBXUnEKcl7+1H3AfEzSQHQ9p/B6eGVec1wQb+hURGecitHZ2YqCEIoyKhBBA5Uz7k 3Ktko9P8GP+fEkLnfgq/DM2otC7jW/45zH3uCS7863AiYx3xQ6GNPTKEn4GVyOLtjpyY elUg==
X-Gm-Message-State: AElRT7Ggfy5zgI8GVEQ2RCUaS740E9GtZYe0CdjuzA17VJlaDLKgCSfi xHHptXbXlfK4an98NccgRcMCrPXwnBvBMP7MgQn4YwXb
X-Google-Smtp-Source: AG47ELsK4qoWkwpqg6Bj0NQgObB433P+eqtfeZXEeBvSuDCVSONvEq92559ogsVtgYwDaYeiUXsEXgvko06ljr0hZQA=
X-Received: by 10.28.66.69 with SMTP id p66mr1138875wma.119.1520954331605; Tue, 13 Mar 2018 08:18:51 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.169.41 with HTTP; Tue, 13 Mar 2018 08:18:51 -0700 (PDT)
In-Reply-To: <62E857A4-6184-4F1A-A6E2-16AC5C16F574@90.212.199.in-addr.arpa>
References: <B7531E71-AC04-4D40-86B0-74F2DCA92446@letsencrypt.org> <62E857A4-6184-4F1A-A6E2-16AC5C16F574@90.212.199.in-addr.arpa>
From: =?UTF-8?B?w5NsYWZ1ciBHdcOwbXVuZHNzb24=?= <olafur@cloudflare.com>
Date: Tue, 13 Mar 2018 11:18:51 -0400
Message-ID: <CAN6NTqxNkL6Ga=VQbTaezCwHSB_MUg=yLM5Sq0N-x88b6zbfNw@mail.gmail.com>
To: Joe Abley <jabley@90.212.199.in-addr.arpa>
Cc: Roland Bracewell Shoemaker <roland@letsencrypt.org>, dnsop <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="001a114c0ceca7c59405674cc6c3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/830tK9ycUxGndnrJPQ76Quy7hzY>
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:18:55 -0000

On Tue, Mar 13, 2018 at 11:16 AM, Joe Abley <jabley@90.212.199.in-addr.arpa>
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.
>
> ^^ Joe spoke the truth

Olafur