IETF Logo Mail Archive

Re: [DNSOP] Clarifying referrals (#35)

P Vix <paul@redbarn.org> Wed, 29 November 2017 13:55 UTC

Return-Path: <paul@redbarn.org>
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 E5E5D127369 for <dnsop@ietfa.amsl.com>; Wed, 29 Nov 2017 05:55:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 MSXpzZnU689G for <dnsop@ietfa.amsl.com>; Wed, 29 Nov 2017 05:55:40 -0800 (PST)
Received: from family.redbarn.org (family.redbarn.org [24.104.150.213]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 73CE0120724 for <dnsop@ietf.org>; Wed, 29 Nov 2017 05:55:40 -0800 (PST)
Received: from [100.71.116.250] (139.sub-174-214-8.myvzw.com [174.214.8.139]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by family.redbarn.org (Postfix) with ESMTPSA id C9A5661FA2; Wed, 29 Nov 2017 13:55:36 +0000 (UTC)
Date: Wed, 29 Nov 2017 13:55:29 +0000
User-Agent: K-9 Mail for Android
In-Reply-To: <20171129122811.bydl23dadf53yzkd@mx4.yitter.info>
References: <20171112075445.tf2ut5dxzhhnqe7l@mx4.yitter.info> <20171128195025.ifzwsjk42wz7ard6@mx4.yitter.info> <5A1DEEE1.3070809@redbarn.org> <20171129014748.7rrm2tvwdnjdl6ss@mx4.yitter.info> <5A1E2491.9070805@redbarn.org> <20171129122101.mv7zlc6kdqe3ojnv@mx4.yitter.info> <13A36237-CA11-44F3-BA80-69302F7D14F9@redbarn.org> <20171129122811.bydl23dadf53yzkd@mx4.yitter.info>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----326GI9CM6K7CPKILN21PPENLKCGEI9"
Content-Transfer-Encoding: 7bit
To: dnsop@ietf.org, Andrew Sullivan <ajs@anvilwalrusden.com>
From: P Vix <paul@redbarn.org>
Message-ID: <C35712C0-0953-4010-99F2-A0083FC35763@redbarn.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/nxFqpi8BtTwIWGw0NFdmJPWIVKc>
Subject: Re: [DNSOP] Clarifying referrals (#35)
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: Wed, 29 Nov 2017 13:55:42 -0000

No, sir. Closer means downward. Nobody believes otherwise. Not even you, or Joe. The only person ever to get it wrong was me, and I have recanted. Please do not write anything that blurs or softens the clear language of downwards-ness in 1034. If you can't keep the clear spirit and intent of the existing document then please write nothing at all.

On November 29, 2017 8:28:11 PM GMT+08:00, Andrew Sullivan <ajs@anvilwalrusden.com> wrote:
>On Wed, Nov 29, 2017 at 12:23:36PM +0000, P Vix wrote:
>> 1034 cannot be reasonably read that way.
>
>Sure it can.  See the discussion in draft-sullivan-dnsop-refer-down
>and on the list not two weeks ago for how.  I think it should _not_ be
>read that way, but an honest reader could read it that way, and the
>terminology document is not the place to rule on the way people should
>read a text.  We're supposed to be doing description, not prescription.
>
>Best regards,
>
>A
>
>
>-- 
>Andrew Sullivan
>ajs@anvilwalrusden.com
>
>_______________________________________________
>DNSOP mailing list
>DNSOP@ietf.org
>https://www.ietf.org/mailman/listinfo/dnsop

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

v2.23.0 | Report a Bug | By Email