Re: [DNSOP] Fwd: New Version Notification for draft-bellis-dnsop-edns-tags-00.txt

Wes Hardaker <wjhns1@hardakers.net> Tue, 05 March 2019 06:26 UTC

Return-Path: <wjhns1@hardakers.net>
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 4820D130FB2 for <dnsop@ietfa.amsl.com>; Mon, 4 Mar 2019 22:26:22 -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, SPF_PASS=-0.001, URIBL_BLOCKED=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 2aabYmyzYMEe for <dnsop@ietfa.amsl.com>; Mon, 4 Mar 2019 22:26:20 -0800 (PST)
Received: from mail.hardakers.net (mail.hardakers.net [168.150.192.181]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B0228130FAB for <dnsop@ietf.org>; Mon, 4 Mar 2019 22:26:19 -0800 (PST)
Received: from localhost (unknown [10.0.0.3]) by mail.hardakers.net (Postfix) with ESMTPA id 99A2128D1B; Mon, 4 Mar 2019 22:26:15 -0800 (PST)
From: Wes Hardaker <wjhns1@hardakers.net>
To: Mark Andrews <marka@isc.org>
Cc: Wes Hardaker <wjhns1@hardakers.net>, Dick Franks <rwfranks@acm.org>, IETF DNSOP WG <dnsop@ietf.org>, Ray Bellis <ray@isc.org>
References: <155171606493.5281.3957934874516100450.idtracker@ietfa.amsl.com> <5c3cc3f9-2225-9077-fb9e-0fb940bd1c1b@isc.org> <yblef7mp7io.fsf@wu.hardakers.net> <CAKW6Ri5doXL=uBpEy3Eqrkoyfu9rvt9upH9qxXkzZKUgS_=dMw@mail.gmail.com> <ybla7iap5nx.fsf@wu.hardakers.net> <B137690E-8063-4416-BFE2-706F0589AD5F@isc.org>
Date: Mon, 04 Mar 2019 22:26:15 -0800
In-Reply-To: <B137690E-8063-4416-BFE2-706F0589AD5F@isc.org> (Mark Andrews's message of "Tue, 5 Mar 2019 11:45:25 +1100")
Message-ID: <yblsgw125x4.fsf@w7.hardakers.net>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/X7YA9G0r6CTpRHGYwEt6oSfpXm0>
Subject: Re: [DNSOP] Fwd: New Version Notification for draft-bellis-dnsop-edns-tags-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
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, 05 Mar 2019 06:26:22 -0000

Mark Andrews <marka@isc.org> writes:

> > Yes, and that's where I see a problem: when the software doesn't know
> > the agreement has been severed.
> 
> Presumably you won’t get back a server tag and you can log that.

No you may get back a server tag, and you're equally as likely to
misinterpret it just as the server misinterpreted your client tag.
Sure, *sometimes* (many times even) it will cause a parse error.  It's
the cases that don't cause parse errors that concern me.  What if the
client and server *think* they understand each other, but actually are
doing very different things because one side of the "agreement" is no
longer acting the same way.

-- 
Wes Hardaker
USC/ISI