RFC 3761:The E.164 to Uniform Resource Identifiers...
RFC-Ref

algorithm


Click on the red underlined text to get to the source

... All other capitalized terms are taken from the vocabulary found in the DDDS algorithm specification found in RFC 3403prop [2]. ...
... non-terminal Rules) where two different Rules both match the given Application Unique String. As each Rule is evaluated within the algorithm, one may match a more significant piece of the AUS than the other. For example, by using a non- terminal ...


... Database the string is converted into a domain-name according to this algorithm: 1. Remove ...
... This Database contains a field that contains flags that signal when the DDDS algorithm has finished. At this time only one flag, "U", is defined. This means that this Rule is the last one and that the output of the Rule is a URI ...
... ENUM Resolver to return two Rules. The ENUM algorithm always returns a single rule. Specific applications may have application-specific knowledge or facilities ...
... application-specific knowledge or facilities that allow them to present multiple results or speed selection, but these should never change the operation of the algorithm. ...


... changes are two: The document uses an explicit DDDS algorithm, and not only NAPTR resource records in an "ad-hoc" mode. In reality this doesn't imply ...
... NAPTR resource records in an "ad-hoc" mode. In reality this doesn't imply any changes in deployed base of applications, as the algorithm used for ENUM resolution is exactly the same. ...


... Mealling, M., "Dynamic Delegation Discovery System (DDDS) Part Two: The Algorithm", RFC 3402prop, October 2002. ...



Google
Web
RFC-Ref