Passive DNS Common Output Format
Find a file
paul vixie 25766cb2b2
Update pdns-qof.xml
origin can't be a URI because the responder has no reason to know the access method (HTTP vs HTTPS for example, or others in the future) that the requestor used to reach the service. what's important is to provide a unique origin name for this row, so as to disambiguate it from other rows which may have the same name and type but a different rrset. for that we need only a domain name, which we might actually prefer to represent in the web's and SNMP's resource style, as in, .info.dnsdb.api rather than api.dnsdb.info. for now i've assumed that we'll use a domain name, which will be the service's understanding of its advertised name, rather than as a URI, which could include a lot of details that the origin server will not know. if a URI is given by some pre-standard server, then only its domain name will be meaningful.
2019-07-24 19:46:13 -06:00
i-d Update pdns-qof.xml 2019-07-24 19:46:13 -06:00
meeting clarify some things from the meeting notes 2013-12-25 17:03:21 +01:00
slides re-do pictures 2014-03-04 16:52:59 +00:00
to-submit chg: [I-D] submitted draft 2019-02-10 12:51:24 +01:00
INSTALL.md document requirements 2013-12-27 16:25:16 +01:00
README.md chg: [doc] fixed the multiple READMEs madness 2019-02-10 22:07:12 +01:00
TODO.md fixed ABNF, updated TODO.md 2014-02-27 14:45:32 +01:00

Passive DNS - Common Output Format

This document describes the output format used between Passive DNS query interface. The output format description includes also a common meaning per Passive DNS system.

How to Contribute to the Document

You can make pull request to the xml document. We are looking for comments from passive DNS developers in order to improve the document.

IETF Internet-Draft