RFC 3966: The tel URI for Telephone Numbers

This document specifies the URI (Uniform Resource Identifier) scheme "tel". The "tel" URI describes resources identified by telephone numbers. This document…

Read RFC 3966 on the RFC Editor

Outgoing relationships (11 related RFCs)

Obsoletes, Informative reference — RFC 2806: URLs for Telephone Calls
Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 3261: SIP: Session Initiation Protocol
Normative reference — RFC 2234: Augmented BNF for Syntax Specifications: ABNF
Informative reference — RFC 2396: Uniform Resource Identifiers (URI): Generic Syntax
Informative reference — RFC 3761: The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)
Informative reference — RFC 2368: The mailto URL scheme
Informative reference — RFC 3191: Minimal GSTN address format in Internet Mail
Informative reference — RFC 3192: Minimal FAX address format in Internet Mail
Informative reference — RFC 3187: Using International Standard Book Numbers as Uniform Resource Names
Informative reference — RFC 3219: Telephony Routing over IP (TRIP)

Incoming relationships (34 related RFCs)

Updated by, Normatively referenced by — RFC 5341: The Internet Assigned Number Authority (IANA) tel Uniform Resource Identifier (URI) Parameter Registry
Normatively referenced by — RFC 6350: vCard Format Specification
Normatively referenced by — RFC 5627: Obtaining and Using Globally Routable User Agent URIs (GRUUs) in the Session Initiation Protocol (SIP)
Normatively referenced by — RFC 8224: Authenticated Identity Management in the Session Initiation Protocol (SIP)
Normatively referenced by — RFC 7852: Additional Data Related to an Emergency Call
Normatively referenced by — RFC 5025: Presence Authorization Rules
Normatively referenced by — RFC 6509: MIKEY-SAKKE: Sakai-Kasahara Key Encryption in Multimedia Internet KEYing (MIKEY)
Normatively referenced by — RFC 7643: System for Cross-domain Identity Management: Core Schema
Normatively referenced by — RFC 4355: IANA Registration for Enumservices email, fax, mms, ems, and sms
Normatively referenced by — RFC 4769: IANA Registration for an Enumservice Containing Public Switched Telephone Network (PSTN) Signaling Information
Normatively referenced by — RFC 4590: RADIUS Extension for Digest Authentication
Normatively referenced by — RFC 4967: Dial String Parameter for the Session Initiation Protocol Uniform Resource Identifier
Normatively referenced by — RFC 5278: IANA Registration of Enumservices for Voice and Video Messaging
Normatively referenced by — RFC 4715: The Integrated Services Digital Network (ISDN) Subaddress Encoding Type for tel URI
Normatively referenced by — RFC 5483: ENUM Implementation Issues and Experiences
Normatively referenced by — RFC 5876: Updates to Asserted Identity in the Session Initiation Protocol (SIP)
Normatively referenced by — RFC 7544: Mapping and Interworking of Diversion Information between Diversion and History-Info Header Fields in the Session Initiation Protocol (SIP)
Normatively referenced by — RFC 7566: Enumservice Registration for 'acct' URI
Normatively referenced by — RFC 9248: Interoperability Profile for Relay User Equipment
Informatively referenced by — RFC 4479: A Data Model for Presence
Informatively referenced by — RFC 5012: Requirements for Emergency Context Resolution with Internet Technologies
Informatively referenced by — RFC 5435: Sieve Email Filtering: Extension for Notifications
Informatively referenced by — RFC 5031: A Uniform Resource Name (URN) for Emergency and Other Well-Known Services
Informatively referenced by — RFC 7044: An Extension to the Session Initiation Protocol (SIP) for Request History Information
Informatively referenced by — RFC 7701: Multi-party Chat Using the Message Session Relay Protocol (MSRP)
Informatively referenced by — RFC 7865: Session Initiation Protocol (SIP) Recording Metadata
Informatively referenced by — RFC 7986: New Properties for iCalendar
Informatively referenced by — RFC 9553: JSContact: A JSON Representation of Contact Data
Informatively referenced by — RFC 5947: Requirements for Multiple Address of Record (AOR) Reachability Information in the Session Initiation Protocol (SIP)
Informatively referenced by — RFC 6271: Requirements for SIP-Based Session Peering
Informatively referenced by — RFC 8197: A SIP Response Code for Unwanted Calls
Informatively referenced by — RFC 6140: Registration for Multiple Phone Numbers in the Session Initiation Protocol (SIP)
Informatively referenced by — RFC 7904: A SIP Usage for REsource LOcation And Discovery (RELOAD)
Informatively referenced by — RFC 10023: The "_for-sale" Underscored and Globally Scoped DNS Node Name