[DNSOP] RFC 8145 on Signaling Trust Anchor Knowledge in DNS Security Extensions (DNSSEC)

rfc-editor@rfc-editor.org Tue, 11 April 2017 23:13 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 80DD91293D8; Tue, 11 Apr 2017 16:13:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level:
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 C8uWC6S3UyyF; Tue, 11 Apr 2017 16:13:19 -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 E8F2D1287A5; Tue, 11 Apr 2017 16:12:55 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 8CAEFB81150; Tue, 11 Apr 2017 16:12:51 -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
Message-Id: <20170411231251.8CAEFB81150@rfc-editor.org>
Date: Tue, 11 Apr 2017 16:12:51 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/GNanH8LsAgcBN-Idru92bRR7VtE>
Subject: [DNSOP] RFC 8145 on Signaling Trust Anchor Knowledge in DNS Security Extensions (DNSSEC)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
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: Tue, 11 Apr 2017 23:13:29 -0000

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

        
        RFC 8145

        Title:      Signaling Trust Anchor Knowledge in 
                    DNS Security Extensions (DNSSEC) 
        Author:     D. Wessels, W. Kumari, P. Hoffman
        Status:     Standards Track
        Stream:     IETF
        Date:       April 2017
        Mailbox:    dwessels@verisign.com, 
                    warren@kumari.net, 
                    paul.hoffman@icann.org
        Pages:      13
        Characters: 27110
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-dnsop-edns-key-tag-05.txt

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

        DOI:        10.17487/RFC8145

The DNS Security Extensions (DNSSEC) were developed to provide origin
authentication and integrity protection for DNS data by using digital
signatures.  These digital signatures can be verified by building a
chain of trust starting from a trust anchor and proceeding down to a
particular node in the DNS.  This document specifies two different
ways for validating resolvers to signal to a server which keys are
referenced in their chain of trust.  The data from such signaling
allow zone administrators to monitor the progress of rollovers in a
DNSSEC-signed zone.

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

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  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