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

U-NAPTR


Click on the red underlined text to get to the source

... Although this is defining a new and separate DDDS Application, dubbed U-NAPTR, it is built from the same principles as the Straightforward NAPTR (S-NAPTR ...
... miss to suit their needs. This U-NAPTR is effectively a modest extension to S-NAPTR, to accommodate the use of URIs ...


... Straightforward URI-Enabled NAPTR (U-NAPTR) ...
... S-NAPTR specification [2]. The intention of U-NAPTR is to provide everything that S-NAPTR does, except that it allows the use of the "U" flag in ...
... U-NAPTR permits the same flags as S-NAPTR ("S", "A", or empty), plus the "U" Flag. For the U-NAPTR ...
... U-NAPTR permits the same flags as S-NAPTR ("S", "A", or empty), plus the "U" Flag. For the U-NAPTR DDDS Application, the presence of the "U" Flag in the NAPTR record ...
... U-NAPTR permits regular expressions of a form that does a complete replacement of the matched string with a URI ...
... URI). The specific allowed syntax for U-NAPTR regular expressions is: ...
... With this limited form of regular expression, applications using U-NAPTR need not implement full regular expression parsers. ...


... Sample U-NAPTR DNS Records ...


... Formal Definition of U-NAPTR Application of DDDS ...
... client obtains a NAPTR RR for a U-NAPTR-using application that contains any other flag, that NAPTR RR ...


... requirements on IANA, but provides the basis upon which U-NAPTR-using services can make use of the existing IANA registries ...


... U-NAPTR has the same considerations for security as S-NAPTR; see ...
... S-NAPTR; see Section 8 of [2]. U-NAPTR has the additional consideration that resolving URIs (from the result of the DDDS ...
... DNSSEC, client software can be confident that the URI obtained using U-NAPTR is indeed the one specified by the administrator of the domain ...



Google
Web
RFC-Ref