[DNSOP] BCP 222, RFC 8552 on Scoped Interpretation of DNS Resource Records through "Underscored" Naming of Attribute Leaves

rfc-editor@rfc-editor.org Wed, 20 March 2019 23:52 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 31ACD130DE3; Wed, 20 Mar 2019 16:52:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id OcGwS9ozor6f; Wed, 20 Mar 2019 16:52:16 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4868F130E8B; Wed, 20 Mar 2019 16:52:16 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id A49C6B81C83; Wed, 20 Mar 2019 16:52:08 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, dnsop@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20190320235208.A49C6B81C83@rfc-editor.org>
Date: Wed, 20 Mar 2019 16:52:08 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/mfpBc9_HKwrs2U5DPEywy2qZm0k>
Subject: [DNSOP] =?utf-8?q?BCP_222=2C_RFC_8552_on_Scoped_Interpretation_o?= =?utf-8?q?f_DNS_Resource_Records_through_=22Underscored=22_Naming_of_Attr?= =?utf-8?q?ibute_Leaves?=
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, 20 Mar 2019 23:52:18 -0000

A new Request for Comments is now available in online RFC libraries.

        BCP 222        
        RFC 8552

        Title:      Scoped Interpretation of DNS Resource Records 
                    through "Underscored" Naming of Attribute Leaves 
        Author:     D. Crocker
        Status:     Best Current Practice
        Stream:     IETF
        Date:       March 2019
        Mailbox:    dcrocker@bbiw.net
        Pages:      15
        Characters: 35306
        See Also:   BCP 222

        I-D Tag:    draft-ietf-dnsop-attrleaf-16.txt

        URL:        https://www.rfc-editor.org/info/rfc8552

        DOI:        10.17487/RFC8552

Formally, any DNS Resource Record (RR) may occur under any domain
name.  However, some services use an operational convention for
defining specific interpretations of an RRset by locating the records
in a DNS branch under the parent domain to which the RRset actually
applies.  The top of this subordinate branch is defined by a naming
convention that uses a reserved node name, which begins with the
underscore character (e.g., "_name").  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
"Underscored and Globally Scoped DNS Node Names" registry with IANA.
The purpose of this registry is to avoid collisions resulting from
the use of the same underscored name for different services.

This document is a product of the Domain Name System Operations Working Group of the IETF.

BCP: This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for 
improvements. Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC