IETF Logo Mail Archive

Re: [DNSOP] New Version Notification for draft-hoffman-dns-terminology-00.txt

John R Levine <johnl@taugh.com> Fri, 28 November 2014 21:22 UTC

Return-Path: <johnl@iecc.com>
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 0F8341A1B4A for <dnsop@ietfa.amsl.com>; Fri, 28 Nov 2014 13:22:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.137
X-Spam-Level:
X-Spam-Status: No, score=-1.137 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_PASS=-0.001] autolearn=no
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 zUEgtrG9RTSM for <dnsop@ietfa.amsl.com>; Fri, 28 Nov 2014 13:22:07 -0800 (PST)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BB1A11A1B44 for <dnsop@ietf.org>; Fri, 28 Nov 2014 13:22:06 -0800 (PST)
Received: (qmail 7685 invoked by uid 100); 28 Nov 2014 21:22:03 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:from:to:cc:subject:in-reply-to:message-id:references:mime-version:content-type:user-agent:cleverness; s=1e04.5478e77b.k1411; i=johnl@user.iecc.com; bh=hQEEbDdg1eRBESA8VmDjfmAPapgDkQa2gh8YVzbPS/Y=; b=aaGbTKVusu7H+8lguwvPANqcozBScx/dLcByOXWxGcNKpapKT+W6k/o7YsFcuG1AZb1Z4bYt4Bq8Z9HUKuLj/Je82tw/UUo7iSv30+VQdOs3vIQgvpCubHeSiK84quq4MDx5FskKrv0LBNsqzmLdid3Dn2pdJ4oa045s7qU+5+/+lMbWV0n5RLKG28IEK940fFssrIHJSsN+FmTzeDFPZRsK4jHU27Ik8of1iqlAytObtTrIQoL1HmI7bZZUjvnV
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:from:to:cc:subject:in-reply-to:message-id:references:mime-version:content-type:user-agent:cleverness; s=1e04.5478e77b.k1411; olt=johnl@user.iecc.com; bh=hQEEbDdg1eRBESA8VmDjfmAPapgDkQa2gh8YVzbPS/Y=; b=N/v1UTPpKfzGb+A2IPyIZ3+PW0KB6a/mknNtkLpoSuwHPRYr3k1PoKi6BSSF/YeNfLJhSztOttiWMJ1Z9JLmP7hAVM/DS1LtbgniizSdGxevRjIXWw8wXDEk9XRwkQPh6vZZ6OyyHS9bqoX3DsZiX2lUlO2SBcoLMjrF2hGSr36zSpDsE9KvXVNIROLwrShITEIWZzErVlYyG7411St1AIX5v2fRtRk4m/Gf+wbR9Hqb/Fs51Hi5EmgiNLwgV43/
Date: Fri, 28 Nov 2014 16:22:03 -0500
From: John R Levine <johnl@taugh.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <D450F722-32B8-4724-B540-D0CF2944E192@vpnc.org>
Message-ID: <alpine.BSF.2.11.1411281611510.6637@miucha.iecc.com>
References: <20141128163818.28938.qmail@ary.lan> <D450F722-32B8-4724-B540-D0CF2944E192@vpnc.org>
User-Agent: Alpine 2.11 (BSF 23 2013-08-11)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/90wE_HhCB7Fn3VifSbHtpThKA3Y
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] New Version Notification for draft-hoffman-dns-terminology-00.txt
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, 28 Nov 2014 21:22:08 -0000

>> with search pages.  Something like default vs. non-default or opt-in vs. opt-out
>> would describe it better.
>
> I don't think "default policy-implementing resolver" makes any sense. 
> While "opt-in policy-implementing resolver" does make sense, "opt-out 
> policy-implementing resolver" does not. I'm not as concerned about the 
> rathole as you are, but I certainly don't want to use terms that make no 
> sense.

I meant default as in it's the one configured by default for a provider's 
users, e.g., by DHCP.

The ISPs I know of that have policy resolvers to rewrite NXDOMAIN 
configure them by default, but provide some way for users to opt out so 
they get the real result instead.  I don't particularly care what the 
wording is so long as it describes what actually happens rather than how 
we think the users ought to feel.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
"I dropped the toothpaste", said Tom, crestfallenly.

v2.29.0 | Report a Bug | By Email | System Status