adulau/pdns-qof
1
0
Fork 0
mirror of https://github.com/adulau/pdns-qof.git synced 2024-10-06 06:21:41 +00:00
Code Issues Projects Releases Packages Wiki Activity

Add a reference to the sample implementation

Browse source
This commit is contained in:
Alexandre Dulaunoy 2013-12-25 12:50:41 +01:00
parent aa427d9fe1
commit fdf99312e0
2 changed files with 48 additions and 42 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

78
i-d/pdns-qof.txt
View file

@ -89,23 +89,23 @@ Table of Contents
7.1. Normative References . . . . . . . . . . . . . . . . . . 6 7.1. Normative References . . . . . . . . . . . . . . . . . . 6
7.2. References . . . . . . . . . . . . . . . . . . . . . . . 7 7.2. References . . . . . . . . . . . . . . . . . . . . . . . 7
7.3. Informative References . . . . . . . . . . . . . . . . . 7 7.3. Informative References . . . . . . . . . . . . . . . . . 7
Appendix A. Appendix . . . . . . . . . . . . . . . . . . . . . . 7 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7
1. Introduction 1. Introduction
Passive DNS is a technique described by Florian Weimer in 2005 in Passive DNS is a technique described by Florian Weimer in 2005 in
Passive DNS replication, F Weimer - 17th Annual FIRST Conference on Passive DNS replication, F Weimer - 17th Annual FIRST Conference on
Computer Security. Since then multiple Passive DNS implementations Computer Security [WEINERPDNS]. Since then multiple Passive DNS
evolved over time. Users of these Passive DNS servers query a server implementations evolved over time. Users of these Passive DNS
(often via WHOIS [RFC3912] or HTTP REST [REST]), parse the results servers query a server (often via WHOIS [RFC3912] or HTTP REST
and process them in other applications. [REST]), parse the results and process them in other applications.
There are multiple implementation of Passive DNS software. Users of There are multiple implementation of Passive DNS software. Users of
passive DNS query each implementation and aggregate the results for passive DNS query each implementation and aggregate the results for
their search. This document describes the output format of three their search. This document describes the output format of four
Passive DNS Systems which are in use today and which already share a Passive DNS Systems ([DNSDB],[PDNSCERTAT], [PDNSCIRCL] and [PDNSCOF])
nearly identical output format. As the format and the meaning of which are in use today and which already share a nearly identical
output format. As the format and the meaning of output fields from
@ -114,11 +114,11 @@ Dulaunoy, et al. Expires June 28, 2014 [Page 2]
Internet-Draft Passive DNS - Common Output Format December 2013 Internet-Draft Passive DNS - Common Output Format December 2013
output fields from each Passive DNS need to be consistent, we propose each Passive DNS need to be consistent, we propose in this document a
in this document a solution to commonly name each field along with solution to commonly name each field along with their corresponding
their corresponding interpretation. The format format is following a interpretation. The format format is following a simple key-value
simple key-value structure in JSON [RFC4627] format. The benefit of structure in JSON [RFC4627] format. The benefit of having a
having a consistent Passive DNS output format is that multiple client consistent Passive DNS output format is that multiple client
implementations can query different servers without having to have a implementations can query different servers without having to have a
separate parser for each individual server. passivedns-client separate parser for each individual server. passivedns-client
[PDNSCLIENT]currently implements multiple parsers due to a lack of [PDNSCLIENT]currently implements multiple parsers due to a lack of
@ -250,7 +250,7 @@ Internet-Draft Passive DNS - Common Output Format December 2013
Specifies the number of times this particular event denoted by the Specifies the number of times this particular event denoted by the
other type fields has been seen in the given time interval (between other type fields has been seen in the given time interval (between
time_last and time_first). Decimal number. time_last and time_first).
3.3.2. bailiwick 3.3.2. bailiwick
@ -349,15 +349,33 @@ Internet-Draft Passive DNS - Common Output Format December 2013
"Black ops 2008: It's the end of the cache as we know "Black ops 2008: It's the end of the cache as we know
it.", 2008, <http://kurser.lobner.dk/dDist/DMK_BO2K8.pdf>. it.", 2008, <http://kurser.lobner.dk/dDist/DMK_BO2K8.pdf>.
[DNSDB] "DNSDB API", 2013, <https://api.dnsdb.info/>.
[PDNSCERTAT]
"pDNS presentation at 4th Centr R&D workshop Frankfurt Jun
5th 2012", 2012, <http://www.centr.org/system/files/agenda
/attachment/rd4-papst-passive_dns.pdf>.
[PDNSCIRCL]
"CIRCL Passive DNS", 2012, <http://pdns.circl.lu/>.
[PDNSCLIENT] [PDNSCLIENT]
"Queries 5 major Passive DNS databases: BFK, CERTEE, "Queries 5 major Passive DNS databases: BFK, CERTEE,
DNSParse, ISC, and VirusTotal.", 2013, <https://github.com DNSParse, ISC, and VirusTotal.", 2013, <https://github.com
/chrislee35/passivedns-client>. /chrislee35/passivedns-client>.
[PDNSCOF] "Passive DNS server interface using the common output
format", 2013, <https://github.com/adulau/pdns-qof-server/
>.
[REST] "Representational State Transfer (REST)", 2000, [REST] "Representational State Transfer (REST)", 2000,
<http://www.ics.uci.edu/~fielding/pubs/dissertation/ <http://www.ics.uci.edu/~fielding/pubs/dissertation/
rest_arch_style.htm>. rest_arch_style.htm>.
[WEINERPDNS]
"Passive DNS Replication", 2005, <http://www.enyo.de/fw/
software/dnslogger/first2005-paper.pdf>.
7.3. Informative References 7.3. Informative References
[I-D.narten-iana-considerations-rfc2434bis] [I-D.narten-iana-considerations-rfc2434bis]
@ -366,24 +384,6 @@ Internet-Draft Passive DNS - Common Output Format December 2013
considerations-rfc2434bis-09 (work in progress), March considerations-rfc2434bis-09 (work in progress), March
2008. 2008.
[RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629,
June 1999.
[RFC3552] Rescorla, E. and B. Korver, "Guidelines for Writing RFC
Text on Security Considerations", BCP 72, RFC 3552, July
2003.
[RFC3912] Daigle, L., "WHOIS Protocol Specification", RFC 3912,
September 2004.
Appendix A. Appendix
Authors' Addresses
@ -394,6 +394,12 @@ Dulaunoy, et al. Expires June 28, 2014 [Page 7]
Internet-Draft Passive DNS - Common Output Format December 2013 Internet-Draft Passive DNS - Common Output Format December 2013
[RFC3552] Rescorla, E. and B. Korver, "Guidelines for Writing RFC
Text on Security Considerations", BCP 72, RFC 3552, July
2003.
Authors' Addresses
Alexandre Dulaunoy Alexandre Dulaunoy
CIRCL CIRCL
41, avenue de la gare 41, avenue de la gare
@ -439,10 +445,4 @@ Internet-Draft Passive DNS - Common Output Format December 2013
Dulaunoy, et al. Expires June 28, 2014 [Page 8] Dulaunoy, et al. Expires June 28, 2014 [Page 8]

12
i-d/pdns-qof.xml
View file

@ -138,7 +138,7 @@
<section title="Introduction"> <section title="Introduction">
<t>Passive DNS is a technique described by Florian Weimer in 2005 in <xref target="WEINERPDNS">Passive DNS replication, F Weimer - 17th Annual FIRST Conference on Computer Security</xref>. Since then multiple Passive DNS implementations evolved over time. Users of these Passive DNS servers query a server (often via <xref target="RFC3912">WHOIS</xref> or HTTP <xref target="REST">REST</xref>), parse the results and process them in other applications.</t> <t>Passive DNS is a technique described by Florian Weimer in 2005 in <xref target="WEINERPDNS">Passive DNS replication, F Weimer - 17th Annual FIRST Conference on Computer Security</xref>. Since then multiple Passive DNS implementations evolved over time. Users of these Passive DNS servers query a server (often via <xref target="RFC3912">WHOIS</xref> or HTTP <xref target="REST">REST</xref>), parse the results and process them in other applications.</t>
<t> <t>
There are multiple implementation of Passive DNS software. Users of passive DNS query each implementation and aggregate the results for their search. This document describes the output format of three Passive DNS Systems (<xref target="DNSDB"/>,<xref target="PDNSCERTAT"/> and <xref target="PDNSCIRCL"/>) which are in use today and which already share a nearly identical output format. There are multiple implementation of Passive DNS software. Users of passive DNS query each implementation and aggregate the results for their search. This document describes the output format of four Passive DNS Systems (<xref target="DNSDB"/>,<xref target="PDNSCERTAT"/>, <xref target="PDNSCIRCL"/> and <xref target="PDNSCOF"/>) which are in use today and which already share a nearly identical output format.
As the format and the meaning of output fields from each Passive DNS need to be consistent, we propose in this document a solution to commonly name each field along with their corresponding interpretation. The format format is following a simple key-value structure in <xref target="RFC4627">JSON</xref> format. As the format and the meaning of output fields from each Passive DNS need to be consistent, we propose in this document a solution to commonly name each field along with their corresponding interpretation. The format format is following a simple key-value structure in <xref target="RFC4627">JSON</xref> format.
The benefit of having a consistent Passive DNS output format is that multiple client implementations can query different servers without having to have a separate parser for each The benefit of having a consistent Passive DNS output format is that multiple client implementations can query different servers without having to have a separate parser for each
@ -204,7 +204,7 @@ The document does not describe the protocol (e.g. <xref target="RFC3912">WHOIS</
<t>Implementation SHOULD support one or more field.</t> <t>Implementation SHOULD support one or more field.</t>
<section title="count"> <section title="count">
<t>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.</t> <t>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.</t>
<t>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.</t> <t>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).</t>
</section> </section>
<section title="bailiwick"> <section title="bailiwick">
<t>The bailiwick is the best estimate of the apex of the zone where this data is authoritative. String.</t> <t>The bailiwick is the best estimate of the apex of the zone where this data is authoritative. String.</t>
@ -331,7 +331,13 @@ The document does not describe the protocol (e.g. <xref target="RFC3912">WHOIS</
<date year="2012"/> <date year="2012"/>
</front> </front>
</reference> </reference>
<reference anchor="PDNSCOF" target="https://github.com/adulau/pdns-qof-server/">
<front>
<title>Passive DNS server interface using the common output format</title>
<author fullname="Alexandre Dulaunoy"/>
<date year="2013"/>
</front>
</reference>
</references> </references>
<references title="Informative References"> <references title="Informative References">