Re: [DNSOP] Interim DNSOP WG meeting on Special Use Names: some reading material

Mark Andrews <marka@isc.org> Fri, 08 May 2015 21:02 UTC

Return-Path: <marka@isc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DCD241AD05F for <dnsop@ietfa.amsl.com>; Fri, 8 May 2015 14:02:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level:
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 saLrMDHhmbL4 for <dnsop@ietfa.amsl.com>; Fri, 8 May 2015 14:02:04 -0700 (PDT)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A1B7F1A90F8 for <dnsop@ietf.org>; Fri, 8 May 2015 14:02:04 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx.ams1.isc.org (Postfix) with ESMTPS id EA9601FCAEB; Fri, 8 May 2015 21:02:01 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id 9F6E716004E; Fri, 8 May 2015 21:02:16 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 8096216008A; Fri, 8 May 2015 21:02:16 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id CmdMtAITHM60; Fri, 8 May 2015 21:02:16 +0000 (UTC)
Received: from rock.dv.isc.org (c122-106-161-187.carlnfd1.nsw.optusnet.com.au [122.106.161.187]) by zmx1.isc.org (Postfix) with ESMTPSA id 14FCF16004E; Fri, 8 May 2015 21:02:16 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id 93FCB2DF5464; Sat, 9 May 2015 07:02:06 +1000 (EST)
To: John R Levine <johnl@taugh.com>
From: Mark Andrews <marka@isc.org>
References: <20150508194223.55320.qmail@ary.lan> <20150508203559.ACC372DF52BA@rock.dv.isc.org> <alpine.OSX.2.11.1505081636310.30695@ary.lan>
In-reply-to: Your message of "08 May 2015 16:37:24 -0400." <alpine.OSX.2.11.1505081636310.30695@ary.lan>
Date: Sat, 09 May 2015 07:02:05 +1000
Message-Id: <20150508210206.93FCB2DF5464@rock.dv.isc.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/u64zSTcquHplCe0qMPsh-vOqo4w>
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] Interim DNSOP WG meeting on Special Use Names: some reading material
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 08 May 2015 21:02:06 -0000

In message <alpine.OSX.2.11.1505081636310.30695@ary.lan>, "John R Levine" write
s:
> > I'm not, but name leaking is different to name use.  I suspect "mail"
> > ends up being qualified whereas "home" and "corp" are actually used as
> > private tlds.  This difference requires different handling.
> 
> From the viewpoint of the outside world, what would be different?

The type of response you send back has a impact.

For a "mail" a secure NXDOMAIN response saying that "mail." doesn't exist
should be fine.

For "foo.home" you actually want a insecure response with a insecure
referal or at least you want "DS home" to come back as a secure
NODATA rather than a secure NXDOMAIN.  This assumes we want to
formalise the defacto use of .home for names in the home.

"corp" would be similar to "home" technically.  The arguments for
formalising ".corp" would be different as most corporations already
have namespace in the global DNS from which they can make their own
private namespace delegation whereas most homes don't.

Mark

> Regards,
> John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
> Please consider the environment before reading this e-mail.
> 
> PS: I'm not being deliberately obtuse, I'm being actually obtuse.
> 
> 
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org