From 7973c9dff3799977059ab2d1c95ac9ccf8dd7a01 Mon Sep 17 00:00:00 2001 From: Aaron Kaplan Date: Tue, 2 Apr 2013 17:23:07 +0200 Subject: [PATCH] session with Paul, Henry --- i-d/pdns-qof.xml | 61 ++++++++++++++++++++++++------------------------ 1 file changed, 30 insertions(+), 31 deletions(-) diff --git a/i-d/pdns-qof.xml b/i-d/pdns-qof.xml index 8c68a7c..2473591 100644 --- a/i-d/pdns-qof.xml +++ b/i-d/pdns-qof.xml @@ -84,6 +84,21 @@ http://www.cert.at/ + + + ISC +
+ + + + + + + + + vixie@isc.org + / General @@ -139,19 +154,6 @@ The document does not describe the protocol (e.g. whois, HTTP REST or XMPP) used Depending on the clients request, there might be one of three different answers from the server: Whois (human readable) output format (key-value), JSON output and optionally Bind zone file output format. XXX FIXME: how does the client select which answer format he wants? XXX -
- - This output format originates with the original design of BFK's passive DNS server implementation. The intent is to be be human readable. Every implementation MUST support the Whois human readable format. - -
A sample output using the Whois format:
-
The intent of this output format is to be easily parseable by scripts. Every implementation SHOULD support the JSON output format.
A sample output using the JSON format:
-
-
A sample output using the Bind format:
-
@@ -184,36 +181,38 @@ google-public-dns-a.google.com. IN A 8.8.8.8 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). Currently known and supported textual descritptions 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 rtype values. In addition, a client MUST be able to handle a decimal value (as mentioned above) as answer. + + XXX reference to RFC 3597.XXX
This field returns the data of the queried resource. In general, this is to be interpreted as string. Depending on the rtype, this can be an IPv4 or IPv6 address, a domain name (as in the case of CNAMEs), an SPF record, etc. A client MUST be able to interpret any value which is legal as the right hand side in a DNS zone file RFC 1035 and RFC 1034. + XXX reference to RFC 3597.XXX
- This field returns the first time that the record / unique tuple (rrname, rrtype, rdata) has been seen by the passive DNS. The date is expressed in ISO 8601 and UTC. + This field returns the first time that the record / unique tuple (rrname, rrtype, rdata) has been seen by the passive DNS. The date is expressed in seconds (decimal ascii) since 1st of January 1970 (unix timestamp). The time zone MUST be UTC.
- This field returns the last time that the unique tuple (rrname, rrtype, rdata) record has been seen by the passive DNS. The date is expressed in ISO 8601 and UTC. + This field returns the last time that the unique tuple (rrname, rrtype, rdata) record has been seen by the passive DNS. The date is XXXX.
Implementation SHOULD support one or more field. -
- This field returns the sensor information where the record was seen. The sensor_id is expressed in a decimal value. -
- Specifies how many authoritative answers were received with the set of answers (i.e. same data) over all sensors. The number of requests is expressed as a decimal value. -
-
- the TTL as specified in RFC 1035 as a decimal value. + #Specifies how many answers were received with the set of answers (i.e. same data). The number of requests is expressed as a decimal value. + Specifies the number of times this particular event denoted by the other type fields has been seen in the given time interval (between time_last and time_first). Decimal number.
- XXX FIXME: input from ISC needed -
-
- the class as specified in RFC 1035. Valid values are IN, HS (for HESIOD), CH (for CHAOS). May be omitted, the default assumption that a client should make is IN. + The bailiwick is the best estimate of the apex of the zone where this data is authoritative. String.
+
+ Implementations MAY support the following fields: +
+ This field returns the sensor information where the record was seen. The sensor_id is an opaque byte string as defined by RFC5001 (XXX ref)) +
+
+
An x- prefixed key means that is an extension and a non-standard field defined by the implementation of the passive DNS.