IETF Logo Mail Archive

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

Evan Hunt <each@isc.org> Mon, 10 September 2018 16:59 UTC

Return-Path: <each@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 25D7812F1A2 for <dnsop@ietfa.amsl.com>; Mon, 10 Sep 2018 09:59:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level:
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 K_bVI7lgHZ0J for <dnsop@ietfa.amsl.com>; Mon, 10 Sep 2018 09:59:45 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) (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 22B5C128D0C for <dnsop@ietf.org>; Mon, 10 Sep 2018 09:59:45 -0700 (PDT)
Received: from bikeshed.isc.org (bikeshed.isc.org [149.20.48.19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id 012C63AB03E; Mon, 10 Sep 2018 16:59:23 +0000 (UTC)
Received: by bikeshed.isc.org (Postfix, from userid 10292) id DED2B216C1C; Mon, 10 Sep 2018 16:59:22 +0000 (UTC)
Date: Mon, 10 Sep 2018 16:59:22 +0000
From: Evan Hunt <each@isc.org>
To: Paul Vixie <paul@redbarn.org>
Cc: Andrew Sullivan <ajs@anvilwalrusden.com>, dnsop@ietf.org
Message-ID: <20180910165922.GA31252@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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <5B96A045.2020905@redbarn.org>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/PM1tiTFp24z_iDA-H2M96pMEvtw>
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 16:59:46 -0000

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.

v2.23.0 | Report a Bug | By Email