A Concise Binary Object Representation (CBOR) of DNS Messages

3.1. Domain Name Representation

Domain names are represented in their commonly known string format (e.g., "example.org", see Section 2.3.1 in [RFC1035]) and in IDNA encoding [RFC5890] as a text string. For the purpose of this document, domain names remain case-insensitive as specified in [RFC1035].¶

The representation of a domain name is defined in Figure 1.¶

domain-name = tstr .regexp "([^\.]+\.)*[^\.]+"

3.2. DNS Queries

DNS queries are encoded as CBOR arrays containing up to 3 entries in the following order: The name (as text string, see Section 3.1), an optional record type (as unsigned integer), and an optional record class (as unsigned integer).¶

If the record type is elided, record type AAAA as specified in [RFC3596] is assumed. If the record class is elided, record class IN as specified in [RFC1035] is assumed. If a record class is required, the record type MUST also be provided.¶

The representation of a DNS query is defined in Figure 2.¶

type-spec = (
  record-type: uint,
  ? record-class: uint,
)
dns-question = (
  name: domain-name,
  ? type: type-spec,
)
dns-query = [dns-question]

3.3. Standard DNS Resource Records (RRs)

DNS resource records are encoded as CBOR arrays containing 2 to 5 entries in the following order: An optional name (as text string, see Section 3.1), a TTL (as unsigned integer), an optional record type (as unsigned integer), an optional record class (as unsigned integer), and lastly a record data entry (as byte string or text string).¶

If the first element of the resource record is a string, the first element is a name. If the name is elided, the name from the query, either derived from transport context or the provided question section, see Section 3.4, is assumed. If the record type is elided, the record type from the question is assumed. If record class is elided, the record class from the question is assumed. If a record class is required, the record type MUST also be provided.¶

The byte format of the record data follows the wire format as specified in Section 3.3 [RFC1035] (or other specifications of the respective record type). Note that this format does not include the RDLENGTH field from [RFC1035] as this value is encoded in the length field of the CBOR byte string.¶

If and only if the record data represents a domain name (e.g., for CNAME or PTR records), the record data MAY be represented as a text string as specified in Section 3.1. This can save 1 bytes of data, because the byte representation of DNS names requires both an additional byte to define the length of the first name component as well as a 0 byte at the end of the name. With CBOR on the other hand only 1 byte is required to define type and length of the text string.¶

The representation of a DNS resource records is defined in Figure 3.¶

rr = (
  ? name: domain-name,
  ttl: uint,
  ? type: record-type,
  rdata: bstr / domain-name,
)
dns-rr = [rr]

3.4. DNS Responses

DNS responses are encoded as array of CBOR arrays containing up to 4 entries.¶

If only 1 array is included, then this is the DNS answer section represented as an array of one or more DNS Resource Records (see Section 3.3).¶

If 2 arrays are included, then the first entry is a question section and the second entry is an answer section. The question section is encoded like a DNS query as specified in Section 3.2, the answer section is represented as an array of one or more DNS Resource Records (see Section 3.3).¶

If 3 arrays are included, then the first section is a question section, the second an answer section, and the third an additional section (TBD: back choice to favor additional section by empirical data). Again, the question section is encoded like a DNS query as specified in Section 3.2 and both answer and additional sections are represented each as an array of one or more DNS Resource Records (see Section 3.3).¶

If 4 arrays are included, then the first section is a question section, the second an answer section, the third an authority section, and the fourth an additional section (TBD: back by empirical data). They follow the specification of 3 arrays in the answer. The authority section is also represented as an array of one or more DNS Resource Records (see Section 3.3).¶

extra-sections = (
  ? authority: [1* dns-rr],
  additional: [1* dns-rr],
)
sections = (
  answer: [1* dns-rr],
) // (
  question: dns-query,
  answer: [1* dns-rr],
  ? extra: extra-sections,
)
dns-response = [sections]

3.5. EDNS(0)

TBD, do we need special formatting here?¶

5.1. Media Type Registration

This document registers the media type for the serialization format of DNS messages in CBOR. It follows the procedures specified in [RFC6838].¶

Type name: application¶

Subtype name: dns+cbor¶

Required parameters: None¶

Optional parameters: None¶

Encoding considerations: Must be encoded as using [RFC7049]. See [TBD-this-spec] for details.¶

Security considerations: See Section 4 of this draft¶

Interoperability considerations: TBD¶

Published specification: [TBD-this-spec]¶

Applications that use this media type: TBD DNS over X systems¶

Fragment Identifier Considerations: TBD¶

Additional information:¶

   Deprecated alias names for this type: N/A¶

   Magic number(s): N/A¶

   File extension(s): dnsc¶

   Macintosh file type code(s): none¶

Person & email address to contact for further information: Martine S. Lenders m.lenders@fu-berlin.de¶

Intended usage: COMMON¶

Restrictions on Usage: None?¶

Author: Martine S. Lenders m.lenders@fu-berlin.de¶

Change controller: Martine S. Lenders m.lenders@fu-berlin.de¶

Provisional registrations? No¶

5.2. CoAP Content-Format Registration

IANA is requested to assign CoAP Content-Format ID for the DNS message media type in the "CoAP Content-Formats" sub-registry, within the "CoRE Parameters" registry [RFC7252], corresponding the "application/dns+cbor" Media Type specified in Section 5.1:¶

Media-Type: application/dns+cbor¶

Encoding: -¶

Id: TBD¶

Reference: [TBD-this-spec]¶

A.1. DNS Queries

A DNS query of the record AAAA in class IN for name "example.org" is represented in CBOR extended diagnostic notation (EDN) (see Section 8 in [RFC7049] and Appendix G in [RFC8610]) as follows:¶

["example.org"]

A query of an A record for the same name is represented as¶

["example.org", 1]

A query of ANY record for that name is represented as¶

["example.org", 255, 255]

A.2. DNS Responses

The responses to the examples provided in Appendix A.1 are shown below. We use the CBOR extended diagnostic notation (EDN) (see Section 8 in [RFC7049] and Appendix G in [RFC8610]).¶

To represent an AAAA record with TTL 300 seconds for the IPv6 address 2001:db8::1, a minimal response to ["example.org"] could be¶

[[[300, h'20010db8000000000000000000000001']]]

In this case, the name is derived from the query.¶

If the name or the context is required, the following response would also be valid:¶

[[["example.org", 300, h'20010db8000000000000000000000001']]]

If the query can not be mapped to the response for some reason, a response would look like:¶

[["example.org"], [[300, h'20010db8000000000000000000000001']]]

To represent a minimal response of an A record with TTL 3600 seconds for the IPv4 address 192.0.2.1, a minimal response to ["example.org", 1] could be¶

[[300, h'c0000201']]

Note that here also the 1 of record type A can be elided, as this record type is specified in the question section.¶

Lastly, a response to ["example.org", 255, 255] could be¶

[
  ["example.org", 255, 255],
  [[3600, 12, "coap._udp.local"]],
  [
    [3600, 2, "ns1.example.org"],
    [3600, 2, "ns2.example.org"],
  ],
  [
    [
      "_coap._udp.local", 3600, 28,
      h'20010db8000000000000000000000001'
    ],
    [
      "_coap._udp.local", 3600, 28,
      h'20010db8000000000000000000000002'
    ],
    [
      "ns1.example.org", 3600, 28,
      h'20010db8000000000000000000000035'
    ],
    [
      "ns2.example.org", 3600, 28,
      h'20010db8000000000000000000003535'
    ]
  ]
]

This one advertises two local CoAP servers (identified by service name _coap._udp.local) at 2001:db8::1 and 2001:db8::2 and two nameservers for the example.org domain, ns1.example.org at 2001:db8::35 and ns2.example.org at 2001.db8::3535. Each of the transmitted records has a TTL of 3600 seconds.¶