Skip to content

Commit e5ba6b8

Browse files
ben221199ben221199
committed
Initial commit
0 parents  commit e5ba6b8

File tree

2 files changed

+116
-0
lines changed

2 files changed

+116
-0
lines changed

‎README.md‎

Whitespace-only changes.

‎draft-yocto-dns-relative-label.xml‎

Lines changed: 116 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,116 @@
1+
<rfc category="info" docName="draft-yocto-dns-relative-label-00" ipr="trust200902" submissionType="IETF" version="3">
2+
<front>
3+
<title abbrev="DNS Relative Labels">Relative Labels in the Domain Name System</title>
4+
<seriesInfo name="Internet-Draft" value="draft-yocto-dns-relative-label-00"/>
5+
<author fullname="B.J. van Hartingsveldt" initials="B.J." surname="van Hartingsveldt">
6+
<organization showOnFrontPage="true">Yocto</organization>
7+
<address>
8+
<email>ben.vanhartingsveldt@yocto.com</email>
9+
</address>
10+
</author>
11+
<abstract>
12+
<t>This document defines a new DNS Label Type using the Extension Mechanisms for DNS to indicate when a relative domain name is used.</t>
13+
</abstract>
14+
</front>
15+
<middle>
16+
<section>
17+
<name>Introduction</name>
18+
<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>
19+
</section>
20+
<section>
21+
<name>Terminology</name>
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 <xref target="RFC2119"/>.</t>
23+
</section>
24+
<section>
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 <xref target="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>
27+
</section>
28+
<section>
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>
31+
<section>
32+
<name>Wire format</name>
33+
<figure>
34+
<artwork> 0 1 2 3 4 5 6 7
35+
+-+-+-+-+-+-+-+-+
36+
|0 1| ELT |
37+
+-+-+-+-+-+-+-+-+</artwork>
38+
</figure>
39+
<dl>
40+
<dt>ELT</dt>
41+
<dd>000000 binary, the six-bit extended label type <xref target="RFC2671"/> assigned to the Relative Label.</dd>
42+
</dl>
43+
</section>
44+
<section>
45+
<name>Representation format</name>
46+
<t>As described in <xref target="RFC1035"/>, relative domain names are domain names that don't end with a dot.</t>
47+
</section>
48+
<section>
49+
<name>Canonical Representation and Sort Order</name>
50+
<t>Before records are sorted for DNSSEC <xref target="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>
51+
</section>
52+
</section>
53+
<section>
54+
<name>IANA Considerations</name>
55+
<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 <xref target="RFC2671"/>.</t>
56+
</section>
57+
<section>
58+
<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 <xref target="RFC2065"/>.</t>
60+
</section>
61+
</middle>
62+
<back>
63+
<references>
64+
<name>Normative References</name>
65+
<reference anchor="RFC1035">
66+
<front>
67+
<title>Domain names - implementation and specification</title>
68+
<author fullname="P. Mockapetris" initials="P." surname="Mockapetris"/>
69+
<date month="November" year="1987"/>
70+
</front>
71+
<seriesInfo name="RFC" value="1035"/>
72+
<seriesInfo name="DOI" value="10.17487/RFC1035"/>
73+
</reference>
74+
<reference anchor="RFC2065">
75+
<front>
76+
<title>Domain Name System Security Extensions</title>
77+
<author fullname="D. Eastlake" initials="D." surname="Eastlake"/>
78+
<date month="January" year="1997"/>
79+
</front>
80+
<seriesInfo name="RFC" value="2065"/>
81+
<seriesInfo name="DOI" value="10.17487/RFC2065"/>
82+
</reference>
83+
<reference anchor="RFC2119">
84+
<front>
85+
<title>Key words for use in RFCs to Indicate Requirement Levels</title>
86+
<author fullname="S. Bradner" initials="S." surname="Bradner"/>
87+
<date month="March" year="1997"/>
88+
<abstract>
89+
<t>In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t>
90+
</abstract>
91+
</front>
92+
<seriesInfo name="BCP" value="14"/>
93+
<seriesInfo name="RFC" value="2119"/>
94+
<seriesInfo name="DOI" value="10.17487/RFC2119"/>
95+
</reference>
96+
<reference anchor="RFC2136">
97+
<front>
98+
<title>Dynamic Updates in the Domain Name System (DNS UPDATE)</title>
99+
<author fullname="P. Vixie" initials="P." surname="Vixie"/>
100+
<date month="April" year="1997"/>
101+
</front>
102+
<seriesInfo name="RFC" value="2136"/>
103+
<seriesInfo name="DOI" value="10.17487/RFC2136"/>
104+
</reference>
105+
<reference anchor="RFC2671">
106+
<front>
107+
<title>Extension mechanisms for DNS (EDNS0)</title>
108+
<author fullname="P. Vixie" initials="P." surname="Vixie"/>
109+
<date month="August" year="1999"/>
110+
</front>
111+
<seriesInfo name="RFC" value="2119"/>
112+
<seriesInfo name="DOI" value="10.17487/RFC2671"/>
113+
</reference>
114+
</references>
115+
</back>
116+
</rfc>

0 commit comments

Comments
 (0)