rfc9448v2.txt | rfc9448.txt | |||
---|---|---|---|---|
Internet Engineering Task Force (IETF) C. Wendt | Internet Engineering Task Force (IETF) C. Wendt | |||
Request for Comments: 9448 Somos Inc. | Request for Comments: 9448 D. Hancock | |||
Category: Standards Track D. Hancock | Category: Standards Track Somos Inc. | |||
ISSN: 2070-1721 Comcast | ISSN: 2070-1721 M. Barnes | |||
M. Barnes | ||||
J. Peterson | J. Peterson | |||
Neustar Inc. | Neustar Inc. | |||
July 2023 | September 2023 | |||
TNAuthList Profile of Automated Certificate Management Environment | TNAuthList Profile of Automated Certificate Management Environment | |||
(ACME) Authority Token | (ACME) Authority Token | |||
Abstract | Abstract | |||
This document defines a profile of the Automated Certificate | This document defines a profile of the Automated Certificate | |||
Management Environment (ACME) Authority Token for the automated and | Management Environment (ACME) Authority Token for the automated and | |||
authorized creation of certificates for Voice over IP (VoIP) | authorized creation of certificates for Voice over IP (VoIP) | |||
telephone providers to support Secure Telephone Identity (STI) using | telephone providers to support Secure Telephone Identity (STI) using | |||
skipping to change at line 666 ¶ | skipping to change at line 665 ¶ | |||
September 2021, <https://www.rfc-editor.org/info/rfc9060>. | September 2021, <https://www.rfc-editor.org/info/rfc9060>. | |||
[RFC9110] Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke, | [RFC9110] Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke, | |||
Ed., "HTTP Semantics", STD 97, RFC 9110, | Ed., "HTTP Semantics", STD 97, RFC 9110, | |||
DOI 10.17487/RFC9110, June 2022, | DOI 10.17487/RFC9110, June 2022, | |||
<https://www.rfc-editor.org/info/rfc9110>. | <https://www.rfc-editor.org/info/rfc9110>. | |||
[RFC9447] Peterson, J., Barnes, M., Hancock, D., and C. Wendt, | [RFC9447] Peterson, J., Barnes, M., Hancock, D., and C. Wendt, | |||
"Automated Certificate Management Environment (ACME) | "Automated Certificate Management Environment (ACME) | |||
Challenges Using an Authority Token", RFC 9447, | Challenges Using an Authority Token", RFC 9447, | |||
DOI 10.17487/RFC9447, July 2023, | DOI 10.17487/RFC9447, August 2023, | |||
<https://www.rfc-editor.org/info/rfc9447>. | <https://www.rfc-editor.org/info/rfc9447>. | |||
11.2. Informative References | 11.2. Informative References | |||
[ATIS-1000080] | [ATIS-1000080] | |||
ATIS, "Signature-based Handling of Asserted information | ATIS, "Signature-based Handling of Asserted information | |||
using toKENs (SHAKEN): Governance Model and Certificate | using toKENs (SHAKEN): Governance Model and Certificate | |||
Management", ATIS-1000080.v005, December 2022, | Management", ATIS-1000080.v005, December 2022, | |||
<https://access.atis.org/apps/group_public/ | <https://access.atis.org/apps/group_public/ | |||
download.php/69428/ATIS-1000080.v005.pdf>. | download.php/69428/ATIS-1000080.v005.pdf>. | |||
skipping to change at line 706 ¶ | skipping to change at line 705 ¶ | |||
contributions to this document. | contributions to this document. | |||
Authors' Addresses | Authors' Addresses | |||
Chris Wendt | Chris Wendt | |||
Somos Inc. | Somos Inc. | |||
United States of America | United States of America | |||
Email: chris-ietf@chriswendt.net | Email: chris-ietf@chriswendt.net | |||
David Hancock | David Hancock | |||
Comcast | Somos Inc. | |||
United States of America | United States of America | |||
Email: davidhancock.ietf@gmail.com | Email: davidhancock.ietf@gmail.com | |||
Mary Barnes | Mary Barnes | |||
Neustar Inc. | Neustar Inc. | |||
United States of America | United States of America | |||
Email: mary.ietf.barnes@gmail.com | Email: mary.ietf.barnes@gmail.com | |||
Jon Peterson | Jon Peterson | |||
Neustar Inc. | Neustar Inc. | |||
End of changes. 4 change blocks. | ||||
7 lines changed or deleted | 6 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. |