RFC 8649 on Hash Of Root Key Certificate Extension

rfc-editor@rfc-editor.org Mon, 26 August 2019 19:04 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 AA18E120D0A; Mon, 26 Aug 2019 12:04:56 -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 L0Dm_1B8FfDR; Mon, 26 Aug 2019 12:04:54 -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 3D113120D09; Mon, 26 Aug 2019 12:04:54 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 632A5B80BC1; Mon, 26 Aug 2019 12:04:40 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8649 on Hash Of Root Key Certificate Extension
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, spasm@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20190826190440.632A5B80BC1@rfc-editor.org>
Date: Mon, 26 Aug 2019 12:04:40 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/B2v9FoL7UpnVS20fNmViiDwWfxU>
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: Mon, 26 Aug 2019 19:05:03 -0000

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

        
        RFC 8649

        Title:      Hash Of Root Key Certificate Extension 
        Author:     R. Housley
        Status:     Informational
        Stream:     IETF
        Date:       August 2019
        Mailbox:    housley@vigilsec.com
        Pages:      10
        Characters: 22410
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-lamps-hash-of-root-key-cert-extn-07.txt

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

        DOI:        10.17487/RFC8649

This document specifies the Hash Of Root Key certificate extension.
This certificate extension is carried in the self-signed certificate
for a trust anchor, which is often called a Root Certification
Authority (CA) certificate.  This certificate extension unambiguously
identifies the next public key that will be used at some point in the
future as the next Root CA certificate, eventually replacing the
current one.

This document is a product of the Limited Additional Mechanisms for PKIX and SMIME Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. 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