From 3c5f0ffd48a7b27631ea8ba30921da4b3869f490 Mon Sep 17 00:00:00 2001 From: Alexandre Dulaunoy Date: Sun, 2 Feb 2014 07:10:45 +0100 Subject: [PATCH] rrtype: Resource Record (RR) TYPEs and not "DNS Label types" (dnsop feedback) --- i-d/pdns-qof.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/i-d/pdns-qof.xml b/i-d/pdns-qof.xml index ebd581d..32fb472 100644 --- a/i-d/pdns-qof.xml +++ b/i-d/pdns-qof.xml @@ -201,7 +201,7 @@ CR = %x0D This field returns the resource record type as seen by the passive DNS. The key is rrtype and the value is in the interpreted record type. If the value cannot be interpreted the decimal value is returned following the principle of transparency as described in RFC 3597. - The resource record type can be any values as described by IANA in the DNS parameters document in the section 'DNS Label types' (http://www.iana.org/assignments/dns-parameters). + The resource record type can be any values as described by IANA in the DNS parameters document in the section 'Resource Record (RR) TYPEs' (http://www.iana.org/assignments/dns-parameters). Currently known and supported textual descriptions of rrtypes are: A, AAAA, CNAME, PTR, SOA, TXT, DNAME, NS, SRV, RP, NAPTR, HINFO, A6. A client MUST be able to understand these textual rrtype values represented as a JSON string. In addition, a client MUST be able to handle a decimal value (as mentioned above) as answer represented as a JSON number.