RFC 8894 on Simple Certificate Enrolment Protocol

rfc-editor@rfc-editor.org Thu, 10 September 2020 17:46 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 AF8003A0AF5 for <ietf-announce@ietfa.amsl.com>; Thu, 10 Sep 2020 10:46:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 ikFY0-Rp9c9J for <ietf-announce@ietfa.amsl.com>; Thu, 10 Sep 2020 10:46:20 -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 35F173A0ADC for <ietf-announce@ietf.org>; Thu, 10 Sep 2020 10:46:19 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 80A84F4075E; Thu, 10 Sep 2020 10:45:57 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: =?UTF-8?B?UkZDIDg4OTQgb24gU2ltcGxlIENlcnRpZmljYXRlIEVucm9sbWVudCBQcm90b2NvbA==?=
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
Content-type: text/plain; charset=UTF-8
Message-Id: <20200910174557.80A84F4075E@rfc-editor.org>
Date: Thu, 10 Sep 2020 10:45:57 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/UoWAm9xEDAMpKmzLVJ1oE07kpTo>
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: Thu, 10 Sep 2020 17:46:22 -0000

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

        
        RFC 8894

        Title:      Simple Certificate Enrolment Protocol 
        Author:     P. Gutmann
        Status:     Informational
        Stream:     IETF
        Date:       September 2020
        Mailbox:    pgut001@cs.auckland.ac.nz
        Pages:      42
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-gutmann-scep-16.txt

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

        DOI:        10.17487/RFC8894

This document specifies the Simple Certificate Enrolment Protocol
(SCEP), a PKI protocol that leverages existing technology by using
Cryptographic Message Syntax (CMS, formerly known as PKCS #7) and
PKCS #10 over HTTP.  SCEP is the evolution of the enrolment protocol
sponsored by Cisco Systems, which enjoys wide support in both client
and server implementations, as well as being relied upon by numerous
other industry standards that work with certificates.


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