Re: [DNSOP] WG review of draft-ietf-homenet-dot-03

Ralph Droms <rdroms.ietf@gmail.com> Tue, 21 March 2017 14:00 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 DDBCB12948B for <dnsop@ietfa.amsl.com>; Tue, 21 Mar 2017 07:00:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 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_LOW=-0.7, 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 lQemcARMyFtF for <dnsop@ietfa.amsl.com>; Tue, 21 Mar 2017 07:00:46 -0700 (PDT)
Received: from mail-qk0-x232.google.com (mail-qk0-x232.google.com [IPv6:2607:f8b0:400d:c09::232]) (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 CB9A6129408 for <dnsop@ietf.org>; Tue, 21 Mar 2017 07:00:46 -0700 (PDT)
Received: by mail-qk0-x232.google.com with SMTP id y76so135317033qkb.0 for <dnsop@ietf.org>; Tue, 21 Mar 2017 07:00:46 -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=bEZUGzT5WIMvLE4Zf1MKCt8XTRdD7OHqrSTFBjEYeY0=; b=e3v5NIsEOycdD+lNMnGBwQHjSvITBLGqfwlVoxrLF8vr/75pri2E1gUs7GeNlQ9q4G JDf/SQcf0w9b+wpALnnbZJLxiv5D6wntDrKe3ZvZABT4wxyDOQJvDH8wYxra6JXcjt7T syMGkYq5eS9Td1clFZ3J8hHWFOSCVvRM2gfif2Zu/uuJXA+ZJ5jjrNpONY1/9b5lnouU fvzQKA8VUmWdzgn92FM8wdM6PVL/hm8L3qRV8FR0z9W9MIiUWTFzfHIPe99C3vpTm8aJ gStf80zSIWJHFtl18+Ip5hz/YbLk8777J0sXB3KijF8LOQd+gMlOYnNkNa8Njguy/VbJ QOFw==
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=bEZUGzT5WIMvLE4Zf1MKCt8XTRdD7OHqrSTFBjEYeY0=; b=EL4q6k07U7zkZe41McsnZZITsr+kgU8PvDnWVEaVWyUs2TOaln/fMGJKM74VHX2n4B rfUxKC4onmhNIvV6EpDyhGVFnyrN6XsUZX2AdJcqWkKta8RzbTxtVylHxo0OG0p9ax88 O/B+Pn67xqQ+TFa/9QJcyhSe0SvHqQAyESaMkS6S3hXX2iVKuXKImWK2wlktrObkwrXm lIi8LecPiIyPURMtkJX4G8fVkLSiS/cbaiSKOk1s+kxDrthISQoUQfOsbICoDr0o7J4V ToT61F00uu7AIqfl9HBxBb57ngOKPmhlW4+vRfL1LaOYnZALfwg3GlmFz+TXo/o9Ly6M ilzA==
X-Gm-Message-State: AFeK/H1AM+hY+GBa4geKl2mYEOJMBjwQRFlTrDEQeFqu1DQkLrQb2hH5GKQWbwfpbG/zVA==
X-Received: by 10.55.190.69 with SMTP id o66mr29758276qkf.0.1490104845748; Tue, 21 Mar 2017 07:00:45 -0700 (PDT)
Received: from ?IPv6:2601:18f:801:600:f006:56a3:f121:7c9b? ([2601:18f:801:600:f006:56a3:f121:7c9b]) by smtp.gmail.com with ESMTPSA id h43sm8295624qth.7.2017.03.21.07.00.44 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 21 Mar 2017 07:00:45 -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: <20170321042249.GK27276@mx4.yitter.info>
Date: Tue, 21 Mar 2017 10:00:43 -0400
Cc: dnsop@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <9D868A95-0C04-4BE9-84A2-F41B53E791E0@gmail.com>
References: <1E14B142-680B-4E30-809B-68E03EB6E326@gmail.com> <61FD3EE3-3043-4AB1-9823-6A9D61B1438C@vigilsec.com> <BE2A3845-D8AA-433A-9F00-1056ECFD335F@fugue.com> <21C8F856-FE3F-42A6-A8ED-888D0797B68B@vigilsec.com> <60C85486-E351-4C42-ADEB-FCBB56F4EA27@fugue.com> <AB11455F-7E43-4CB3-9F13-DB6A09F739EB@vigilsec.com> <CEC8CC6A-861A-471C-B7FA-4BB05C81CCF0@gmail.com> <20170321042249.GK27276@mx4.yitter.info>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/wcJhMY0V6wn0_G4e9Ib0cLfT2Io>
Subject: Re: [DNSOP] WG review of draft-ietf-homenet-dot-03
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, 21 Mar 2017 14:00:49 -0000

> On Mar 21, 2017, at 12:22 AM, Andrew Sullivan <ajs@anvilwalrusden.com> wrote:
> 
> Hi,
> 
> On Mon, Mar 20, 2017 at 01:14:25PM -0400, Ralph Droms wrote:
> 
>> Russ - In my opinion, the special-use domain registry is not being
>> used to put the name in the root zone.  The observation is that the
>> special-use definition of this TLD requires both an entry in the
>> special-use domain name registry, and an entry in the root zone
> 
> I am having a hard time making the above two sentences consistent.
> This special-use case requires an entry in the root zone, and so by
> definition the entry into one (the special-use registry) with
> processing rules that require normal DNS processing, combined with the
> request for a provably-insecure delegation, is either incoherent or
> else links the two registries.  I don't know which it is, but I see no
> way it can be other than one of them.

Let me try again...  As I see the process, draft-ietf-homenet-dot-03 defines the protocol behaviors for ".homenet".  draft-ietf-homenet-dot-03 requests an entry in the root zone for .homent and an entry in the special-use names registry.  While those two actions are related, and the entry in the special-use names registry may describe behavior that depends on the entry in the root zone, I think of the request for the entry in the root zone as coming explicitly from draft-ietf-homenet-dot-03 rather than implicitly from the entry in the special-use names registry.

The point I'm trying to make is that making the entry in the special-use names registry is not a back door to an entry in the root zone.  The request for the entry in the root zone has to be explicit; in this case, in draft-ietf-homenet-dot-03.

- Ralph

> 
> Best regards,
> 
> A
> 
> -- 
> Andrew Sullivan
> ajs@anvilwalrusden.com
> 
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop