RFC 8624 on Algorithm Implementation Requirements and Usage Guidance for DNSSEC

rfc-editor@rfc-editor.org Tue, 11 June 2019 21:54 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 CF81D12009C; Tue, 11 Jun 2019 14:54:24 -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 8WufiYlbcNUI; Tue, 11 Jun 2019 14:54:22 -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 DE20F12000F; Tue, 11 Jun 2019 14:54:22 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 5B445B82287; Tue, 11 Jun 2019 14:54:08 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: =?UTF-8?B?UkZDIDg2MjQgb24gQWxnb3JpdGhtIEltcGxlbWVudGF0aW9uIFJlcXVpcmVtZW50cyBhbmQgVXNhZ2UgR3VpZGFuY2UgZm9yIEROU1NFQw==?=
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: <20190611215408.5B445B82287@rfc-editor.org>
Date: Tue, 11 Jun 2019 14:54:08 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/8omBnwxCxhd01OQa4vgoIPfjQ08>
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: Tue, 11 Jun 2019 21:54:25 -0000

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

        
        RFC 8624

        Title:      Algorithm Implementation Requirements and Usage 
                    Guidance for DNSSEC 
        Author:     P. Wouters, 
                    O. Sury
        Status:     Standards Track
        Stream:     IETF
        Date:       June 2019
        Mailbox:    pwouters@redhat.com, 
                    ondrej@isc.org
        Pages:      11
        Characters: 24118
        Obsoletes:  RFC 6944

        I-D Tag:    draft-ietf-dnsop-algorithm-update-10.txt

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

        DOI:        10.17487/RFC8624

The DNSSEC protocol makes use of various cryptographic algorithms in
order to provide authentication of DNS data and proof of
nonexistence.  To ensure interoperability between DNS resolvers and
DNS authoritative servers, it is necessary to specify a set of
algorithm implementation requirements and usage guidelines to ensure
that there is at least one algorithm that all implementations
support.  This document defines the current algorithm implementation
requirements and usage guidance for DNSSEC.  This document obsoletes
RFC 6944.

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