[DNSOP] Moving towards completing draft-ietf-dnsop-terminology-bis

"Paul Hoffman" <paul.hoffman@vpnc.org> Tue, 24 October 2017 20:18 UTC

Return-Path: <paul.hoffman@vpnc.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 C3672139938 for <dnsop@ietfa.amsl.com>; Tue, 24 Oct 2017 13:18:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level:
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, URIBL_BLOCKED=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 k4jO-MajKqCU for <dnsop@ietfa.amsl.com>; Tue, 24 Oct 2017 13:18:54 -0700 (PDT)
Received: from mail.proper.com (Opus1.Proper.COM [207.182.41.91]) (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 929DD1394F2 for <dnsop@ietf.org>; Tue, 24 Oct 2017 13:18:54 -0700 (PDT)
Received: from [169.254.8.54] (50-1-51-141.dsl.dynamic.fusionbroadband.com [50.1.51.141]) (authenticated bits=0) by mail.proper.com (8.15.2/8.14.9) with ESMTPSA id v9OKHWnV084238 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <dnsop@ietf.org>; Tue, 24 Oct 2017 13:17:33 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: mail.proper.com: Host 50-1-51-141.dsl.dynamic.fusionbroadband.com [50.1.51.141] claimed to be [169.254.8.54]
From: "Paul Hoffman" <paul.hoffman@vpnc.org>
To: "dnsop WG" <dnsop@ietf.org>
Date: Tue, 24 Oct 2017 13:18:51 -0700
Message-ID: <7CCE8BB2-3851-42D7-AD01-225553C128B2@vpnc.org>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed
X-Mailer: MailMate (1.9.7r5425)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/-BsE-EIXaFfGX4td6bYPkYlEP5E>
Subject: [DNSOP] Moving towards completing draft-ietf-dnsop-terminology-bis
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, 24 Oct 2017 20:18:56 -0000

Greetings again. One of the last major large issues for 
draft-ietf-dnsop-terminology-bis is to re-look at issues that were 
brought up in the preparation of RFC 7719 but were deferred to the -bis 
document. I have recently discovered that us doing that deferral pissed 
off some folks pretty heavily, and for that I apologize. I hope that 
people on this list are still willing to engage on the last bits of this 
document so that we can finish it in the near term.

To that end, I have opened up four issues in the GitHub tracker for 
things that I found we had deferred but not dealt with:
https://github.com/DNSOP/draft-ietf-dnsop-terminology-bis/issues/32: 
superordinate and subordinate
https://github.com/DNSOP/draft-ietf-dnsop-terminology-bis/issues/33: 
Four new terms about queries
https://github.com/DNSOP/draft-ietf-dnsop-terminology-bis/issues/34: 
Split out error names in their own terms
https://github.com/DNSOP/draft-ietf-dnsop-terminology-bis/issues/35: 
Clarifying "referral"
Please comment here on the list or in GitHub if you have any opinion 
about them. Personally, I believe all should be acted on.

Also, if you have the stomach for it, please review the entire 
draft-ietf-dnsop-terminology-bis (yet?) again and see if there are 
issues you remember from before that weren't brought up, or new issues 
that should be brought up now. This time, there is clearly no rush like 
there was before, and it would be good to get it more right this time.

--Paul Hoffman