[DNSOP] Fwd: New Version Notification for draft-ietf-dnsop-attrleaf-03.txt

Dave Crocker <dhc2@dcrocker.net> Tue, 20 March 2018 00:35 UTC

Return-Path: <dhc2@dcrocker.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 4BFD912D80F for <dnsop@ietfa.amsl.com>; Mon, 19 Mar 2018 17:35:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=dcrocker.net
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 9jK5nCj6quZr for <dnsop@ietfa.amsl.com>; Mon, 19 Mar 2018 17:35:35 -0700 (PDT)
Received: from simon.songbird.com (simon.songbird.com [72.52.113.5]) (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 922C112D864 for <dnsop@ietf.org>; Mon, 19 Mar 2018 17:35:35 -0700 (PDT)
Received: from [192.168.1.168] (76-218-8-128.lightspeed.sntcca.sbcglobal.net [76.218.8.128]) (authenticated bits=0) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id w2K0atEA003708 (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256 verify=NOT) for <dnsop@ietf.org>; Mon, 19 Mar 2018 17:36:55 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=default; t=1521506215; bh=B/fmxqhc+mxAj7LBEsDRc3Ab1cTi2kx3o/SyfQcg5cM=; h=From:Subject:References:To:Reply-To:Date:In-Reply-To:From; b=LpQ+ZzZ8WPAsxU6HjwC2bzSCkul7Ty00KHGcti5T+C67T5jD1v8nOW/Wd497c1UWW z3H5sHTj15ehbna3s1kggn2jVmmD+GtLBoZZbe/xS9nYYmKYBvdECgysUP4dRNwUfY ENyKZYjZLINBGLJzhPsdAcDBN9+wFbHLlysUY410=
From: Dave Crocker <dhc2@dcrocker.net>
References: <152150434726.9747.3586273536264334521.idtracker@ietfa.amsl.com>
Organization: Brandenburg InternetWorking
To: dnsop <dnsop@ietf.org>
Reply-To: dcrocker@bbiw.net
Message-ID: <f7b85bac-b050-5003-2df0-a48b1ef2f929@dcrocker.net>
Date: Mon, 19 Mar 2018 17:35:29 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <152150434726.9747.3586273536264334521.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/ELZNFOFi7KFv_B4d1qM35kkU6i4>
Subject: [DNSOP] Fwd: New Version Notification for draft-ietf-dnsop-attrleaf-03.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: Tue, 20 Mar 2018 00:35:37 -0000

Folks,

I'll limit what should be an extensive and elaborate apology to just 
this: I'm sorry for the year of inactivity.

The -03 version should provide some useful substance of progress.

I've gone over last summer's comments and the -03 version should reflect 
what the wg agreed to.  Basically, it has been significantly 
streamlined, essentially to reflect a clean-sheet model of the world. 
That is, it doesn't deal with the ugliness that SRV, et al, created.  It 
merely establishes the two registries we need, long term, and populates 
them.  This document should have continuing utility.

-03 defines two registries, 'global' and 'second-level'.  I'm suspicious 
of how short the global one is, though it does make sense.

As noted in the document, absent major concerns with the substance of 
the document, please send me or the list s/old/new/ types of change 
suggestions, and if the change is for a reference, I'd love the 
suggestion to be <reference> xml...


A second document will attempt to fix up the uglinesses in some existing 
documents, to get them to align with a world that has these registries. 
It should be viewed as a transitional document, though we all know how 
glacial 'transitions' are in the Internet...

Deciding how to pursue that reasonably has been the effort.  The changes 
this 'fixes' document defines will be to documentation, but not to 
existing operation.  Existing uses in the field will be preserved.


Here's the approach I'm taking:


1. Simple underscore usage

    For many/most specifications that use underscore naming, the text 
merely says to use it.  They are straightforward.

    These specifications need to be listed in this document, explicitly, 
so that later updates to them will know to deal with the revisions 
called for by this document.

    But this document doesn't really need s/old/new kinds of precise 
detail for them. Rather than provide precise language for changing each 
of these, I propose to provide some generic text, and generic IANA 
Considerations.  This will permit this Fixes document to be cited as 
Updating those RFCs.


2. SRV and URI

    These need more detailed text, very much in the s/old/new style.

    The current text in them does a use-by-reference of existing tables 
defined for other purposes.  The Update text will, instead, specify a 
requirement for adding entries in the Global or Common Second-Level 
registries.


d/


-------- Forwarded Message --------

Name:		draft-ietf-dnsop-attrleaf
Revision:	03
Title:		DNS Scoped Data Through '_Underscore' Naming of Attribute Leaves
Document date:	2018-03-19
Group:		dnsop
Pages:		14
URL: https://www.ietf.org/internet-drafts/draft-ietf-dnsop-attrleaf-03.txt
Status:         https://datatracker.ietf.org/doc/draft-ietf-dnsop-attrleaf/
Htmlized:       https://tools.ietf.org/html/draft-ietf-dnsop-attrleaf-03
Htmlized: https://datatracker.ietf.org/doc/html/draft-ietf-dnsop-attrleaf
Diff: https://www.ietf.org/rfcdiff?url2=draft-ietf-dnsop-attrleaf-03

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net