RFC 2916:E.164 number and DNS
RFC-Ref

E.164


Click on the red underlined text to get to the source

... Through transformation of E.164 numbers into DNS names and the use of existing DNS ...


... E.164 numbers and DNS ...
... domain "e164.arpa" is being populated in order to provide the infrastructure in DNS for storage of E.164 numbers. In order to facilitate distributed operations, this domain is divided into ...
... facilitate distributed operations, this domain is divided into subdomains. Holders of E.164 numbers which want to be listed in DNS should contact the appropriate zone administrator ...
... To find the DNS names for a specific E.164 number, the following procedure is to be followed: ...
... 1. See that the E.164 number is written in its full form, including the countrycode IDDD. Example: +46-8-9761234 ...
... The '+' is kept in stage 2 in section 2 to flag that the number which the regular expression is operating on is a E.164 number. Future work will be needed to determine how other numbering plans (such as closed ones) might be identified. It is possible, but not definite, ...


... Fetching URIs given an E.164 number ...
... The input is an E.164 encoded telephone number. The output is a Uniform Resource Identifier ...
... An E.164 number, without any characters but leading '+' and digits, (result of step 2 in section 2 above) is the input to the NAPTR ...
... Specification of Service E2U (E.164 to URI) ...
... * Name: E.164 to URI * Mnemonic ...
... E2U * Number of Operands: 1 * Type of Each Operand: First operand is an E.164 number. * Format of Each Operand: First operand is the E.164 number in the ...
... * Type of Each Operand: First operand is an E.164 number. * Format of Each Operand: First operand is the E.164 number in the form as specified in step 2 in section 2 in this document. * Algorithm ...
... * Error Conditions: o E.164 number not in the numbering plan o E.164 ...
... E.164 number not in the numbering plan o E.164 number in the numbering plan, but no URIs exist for ...
... database will cause clients to resolve the E.164 into the wrong URI. The possible intent may be to cause the client ...
... By removing the URI to which the E.164 maps, a malicious intruder may remove the client ...
... This operation is used to map a one E.164 number to a list of URIs. The first well-known ...
... well-known step in the resolution process is to remove all non-digits apart from the leading '+' from the E.164 number as described in step 1 and 2 in section 2 of this document. ...
... URI scheme [7], the procedure is restarted with this new E.164 number. The client is responsible for loop detection. ...
... E2U" "!^+46(.*)$!ldap://ldap.se/cn=01!" . We see in this example that information about all E.164 numbers in the 46 countrycode (for Sweden) exists in an LDAP server, and the ...


... zone are to be delegated to parties according to the ITU recommendation E.164. The names allocated should be hierarchic in accordance with ITU Recommendation E.164 ...
... E.164. The names allocated should be hierarchic in accordance with ITU Recommendation E.164, and the codes should assigned in accordance with that Recommendation. ...


... A user, John Smith, want to contact Sven Svensson, he to start with only has the E.164 number of Sven, i.e. +46-8-9761234. He takes the number, and enters the number in his communication client, which ...
... client removes the dashes, and ends up with the E.164 number +4689761234. That is what is used in the algorithm for NAPTR records ...
... The client converts the E.164 number into the domain name 4.3.2.1.6.7.9.8.6.4.e164.arpa., and queries ...



Google
Web
RFC-Ref