Re: [DNSOP] I-D Action: draft-ietf-dnsop-resolver-information-01.txt

"Robert Mortimer" <robm@scramworks.net> Wed, 12 February 2020 10:00 UTC

Return-Path: <robm@scramworks.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 D229E1200B1 for <dnsop@ietfa.amsl.com>; Wed, 12 Feb 2020 02:00:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, 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=scramworks.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 htoTydbOEu-T for <dnsop@ietfa.amsl.com>; Wed, 12 Feb 2020 02:00:09 -0800 (PST)
Received: from knid.scramworks.net (knid.scramworks.net [IPv6:2a01:4f8:c17:50eb::2]) (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 05F2F120077 for <dnsop@ietf.org>; Wed, 12 Feb 2020 02:00:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=scramworks.net; s=bofh; h=References:In-Reply-To:To:From:Subject:Message-ID :Date:MIME-Version:Content-Type:Sender:Reply-To:Cc:Content-Transfer-Encoding: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=49wdsW4Fvup3DGmP/dECL1PajVFOG9s6v388+RTs3Ag=; b=Ohtol3/ZChghRNAHkBsv/V1lEt f9PG1j+fg+xJAm/Rcie+c+2fLv2zvMezfsBPKbeMobtJ391InFZsUES8c+9/K+yoyH/0Ci87F3j0K 07hFztcmU58kC0mCwYxsH7dEkzcY0fTB4hbV3QSd0cYLkFqDn2TI0hRhvJTAVc+ZLW+o=;
Received: from host-78-146-5-137.as13285.net ([78.146.5.137] helo=[192.168.1.106]) by knid.scramworks.net with esmtpsa (TLS1.1:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.90_1) (envelope-from <robm@scramworks.net>) id 1j1ooP-0001jr-Q0 for dnsop@ietf.org; Wed, 12 Feb 2020 10:00:06 +0000
Content-Type: multipart/alternative; boundary="----=_NextPart_63940416.579629316961"
MIME-Version: 1.0
Date: Wed, 12 Feb 2020 09:59:04 +0000
Message-ID: <Mailbird-d05777a4-cadd-4f3a-8a11-be497b917f90@scramworks.net>
From: Robert Mortimer <robm@scramworks.net>
To: dnsop@ietf.org
In-Reply-To: <158147423681.20010.1215769228895202180@ietfa.amsl.com>
References: <158147423681.20010.1215769228895202180@ietfa.amsl.com>
User-Agent: Mailbird/2.7.9.0
X-Mailbird-ID: Mailbird-d05777a4-cadd-4f3a-8a11-be497b917f90@scramworks.net
X-Spam-Score-SW: -1.0 (-)
X-SW-Scan: 9ea665e5bd3ec367a02cbccb0e57f621
X-Clacks-Overhead: GNU Terry Pratchett
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/r3ItBwn3FtFnqYtyIFXnrWyG5nA>
Subject: Re: [DNSOP] I-D Action: draft-ietf-dnsop-resolver-information-01.txt
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: Wed, 12 Feb 2020 10:00:11 -0000

I may be missing something obvious but this draft seems to contradict it self as it says in the introduction:

"Authoritative servers MUST NOT answer queries that are defined in this protocol."

and then goes onto say in section 2:

"if the resolver can be configured to also be authoritative for some zones, it can use that configuration to actually be authoritative for the addresses on which it responds."

I also wonder what the correct behavior is for a server which is both recursive and authoritative - is it prohibited from supporting this protocol by that first "MUST NOT"? 

-- 
RobM
On 12/02/2020 02:25:52, internet-drafts@ietf.org <internet-drafts@ietf.org> wrote:

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Domain Name System Operations WG of the IETF.

Title : DNS Resolver Information Self-publication
Authors : Puneet Sood
Roy Arends
Paul Hoffman
Filename : draft-ietf-dnsop-resolver-information-01.txt
Pages : 9
Date : 2020-02-11

Abstract:
This document describes methods for DNS resolvers to self-publish
information about themselves, such as whether they perform DNSSEC
validation or are available over transports other than what is
defined in RFC 1035. The information is returned as a JSON object.
The names in this object are defined in an IANA registry that allows
for light-weight registration. Applications and operating systems
can use the methods defined here to get the information from
resolvers in order to make choices about how to send future queries
to those resolvers.

There is a GitHub repo for this draft where pull requests can be
issued: https://github.com/DNSOP/draft-ietf-dnsop-resolver-
information However, starting issues on the WG mailing list is
preferred.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dnsop-resolver-information/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-dnsop-resolver-information-01
https://datatracker.ietf.org/doc/html/draft-ietf-dnsop-resolver-information-01

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-dnsop-resolver-information-01


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop