Source note · E.164 numbering and dial string normalization
Under RFC 3966, two tel URIs can be equivalent only if both are global numbers or both are local numbers, so a global number never equals a local number.
Checked 2026-09-23
Both must be either a 'local-number' or a 'global-number', i.e., start with a '+'.
- Vendor
- IETF
- Product
- tel URI
- Subsystem
- comparison
- Deployment
- standard
- Region
- not restricted
- Release range
- RFC 3966
- Checked
- 2026-09-23
Sources
- RFC 3966: The tel URI for Telephone Numbers — IETF / RFC Editor · tier 1 standards and regulators · Section 4 URI Comparisons
Cite this note
APA
WarmTransfer. (2026, September 23). E.164 numbering and dial string normalization: source note e164-numbering-tel-global-local-unequal. WarmTransfer. https://warmtransfer.net/knowledge/claims/e164-numbering-tel-global-local-unequal
BibTeX
@misc{warmtransfer-claim-e164-numbering-tel-global-local-unequal,
title = {E.164 numbering and dial string normalization: source note e164-numbering-tel-global-local-unequal},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/e164-numbering-tel-global-local-unequal},
note = {Source note e164-numbering-tel-global-local-unequal, checked 2026-09-23}
}