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:    msa...@paloaltonetworks.com,
                    stripa...@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-edi...@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


_______________________________________________
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

Reply via email to