Re: [dbound] [dmarc-ietf] Fwd: New Version Notification for draft-dcrocker-dns-perimeter-00.txt

Dave Crocker <dhc@dcrocker.net> Thu, 04 April 2019 02:54 UTC

Return-Path: <dhc@dcrocker.net>
X-Original-To: dbound@ietfa.amsl.com
Delivered-To: dbound@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 13F46120153 for <dbound@ietfa.amsl.com>; Wed, 3 Apr 2019 19:54:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 (1024-bit key) header.d=dcrocker.net
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 kEP79dq5SAAQ for <dbound@ietfa.amsl.com>; Wed, 3 Apr 2019 19:54:23 -0700 (PDT)
Received: from simon.songbird.com (simon.songbird.com [72.52.113.5]) (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 7B1C31200F1 for <dbound@ietf.org>; Wed, 3 Apr 2019 19:54:23 -0700 (PDT)
Received: from [192.168.1.85] (108-226-162-63.lightspeed.sntcca.sbcglobal.net [108.226.162.63]) (authenticated bits=0) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1.1) with ESMTP id x342u1k7013845 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 3 Apr 2019 19:56:01 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=default; t=1554346562; bh=FLlYN4FSnr4VR+s8HFghhV5sB9HSY4ZYLKez461noQc=; h=Subject:To:Cc:References:From:Reply-To:Date:In-Reply-To:From; b=MgOswz3M3Aq7dfmCunhOfx7R0zqSeAO7cFiszh6Z3EacplR6ctAdvCHcRaLtPks8g LcZ6ioAYclj+Xh8x0cVNWkDHLddta6rEJY2iQuzEDo2K5GRuTl5LBpbiuaO6FALlPv qQyTUC5kfd0oMBlp2jwUTXkgqcAEBmFiGTiJGDpI=
To: "John R. Levine" <johnl@iecc.com>
Cc: tjw ietf <tjw.ietf@gmail.com>, dbound@ietf.org
References: <20190403175820.8391420115F376@ary.qy> <2445c121-f77b-0fa2-ca6a-402479abb5a7@dcrocker.net> <alpine.OSX.2.21.1904031430270.21189@ary.qy> <7e61b445-3844-f769-6a59-16fa396388d0@dcrocker.net> <alpine.OSX.2.21.1904031459480.21189@ary.qy> <AFE01C0B-E47E-4D4E-B60C-FA0810BBE8F8@gmail.com> <310cc611-e1f0-2fbb-6efe-9d266869d025@dcrocker.net> <alpine.OSX.2.21.1904032056230.22661@ary.qy> <da2b2c91-8b9f-1254-d159-997bb77c1a9e@bbiw.net> <alpine.OSX.2.21.1904032126480.22887@ary.qy> <a5f53382-b1f5-bf9b-aa3e-1fc2e93786f4@bbiw.net> <alpine.OSX.2.21.1904032148150.22920@ary.qy>
From: Dave Crocker <dhc@dcrocker.net>
Reply-To: dcrocker@bbiw.net
Organization: Brandenburg InternetWorking
Message-ID: <0ccf632e-aade-3611-3beb-15b81e35679a@dcrocker.net>
Date: Wed, 3 Apr 2019 19:54:12 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <alpine.OSX.2.21.1904032148150.22920@ary.qy>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dbound/sJuSDX_Xzsp9VL2m6D7vd-R6zps>
Subject: Re: [dbound] [dmarc-ietf] Fwd: New Version Notification for draft-dcrocker-dns-perimeter-00.txt
X-BeenThere: dbound@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DNS tree bounds <dbound.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dbound>, <mailto:dbound-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dbound/>
List-Post: <mailto:dbound@ietf.org>
List-Help: <mailto:dbound-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dbound>, <mailto:dbound-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Apr 2019 02:54:26 -0000

On 4/3/2019 7:14 PM, John R. Levine wrote:
> That bit in the parentheses, who does the modifying, and how does it get 
> into the running versions of BIND and NSD and PowerDNS and all the other 
> DNS servers and caches that people use?

You appear to be confusing 'adding to an implementation' with 'changing 
the protocol'.  Modifying the protocol is changing DNS.  Adding code 
might or might not be and in this case, it isn't.  It is adding a /use/ 
of /existing/ DNS mechanisms.  That's not 'changing the DNS'.


> Although now that I think about it, it won't work anyway.  For one 
> thing, if you ask for _perim.a.b.c.tld, and there is only _perim.c.tld, 
> the DNS response will be an NXDOMAIN and I don't think that DNS clients 
> expect to find additional records in an NXDOMAIN response.  Or if we 
> wave our hands some more and somehow make it a NODATA (positive response 
> with no records), the fact that there's _perim.c.tld in the additional 
> section doesn't mean that there wouldn't also be _perim.b.c.tld if you 
> asked for it.  There's another whole set of failures if there's a zone 
> cut between the name you ask for and the _perim above it.

The NXDomain looks like an interesting bit of inconvenience.  Have to 
think about it some more.

And yes, zone boundaries are always fun.  But since these are names that 
are, by definition, within a single administrative scope, I suspect 
that's solvable too.


> Don't take my word for it, ask in dnsop.  Or perhaps Tim has some opinions.
I already sent a note to dnsop, inviting them to dbound for this discussion.

d/


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net