[DNSOP] RFC 8509 on A Root Key Trust Anchor Sentinel for DNSSEC

rfc-editor@rfc-editor.org Tue, 18 December 2018 21:48 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 5196C130F19; Tue, 18 Dec 2018 13:48:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 VGQMm7T9L5cy; Tue, 18 Dec 2018 13:47:59 -0800 (PST)
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 7B2B2130934; Tue, 18 Dec 2018 13:47:59 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id D7877B80C14; Tue, 18 Dec 2018 13:47:36 -0800 (PST)
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: <20181218214736.D7877B80C14@rfc-editor.org>
Date: Tue, 18 Dec 2018 13:47:36 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/9TBa_Llj-V5lIk18a50Tj5vuemw>
Subject: [DNSOP] =?utf-8?q?RFC_8509_on_A_Root_Key_Trust_Anchor_Sentinel_f?= =?utf-8?q?or_DNSSEC?=
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: Tue, 18 Dec 2018 21:48:01 -0000

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

        
        RFC 8509

        Title:      A Root Key Trust Anchor 
                    Sentinel for DNSSEC 
        Author:     G. Huston, 
                    J. Damas,
                    W. Kumari
        Status:     Standards Track
        Stream:     IETF
        Date:       December 2018
        Mailbox:    gih@apnic.net, 
                    joao@apnic.net, 
                    warren@kumari.net
        Pages:      19
        Characters: 43683
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-dnsop-kskroll-sentinel-17.txt

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

        DOI:        10.17487/RFC8509

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 a mechanism that
will allow an end user and third parties to determine the trusted key
state for the root key of the resolvers that handle that user's DNS
queries.  Note that this method is only applicable for determining
which keys are in the trust store for the root key.

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