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

Bob Harold <rharolde@umich.edu> Fri, 23 March 2018 16:51 UTC

Return-Path: <rharolde@umich.edu>
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 CA05E12D88C for <dnsop@ietfa.amsl.com>; Fri, 23 Mar 2018 09:51:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=umich.edu
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 CqcEls3OaWFG for <dnsop@ietfa.amsl.com>; Fri, 23 Mar 2018 09:51:55 -0700 (PDT)
Received: from mail-lf0-x22a.google.com (mail-lf0-x22a.google.com [IPv6:2a00:1450:4010:c07::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4E42912D869 for <dnsop@ietf.org>; Fri, 23 Mar 2018 09:51:55 -0700 (PDT)
Received: by mail-lf0-x22a.google.com with SMTP id e5-v6so19275248lfb.7 for <dnsop@ietf.org>; Fri, 23 Mar 2018 09:51:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umich.edu; s=google-2016-06-03; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=SoA0LwrJ7kFbgotjr4HRUwail5UeE28i1prGPinw+sw=; b=kZzTbhokSpp+GziP7fTNtLumTdKDiN319CMmsWHZqb9nKl6Z8ZemE/XTGgmewPQBoU xJxWu+b1mFF+TV5zM8i+khPn/9cuwOGBwfD3TmO8YXndjjjf1bDA2Rv/pX5Xl84mpipV g8aTg195cQ7Qki4GIyOwWguKOI3vwmb02UcE/iXF0OFrVX6pDvmWHJJR8xyC4xnKlKXW g7Wt+CG3ifO4KmtBXlO2vnxw1pHMLqO3/8eHHLVJ2Fnz4WQe2gavzoGpqp3F91WdUZ9y 192YeGg8DOpuWdQcmDsI4DuewXX527R3bfjK74Z7d3DsKaD5tCSH9o5oL7QnyGpv5mus /DEw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=SoA0LwrJ7kFbgotjr4HRUwail5UeE28i1prGPinw+sw=; b=WbMglcB8zAe62Ai4LAg8n8Fm2ar4fZLQX3W739F4Ld9OPGklnZl9GVV6znirbzTV/p 3HjHhy73Bn8hXdrnJt7gWWTz7Hvm56oNnYZwA3cqhLsET72KDqCZCSIAbYsGEq81NlOH cwH6ZBuiG+R+tfrdb6hxdUn+4oOzmk34PKbXlOA3Pt6DAtqxNU2WHLbQMqFqpAj/eDgI FdVJx1369S7tQu+uQOjrMpwb1+Wv61rDdJfx7srMrzXxh7x7dvchmqq6lm1ChkqRYRWC lfTyu9lGC2qK5FNOPv0MorHBzFrEk7oEBoQONCYUw86eTjvpY/MNwSsaw02TL0/5ZTTN ycIg==
X-Gm-Message-State: AElRT7GNPhtnnp//vXoeRwy/mjYvXJo1gWRLninUT6zVjY4LfqaUsjGQ wCCycrX2aLen6bYskX7TQTmaJaAXkhVOfXyvIMW9lmWs
X-Google-Smtp-Source: AIpwx4+sFwJr1chmCZLwxdygYebvjH027VHTC0Sq+YMnm0oGLgN09PPcLit3hPN7sDGf/8XdoFv+R3gwaCAUPbho3F0=
X-Received: by 2002:a19:c713:: with SMTP id x19-v6mr2107566lff.32.1521823913282; Fri, 23 Mar 2018 09:51:53 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.46.155.140 with HTTP; Fri, 23 Mar 2018 09:51:52 -0700 (PDT)
In-Reply-To: <40ABB9EB-58EC-48FF-8117-60EE0E7006EF@isc.org>
References: <152180695934.17546.2068402636242578841.idtracker@ietfa.amsl.com> <9CEA4F8F-4E71-4508-A088-103DD58F88E1@isc.org> <CA+nkc8DhXEEhiDqwHuA-_zNQc0n=rTZ-VZ6X8-0w-tY_0SC0eA@mail.gmail.com> <40ABB9EB-58EC-48FF-8117-60EE0E7006EF@isc.org>
From: Bob Harold <rharolde@umich.edu>
Date: Fri, 23 Mar 2018 12:51:52 -0400
Message-ID: <CA+nkc8BfMKRUHuW+3EzOCeZHfmu1jeOgfVcszTbTYh9k2VTBcA@mail.gmail.com>
To: =?UTF-8?B?T25kxZllaiBTdXLDvQ==?= <ondrej@isc.org>
Cc: dnsop <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000c326020568173d61"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/ElI9CTa7dr47qoUPD1xdjBMGwqs>
Subject: Re: [DNSOP] Fwd: New Version Notification for draft-sury-deprecate-obsolete-resource-records-00.txt
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: Fri, 23 Mar 2018 16:51:59 -0000

On Fri, Mar 23, 2018 at 12:05 PM, Ondřej Surý <ondrej@isc.org>; wrote:

> No, I don’t mean that. While in theory you can call an aquarium with dead
> fish and algae “in use” and tell your neighbors that you have fish and have
> a green thumb, it wouldn’t be necessarily an accurate assessment of the
> situation. Similarly, an occasional user that tries things doesn’t make
> those experimental RRTYPEs to be “in use”.
>
> What I mean is to make DNS simpler by kicking out stuff that has no use in
> existing protocols.
>
> Ondřej
> --
> Ondřej Surý — ISC
>
>
Ok, sorry to sound mean.  But I think 'not in use' needs to be defined in
the rfc so we all understand it the same.  How do we decide when something
in no longer in use?  Perhaps there is no quantitative measurement and we
just have to make a judgement call.

"no known practical usage" ?
"no known use that will break anything if removed" ?
"use is so low that the the advantage of removing exceeds the advantage of
continuing to support it" ?
"there is very little use and we don't think removing it will cause a
problem" ?

-- 
Bob Harold



> On 23 Mar 2018, at 14:18, Bob Harold <rharolde@umich.edu>; wrote:
>
>
> On Fri, Mar 23, 2018 at 8:11 AM, Ondřej Surý <ondrej@isc.org>; wrote:
>
>> Heya,
>>
>> this is a first attempt to start reducing the load on DNS Implementors
>> and actually remove the stuff from DNS that’s not used and not needed
>> anymore.
>>
>> There’s github for the draft: https://github.com/oerd
>> nj/draft-sury-dnsop-deprecate-obsolete-resource-records
>>
>> Ondrej
>> --
>> Ondřej Surý
>> ondrej@isc.org
>>
>> Begin forwarded message:
>>
>> *From: *internet-drafts@ietf.org
>> *Subject: **New Version Notification for
>> draft-sury-deprecate-obsolete-resource-records-00.txt*
>> *Date: *23 March 2018 at 12:09:19 GMT
>> *To: *"Ondrej Sury" <ondrej@isc.org>;
>>
>>
>> A new version of I-D, draft-sury-deprecate-obsolete-
>> resource-records-00.txt
>> has been successfully submitted by Ondrej Sury and posted to the
>> IETF repository.
>>
>> Name: draft-sury-deprecate-obsolete-resource-records
>> Revision: 00
>> Title: Deprecating obsolete DNS Resource Records
>> Document date: 2018-03-22
>> Group: Individual Submission
>> Pages: 4
>> URL:            https://www.ietf.org/internet-drafts/draft-sury-
>> deprecate-obsolete-resource-records-00.txt
>> Status:         https://datatracker.ietf.org/doc/draft-sury-deprecat
>> e-obsolete-resource-records/
>> Htmlized:       https://tools.ietf.org/html/draft-sury-deprecate-obsol
>> ete-resource-records-00
>> Htmlized:       https://datatracker.ietf.org/doc/html/draft-sury-depre
>> cate-obsolete-resource-records
>>
>>
>> Abstract:
>>   This document deprecates Resource Records that are neither being used
>>   for anything meanigful nor already made obsolete by other RFCs.  This
>>   document updates [RFC1035].
>>
>>
> I don't mind deprecating unused types.  But I don't understand how an
> unused type can affect compression.  I can only imagine it having an effect
> if the type actually exists in a packet, which means that it is 'in use'.
>
> Do you mean 'types that have DNS records, and hosts query for those
> records, but we think they are not really used'  ?
>
> --
> Bob Harold
>
>
>