RFC 8226: Secure Telephone Identity Credentials: Certificates

In order to prevent the impersonation of telephone numbers on the Internet, some kind of credential system needs to exist that cryptographically asserts…

Read RFC 8226 on the RFC Editor

Outgoing relationships (17 related RFCs)

Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 8174: Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
Normative reference — RFC 3986: Uniform Resource Identifier (URI): Generic Syntax
Normative reference — RFC 5280: Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile
Normative reference — RFC 7230: Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing
Normative reference — RFC 5912: New ASN.1 Modules for the Public Key Infrastructure Using X.509 (PKIX)
Normative reference — RFC 7519: JSON Web Token (JWT)
Normative reference — RFC 7258: Pervasive Monitoring Is an Attack
Normative reference — RFC 8017: PKCS #1: RSA Cryptography Specifications Version 2.2
Normative reference — RFC 5958: Asymmetric Key Packages
Normative reference — RFC 8224: Authenticated Identity Management in the Session Initiation Protocol (SIP)
Normative reference — RFC 8225: PASSporT: Personal Assertion Token
Normative reference — RFC 2392: Content-ID and Message-ID Uniform Resource Locators
Informative reference — RFC 2046: Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types
Informative reference — RFC 3647: Internet X.509 Public Key Infrastructure Certificate Policy and Certification Practices Framework
Informative reference — RFC 7340: Secure Telephone Identity Problem Statement and Requirements
Informative reference — RFC 7375: Secure Telephone Identity Threat Model

Incoming relationships (10 related RFCs)

Updated by, Normatively referenced by — RFC 9118: Enhanced JSON Web Token (JWT) Claim Constraints for Secure Telephone Identity Revisited (STIR) Certificates
Normatively referenced by — RFC 9060: Secure Telephone Identity Revisited (STIR) Certificate Delegation
Normatively referenced by — RFC 8862: Best Practices for Securing RTP Media Signaled with SIP
Normatively referenced by — RFC 9475: Messaging Use Cases and Extensions for Secure Telephone Identity Revisited (STIR)
Normatively referenced by — RFC 9410: Handling of Identity Header Errors for Secure Telephone Identity Revisited (STIR)
Normatively referenced by — RFC 9448: TNAuthList Profile of Automated Certificate Management Environment (ACME) Authority Token
Normatively referenced by — RFC 9795: Personal Assertion Token (PASSporT) Extension for Rich Call Data
Informatively referenced by — RFC 8224: Authenticated Identity Management in the Session Initiation Protocol (SIP)
Informatively referenced by — RFC 9115: An Automatic Certificate Management Environment (ACME) Profile for Generating Delegated Certificates
Informatively referenced by — RFC 9447: Automated Certificate Management Environment (ACME) Challenges Using an Authority Token