Re: [DNSOP] Brief addition to terminology-bis draft

Mark Andrews <marka@isc.org> Mon, 10 September 2018 20:38 UTC

Return-Path: <marka@isc.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 E1D36130F9D for <dnsop@ietfa.amsl.com>; Mon, 10 Sep 2018 13:38:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level:
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_HI=-5, 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 u7xxKRvgmdkv for <dnsop@ietfa.amsl.com>; Mon, 10 Sep 2018 13:38:45 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [149.20.64.53]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E6E0130F94 for <dnsop@ietf.org>; Mon, 10 Sep 2018 13:38:45 -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)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id 526B33AB041; Mon, 10 Sep 2018 20:38:44 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id 20CD416007D; Mon, 10 Sep 2018 20:38:43 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 1213216007C; Mon, 10 Sep 2018 20:38:43 +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 h0FZpKrUfGtb; Mon, 10 Sep 2018 20:38:43 +0000 (UTC)
Received: from [172.30.42.88] (c27-253-115-14.carlnfd2.nsw.optusnet.com.au [27.253.115.14]) by zmx1.isc.org (Postfix) with ESMTPSA id A841716005B; Mon, 10 Sep 2018 20:38:42 +0000 (UTC)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (1.0)
From: Mark Andrews <marka@isc.org>
X-Mailer: iPhone Mail (15G77)
In-Reply-To: <20180910165922.GA31252@isc.org>
Date: Tue, 11 Sep 2018 06:38:40 +1000
Cc: Paul Vixie <paul@redbarn.org>, dnsop@ietf.org, Andrew Sullivan <ajs@anvilwalrusden.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <FA185185-3195-45A3-9F6D-13FB684D759F@isc.org>
References: <4AA8656A-7D2F-4584-B84D-47E97483CCC2@gmail.com> <5B8D548E.5080205@redbarn.org> <30BF3D0E-1EE9-4310-ACCB-413E019B6D93@isc.org> <CANeU+ZDMLxpS1VLCunM6DRmkLqtt521Q+QSHwdhvMZ-+eGqSMA@mail.gmail.com> <20180910125533.a2wkwdci3won7shg@mx4.yitter.info> <5B96A045.2020905@redbarn.org> <20180910165922.GA31252@isc.org>
To: Evan Hunt <each@isc.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/ZWfRhHZneziOrd2Qvfu7y1vpHJg>
Subject: Re: [DNSOP] Brief addition to terminology-bis draft
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, 10 Sep 2018 20:38:47 -0000

And part of not making that too difficult is making new types IN specific by default. You need to argue for class agnostic.

You can always replicate a class specific type in a new class. You can’t go from class agnostic to class specific. 

-- 
Mark Andrews

> On 11 Sep 2018, at 02:59, Evan Hunt <each@isc.org>; wrote:
> 
>> On Mon, Sep 10, 2018 at 09:48:05AM -0700, Paul Vixie wrote:
>> Andrew Sullivan wrote:
>>> ...
>>> 
>>> I agree with Paul Vixie that classes were never defined well enough to
>>> be made to work properly, at least at Internet scale.
>> 
>> this thread has further cemented my prejudice against CLASS. however, it 
>> has also motivated me to define it well enough that we can create a 
>> global "CHAOS" system, with very different zone cuts, which seems like 
>> an idea bad enough to be good.
> 
> This is not in any way an *urgent* consideration, but I do sometimes
> wonder what we (or, y'know, our grandchildren) are going to do if we
> ever run short of type codes.
> 
> The obvious thing would be to expand into the CLASS field.  Someone in
> the future might be grateful if we avoid making that too difficult.
> 
> -- 
> Evan Hunt -- each@isc.org
> Internet Systems Consortium, Inc.
> 
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop