RFC 9448: TNAuthList Profile of Automated Certificate Management Environment (ACME) Authority Token
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC9448
- Published
- September 2023
- Authors
- C. Wendt; D. Hancock; M. Barnes; J. Peterson
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 15
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8946Personal Assertion Token (PASSporT) Extension for Diverted CallsCurrent
February 2021
- RFC 8688A Session Initiation Protocol (SIP) Response Code for Rejected CallsCurrent
December 2019
- RFC 9449OAuth 2.0 Demonstrating Proof of Possession (DPoP)Current
September 2023
- RFC 9447Automated Certificate Management Environment (ACME) Challenges Using an Authority TokenCurrent
September 2023
- RFC 9444Automated Certificate Management Environment (ACME) for SubdomainsCurrent
August 2023
- RFC 9458Oblivious HTTPCurrent
January 2024
- RFC 9459CBOR Object Signing and Encryption (COSE): AES-CTR and AES-CBCCurrent
September 2023
- RFC 9464Internet Key Exchange Protocol Version 2 (IKEv2) Configuration for Encrypted DNSCurrent
November 2023
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?