URI Schemes and Formats

RFC 2806: URLs for Telephone Calls

RFC 2806 defines the format for telephone URLs, which are URLs that represent telephone numbers. This is crucial for integrating telephone services with the web and allows users to initiate telephone calls via hyperlinks. The document specifies how to represent global telephone numbers, local numbers, extensions, and service codes within a URL format, enabling these numbers to be used within Internet services, including SIP. This integration facilitates the launching of calls from web browsers or other Internet-enabled devices and services.

RFC 3966: The tel URI for Telephone Numbers

RFC 3966 obsoletes RFC 2806 by providing a standardized method for representing telephone numbers as Uniform Resource Identifiers (URIs), thus enhancing the way telephone calls are integrated with various Internet services. It establishes a more structured format for 'tel' URIs, offering clear guidelines for encoding global and local phone numbers in internet-based applications.

RFC 5341: The Internet Assigned Number Authority (IANA) tel Uniform Resource Identifier (URI) Parameter Registry

RFC 5341 updates RFC 3966 by establishing a registry for the parameters used in 'tel' URIs. This document outlines the process and criteria for adding new parameters to the 'tel' URI scheme, managed by the Internet Assigned Number Authority (IANA). This update ensures a structured and standardized approach to extending the 'tel' URI scheme, facilitating its adaptability and evolution in line with emerging telecommunications and internet technologies.

RFC 4694: Number Portability Parameters for the "tel" URI

RFC 4694 extends the "tel" Uniform Resource Identifier (URI) scheme by introducing parameters that support number portability. Number portability allows telephone numbers to be moved across different service providers or geographical locations while retaining the same number. This is crucial for maintaining continuity for users despite changes in their telecommunication services. The RFC specifies how these parameters can be used within the "tel" URI scheme to indicate the original network or carrier from which a number has been ported. This enhancement aids in the correct routing and billing of calls in systems where number portability is a factor, ensuring that calls are correctly directed to the ported numbers without disruption.

RFC 6068: The 'mailto' URI Scheme

RFC 6068 specifies the 'mailto' URI (Uniform Resource Identifier) scheme, which is used for generating email addresses in hyperlinks. This RFC builds upon previous specifications by detailing how email addresses and headers can be incorporated into a URI format, allowing for the creation of clickable links that can automatically populate the recipient's address, subject line, body text, and other email fields when opened in an email client. This functionality is instrumental in web pages, documents, and applications, providing a streamlined method for users to initiate email communication without manually entering email details. RFC 6068 defines the syntax for these URIs, including rules for encoding special characters to ensure compatibility across different email clients and platforms. By formalizing the 'mailto' URI scheme, RFC 6068 enhances the usability and interoperability of email links, facilitating more efficient communication and interaction in digital content.