RFC 3958:Domain-Based Application Service Location...
RFC-Ref

tree


Click on the red underlined text to get to the source

... NAPTR process for a particular application service can be thought of as a "tree". Each NAPTR RR that is retrieved points to more NAPTR ...
... Even though a particular client can "prune" the tree to use only those records referring to application protocols supported by the client ...
... those records referring to application protocols supported by the client, the tree could be quite deep, and retracing the tree to retry other targets ...
... application protocols supported by the client, the tree could be quite deep, and retracing the tree to retry other targets can become expensive if the tree ...
... tree to retry other targets can become expensive if the tree has many branches. Therefore, ...
... target, the application will be expected to continue through the S-NAPTR tree to try the (less preferred) alternatives. ...


... host-port in the S-NAPTR tree. The pseudocode ...
... sheds all context of where in the S-NAPTR tree it finished. Therefore, client software writers could ...



Google
Web
RFC-Ref