BCP 222, RFC 8553 on DNS Attrleaf Changes: Fixing Specifications That Use Underscored Node Names
rfc-editor@rfc-editor.org Wed, 20 March 2019 23:52 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 680141310F4; Wed, 20 Mar 2019 16:52:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vkGkQkSPkPFT; Wed, 20 Mar 2019 16:52:21 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 124F8130EB3; Wed, 20 Mar 2019 16:52:21 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 6620BB81C90; Wed, 20 Mar 2019 16:52:13 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: BCP 222, RFC 8553 on DNS Attrleaf Changes: Fixing Specifications That Use Underscored Node Names
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: <20190320235213.6620BB81C90@rfc-editor.org>
Date: Wed, 20 Mar 2019 16:52:13 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/gvl9YkyaO1S8341883BI2QXjWbk>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Mar 2019 23:52:31 -0000
A new Request for Comments is now available in online RFC libraries.
BCP 222
RFC 8553
Title: DNS Attrleaf Changes: Fixing Specifications
That Use Underscored Node Names
Author: D. Crocker
Status: Best Current Practice
Stream: IETF
Date: March 2019
Mailbox: dcrocker@bbiw.net
Pages: 15
Characters: 33458
Updates: RFC 2782, RFC 3263, RFC 3529, RFC 3620,
RFC 3832, RFC 3887, RFC 3958, RFC 4120,
RFC 4227, RFC 4386, RFC 4387, RFC 4976,
RFC 5026, RFC 5328, RFC 5389, RFC 5415,
RFC 5518, RFC 5555, RFC 5617, RFC 5679,
RFC 5766, RFC 5780, RFC 5804, RFC 5864,
RFC 5928, RFC 6120, RFC 6186, RFC 6376,
RFC 6733, RFC 6763, RFC 7208, RFC 7489,
RFC 8145
See Also: BCP 222
I-D Tag: draft-ietf-dnsop-attrleaf-fix-07.txt
URL: https://www.rfc-editor.org/info/rfc8553
DOI: 10.17487/RFC8553
Using an underscore for a prefix creates a space for constrained
interoperation of resource records. Original uses of an underscore
character as a domain node name prefix were specified without the
benefit of an IANA registry. This produced an entirely uncoordinated
set of name-creation activities, all drawing from the same namespace.
A registry for these names has now been defined by RFC 8552.
However, the existing specifications that use underscored naming need
to be modified in order to be in line with the new registry. This
document specifies those changes. The changes preserve existing
software and operational practice, while adapting the specifications
for those practices to the newer underscore registry model.
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
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
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