Re: [DNSOP] [Ext] Fwd: New Version Notification for draft-sury-deprecate-obsolete-resource-records-01.txt

Andrew Sullivan <ajs@anvilwalrusden.com> Mon, 13 May 2019 21:05 UTC

Return-Path: <ajs@anvilwalrusden.com>
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 E358B1200E6 for <dnsop@ietfa.amsl.com>; Mon, 13 May 2019 14:05:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=yitter.info header.b=boiSxlrp; dkim=pass (1024-bit key) header.d=yitter.info header.b=hZvU4ly4
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 7i_bECiKcICB for <dnsop@ietfa.amsl.com>; Mon, 13 May 2019 14:05:06 -0700 (PDT)
Received: from mx4.yitter.info (mx4.yitter.info [159.203.56.111]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CCA7212006A for <dnsop@ietf.org>; Mon, 13 May 2019 14:05:06 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx4.yitter.info (Postfix) with ESMTP id 3A5D7BB84B for <dnsop@ietf.org>; Mon, 13 May 2019 21:05:05 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1557781505; bh=vdx++upRc3cVBKJOFn+2mWV2l2MlH/e0MHlnduvGtXY=; h=Date:From:To:Subject:References:In-Reply-To:From; b=boiSxlrpTqvtLsmNWlEYySSTqvHrN18zm5GU1YpW3aL8IxbfNWwZVhzPtYnUHpjy4 HUNSk9ASPLdEj10HGsTmXCyGU/QokjpTJGWLkt5vzMtn8dnME3IG/3e2JfQUhAvS4+ ytdpnTMjNvWxcs6FLy1BTbLXt1aZoGCanvXN9ssg=
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx4.yitter.info ([127.0.0.1]) by localhost (mx4.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YJ5736qmDzLo for <dnsop@ietf.org>; Mon, 13 May 2019 21:05:03 +0000 (UTC)
Date: Mon, 13 May 2019 17:05:01 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1557781503; bh=vdx++upRc3cVBKJOFn+2mWV2l2MlH/e0MHlnduvGtXY=; h=Date:From:To:Subject:References:In-Reply-To:From; b=hZvU4ly4XxwGgfKKop3xfgTwuEKOtfE4ebZCZS+9k2XYBYtuzloETRZcpDB7JRxW6 1mNtMxoIoRSdshIeDUOtXBiIpb/Q2EE02xLVwqETKhJK3ncU8fsdWR3OrSGZFZEykC aHKWC1//I03yQgr4c1UeFlDQGKGupbgHB4sSko/4=
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: dnsop@ietf.org
Message-ID: <20190513210501.4nqa2mnskjdvmmtw@mx4.yitter.info>
References: <155771990790.31813.2767356343632633845.idtracker@ietfa.amsl.com> <F8E0E608-524F-452A-9549-B5085C927487@icann.org> <CAJrXxAPdg_DYu-OpW=NDz7zW3EAfAYF3-LMkRwNuKHYFFgn2gQ@mail.gmail.com> <2247542.gD6P9zcVKM@linux-9daj>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <2247542.gD6P9zcVKM@linux-9daj>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/auELkb3BmZCdJ31lqftl532KMKE>
Subject: Re: [DNSOP] [Ext] Fwd: New Version Notification for draft-sury-deprecate-obsolete-resource-records-01.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: Mon, 13 May 2019 21:05:09 -0000

On Mon, May 13, 2019 at 07:30:44PM +0000, Paul Vixie wrote:
> maintainers will know which burdens they can avoid. having it be a matter of 
> ad-hoc "in-crowd" knowledged passed down from mother to daughter is not the 
> internet engineering way.

Well, it might _be_ the Internet engineering way, but it doesn't make
for tremendous interoperability.

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com