E.164
Click on the red underlined text to get to the source
... Domain Name System (DNS) for
storage of E.164 numbers. More specifically, how DNS can be used for
identifying available services ...
... DNS can be used for
identifying available services connected to one E.164 number. It
specifically obsoletes RFC 2916(-> 3761prop) to bring it in line with the Dynamic
Delegation Discovery System ...
... Numbers in the international format [5], called within this document
E.164 numbers, into DNS names and the use of existing DNS services ...
... NAPTR records, one can look up
what services are available for a specific E.164 in a decentralized
way with distributed management of the different levels in the lookup ...
... 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 ...
... context of numbers allocated according to the ITU-T recommendation
E.164. The same mechanisms might be used for private dialing plans.
If these mechanisms are re-used, the suffix ...
... policy and where it is not. The Order field in the NAPTR is a
request from the holder of the E.164 number that the records be
handled in a specific way. The Preference field is merely a
suggestion from that E.164 ...
... E.164 number that the records be
handled in a specific way. The Preference field is merely a
suggestion from that E.164 holder that one record might be better
than another. A client implementing ENUM ...
... applications MUST only query DNS for what it believes is an E.164
number. Since there are numerous dialing plans which can change over
time, it is probably impossible for a client ...
... client application to have
perfect knowledge about every valid and dialable E.164 number.
Therefore a client application, doing everything within its power,
...
... Therefore a client application, doing everything within its power,
can end up with what it thinks is a syntactically correct E.164
number which in reality is not actually valid or dialable. This
...
... user mistypes a number in a user interface. Because of this, there
is the risk that collisions between E.164 numbers and non-E.164
numbers can occur. To mitigate this risk, the E2U ...
... user interface. Because of this, there
is the risk that collisions between E.164 numbers and non-E.164
numbers can occur. To mitigate this risk, the E2U portion of the
...
...
The Application Unique String is a fully qualified E.164 number minus
any non-digit characters except for the '+' character which appears
at the beginning of the number. The "+" is kept to provide a well
...
... anchor for the AUS in order to distinguish it from other
telephone numbers that are not part of the E.164 namespace.
...
... namespace.
For example, the E.164 number could start out as "+44-116-496-0348".
To ensure that no syntactic sugar is allowed into the AUS, all non-
...
... identity rule.
The output of this rule is the same as the input. This is because
the E.164 namespace and this Applications databases are organized in
...
... The output of the First Well Known Rule for the ENUM Application is
the E.164 number minus all non-digit characters except for the +. In
order to convert this to a unique key in this Database the string is
...
... character set used to encode the substitution expression is UTF-
8. The allowed input characters are all those characters that are
allowed anywhere in an E.164 number. The characters allowed to be in
a Key are those that are currently defined for DNS domain ...
... there is a risk for a new ENUM lookup, and because of that an
infinite loop in the overall resolution process of the E.164.
2. Complex Enumservices ...
... Names within this zone are to be delegated to parties according to
the ITU-T Recommendation E.164. The names allocated should be
hierarchic in accordance with ITU-T Recommendation E.164 ...
... E.164. The names allocated should be
hierarchic in accordance with ITU-T Recommendation E.164, and the
codes should be assigned in accordance with that Recommendation.
...
... ITU-T, "The International Public Telecommunication Number Plan", Recommendation E.164, May 1997. ...