Re: [DNSOP] .arpa

Ralph Droms <rdroms.ietf@gmail.com> Fri, 24 March 2017 02:28 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 D4F041296FA for <dnsop@ietfa.amsl.com>; Thu, 23 Mar 2017 19:28:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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] 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 RjDQOin4C2s3 for <dnsop@ietfa.amsl.com>; Thu, 23 Mar 2017 19:28:45 -0700 (PDT)
Received: from mail-qt0-x22f.google.com (mail-qt0-x22f.google.com [IPv6:2607:f8b0:400d:c0d::22f]) (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 3C599129417 for <dnsop@ietf.org>; Thu, 23 Mar 2017 19:28:45 -0700 (PDT)
Received: by mail-qt0-x22f.google.com with SMTP id x35so1310897qtc.2 for <dnsop@ietf.org>; Thu, 23 Mar 2017 19:28:45 -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=H3YtQIz8TUs+R7xr4hByT3l5JZL2iphrutbGp9CFdqA=; b=gtlbPMPwrgZXmvPXWjsBIw+tVotwjvoEhK5MIRy4VWpJs9vYMQQiojh5OTce/XO8Wn Zx4YUTInU1ob+QNZyKoAqoCNtl+cwVhnPRoNYQCZIzIn/jPzJVEOFGjv+1JtGFq8rhAF Sa36GHjCyUt9icIZeOB1A12I6/VB0fIqSO9wfeZMwbfkxj7rbVCZSUVMQsY4AGqEtORB NYVKJQnsPeDSM8RUTbn2RS9eycSdOwXAQqndEPFHpumRxP047iuQnvt5bojGvTjnTQ80 ubAB77R7JAIT8HDAAWSiKKZBx0fSdG2RoExM4qKgxUNknGRbjFF+Ad1LowtU2oUPJxKM jEdw==
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=H3YtQIz8TUs+R7xr4hByT3l5JZL2iphrutbGp9CFdqA=; b=gGpEw+Ta/ZD8YIJBMUuEyIXBQd7ApuBwHAunem7ITwgiw0X8PH3L4YdqWpmWom8Shu +D9EkRQiq6uoXP8Kpmu9//IQQN/ObUCjVroy6+BwuCHO49SZ4IqU88ShN4hZLeXkZXjX iZPlaKvT+t6uQiGa7wmeISKAp1PVVKKkfnsvb6OYkIumSXhbjOyvK4wMLk8zymRbYUW/ TV0NWQhLf3qDrIC94lT4EpNVRgcWfyDijK3Xkl3cPFDjdWS02L9YzFixstoS2kNbFRsS SnztHpN87TK/tAXfa2O6kge1KlGrPWk7OsRyPs4qh2UkjRGhl6/kgCrpLxFL2/XOunK3 800Q==
X-Gm-Message-State: AFeK/H3HQzHKyKtklZsj8FFcMXDU31zgexLlzevXnb8tHrsTaYlMzdIT8NTGnBgGTzx6GA==
X-Received: by 10.200.52.52 with SMTP id u49mr5383340qtb.101.1490322524313; Thu, 23 Mar 2017 19:28:44 -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 g15sm613924qte.58.2017.03.23.19.28.43 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 23 Mar 2017 19:28:43 -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: <18A3100E-2135-4FD0-811A-394DDE56EC94@fugue.com>
Date: Thu, 23 Mar 2017 22:28:42 -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: <07AFEFF0-C846-462E-9517-CA10A8D23877@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> <77CC814A-823F-4239-8853-97D771F02490@gmail.com> <18A3100E-2135-4FD0-811A-394DDE56EC94@fugue.com>
To: Ted Lemon <mellon@fugue.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/hCOhe84mX67fACLzP76vWXxAm00>
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: Fri, 24 Mar 2017 02:28:47 -0000

> On Mar 23, 2017, at 5:54 PM, Ted Lemon <mellon@fugue.com> wrote:
> 
> On Mar 23, 2017, at 5:47 PM, Ralph Droms <rdroms.ietf@gmail.com> wrote:
>> 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.
> 
> Is this even necessary?

"this" == "differentiate homenet from DNS"?

>   The MoU uses the example of in-addr.arpa, which is resolved using the DNS protocol, so from the perspective of the MoU, I don't think it is.
> 

I was mostly referring to the idea that DNSSEC will work because the homenet name resolution mechanism is "just DNS".  I thought it was important to point out that homenet name resolution isn't exactly DNS, so we should be careful to make assumptions about its behavior based on DNS.

- Ralph