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

        
        RFC 9448

        Title:      TNAuthList Profile of Automated Certificate 
                    Management Environment (ACME) Authority Token 
        Author:     C. Wendt,
                    D. Hancock,
                    M. Barnes,
                    J. Peterson
        Status:     Standards Track
        Stream:     IETF
        Date:       September 2023
        Mailbox:    [email protected],
                    [email protected],
                    [email protected],
                    [email protected]
        Pages:      15
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-acme-authority-token-tnauthlist-13.txt

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

        DOI:        10.17487/RFC9448

This document defines a profile of the Automated Certificate
Management Environment (ACME) Authority Token for the automated and
authorized creation of certificates for Voice over IP (VoIP)
telephone providers to support Secure Telephone Identity (STI) using
the TNAuthList defined by STI certificates.

This document is a product of the Automated Certificate Management Environment 
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 [email protected].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


_______________________________________________
Acme mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/acme

Reply via email to