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

Removed useless references

Browse source
This commit is contained in:
Alexandre Dulaunoy 2013-12-25 10:53:13 +01:00
parent 05566c0a71
commit 835483d2a0
2 changed files with 28 additions and 39 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

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

@ -88,8 +88,7 @@ Table of Contents
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
7.1. Normative References . . . . . . . . . . . . . . . . . . 6 7.1. Normative References . . . . . . . . . . . . . . . . . . 6
7.2. References . . . . . . . . . . . . . . . . . . . . . . . 7 7.2. References . . . . . . . . . . . . . . . . . . . . . . . 7
7.3. References . . . . . . . . . . . . . . . . . . . . . . . 7 7.3. Informative References . . . . . . . . . . . . . . . . . 7
7.4. Informative References . . . . . . . . . . . . . . . . . 7
Appendix A. Appendix . . . . . . . . . . . . . . . . . . . . . . 7 Appendix A. Appendix . . . . . . . . . . . . . . . . . . . . . . 7
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7
@ -106,6 +105,7 @@ Table of Contents
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 three
Passive DNS Systems which are in use today and which already share a Passive DNS Systems which are in use today and which already share a
nearly identical output format. As the format and the meaning of
@ -114,19 +114,18 @@ Dulaunoy, et al. Expires June 28, 2014 [Page 2]
Internet-Draft Abbreviated Title December 2013 Internet-Draft Abbreviated Title December 2013
nearly identical output format. As the format and the meaning of
output fields from each Passive DNS need to be consistent, we propose output fields from each Passive DNS need to be consistent, we propose
in this document a solution to commonly name each field along with in this document a solution to commonly name each field along with
their corresponding interpretation. The format format is following a their corresponding interpretation. The format format is following a
simple key-value structure in JSON [RFC4627] format. The benefit of simple key-value structure in JSON [RFC4627] format. The benefit of
having a consistent Passive DNS output format is that multiple client having a 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. [https://github.com/ separate parser for each individual server. passivedns-client
chrislee35/passivedns-client] currently implements multiple parsers [PDNSCLIENT]currently implements multiple parsers due to a lack of
due to a lack of standardization. The document does not describe the standardization. The document does not describe the protocol (e.g.
protocol (e.g. WHOIS [RFC3912], HTTP REST or XMPP) nor the query WHOIS [RFC3912], HTTP REST or XMPP) nor the query format used to
format used to query the Passive DNS. Neither does this document query the Passive DNS. Neither does this document describe "pre-
describe "pre-recursor" Passive DNS Systems. recursor" Passive DNS Systems.
1.1. Requirements Language 1.1. Requirements Language
@ -165,6 +164,7 @@ Internet-Draft Abbreviated Title December 2013
Dulaunoy, et al. Expires June 28, 2014 [Page 3] Dulaunoy, et al. Expires June 28, 2014 [Page 3]
Internet-Draft Abbreviated Title December 2013 Internet-Draft Abbreviated Title December 2013
@ -329,7 +329,7 @@ Internet-Draft Abbreviated Title December 2013
[RFC5001] Austein, R., "DNS Name Server Identifier (NSID) Option", [RFC5001] Austein, R., "DNS Name Server Identifier (NSID) Option",
RFC 5001, August 2007. RFC 5001, August 2007.
[min_ref] authSurName, authInitials., "Minimal Reference", 2006.
@ -340,18 +340,21 @@ Internet-Draft Abbreviated Title December 2013
7.2. References 7.2. References
[CACHEPOISONING]
"Black ops 2008: It's the end of the cache as we know
it.", 2008, <http://kurser.lobner.dk/dDist/DMK_BO2K8.pdf>.
7.3. References
[BAILIWICK] [BAILIWICK]
"Passive DNS Hardening", 2010, <https:// "Passive DNS Hardening", 2010, <https://
archive.farsightsecurity.com/Passive_DNS/ archive.farsightsecurity.com/Passive_DNS/
passive_dns_hardening_handout.pdf>. passive_dns_hardening_handout.pdf>.
7.4. Informative References [CACHEPOISONING]
"Black ops 2008: It's the end of the cache as we know
it.", 2008, <http://kurser.lobner.dk/dDist/DMK_BO2K8.pdf>.
[PDNSCLIENT]
"Queries 5 major Passive DNS databases: BFK, CERTEE,
DNSParse, ISC, and VirusTotal.", 2013, <https://github.com
/chrislee35/passivedns-client>.
7.3. Informative References
[I-D.narten-iana-considerations-rfc2434bis] [I-D.narten-iana-considerations-rfc2434bis]
Narten, T. and H. Alvestrand, "Guidelines for Writing an Narten, T. and H. Alvestrand, "Guidelines for Writing an
@ -371,8 +374,6 @@ Internet-Draft Abbreviated Title December 2013
Appendix A. Appendix Appendix A. Appendix
This becomes an Appendix.
Authors' Addresses Authors' Addresses
Alexandre Dulaunoy Alexandre Dulaunoy
@ -388,7 +389,6 @@ Authors' Addresses
Dulaunoy, et al. Expires June 28, 2014 [Page 7] Dulaunoy, et al. Expires June 28, 2014 [Page 7]
Internet-Draft Abbreviated Title December 2013 Internet-Draft Abbreviated Title December 2013

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

@ -142,7 +142,7 @@
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
individual server. [https://github.com/chrislee35/passivedns-client] currently implements multiple parsers due to a lack of standardization. individual server. <xref target="PDNSCLIENT">passivedns-client</xref>currently implements multiple parsers due to a lack of standardization.
The document does not describe the protocol (e.g. <xref target="RFC3912">WHOIS</xref>, HTTP REST or XMPP) nor the query format used to query the Passive DNS. Neither does this document describe "pre-recursor" Passive DNS Systems. The document does not describe the protocol (e.g. <xref target="RFC3912">WHOIS</xref>, HTTP REST or XMPP) nor the query format used to query the Passive DNS. Neither does this document describe "pre-recursor" Passive DNS Systems.
</t> </t>
@ -273,20 +273,6 @@ The document does not describe the protocol (e.g. <xref target="RFC3912">WHOIS</
&RFC4627; &RFC4627;
&RFC5001; &RFC5001;
&RFC3597; &RFC3597;
<reference anchor="min_ref">
<!-- the following is the minimum to make xml2rfc happy -->
<front>
<title>Minimal Reference</title>
<author initials="authInitials" surname="authSurName">
<organization></organization>
</author>
<date year="2006" />
</front>
</reference>
</references> </references>
<references> <references>
<reference anchor="CACHEPOISONING" target="http://kurser.lobner.dk/dDist/DMK_BO2K8.pdf"> <reference anchor="CACHEPOISONING" target="http://kurser.lobner.dk/dDist/DMK_BO2K8.pdf">
@ -296,9 +282,6 @@ The document does not describe the protocol (e.g. <xref target="RFC3912">WHOIS</
<date year="2008"/> <date year="2008"/>
</front> </front>
</reference> </reference>
</references>
<references>
<reference anchor="BAILIWICK" target="https://archive.farsightsecurity.com/Passive_DNS/passive_dns_hardening_handout.pdf"> <reference anchor="BAILIWICK" target="https://archive.farsightsecurity.com/Passive_DNS/passive_dns_hardening_handout.pdf">
<front> <front>
<title>Passive DNS Hardening</title> <title>Passive DNS Hardening</title>
@ -306,6 +289,13 @@ The document does not describe the protocol (e.g. <xref target="RFC3912">WHOIS</
<date year="2010"/> <date year="2010"/>
</front> </front>
</reference> </reference>
<reference anchor="PDNSCLIENT" target="https://github.com/chrislee35/passivedns-client">
<front>
<title>Queries 5 major Passive DNS databases: BFK, CERTEE, DNSParse, ISC, and VirusTotal.</title>
<author fullname="Chris Lee"/>
<date year="2013"/>
</front>
</reference>
</references> </references>
<references title="Informative References"> <references title="Informative References">
@ -322,7 +312,6 @@ The document does not describe the protocol (e.g. <xref target="RFC3912">WHOIS</
</references> </references>
<section anchor="app-additional" title="Appendix"> <section anchor="app-additional" title="Appendix">
<t>This becomes an Appendix.</t>
</section> </section>
</back> </back>
</rfc> </rfc>