[Ace] RFC 9482 on Constrained Application Protocol (CoAP) Transfer for the Certificate Management Protocol

rfc-editor@rfc-editor.org Sun, 05 November 2023 15:40 UTC

Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: ace@ietfa.amsl.com
Delivered-To: ace@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E3AC1C3799AF; Sun, 5 Nov 2023 07:40:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.468
X-Spam-Level:
X-Spam-Status: No, score=-4.468 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, RDNS_NONE=0.793, SPF_HELO_SOFTFAIL=0.732, SPF_SOFTFAIL=0.665, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HJzH_79JvWb1; Sun, 5 Nov 2023 07:40:30 -0800 (PST)
Received: from rfcpa.amsl.com (unknown [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8D5F9C008A6F; Sun, 5 Nov 2023 07:39:09 -0800 (PST)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 66600289D5; Sun, 5 Nov 2023 07:39:09 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, ace@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20231105153909.66600289D5@rfcpa.amsl.com>
Date: Sun, 05 Nov 2023 07:39:09 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ace/vQBnP8oMN9-UczEK2PD9lJT8HD0>
Subject: [Ace] RFC 9482 on Constrained Application Protocol (CoAP) Transfer for the Certificate Management Protocol
X-BeenThere: ace@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Authentication and Authorization for Constrained Environments \(ace\)" <ace.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ace>, <mailto:ace-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ace/>
List-Post: <mailto:ace@ietf.org>
List-Help: <mailto:ace-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ace>, <mailto:ace-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 05 Nov 2023 15:40:34 -0000

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

        
        RFC 9482

        Title:      Constrained Application Protocol (CoAP) Transfer 
                    for the Certificate Management Protocol 
        Author:     M. Sahni, Ed.,
                    S. Tripathi, Ed.
        Status:     Standards Track
        Stream:     IETF
        Date:       November 2023
        Mailbox:    msahni@paloaltonetworks.com,
                    stripathi@paloaltonetworks.com
        Pages:      9
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-ace-cmpv2-coap-transport-10.txt

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

        DOI:        10.17487/RFC9482

This document specifies the use of the Constrained Application
Protocol (CoAP) as a transfer mechanism for the Certificate
Management Protocol (CMP). CMP defines the interaction between
various PKI entities for the purpose of certificate creation and
management. CoAP is an HTTP-like client-server protocol used by
various constrained devices in the Internet of Things space.

This document is a product of the Authentication and Authorization for Constrained Environments 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