Re: [DNSOP] I-D Action: draft-ietf-dnsop-attrleaf-12.txt

Mats Dufberg <> Tue, 24 July 2018 09:13 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 6128D131051 for <>; Tue, 24 Jul 2018 02:13:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.299
X-Spam-Status: No, score=-4.299 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_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id fdqv9Vxqon44 for <>; Tue, 24 Jul 2018 02:13:54 -0700 (PDT)
Received: from ( [IPv6:2001:67c:124c:2007::38]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 88FA8130E41 for <>; Tue, 24 Jul 2018 02:13:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple;; s=iis2015; h=received:received:received:from:to:subject:thread-topic:thread-index:date: message-id:references:in-reply-to:accept-language:content-language: x-ms-has-attach:x-ms-tnef-correlator:user-agent: x-ms-exchange-messagesentrepresentingtype: x-ms-exchange-transport-fromentityheader:x-originating-ip:content-type: mime-version; bh=oWSyHHPQNyAadIOEqRtliWa/lUunF+MStTIvFjs+Y/E=; b=BEb9JDhyhvgLMrSgoh64l2NL6Y5g6/WbZCNA4MxxlDQg8KrSoBw9IsqUM/UuYtKcnBGpLtFTPW6x4 jDoCXiuyEBm+JAyyTN5cENOHIh6xeK3/P/TOq8/vmr3i41862s29spkxz3CtrGWd/0y7X8T98eIfS3 hZ/scQdyghaGN5qM=
Received: from (unknown [2001:67c:124c:2043::25]) by (Halon) with ESMTPS id e0a790d8-8f21-11e8-a624-00505682e997; Tue, 24 Jul 2018 09:13:50 +0000 (UTC)
Received: from (2001:67c:124c:2043::25) by (2001:67c:124c:2043::25) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Tue, 24 Jul 2018 11:13:49 +0200
Received: from ([fe80::681b:9cef:675b:d880]) by ([fe80::681b:9cef:675b:d880%14]) with mapi id 15.00.1347.000; Tue, 24 Jul 2018 11:13:49 +0200
From: Mats Dufberg <>
Thread-Topic: [DNSOP] I-D Action: draft-ietf-dnsop-attrleaf-12.txt
Thread-Index: AQHUIQ2O3J4r9aQsT0KO8hjBUPQQ/KSdIcuAgAD5XYA=
Date: Tue, 24 Jul 2018 09:13:49 +0000
Message-ID: <>
References: <> <>
In-Reply-To: <>
Accept-Language: en-US, sv-SE
Content-Language: en-US
user-agent: Microsoft-MacOutlook/10.f.0.180709
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [2001:67c:124c:5024::193c]
Content-Type: multipart/alternative; boundary="_000_9DA145F4DF6A4BFAB3C956027B228050iisse_"
MIME-Version: 1.0
Archived-At: <>
Subject: Re: [DNSOP] I-D Action: draft-ietf-dnsop-attrleaf-12.txt
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: IETF DNSOP WG mailing list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 24 Jul 2018 09:13:58 -0000

In table 2 on page 9, the draft refers to RFC 2782 for _dccp and _sctp (SRV), but those “_node names” are not even mentioned in the RFC. Are they defined elsewhere?

In the same table, the draft refers to RFC 7553 for a number URI _node names, but the references are quite indirect. Could references to relevant IANA registries be added?


Mats Dufberg
DNS Specialist, IIS
Mobile: +46 73 065 3899

From: DNSOP <> on behalf of Bob Harold <>
Date: Monday, 23 July 2018 at 22:22
Subject: Re: [DNSOP] I-D Action: draft-ietf-dnsop-attrleaf-12.txt

On Sat, Jul 21, 2018 at 12:11 PM <<>> 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 Scoped Data Through "Underscore" Naming of Attribute Leaves
        Author          : Dave Crocker
        Filename        : draft-ietf-dnsop-attrleaf-12.txt
        Pages           : 13
        Date            : 2018-07-21

   Formally, any DNS resource record may occur under any domain name.
   However some services have defined an operational convention, which
   applies to DNS leaf nodes that are under a DNS branch having one or
   more reserved node names, each beginning with an _underscore.  The
   underscored naming construct defines a semantic scope for DNS record
   types that are associated with the parent domain, above the
   underscored branch.  This specification explores the nature of this
   DNS usage and defines the "DNS Global Underscore Scoped Entry
   Registry" with IANA.  The purpose of the Underscore registry is to
   avoid collisions resulting from the use of the same underscore-based
   name, for different services.

The IETF datatracker status page for this draft is:

There are also htmlized versions available at:

A diff from the previous version is available at: