You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<t>This document defines a "Relative Label" which may appear within domain names. This new label type enables resource records to be stored with their relative form (e.g. "www" instead of "www.example.com.").</t>
18
+
<t>This document defines a "Relative Label" which may appear within domain names. This new label type enables resource records to be used with their relative form (e.g. "www" instead of "www.example.com.").</t>
19
19
</section>
20
20
<section>
21
21
<name>Terminology</name>
22
22
<t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in <xreftarget="RFC2119"/>.</t>
23
23
</section>
24
24
<section>
25
25
<name>Motivation</name>
26
-
<t>Relative labels are intended to efficiently solve the problem of using FQDNs when a relative label is wanted. For example, when someone wants to add the MX record "0 mx" instead of "0 mx.example.com." using DNS UPDATE <xreftarget="RFC2136"/>. It is also useful for DNS providers that store all the records in binary format. Saving data in binary requires less space and the data is already in wire format, but at the moment there is no way to save relative domains.</t>
26
+
<t>Relative labels are intended to efficiently solve the problem of using FQDNs when a relative label is wanted. For example, when someone wants to add the MX record "0 mx" instead of "0 mx.example.com." to a zone using DNS UPDATE <xreftarget="RFC2136"/>. It is also useful for DNS providers that store all the records in binary format. Saving data in binary requires less space and the data is already in wire format, but at the moment there is no way to save relative domains in their binary form.</t>
27
27
</section>
28
28
<section>
29
29
<name>Label Format</name>
30
-
<t>Relative labels can only appear in the end of a relative FQDN, like the zero octet only appears in the end of an absolute FQDN. Message compression is possible when also using the relative label, but because the relative label already gives the possibility to leave out the zone name, message compression will likely have less effect.</t>
30
+
<t>Relative labels can only appear in the end of a relative FQDN, like the zero octet only appears in the end of an absolute FQDN. [TODO: MOVE -->] Message compression is possible when also using the relative label, but because the relative label already gives the possibility to leave out the zone name, message compression will likely have less effect.</t>
31
31
<section>
32
32
<name>Wire format</name>
33
33
<figure>
@@ -46,17 +46,29 @@
46
46
<t>As described in <xreftarget="RFC1035"/>, relative domain names are domain names that don't end with a dot.</t>
47
47
</section>
48
48
<section>
49
-
<name>Canonical Representation and Sort Order</name>
50
-
<t>Before records are sorted for DNSSEC <xreftarget="RFC2065"/> purposes, the resource record MUST be converted to canonical form. This simply happens by replacing the relative label by the whole zone name. Also, the relative label should not appear when doing queries, except for AXFR and IXFR.</t>
49
+
<name>Examples</name>
50
+
<t>When an absolute domain name like "www.example.com." is converted to binary, its hexadecimal representation would be: [03] 77 77 77 [07] 65 78 61 6D 70 6C 65 [03] 63 6F 6D [00]. The square brackets indicate the label lengths.</t>
51
+
<t>When converting a relative domain name like "www.subdomain" to binary, its hexadecimal representation becomes: [03] 77 77 77 [09] 73 75 62 64 6F 6D 61 69 6E [40]. The square brackets also indicate the labels lengths here, except for [40], which is the extended label type defined by this specification.</t>
51
52
</section>
52
53
</section>
54
+
<section>
55
+
<name>Canonical Representation</name>
56
+
<t>Relative domain names do not contain the zone they belong to. For the resource records, in order to be queried with the QUERY opcode or sorted for DNSSEC <xreftarget="RFC4033"/>, at some moment the records should be converted to their canonical form. To be able to do that, the absolute form of the domain name should be known.</t>
57
+
<t>To retrieve the absolute domain name from a relative domain name, the containing zone MUST be known from context. In DNS UPDATE <xreftarget="RFC2136"/>, the zone is sent in the zone section, which a renaming of the question section. When using binary zone files, the zone will likely be encoded in the file header or the file name.</t>
58
+
<t>On binary level, to get the absolute form of the domain name, the last byte of the relative domain name, 0x40, MUST be removed. Then, the binary form of the zone name MUST be appended. For example, [03] 77 77 77 [40] (www) and [07] 65 78 61 6D 70 6C 65 [03] 63 6F 6D [00] (example.com.), will become [03] 77 77 77 [07] 65 78 61 6D 70 6C 65 [03] 63 6F 6D [00] (www.example.com.).
59
+
<t>Relative labels should be avoided in QUERY results, because clients MAY NOT support it. Also, for supporting clients, it is impossible know which zone the records belong to. For AXFR and IXFR, it is possible to know the zone, so using the relative label for those queries MAY be considered.</t>
60
+
</section>
61
+
<section>
62
+
<name>Implementation</name>
63
+
<t>Implementation is OPTIONAL, so clients SHOULD NOT expect every server to support this feature. An indicator MAY BE added in the future for servers to indicate that they support relative labels and for which record types.</t>
64
+
</section>
53
65
<section>
54
66
<name>IANA Considerations</name>
55
67
<t>This document defines one Extended Label Type, termed the Relative Label, and requests registration of the code point 000000 binary in the space defined by <xreftarget="RFC2671"/>.</t>
56
68
</section>
57
69
<section>
58
70
<name>Security Considerations</name>
59
-
<t>All security considerations which apply to traditional ASCII DNS labels apply equally to binary labels. The canonicalization and sorting rules of section 3.3 allow these to be addressed by DNS Security <xreftarget="RFC2065"/>.</t>
71
+
<t>All security considerations which apply to traditional ASCII DNS labels apply equally to binary labels. The canonicalization and sorting rules of section 3.3 allow these to be addressed by DNS Security <xreftarget="RFC4033"/>.</t>
60
72
</section>
61
73
</middle>
62
74
<back>
@@ -71,15 +83,6 @@
71
83
<seriesInfoname="RFC"value="1035"/>
72
84
<seriesInfoname="DOI"value="10.17487/RFC1035"/>
73
85
</reference>
74
-
<referenceanchor="RFC2065">
75
-
<front>
76
-
<title>Domain Name System Security Extensions</title>
0 commit comments