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

Phillip Hallam-Baker <> Thu, 29 March 2018 15:45 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 1501112DA15 for <>; Thu, 29 Mar 2018 08:45:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, 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: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id v5_HgLA4wX6M for <>; Thu, 29 Mar 2018 08:45:56 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4003:c06::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 9F9C812DA00 for <>; Thu, 29 Mar 2018 08:45:56 -0700 (PDT)
Received: by with SMTP id t16-v6so5563175oih.3 for <>; Thu, 29 Mar 2018 08:45:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to; bh=fLEsvkQhXAKduT9AD8qtqFIH42kMCmziTWabAioUFUU=; b=X93sG8Um0BiqZwaRzhnFNca70TnISD5m4NMhMbIf0IcbXqiiiAkuhFTKjROs58Ut2s fzmIOprgs6um6C22Sti0WzODuHUfEBmyB4jfd38or8HM6GdYojT7wcqLTKgky9cxaV/3 nx1u+3Z3gEiExh/3Z3mIvHIE3Jfg4Csc53z6oilmVs1W0FjlWUCaTTU7qivvJvu7Mv5P GmzzpbKZgEcnPTMjy53uUdfwykR+AUfi0xy/9hYJbfsYcW2uPAsmySWivVG4JEbSvlHY C6jKs3K4GQerx6VYFXqRyUa2OU25QrM/KtuVRgCuDtGeQQXLlGqEEM6/a0tQVMLc+tWm +8rg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to; bh=fLEsvkQhXAKduT9AD8qtqFIH42kMCmziTWabAioUFUU=; b=PxCL1OPaHApEFZO8Miq0sE/1K6HJENHB78Gk9gy+ChFvrqBtjT5EFHzGv87V6I/pAx 1yuRtdXjJN+TsjsMIGOX4M97ypbsfN0ECnPqJVzFEtVkKsFXiit5L2g4/IQNv5a3UPez QMeeltuAgQxJlztaJfEe3oBOZUOaQ7iyFbZx5buvrLGl2w8NXgUWJHTD52FYrH6ElPCa BLBnHOm/pUFf5v0+v48Pg6IDpQ+ulGk2JeZdEFxzswV8CLeNxxtoglWFHiDNN650Vu1U RzciMjl2Ft8n6wN53e9TAdNsH84HPZmVnhlJ3LpQ+ZnDLr6Itl6/98EtL7LgetxPD2JW AaDw==
X-Gm-Message-State: ALQs6tAWhSqO6iit8U1dETw4hKjn+pmRBpBwiE3rRUrSfqQTOpuf4CXk R8DBTusFsCG712z0xPiXsJgM6kkISG7XwNTHrdM=
X-Google-Smtp-Source: AIpwx4/NieQWQHV7NN4sd7+7GQpmpQPCLPLfAH8k/cOrx9wmoDIZb75Ezmo/Jk5K1rKkvqX3CeGUq3DnnOaazBeQ28o=
X-Received: by with SMTP id e13mr5022096oig.34.1522338355620; Thu, 29 Mar 2018 08:45:55 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a9d:233c:0:0:0:0:0 with HTTP; Thu, 29 Mar 2018 08:45:55 -0700 (PDT)
In-Reply-To: <>
References: <>
From: Phillip Hallam-Baker <>
Date: Thu, 29 Mar 2018 11:45:55 -0400
X-Google-Sender-Auth: QP8eFpw1-qQ4sCoxi8It0rvtIp0
Message-ID: <>
To: dnsop <>
Content-Type: multipart/alternative; boundary="001a113d225aea310e05688f040d"
Archived-At: <>
Subject: Re: [DNSOP] I-D Action: draft-ietf-dnsop-attrleaf-06.txt
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 29 Mar 2018 15:45:59 -0000

A bit of context here, this is probably a document you have seen before and
it is one of those cleanup documents that tends to languish.

The reason I asked Dave to restart work on this draft is that I was
reviewing another draft (SMTPRPT) that clearly needs to register a new
prefix and indeed really needs a new prefix registry.

This this draft is about to become critical path for another draft which
means that it is much more likely that it will actually make it to RFC this
time which means that if you have an opinion on it, now is the time to
speak or forever hold your peace.

On Wed, Mar 28, 2018 at 11:30 AM, <>; 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
>         Title           : DNS Scoped Data Through '_Underscore' Naming of
> Attribute Leaves
>         Author          : Dave Crocker
>         Filename        : draft-ietf-dnsop-attrleaf-06.txt
>         Pages           : 9
>         Date            : 2018-03-28
> Abstract:
>    Formally, any DNS resource record may occur for 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
>    underscore naming construct defines a semantic scope for DNS records
>    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:
> Please note that it may take a couple of minutes from the time of
> submission
> until the htmlized version and diff are available at
> Internet-Drafts are also available by anonymous FTP at:
> _______________________________________________
> DNSOP mailing list