| rfc7553v4.txt | rfc7553.txt | |||
|---|---|---|---|---|
| Internet Engineering Task Force (IETF) P. Faltstrom | Internet Engineering Task Force (IETF) P. Faltstrom | |||
| Request for Comments: 7553 Netnod | Request for Comments: 7553 Netnod | |||
| Category: Informational O. Kolkman | Category: Informational O. Kolkman | |||
| ISSN: 2070-1721 ISOC | ISSN: 2070-1721 ISOC | |||
| May 2015 | June 2015 | |||
| The Uniform Resource Identifier (URI) DNS Resource Record | The Uniform Resource Identifier (URI) DNS Resource Record | |||
| Abstract | Abstract | |||
| This document describes the already registered DNS resource record | This document describes the already registered DNS resource record | |||
| (RR) type, called the Uniform Resource Identifier (URI) RR, that is | (RR) type, called the Uniform Resource Identifier (URI) RR, that is | |||
| used for publishing mappings from hostnames to URIs. | used for publishing mappings from hostnames to URIs. | |||
| Status of This Memo | Status of This Memo | |||
| skipping to change at page 7, line 14 | skipping to change at page 7, line 14 | |||
| 5.2. Relation to S-NAPTR | 5.2. Relation to S-NAPTR | |||
| The URI resource record type is not a replacement for the S-NAPTR. | The URI resource record type is not a replacement for the S-NAPTR. | |||
| It is instead an extension and the second step of the S-NAPTR | It is instead an extension and the second step of the S-NAPTR | |||
| resolution can resolve a URI resource record instead of using SRV | resolution can resolve a URI resource record instead of using SRV | |||
| records and yet another algorithm for how to use SRV records for the | records and yet another algorithm for how to use SRV records for the | |||
| specific protocol. | specific protocol. | |||
| $ORIGIN example.com. | $ORIGIN example.com. | |||
| ;; order pref flags | ;; order pref flags | |||
| IN NAPTR 100 10 "D" "EM:ProtA" ( ; service | IN NAPTR 100 10 "D" "EM:ProtA" ( ; service | |||
| "" ; regexp | "" ; regexp | |||
| _http._tcp.example.com. ; replacement | _http._tcp.example.com. ) ; replacement | |||
| _http._tcp IN URI 10 1 "http://www.example.com/path" | ||||
| _http._tcp IN URI 10 1 "http://www.example.com/path" | ||||
| 5.3. Relation to U-NAPTR | 5.3. Relation to U-NAPTR | |||
| The URI resource record type, together with S-NAPTR, can be viewed as | The URI resource record type, together with S-NAPTR, can be viewed as | |||
| a replacement for U-NAPTR [RFC4848]. The URI resource record type is | a replacement for U-NAPTR [RFC4848]. The URI resource record type is | |||
| only interesting when one know a base domain name, a protocol, and a | only interesting when one know a base domain name, a protocol, and a | |||
| service so that one can compose the record to look up. NAPTR records | service so that one can compose the record to look up. NAPTR records | |||
| of any kind are used to look up what services exist for a certain | of any kind are used to look up what services exist for a certain | |||
| domain, which is one step before the URI resource record is used. | domain, which is one step before the URI resource record is used. | |||
| End of changes. 2 change blocks. | ||||
| 6 lines changed or deleted | 7 lines changed or added | |||
This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||