[DNSOP] Last Call: <draft-ietf-dnsop-attrleaf-fix-04.txt> (DNS Attrleaf Changes: Fixing Specifications with Underscored Node Name Use) to Best Current Practice

The IESG <iesg-secretary@ietf.org> Tue, 11 September 2018 19:27 UTC

Return-Path: <iesg-secretary@ietf.org>
X-Original-To: dnsop@ietf.org
Delivered-To: dnsop@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D24EE130F17; Tue, 11 Sep 2018 12:27:50 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.83.1
Auto-Submitted: auto-generated
Precedence: bulk
CC: dnsop-chairs@ietf.org, Benno Overeinder <benno@NLnetLabs.nl>, dnsop@ietf.org, draft-ietf-dnsop-attrleaf-fix@ietf.org, benno@NLnetLabs.nl, warren@kumari.net
Reply-To: ietf@ietf.org
Sender: <iesg-secretary@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Reply-To: ietf@ietf.org
Message-ID: <153669407082.17065.3260310140712562222.idtracker@ietfa.amsl.com>
Date: Tue, 11 Sep 2018 12:27:50 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/J7POabk1MCzaZHa4tELuvLPN6fI>
Subject: [DNSOP] Last Call: <draft-ietf-dnsop-attrleaf-fix-04.txt> (DNS Attrleaf Changes: Fixing Specifications with Underscored Node Name Use) to Best Current Practice
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 11 Sep 2018 19:27:51 -0000

The IESG has received a request from the Domain Name System Operations WG
(dnsop) to consider the following document: - 'DNS Attrleaf Changes: Fixing
Specifications with Underscored Node Name
   Use'
  <draft-ietf-dnsop-attrleaf-fix-04.txt> as Best Current Practice

PLEASE NOTE: The draft-ietf-dnsop-attrleaf-fix and 
draft-ietf-dnsop-attrleaf documents are very closely related. Please
read **both** of them when commenting.


The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2018-09-25. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the beginning of
the Subject line to allow automated sorting.

Abstract


   Original uses of an underscore character as a domain node name
   prefix, which creates a space for constrained interpretation of
   resource records, 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
   now has been defined.  However the existing specifications that use
   underscore naming need to be modified, 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.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-dnsop-attrleaf-fix/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-dnsop-attrleaf-fix/ballot/


No IPR declarations have been submitted directly on this I-D.


The document contains these normative downward references.
See RFC 3967 for additional information: 
    rfc3887: Message Tracking Query Protocol (Proposed Standard - IETF stream)
    rfc5415: Control And Provisioning of Wireless Access Points (CAPWAP) Protocol Specification (Proposed Standard - IETF stream)
    rfc4976: Relay Extensions for the Message Sessions Relay Protocol (MSRP) (Proposed Standard - IETF stream)
    rfc5518: Vouch By Reference (Proposed Standard - IETF stream)
    rfc3861: Address Resolution for Instant Messaging and Presence (Proposed Standard - IETF stream)
    rfc4387: Internet X.509 Public Key Infrastructure Operational Protocols: Certificate Store Access via HTTP (Proposed Standard - IETF stream)
    rfc4386: Internet X.509 Public Key Infrastructure Repository Locator Service (Experimental - IETF stream)
    rfc6011: Session Initiation Protocol (SIP) User Agent Configuration (Informational - IETF stream)
    rfc4120: The Kerberos Network Authentication Service (V5) (Proposed Standard - IETF stream)
    rfc5679: Locating IEEE 802.21 Mobility Services Using DNS (Proposed Standard - IETF stream)
    rfc5928: Traversal Using Relays around NAT (TURN) Resolution Mechanism (Proposed Standard - IETF stream)
    rfc8145: Signaling Trust Anchor Knowledge in DNS Security Extensions (DNSSEC) (Proposed Standard - IETF stream)
    rfc5864: DNS SRV Resource Records for AFS (Proposed Standard - IETF stream)
    rfc7489: Domain-based Message Authentication, Reporting, and Conformance (DMARC) (Informational - Independent Submission Editor stream)
    rfc2782: A DNS RR for specifying the location of services (DNS SRV) (Proposed Standard - IETF stream)
    rfc5766: Traversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN) (Proposed Standard - IETF stream)
    rfc6117: IANA Registration of Enumservices: Guide, Template, and IANA Considerations (Proposed Standard - IETF stream)
    rfc3263: Session Initiation Protocol (SIP): Locating SIP Servers (Proposed Standard - IETF stream)
    rfc3529: Using Extensible Markup Language-Remote Procedure Calling (XML-RPC) in Blocks Extensible Exchange Protocol (BEEP) (Experimental - Independent Submission Editor stream)
    rfc7208: Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1 (Proposed Standard - IETF stream)
    rfc6733: Diameter Base Protocol (Proposed Standard - IETF stream)
    rfc5780: NAT Behavior Discovery Using Session Traversal Utilities for NAT (STUN) (Experimental - IETF stream)
    rfc6186: Use of SRV Records for Locating Email Submission/Access Services (Proposed Standard - IETF stream)
    rfc3832: Remote Service Discovery in the Service Location Protocol (SLP) via DNS SRV (Experimental - IETF stream)
    rfc5509: Internet Assigned Numbers Authority (IANA) Registration of Instant Messaging and Presence DNS SRV RRs for the Session Initiation Protocol (SIP) (Proposed Standard - IETF stream)
    rfc3958: Domain-Based Application Service Location Using SRV RRs and the Dynamic Delegation Discovery Service (DDDS) (Proposed Standard - IETF stream)
    rfc3620: The TUNNEL Profile (Proposed Standard - IETF stream)
    rfc5026: Mobile IPv6 Bootstrapping in Split Scenario (Proposed Standard - IETF stream)
    rfc6120: Extensible Messaging and Presence Protocol (XMPP): Core (Proposed Standard - IETF stream)
    rfc5389: Session Traversal Utilities for NAT (STUN) (Proposed Standard - IETF stream)
    rfc7553: The Uniform Resource Identifier (URI) DNS Resource Record (Informational - IETF stream)
    rfc4227: Using the Simple Object Access Protocol (SOAP) in Blocks Extensible Exchange Protocol (BEEP) (Proposed Standard - IETF stream)
    rfc5617: DomainKeys Identified Mail (DKIM) Author Domain Signing Practices (ADSP) (Historic - IETF stream)
    rfc3921: Extensible Messaging and Presence Protocol (XMPP): Instant Messaging and Presence (Proposed Standard - IETF stream)
    rfc5555: Mobile IPv6 Support for Dual Stack Hosts and Routers (Proposed Standard - IETF stream)
    rfc3404: Dynamic Delegation Discovery System (DDDS) Part Four: The Uniform Resource Identifiers (URI) (Proposed Standard - IETF stream)
    rfc5328: A Uniform Resource Name (URN) Namespace for the Digital Video Broadcasting Project (DVB) (Informational - IETF stream)
    rfc5804: A Protocol for Remotely Managing Sieve Scripts (Proposed Standard - IETF stream)
    rfc7671: The DNS-Based Authentication of Named Entities (DANE) Protocol: Updates and Operational Guidance (Proposed Standard - IETF stream)