IETF Logo Mail Archive

Re: [DNSOP] .arpa

Ralph Droms <rdroms.ietf@gmail.com> Thu, 23 March 2017 21:47 UTC

Return-Path: <rdroms.ietf@gmail.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 DCDAF13167B for <dnsop@ietfa.amsl.com>; Thu, 23 Mar 2017 14:47:52 -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, FREEMAIL_FROM=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 (2048-bit key) header.d=gmail.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 ZpODyTF6dmnN for <dnsop@ietfa.amsl.com>; Thu, 23 Mar 2017 14:47:51 -0700 (PDT)
Received: from mail-qk0-x242.google.com (mail-qk0-x242.google.com [IPv6:2607:f8b0:400d:c09::242]) (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 3A86C129542 for <dnsop@ietf.org>; Thu, 23 Mar 2017 14:47:51 -0700 (PDT)
Received: by mail-qk0-x242.google.com with SMTP id v127so32202374qkb.1 for <dnsop@ietf.org>; Thu, 23 Mar 2017 14:47:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=/aALtc8pqHTeivCNXOsqmW/4QT8moUI6mCna1IibSNM=; b=bmfjfGBOURKogeqsgTLirbvaAhVQGncFUP5MLuTjJExb22rD4D3+oB2IBq6/3T0bCL kabgRsmQUYklwOKn+Us2ydiYI4fNWFqFc2blvWB7UjDV1YVASDJKBT2Fe96WLOyFh7R9 AMyHTpEf5fzVDAcVIUsozv41IBobbH0JN2braLrnGbiENh/Gc6T9pn+9fKQAzG5T2kDj 4Ap4fVl1EcN9pi0v+emzPsGlVriuWgY8+bRFGsBWO2j4aRJtX6OWBssuu/QVwI/4ciR/ Ha7+nJnDGjCsWVfrFiBmFedQNB/0G0fWKJiR9KRswixe8+MhPQxaROOOu3I5fSOPXn3P 9HsQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=/aALtc8pqHTeivCNXOsqmW/4QT8moUI6mCna1IibSNM=; b=aSrcsQEOcPgdqBiHoP1MPX5Qo6NUwtHq5B0TAV+woM0wN933rmysqao77p7e1++tXo u7cUMnq7WetY8iFrq8ma6SEoCWC0YZc1qIhIapXIrELWm4qxqOHouSMNG2PjLxIZcJ0y 2+uvkVZx7nSntNnNLXM8xXB8ZD56fvBVTQqwMTcAKa/ftZaRlVFgDFepyO5webXODaGY iMq+3KDxSkfd7G/G5rFPAT5YPwMtqk+KvSXkvCQu/q0nY+pntIWxLOJ24yWc6ucBWwOu wAf1g2Rgw5IqXYydy2liHpqMvq6Vfbgz2G9layP3n2HucEX9AxwXYdTd5yeKLaX/HH30 wwQg==
X-Gm-Message-State: AFeK/H0bF8Wm9f2nNNJIRPMa1TAb5NA8cDI5eHvh7mY9OcnJ4PMpTRvw/RR6vC5H4W0jtQ==
X-Received: by 10.55.66.65 with SMTP id p62mr4203392qka.191.1490305670407; Thu, 23 Mar 2017 14:47:50 -0700 (PDT)
Received: from ?IPv6:2601:18f:801:600:6978:b683:5f6a:4f3e? ([2601:18f:801:600:6978:b683:5f6a:4f3e]) by smtp.gmail.com with ESMTPSA id o92sm201536qkh.48.2017.03.23.14.47.49 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 23 Mar 2017 14:47:49 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <F5854071-6507-444B-90DB-B0CF0C27B7D0@fugue.com>
Date: Thu, 23 Mar 2017 17:47:48 -0400
Cc: Ray Bellis <ray@bellis.me.uk>, IETF dnsop Working Group <dnsop@ietf.org>, matt@kahlerlarson.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <77CC814A-823F-4239-8853-97D771F02490@gmail.com>
References: <20170323042741.79108.qmail@ary.lan> <2C6B4EB6-D0F0-44A8-95E4-68DF32244639@fugue.com> <20170323163205.GD19105@mx4.yitter.info> <500af1ed-5425-4452-ad8e-c2d511ee738d@bellis.me.uk> <850A8729-8762-4375-90EF-50CDF4AC232E@gmail.com> <47548136-78d7-8c53-462e-62439d6194ac@bellis.me.uk> <360B2807-049F-4707-95FE-AA279C583884@gmail.com> <F5854071-6507-444B-90DB-B0CF0C27B7D0@fugue.com>
To: Ted Lemon <mellon@fugue.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/KXAauJRLPcLGxED99MJp5ow_17c>
Subject: Re: [DNSOP] .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: Thu, 23 Mar 2017 21:47:53 -0000

> On Mar 23, 2017, at 2:30 PM, Ted Lemon <mellon@fugue.com> wrote:
> 
> On Mar 23, 2017, at 2:11 PM, Ralph Droms <rdroms.ietf@gmail.com> wrote:
>> No snark intended, but if "the protocol" were really just DNS, we wouldn't be having this discussion.  Rather, it is the DNS wire protocol using a local resolution context rather than the root zone.  In any event, yes, the locally server homenet zone can function with DNSSEC.
> 
> So do locally-served zones, by this definition, use a different protocol?

As Matt Larson just pointed out, "different protocol" may turn into a distraction.  .homenet is asking for an entry in the special-use domain name registry and a specific kind of entry in the DNS root zone.  I take those characteristics to differentiate homenet, perhaps as an extension or variant of DNS.

- Ralph

>

v2.23.0 | Report a Bug | By Email